Job Priority: Decide What Needs Attention Without Inventing Urgency
Question: How can a service team decide what to review first without turning every new request into an unsupported emergency?
Priority is a documented decision
A message, customer request, schedule conflict, or field update can require attention. It does not automatically prove risk, urgency, service eligibility, safety status, or a response commitment.
Use your team’s approved criteria and assign a human owner whenever the record does not support a clear priority.
The priority review
- Open the right record. Confirm the lead, customer, job, work order, or task.
- Write the factual signal. Describe what was requested or observed without diagnosing or exaggerating.
- Check the agreed criteria. Use the approved internal process for deciding what needs attention first.
- Identify missing information. Say what must be verified before the team can change the plan.
- Choose one next action. Clarify, schedule review, assign a human task, escalate, or retain the current plan.
- Name the decision owner. Do not leave a priority label with no accountable person.
- Review customer-facing language. A priority decision is not automatically a promise of response time or service.
Common signals
| Signal | Safe response |
|---|---|
| Customer requests immediate help | Record the request; route it to approved human review. |
| A job date is near and work is incomplete | Review the record, owner, and next task before changing the schedule. |
| Field team identifies a possible concern | Capture the observation and escalate if qualified review is needed. |
| Multiple jobs compete for attention | Compare through the team’s approved process; document the decision owner. |
| Details are incomplete | Ask for the minimum clarification rather than guessing priority. |
Do not use priority as a shortcut
Avoid labels such as “emergency,” “critical,” “guaranteed,” or “dispatched” unless the approved record and qualified decision support them. Do not put private customer information, access codes, payment data, or sensitive attachments into a general priority note.
For after-hours capture, see After-Hours Requests. For human override, see Escalations.
Boundaries
This guide supports transparent work prioritization. It does not establish emergency service, response time, safety assessment, technician availability, booking, customer consent, legal duty, payment, or service completion. Use qualified people and approved processes for high-consequence decisions.