Job Status: Use Labels the Whole Team Can Explain
Question: How should a service team update a job status so the label reflects reality and the next person knows what to do?
A status is a shared statement
A job label is useful only when teammates can explain what it means, what evidence supports it, and what action follows it. Do not choose a status just to clear a queue.
Before changing it, ask:
- What fact changed?
- Which record supports the change?
- Does a person still need to act?
- Does the customer need an approved update?
- Is there a related task, work order, estimate, or invoice that must also be reviewed?
Use factual transitions
| Do this | Instead of this |
|---|---|
| “Work requires dispatcher review.” | “Completed” when a decision is still open. |
| “Requested visit recorded; timing unconfirmed.” | “Scheduled” without a verified schedule. |
| “Field update received; quality review pending.” | “Closed” based on a note alone. |
| “Invoice draft needs review.” | “Paid” without proof in the invoice record. |
The update routine
- Open the job and confirm its identity.
- Read the latest notes, tasks, and related work order.
- Change the status only for an observable reason.
- Add a concise note when the reason is not obvious.
- Assign the next owner if work remains.
- Review the result as another teammate would see it.
For the broader job workflow, see Jobs: Keep the Work Moving Without Losing Context. For field-side context, see Field Updates: Record What Happened, Not What You Expected.
Boundaries
This guide helps teams keep labels honest. It does not prove job completion, customer approval, payment, service quality, technician location, compliance, or any automated state change. Confirm those facts in the appropriate records.