A job status code is a label that tells everyone where a job sits in its life, from first request to final payment. Most service and engineering businesses need between six and ten of them. Each one should be triggered by something that actually happened, such as an engineer being assigned, a certificate being uploaded or an invoice being raised. Get that right and your schedule, your reporting and your compliance records all start to agree with each other.
This guide is for office managers, operations leads and owners of field service, maintenance and facilities businesses. It explains what the codes mean, shows a working set you can adapt, and covers how to avoid the usual problem: the same status meaning different things to different people. (If you landed here looking for HTTP codes such as 404, this is about the other kind: the job lifecycle in a service business.)
TL;DR
- A job status code shows the current stage of a job. It is not the same as a job code or job type, which groups similar work for reporting.
- A sound lifecycle covers request, quote, scheduled, in progress, on hold, completed, invoiced and cancelled. Compliance work adds a few more.
- Statuses are not standard. UK universities, public bodies and software vendors all use different sets, so define yours and write down what each one means.
- Tie every status to evidence: an assignment, a check-in, uploaded photos, a signed-off certificate or a raised invoice.
- Fewer, clearer statuses beat long lists that nobody applies consistently.
Table of Contents
- What job status codes actually are
- A working set of job statuses for a UK service business
- How UK organisations structure the lifecycle
- Handling "on hold" properly
- Are job status codes standard?
- How to design statuses that people use correctly
- Extra statuses for compliance-led work
- What consistent statuses do for reporting and audit
- Common mistakes to avoid
- Putting statuses to work in Curcle
- FAQ
- Sources
What job status codes actually are
A status code answers one question: what is happening with this job right now? Field service systems usually express it as a short list of named stages. Typical stages run from unscheduled and scheduled through in progress and completed, with cancelled as an exit at any point. Some systems keep a separate status for the engineer's booking, so the job can be "scheduled" while the engineer's visit is "travelling" or "on site". Keeping those two layers apart stops the job record from being rewritten every time someone sets off in a van.
The word "code" matters less than it sounds. Some businesses use numbers (10, 20, 30), others use words. Words win for people reading a schedule at 7am. If you need codes for integrations or exports, keep a short code alongside the plain-English name and never use the code alone on screen.
Job status versus job code
These two get confused constantly. A job status describes progress: where the job is now, and it changes as work moves along. A job code, type or class describes what kind of work it is, such as a gas service, an electrical inspection or a reactive repair, and it stays put. Reporting tools use the class to group similar work and the status to show progress. If you ask "how many boiler repairs are still open?", you need both fields to answer it.
There is a third thing worth separating: employee status, which describes a person's employment (active, on leave, suspended). It has nothing to do with the job record and should live somewhere else entirely.
A working set of job statuses for a UK service business
There is no single correct list, but most service businesses converge on something like this. Use it as a starting point and rename to suit how your team talks.
| Status | What it means | Evidence that triggers it |
|---|---|---|
| Reported | A request or enquiry has been logged | Job record created from a call, email or portal request |
| Quoted | A price has been issued and is awaiting a decision | Quote sent to the customer |
| Approved | The customer has accepted the quote or the work is authorised | Acceptance or purchase order captured |
| Scheduled | An engineer and a date are assigned | Booking created |
| In progress | Work has started on site | Engineer check-in |
| On hold | Work is paused, with a stated reason | Reason selected by the engineer or office |
| Completed | Work is finished on site | Engineer marks works complete, with required photos and paperwork |
| Reviewed | The office has checked the paperwork | Back-office sign-off |
| Invoiced | The customer has been billed | Invoice created |
| Cancelled | The job will not go ahead | Cancellation with a reason |
That is ten, which is already at the upper end. If you are a small team, merge Quoted and Approved into one "Awaiting approval" step, or drop Reviewed and let completion trigger invoicing.
Why "completed" is not the end
One of the commonest reporting errors is treating "completed" as "finished". On site, the engineer is done. In the office, the paperwork still needs checking, the certificate needs issuing and the invoice needs raising. Field service platforms commonly handle this by having back-office staff review a completed job and move it to a further status, which can in turn trigger invoicing. Whatever you call it, keep a gap between "the engineer left site" and "we have been paid", or your cash flow reports will flatter you.
How UK organisations structure the lifecycle
Public and institutional bodies publish their workflows, and they show how much detail a large organisation chooses to carry. The University of Nottingham's estates guide for contractors describes a work-order path running through Reported, Accepted, Estimate Costs, Quote approved, Assigned, In progress, Technically completed, Operationally completed, Administratively completed and Financially completed. In that workflow, Reported means a request has reached the helpdesk, Accepted means triage has approved it, and Estimate Costs means the contractor has been asked to quote.

