From Request to Paid: The Work Order Lifecycle on One Record

A job can be done well and still lose money in the gaps between the person who did it, the person who bills it and the person who books it.

The technician does the work properly. The estimate was reasonable. The customer is happy. And somewhere between the driveway and the ledger, an hour is missing, a part isn't on the invoice and the payment arrives three weeks after it could have.

Most field service software does some of the lifecycle well. What matters is what happens between the steps, because that is where the work goes. This article walks through six steps from request to payment, and for each one, what happens when it lives on one record and what happens when it doesn't.

The six steps

A work order lifecycle is the sequence a job passes through from the moment a customer asks for service to the moment the money is in the books. Six steps cover it: the request arrives, the job is assigned, the work is captured on site, the estimate goes out and comes back, the invoice is ready, and accounting has it. Every gap named in the six information gaps behind every field service problem is a place where one of these hand-offs is done by a person.

Step 1. The request arrives

On one record: A customer submits a request through the portal and it lands in the queue as a work order. There is no voicemail to transcribe and no detail lost in someone's handwriting.

When it doesn't: The request arrives by phone or voicemail, and someone types it up. Details get shortened. Access notes and the actual symptom don't always make it into the ticket.

Gap closed: The customer's only channel being the phone. See when the customer's only status channel is the phone.

Step 2. The job is assigned

On one record: The dispatcher sees every technician's workload and their experience with similar work, and assigns from that. No spreadsheet is consulted and no one is asked over the radio.

When it doesn't: Assignment happens from a mix of memory, a whiteboard and a text thread. The person best suited to the job may not be the one who was free when the dispatcher happened to look.

A dispatcher makes more decisions per hour than nearly anyone else in the business, and this is the one that sets up every step after it. A day in dispatch on one board follows one dispatcher through the whole shift.

Step 3. The work is captured on site

On one record: Photos, signatures, notes, parts, materials and time are logged against the work order on the phone, as the work happens. There is no end-of-day pile to type up.

When it doesn't: The technician writes it down, or plans to, and the details get reconstructed at the end of the day or the end of the week. Time entries drift toward round numbers. Parts that were used but not logged simply disappear.

Gap closed: What happened on site not being what reaches the bill. This is where most billable work is lost, and it's the least visible place to lose it.

Step 4. The estimate goes out and comes back

On one record: The estimate is built from the price book on site, approved on the device and converted to a work order with one click. Nothing is re-keyed, and nobody waits three days.

When it doesn't: The diagnosis happens on Tuesday and the quote goes out on Friday, built from a price list that may not match what the office would have charged. By then someone else has been out.

Gaps closed: Inconsistent pricing and slow estimates. The detail is in the price depends on which technician showed up.

Step 5. The invoice is ready

On one record: Labor, parts, materials and travel populate at price book rates from what the technician logged, once the job is complete. There is no missing billable line, because the lines came from the work.

When it doesn't: Someone re-keys the ticket, and each hop is another chance to drop something. Days to invoice depend on how busy the office is.

Gap closed: The job being done before the invoice exists. Every day the invoice waits is a day your cash is funding work you've already done.

Step 6. Accounting has it

On one record: The invoice and its payments sync in both directions with QuickBooks, Sage, NetSuite or another accounting or ERP system. The back office reviews exceptions instead of retyping records.

When it doesn't: The same invoice is entered twice, once in the field service tool and once in the books, and someone reconciles the two at month end.

Ask any vendor which accounting systems they sync with in both directions, by name, and to show one round trip. It's question nine in our evaluation guide.

What "work order" has to mean for this to work

The work order is the system of record for every job: what was done, who did it, when, for whom and at what cost. If it's a form that gets filled in after the fact, the rest of the lifecycle has nothing reliable to build on. If it's the live record the whole job runs through, the invoice, the cost report and the customer's view all come from it.

For that to work, a few things have to be true of the work order itself:

• It can be created and updated from mobile or desktop, with configurable multi-step workflows and real-time status.
• It has templates for common jobs, with pre-filled checklists, standard labor estimates and required documentation for recurring service calls, planned maintenance and warranty work.
• Photos, signatures, notes, parts and time attach to it on site and flow onward into invoicing and job costing.
• Priority levels, SLA tracking and escalation rules keep urgent work visible.
• Every change is in a full audit trail.

We list this once and briefly because this article is about the hand-offs, and the Field Service Suite page covers the feature set. The point is that a work order that does all of the above is the thing the six steps hang from.

Cost capture: where billable work goes missing

