Guide
Work Order Tracking:Statuses, Status Owners, Timestamps and the Customer View from Creation to Close
Work order tracking from creation to close: a status model, who updates each status, timestamps and time in status, what the customer sees, and a sample job.
Work order tracking is the record of where each work order stands between creation and close: a defined status, set by a named person or event, with a timestamp at every change. The status tells the dispatcher what to do next, tells the office what to invoice, and tells the customer when the technician will arrive.
Tracking breaks in places a status model would have caught. The status lives in the dispatcher's head, so nobody else can answer the customer who calls at 11:00 asking where the technician is. A job waits on a part with no date attached and drops out of sight for two weeks. A technician finishes at 3:00 and the office learns of it the next morning, so the invoice goes out a day late. This page belongs to the fieldranger.ai guides for service business owners. It sets out a status model from created to closed, the owner of each status, the timestamps and the time-in-status measures they produce, what the customer is shown, the stalled orders the model exposes, a sample job and a sample month of status calls; a checklist and the FieldRanger status record come last.
The status model rests on five definitions. A status is the single current state of a work order, such as scheduled or on hold. A status owner is the role allowed to move an order into that status. A status change is the event of moving it, stamped with a date, a time and the person or system that made it. Time in status is the interval between two status changes. An exception status is one outside the forward path, such as on hold, that requires a reason and a new date.
Work order statuses from created to closed
A status model for field service has eight statuses, and each one has an entry test: the evidence that must exist before the order can move into it.
| Status | Set by | Entry test | Customer sees |
|---|---|---|---|
| Created | Office | Customer, site, problem and access notes recorded | Request acknowledged |
| Scheduled | Dispatcher | Technician, date and arrival window assigned | Confirmation with date and window |
| En route | Technician | Technician has left for the site | Arrival notice |
| On site | Technician | Clock-in at the site | None |
| On hold | Technician or office | Reason and next action date recorded | New date and the reason in plain terms |
| Completed | Technician | Work, parts, photos, checklist and signature or its exception recorded | Completion summary |
| Invoiced | Office | Close-out review passed; invoice sent | Invoice |
| Closed | Office | Paid, or closed with a recorded reason | Nothing further |
The stage view in work order management describes the work each stage contains. The status view is narrower: it records which of those stages the order is in now, and nothing else. Eight statuses are enough to answer every question the office is asked; a model with twenty statuses splits the same states into ones nobody sets consistently.
Status owners and update rules
Each status has one owner role, and the rules below keep the record trustworthy.
- Only the owner role moves an order into a status. The dispatcher schedules, the technician starts and completes, the office invoices and closes. A dispatcher who marks a job complete on a technician's behalf records a status without the evidence behind it.
- Every status change needs its entry test. An order is not scheduled until a technician and window are attached, and not completed until the record holds what the invoice needs.
- The forward path runs one way. Created, scheduled, en route, on site, completed, invoiced, closed. The only backward moves are from on hold to scheduled, and from closed back to scheduled for a return visit, which opens a new visit on the same order.
- On hold carries a reason code and a date. Waiting for parts, waiting for customer approval, no access, and weather each get a code, and each code has an owner who clears it by the date.
- The technician updates from the job, not from memory. A status typed in at 5:00 records the time of entry, not the time of the event, and every interval measured from it is wrong.
Rule five decides whether the timestamps mean anything, since a status change made in the field, at the moment of the event, gives a real arrival time; the same change typed in at 5:00 gives a fiction.
A pipeline can enforce rule two. HubSpot's pipeline settings support conditional stage properties, shown when a user manually creates a record in a stage or moves one into it, and a required property blocks the create or update until it has a value. Pipelines are available for deals, tickets and other objects on all plans, with custom object pipelines on Enterprise (HubSpot Knowledge Base, set up and customize pipelines, updated September 29, 2026).
Status timestamps and time in status
A timestamp on every status change turns the log into measures, and four intervals answer the questions an owner asks of the board.
| Measure | From | To | Exposes |
|---|---|---|---|
| Time to schedule | Created | Scheduled | Requests waiting for a slot |
| Arrival against window | Scheduled window start | On site | Late arrivals, by technician and by route |
| Time on hold | On hold | Scheduled | Parts and approval delays, by reason code |
| Completion to invoice | Completed | Invoiced | Close-out backlog in the office |
HubSpot computes these intervals for records in a pipeline. Its stage calculated properties include the date a record entered and exited each stage, the latest time in a stage, the cumulative time in a stage across re-entries, and the time in the current stage; they apply to deals, tickets and other pipeline objects, are turned off by default for new pipelines and stages, and are listed for Professional and Enterprise subscriptions (HubSpot Knowledge Base, stage calculated properties, updated July 15, 2026). A business tracking work orders as HubSpot records turns the properties on per stage before the first order moves, since a stage without them records no history to measure.
Cumulative time is the measure for on hold: an order that goes on hold twice, for two days and then for five, shows five days in latest time and seven in cumulative time, and only the cumulative figure is the delay the customer felt.
Customer-facing work order status
The customer sees a subset of the statuses, worded for the customer. Five messages cover the path: an acknowledgement at created, a confirmation with the date and arrival window at scheduled, an arrival notice at en route, the reason and new date at on hold, and the completion summary at completed. On site and invoiced need no message, since the customer is present for one and receives the other.
The en route notice is the message that replaces a phone call. A customer who receives it does not call the office to ask where the technician is, and the office minute saved is priced in the sample month below. The message costs little: Twilio lists US SMS at $0.0083 per outbound segment, plus carrier fees that run from $0.0035 to $0.005 per outbound segment on long codes (Twilio, US SMS pricing, current as of November 2026).
The on hold message decides how a delay reads: an order on hold for a part, with no message, reads to the customer as a forgotten job, and the same hold with the reason and the next date reads as a plan.
Stalled work orders: symptoms, causes and fixes
A status model exposes stalled orders, and each stall has a cause that the status log identifies.
| Symptom | Cause | Fix |
|---|---|---|
| Scheduled order with no on-site stamp after its window closes | Technician late, or arrived and did not update | Alert the dispatcher at window close; check the clock-in |
| On hold past its next action date | Part not ordered, or approval not chased | Reason code with a named owner and a date |
| Completed order not invoiced after two business days | Close-out review backlog | Daily close-out queue sorted by completion date |
| Completed order missing a signature | Customer absent, exception not recorded | Exception reason required before completed is allowed |
| Closed order reopened for a return visit | Incomplete first visit | Return-visit reason recorded at reopening |
The completion-to-invoice row is the one with money attached. A job completed on Friday and invoiced on Tuesday has postponed its payment by four days before the customer sees a bill, and the status log shows exactly which orders sit in that gap.
Sample job: a water heater replacement from creation to close
The timeline below is a sample work order for a hypothetical plumbing company. Every time and step is a sample input; the intervals are computed from them.
| Time | Status | Set by | Note |
|---|---|---|---|
| Mon 8:12 | Created | Office | No hot water; 40-gallon gas heater, garage |
| Mon 8:40 | Scheduled | Dispatcher | Tue, 10:00 to 12:00 window |
| Tue 9:35 | En route | Technician | Arrival notice sent |
| Tue 10:20 | On site | Technician | Clock-in at the address |
| Tue 10:55 | On hold | Technician | Reason: part; gas valve not on the van; next date Wed |
| Tue 11:30 | Scheduled | Dispatcher | Wed, 8:00 to 10:00 window; customer told |
| Wed 8:30 | On site | Technician | Clock-in at the address |
| Wed 11:15 | Completed | Technician | Photos, permit number, signature |
| Wed 14:00 | Invoiced | Office | Close-out review passed |
| Fri 9:00 | Closed | Office | Paid |
The log yields the measures without extra entry. Time to schedule was 28 minutes; the first arrival came 20 minutes into its window and the second 30 minutes into its window. Time on hold was 35 minutes in status, but the customer waited from Tuesday 10:55 to Wednesday 8:30 for the part, and completion to invoice took 2 hours 45 minutes. The hold reason, a part missing from the van, points at dispatch: the order named the heater type at creation, so the valve could have been loaded before the first trip.
Sample month of status calls for six technicians
The month below prices the status questions a company answers by phone. The office and dispatcher wages and the text price are published figures; the job count, call rates and minutes are sample inputs.
| Line | Basis | Amount |
|---|---|---|
| Work orders | 6 technicians × 5 jobs × 22 days | 660 |
| Customer calls asking for arrival time | 1 call per 4 jobs × 4 minutes = 11 hours × $21.53 | $236.83 |
| Dispatcher calls to technicians for status | 1 call per job × 2 minutes = 22 hours × $24.20 | $532.40 |
| Calls total | Sum | $769.23 |
| Arrival texts instead | 660 × 1 segment × $0.0133 | $8.78 |
Sources: customer service representatives' median wage of $21.53 an hour, May 2025 (BLS, modified October 29, 2026); dispatchers' median of $24.20 an hour in 2025 BLS wage data (O*NET, dispatchers except police, fire and ambulance); Twilio's $0.0083 per segment plus the highest outbound long-code carrier fee of $0.005.
The dispatcher's calls are the larger line, at 22 hours a month, and they exist because the board does not update itself. A status set by the technician from the job removes those calls, and an arrival text set off by the en route status removes the customer's call. The texts cost $8.78 for the month, against 33 hours of office and dispatch time that a status model recovers.
Work order tracking checklist
- Eight statuses defined, each with an entry test
- One owner role per status, written down
- On hold requires a reason code, an owner and a next action date
- The technician sets en route, on site and completed from the job, at the moment of the event
- Every status change is stamped with date, time and the person or system
- Time-in-status measures turned on before the first order moves
- Five customer messages mapped to statuses, with the on hold message stating reason and date
- A daily queue of completed orders awaiting invoice, sorted by completion date
- Return visits reopened on the same order with a recorded reason
- Stalled-order report reviewed weekly: late arrivals, holds past date, completion-to-invoice backlog
Job status tracking in FieldRanger
FieldRanger records status from the job rather than from the office. The technician starts a job, completes it and updates its status with one tap in the mobile app, and the dispatcher sees the status in real time. The job status shows on the HubSpot deal record the job came from, and job completions, notes and updates are logged to the HubSpot timeline. Job status changes can trigger HubSpot workflows, so a completed status can start the close-out task or the customer message the business already runs.
The record behind each status is the digital work order: job details, customer information and instructions on the technician's phone, with job-specific checklists, before and after photos and the customer's signature as proof of completion. Clock-ins log time against each job, and time window management sets arrival windows and tracks on-time performance. Technician performance reports show completion rates and on-time arrivals, and the operations dashboard gives a live view of jobs and technicians. The invoice is generated from the completed work order, and customer messages go out as SMS notifications and reminders through Twilio, or through HubSpot.
The job tracking page shows the status flow, the work order software page shows the work order itself, and the work order template lists the fields an order carries before it is digital. The move from paper job sheets to the phone is covered in work order management.
Frequently asked questions
What is work order tracking?
Work order tracking is the record of each work order's current status, from created to closed, with the person or event that set each status and a timestamp at every change.
What statuses should a work order have?
Eight cover field service: created, scheduled, en route, on site, on hold, completed, invoiced and closed. Each has an entry test, such as a technician and window for scheduled, and on hold requires a reason and a date.
Who updates the status of a work order?
One owner role per status: the dispatcher schedules, the technician sets en route, on site and completed from the job, and the office invoices and closes.
How to track work orders in HubSpot?
Track them as records in a pipeline whose stages are the statuses, and turn on stage calculated properties for each stage, which record the date entered and exited and the time in stage. HubSpot lists those properties for Professional and Enterprise subscriptions.
What should a customer see when tracking a work order?
An acknowledgement, a confirmation with the date and arrival window, an arrival notice, the reason and new date if the job goes on hold, and a completion summary with the invoice.
How to find stalled work orders?
Compare each status timestamp with its target: scheduled orders with no on-site stamp after the window, holds past their next action date, and completed orders not invoiced within two business days.
The timestamp as the unit of work order tracking
Scheduling and close-out from the same records are in the guides for service business owners; the stages behind each status are in work order management; plans are on pricing, and Start free trial runs 14 days without a card.
In the sample log, ten timestamps answered every question asked of that water heater job, including the customer's own question: why a 35-minute hold became a wait of 21 hours 35 minutes.
Run field service on HubSpot with FieldRanger
Estimates with e-signature, scheduling and dispatch, a technician mobile app and invoicing, synced to the HubSpot deals and contacts the business already keeps.
Book a demo