The interesting part is the finish. Rather than one "completed" state, the path splits completion into three: the work is technically done, then operationally done, then administratively and financially closed. That is the same idea as the Completed, Reviewed and Invoiced steps above, expressed more formally. A small business rarely needs three completion states, but it does need to know which of those moments a report is counting.
The London School of Economics takes a different angle in its supervisor guide, using colour to show ownership. According to the LSE guide, red or yellow statuses indicate helpdesk or supervisor ownership, blue indicates assignment or work in progress, green indicates completed work, and grey marks a closed request that cannot be changed. Colour-coding by owner is a smart habit to copy: a glance at the board should tell a planner who has to act next.
Handling "on hold" properly
"On hold" is the status that hides the most problems, because it is where jobs go to be forgotten. The same LSE guide notes that a job can be paused for reasons such as a contractor being required, parts being unavailable or priority changing. Those are three completely different situations with three different owners.
A better approach is to name the reason in the status itself or to force a reason when the status is chosen. Useful splits include:
- On hold, awaiting parts: the stock or purchasing owner needs to act.
- On hold, awaiting customer: access, approval or a purchase order is outstanding.
- On hold, awaiting subcontractor: a third party has to attend first.
- On hold, priority changed: a manager has deliberately paused it.
With reasons attached, "on hold" stops being a dumping ground. Your weekly review can ask a sharper question: which jobs have been waiting on parts for more than five days? If you also run SLAs, that split tells you whether the clock is yours or the customer's. Our guide to priority-based scheduling goes into how priority and status work together to keep response times on track.
Are job status codes standard?
No. There is no universal list, and that surprises people who expect one. Even public bodies treat the topic as a vocabulary to be defined: the Environment Agency's asset management definitions include a class of concepts for maintenance activity and task status, which exists precisely so that organisations can describe status consistently rather than because everyone shares one fixed list.
The practical consequence is that your statuses need to be defined by you, in writing. Two businesses can both have a status called "Completed" and mean different things: one when the engineer leaves site, the other when the certificate has been issued. If you ever merge systems, hire a new office manager or share data with a client, those hidden differences cause disputes.
How to design statuses that people use correctly
The most common failure is a status that depends on someone remembering to change it. A manual label with no evidence behind it drifts from reality within weeks. The better principle, set out in workflow guidance from 5M Consulting, is to define the event that proves a stage has changed. Examples include a booking being assigned, an engineer checking in, works being marked complete, required photos being uploaded, variation approval being captured or an invoice being created.
Here is a simple method you can run in an afternoon.
- List what actually happens. Walk a recent job from first call to payment and write down each handover between people.
- Name a status for each handover. If nobody changes hands at a step, it probably does not need its own status.
- Write the proof. For each status, note the event or document that justifies it. "Completed" might require the engineer's sign-off, photos and any certificate.
- Name the owner. Every status should have one person or team responsible for moving it on.
- Choose meaningful names. Descriptive labels such as "On hold by us" and "On hold by client" are clearer than a bare "On hold", a point also made in HelpMaster's guidance on job status codes, which also suggests keeping only common, generic statuses visible everywhere and moving specialist ones into templates.
- Set the exits. Decide which statuses can be skipped, which can be reversed and who is allowed to reverse them.
- Review after a month. Look for statuses nobody uses and jobs that sit in one status far longer than the rest.
Keep the list short
Every extra status is another decision for an engineer standing in a boiler room with a phone. Our rule is that every click should earn its place. If a status does not change who acts next, or does not feed a report someone reads, remove it. You can always add detail through a reason field or a tag without lengthening the main list.
Extra statuses for compliance-led work
If you issue certificates or run inspection programmes, the standard lifecycle needs a few additions, because the paperwork is part of the product. Consider these on top of the base set:
- Awaiting certificate: the visit is done but the certificate or report has not yet been issued.
- Defects found: the inspection raised issues that need follow-up work or a quote.
- Follow-up required: a remedial job has been created and linked to the original.
- Certificate issued: the document has gone to the customer and is stored against the asset.
These matter in practice for gas, electrical, fire safety, water hygiene, lifting equipment and F-Gas work, where a visit without an issued record leaves you exposed. A status that makes "visited but not documented" visible is worth more than any dashboard. For ideas on tracking work between start and finish, our article on work in progress tracking and six statuses for UK field operations shows how to avoid audit surprises.
Electrical contractors in particular often want a guided path that matches how inspection and testing work flows, which is the focus of our electrical contractor workflow pilot.
What consistent statuses do for reporting and audit
Statuses are only useful if you can ask questions of them. A status-aware report can filter by status, work type, site, asset, assigned engineer and date range. Better still, it can use different dates for different questions: when the job was created, started, completed, cancelled or required. Reporting against "required by" tells you about lateness, while reporting against "completed" tells you about throughput. A single generic job date cannot do both.
Status changes also work as control points, not just labels. They can trigger searches, automations, escalations and reports, and a well-run system records each change in an audit history. That last part is what auditors and customers care about: who changed the job to completed, when, and what evidence was attached. If your statuses are driven by events, that trail builds itself rather than being reconstructed from memory.
Here are the questions a clean status set lets you answer quickly:
- How many jobs are waiting on customer approval, and for how long?
- Which completed jobs have not yet been invoiced?
- Which on-hold jobs are blocked by parts, and what is the oldest?
- Which visits have no certificate issued against them?
- How many jobs are at risk of breaching their SLA this week?
If you cannot answer these from your system without a spreadsheet, the statuses are probably too vague or are not tied to evidence.
Common mistakes to avoid
- One status doing two jobs. "Awaiting" covering parts, approval and access hides the real blocker.
- Statuses that only the office can set. If engineers cannot update from site, the record lags behind reality.
- No cancellation reason. Without one you cannot tell lost work from duplicates.
- Reopening completed jobs. Reopening quietly rewrites history. Create a follow-up job instead and link it.
- Different meanings per team. Hold a short session so planners, engineers and accounts agree on each definition.
- Changing the list too often. Each change breaks historic reports. Review quarterly, not weekly.
A short worked example shows the effect. A commercial kitchen contractor has a reactive call for a failed extraction fan. The job is Reported at 8:10, Scheduled by 8:30, In progress when the engineer checks in at 11:00 and put On hold, awaiting parts at 11:40. When the part arrives it returns to Scheduled, then Completed with photos on the second visit, Reviewed by the office the same day and Invoiced the next morning. Every step has a person, an event and a timestamp, so when the customer asks why the fix took two days, the answer is a report rather than an argument.
Our view on job statuses
Curcle was born inside a real UK service and engineering business, and the lesson we took from it is simple: a status is only worth having if it tells someone what to do next. We have watched teams drown in twenty-line status lists that nobody applied the same way twice, and we have watched jobs marked complete while the certificate was still missing.
That is why we build compliance into the backbone of the platform rather than bolting it on. We want a job's status to reflect what has been captured, such as the engineer's check-in, the photos, the certificate and the invoice, so the record stays consistent for the field team, the office and the auditor alike.
We also believe software should help a business see what needs attention, not merely record what has already happened. A good status model is the foundation for that: once every job carries a clear stage, an owner and evidence, AI and reporting can point to the stuck job before the customer calls. Human judgement still decides what to do about it.
Luke Herridge
Putting statuses to work in Curcle
If you are replacing spreadsheets or several disconnected tools, the statuses are easier to keep honest when jobs, assets, compliance records, stock and invoicing live in one connected system. Curcle brings these together so field and office teams work from the same information, with a mobile engineer app that works offline, audit trails, and document and photo capture on every job. You can see how a job's record flows from request to invoice on our workflows page, or browse the full feature list.
Plans start from £99 per month for Starter, from £249 per month for Professional and from £499 per month for Business, with Enterprise available on request. Compare them on the Curcle pricing page and start with a free trial or demo. Facilities teams running multiple sites can also look at our facilities management software.
FAQ
What is a job status code?
It is a label showing the current stage of a job, such as scheduled, in progress, on hold or completed. It lets planners, engineers and the office see what is happening and who needs to act. It describes progress, not the type of work.
What is the difference between a job status and a job code?
The status changes as the job moves along. The job code, type or class describes the kind of work and normally stays fixed. Reports use the class to group similar jobs and the status to show how far each one has got.
How many job statuses should a service business have?
Most need between six and ten. Start with request, quote, scheduled, in progress, on hold, completed, invoiced and cancelled, then add compliance-specific steps only if you issue certificates or inspection reports. If a status does not change who acts next, remove it.
Are job status codes the same in every system?
No. Different organisations and software use different lists and different definitions, even for a word like "completed". Write down what each of your statuses means and what event triggers it, so everyone applies it the same way.
Should engineers change statuses themselves?
Where possible, yes, or better still the status should change automatically from an event such as check-in or a completed form. That keeps the record close to what really happened on site and cuts down on chasing from the office.
Sources
- University of Nottingham: Planon user guide for contractors
- London School of Economics: Planon residences supervisor user guide
- Environment Agency: maintenance activity status definition
- 5M Consulting: stopping job statuses meaning different things
- HelpMaster: job status codes

