TABLE OF CONTENTS

• Importance — how urgent work is for your team
  • Where it comes from
  • Where you’ll see it
• Priority — your customer’s own labels
  • Where it comes from
  • Where you’ll see it
• Why have both?
• Easy mix-ups to avoid

Work orders have two separate fields that both relate to “how urgent” work feels—but they serve different purposes. Understanding both helps you plan work in Fieldclix and stay aligned with how your customer labels jobs in their own systems.

Importance — how urgent work is for your team

Importance is Fieldclix’s built-in urgency level. Every Work Order must have one of three values:

• Low
• Normal
• High

Where it comes from

When you create a Work Order, Importance is usually filled in automatically from the Work Order Type you choose. Types can define a default (for example, Normal for routine work, High for emergency repairs). You can change it on the Work Order if the situation calls for it.

Importance is required. The system won’t leave a Work Order without it.

Where you’ll see it

Importance is meant for schedulers and dispatchers inside Fieldclix:

• On the Work Orders dashboard
• On the Work Order card
• On the Dispatch Calendar
• On the Scheduler map — sites with at least one active Work Order set to High can stand out visually so planners spot urgent work quickly
• In the mobile app on the Dispatch screen (so crews see how the office classified urgency)

High is the level to use when you want the Work Order to draw extra attention during planning—not because of a customer label, but because your team needs to prioritize it on the board and map.

Priority — your customer’s own labels

Priority is optional. It comes from a Work Order Priorities list that your organization maintains (for example, “24 Hours,” “Standard,” “Emergency,” or whatever terms your contracts and integrations use).

Where it comes from

Priority is often set when Work Orders are created or updated from email or integrations, using the priority name from the external ticket or system. If a new label appears that isn’t in the list yet, your administrator may add it to the reference so future imports match correctly.

Unlike Importance, Priority:

• Is not required
• Does not default from the Work Order Type
• Is not limited to three values —i t follows your custom list

Where you’ll see it

Priority is mainly for reference and consistency with outside systems:

• Work Order card and Work Orders dashboard (view and edit when the work order is still active)
• Mobile app on the dispatch screen (read-only, for context)
• Notifications and published Work Order details where priority is shown alongside other job information

Priority does not change how Fieldclix highlights work on the calendar or scheduler map, and it does not affect timekeeping, payroll, or automatic hour allocation.

Why have both?

Example: A ticket might arrive with Priority “24 Hours” from the customer’s system, while your team sets Importance to Normal until a dispatcher escalates it to High on the map. Both values can stay on the record without conflict.

The system does not automatically copy Priority into Importance or the other way around. You decide when internal urgency (Importance) should differ from the customer’s label (Priority).

Easy mix-ups to avoid

• Importance is not the same as the Important idea described in some scheduling guides — that usually means setting Importance to High, not filling in the Priority field.
• Priority on a Work Order is not the same as Work Order Categories named “Priority 1” or “Priority 2.” Categories group types of work; the Priority field stores a separate priority label.
• Financial Account or Cost Type “priority” in timekeeping is a different topic entirely — it applies to how hours are allocated in payroll, not to Work Order Priority or Importance.