Skip to main content

Manage deadlines and priorities in assignment definitions

Set up advanced controls for start and end deadlines, and define priorities for assignments to match your operational needs.

Logan Bowlby avatar
Written by Logan Bowlby
Updated yesterday

Overview

Mobaro now lets you manage assignment deadlines and priorities with greater precision. With the latest update, you can customize when assignments start and end, and define multiple priority levels with unique rules for each assignment definition. This makes it easy to ensure critical work is completed on time—whether it’s a routine inspection or an urgent work order.


Configuring deadlines for assignments

When you create or edit an assignment definition, you’ll see a new section for deadline delay policies. Here’s how it works:

  • Choose between the Default and Relative delay policies.

    • The Default policy will automatically set the deadline to a fixed period after creation (one week later).

    • The Relative policy allows you to set more flexible deadlines, such as “End of week” or a specific number of hours or days after the assignment starts.

If you pick a relative policy, you can also specify a fixed time for the deadline (e.g., always due by 6:00 PM).


Setting priorities and time frame policies

Each assignment definition can now have multiple priorities—such as P1 (critical), P2, P3, and P4. For each priority, you can:

  • Mark it as Critical for operation, which cannot be changed for existing priorities. If you need to update this, you’ll need to create a new priority and delete the old one.

  • Set the priority as Default, which will be applied unless another is selected.

  • Choose a Time frame policy for deadlines:

    • Disabled: Start and deadline fields are hidden and cleared.

    • Optional: Start and deadline fields are available but not required.

    • Required: Start and deadline fields must be filled before the assignment can be saved.

You can customize these settings for each priority to reflect the urgency and operational impact of different assignment types.


Example workflow

Let’s say you’re setting up a work order assignment definition for your team. You want to make sure critical jobs are completed as soon as possible, while other tasks have more flexible timing.

  • For P1 (Critical), you select the Disabled time frame policy. This means the start and end time fields are hidden—no deadline needs to be set, as this work should begin immediately and be completed as soon as possible.

  • For P2, you choose the Required time frame policy. This forces the assignment creator to enter both a start and end deadline before saving.

  • For P3 and P4, you select the Optional time frame policy. These lower-priority assignments can have start and end times entered if desired, but they aren’t mandatory.

With this setup, your critical assignments are streamlined for speed, while important and routine tasks get the scheduling detail they need.


Frequently asked questions

Q: Can I set different deadlines for different assignment types?
A: Yes. Each assignment definition can have its own deadline policy and priority structure.

Q: Can deadlines be set automatically based on when an assignment is created?
A: Absolutely. Use the default delay policy for automatic deadlines, or use relative policies for more flexible scheduling.

Did this answer your question?