A technician writes hours and parts on paper. Someone types them into an invoice. Someone else types them into accounting. Every hop is a chance to lose a billable part or an hour of labor, and what goes missing there never shows up as a line item anywhere.

That last part is what makes cost capture different from the other gaps. A late invoice is on a report. A part that was fitted, never logged and never billed is on nothing. Nobody knows what they're missing, so nobody goes looking.

The fix has three parts. Labor is logged where the work happens, as it's worked, not reconstructed on Friday. Parts and materials are recorded against the work order on site and priced from the price book, so what was fitted is what's billed. And the work order, the estimate and the invoice share one data model, so what the technician captured is what the customer sees on the bill.

The truck is part of the record too

A vehicle is one of the biggest assets in a service business and one of the least tracked. It belongs in the job record for a practical reason: you can't allocate the cost of a job without knowing what it cost to get there.

Vehicles are tracked alongside their assigned technician and linked to the work orders they served, with mileage and fuel recorded at checkout. A vehicle marked out of service can't be checked out, so nobody is sent in a truck that isn't roadworthy. Registrations and insurance surface ahead of their expiry dates instead of being discovered at a roadside stop.

The point isn't fleet software for its own sake. It's that fuel, mileage and vehicle cost can land on the job they belong to.

What this looks like from the office

For the person who runs the back office, the difference between one record and several is the difference between reviewing and retyping. The invoice is built from the work the technician logged. It's queued for review before it goes out, so nothing bills unreviewed and nothing that was captured gets left off. Exceptions surface before the run rather than after the customer calls.

With two-way accounting sync, the back office looks at exceptions, and doesn't re-enter the day's jobs.

One data layer

Underneath all six steps is one data layer: the job, the money, the customer and any agreement covering them share a single set of records. It's the reason the six steps can hand off without a person in the middle.

MangoApps Field Service Suite is built on that layer and delivered inside the same platform as communications, HR, learning and AI. A technician's certification, a customer's request and a price change are all facts on one record. If you want to see how that changes a dispatcher's day, read the day-in-dispatch walkthrough.

Practically, it also means you don't have to bring everything over at once. Read we just bought an FSM tool if you're wondering how to add this to what you already run.

What to measure

If you want to know whether the hand-offs are working, three numbers tell you. Days from job completion to invoice issued shows whether Step 5 is waiting on people. The share of completed jobs with a billing correction after the invoice goes out shows whether Step 3 is capturing what happened. And the number of times any fact is entered more than once between request and payment shows how many hand-offs still depend on someone retyping.

You don't need a dashboard for any of them. A sample of twenty jobs and a pen will do for the first pass.

A demo that settles it

If a vendor can show a job marked complete and an invoice ready with nothing typed in between, the rest of the lifecycle is probably on one record too. If they can't, it isn't.

That's question one in how to evaluate a field service platform, and it's worth making them do it live.

The six steps are part of a longer walk through work orders, dispatch, estimates, invoicing and the customer portal in the Field Service Management guide. You can also see the Field Service Suite itself.

Frequently asked questions

What are the stages of a work order?

A work order moves through six steps: the request arrives, the job is assigned, the work is captured on site, the estimate goes out and comes back, the invoice is ready, and accounting has it. On one record, each step hands off to the next without anyone retyping information. Gaps appear wherever a hand-off depends on a person to carry the fact.

How does field service software generate invoices automatically?

The invoice is built from what the technician logged against the work order (labor, parts, materials and travel) at the rates in the price book. Because those lines come from the job itself, nothing is retyped, and the invoice is queued for review before it goes out. The test is to complete a job and see whether an invoice is ready with nothing typed in between. In MangoApps, the invoice is ready at price book rates the moment the job is marked complete.

What is job costing and why does it fail with paper work orders?

Job costing means knowing what a job actually cost in labor, parts, materials and equipment, so you can see its margin. It fails with paper because the details are written down, typed into an invoice and typed again into accounting, and every hop is a chance to lose a part or an hour. What goes missing leaves no trace, so the costs look lower than they really were.

Can a work order capture photos and signatures offline?

Yes. The technician can keep working the work order in a dead zone, and photos, time entries and signatures upload as soon as service comes back. See why technicians work around the tools for what an app built for field conditions has to do.

Does the work order sync with accounting software?

It should sync both ways, so invoices, payments and completed jobs move between the field service platform and your accounting system with no double entry. Ask any vendor for the named systems that sync in both directions and to show an invoice posting and a payment returning. MangoApps syncs two ways with QuickBooks, Sage, NetSuite and other accounting and ERP systems.