Work Order Software: What It Must Capture

A work order has three jobs: it tells someone what to do, it records what was actually done, and it stands as evidence when somebody later disputes the bill, the standard or the timing. Most systems do the first well and skimp on the other two.

The third job is the one that pays for the software, because an argument six months later about whether a part was replaced or whether access was refused is settled by what was captured on the day. This guide covers the lifecycle and where it leaks, the fields that are missing when you need them, offline reality on site, and when a packaged product will not bend far enough.

Get a free quote for your project

What a Work Order Is Actually For

A work order has three jobs, and most systems do the first well and the other two badly. It tells someone what to do, it records what was actually done, and it stands as evidence afterwards when somebody disputes the bill, the standard or the timing.

The third job is the one that pays for the software. An argument six months later about whether a part was replaced, whether access was refused, or whether a job took the hours invoiced, is settled by what the work order captured on the day. If it captured a tick and a signature, the argument is settled against you.

Instruction: enough detail that the right person can arrive and start without phoning the office
Record: what was found, what was done, what was used, how long it took, what is outstanding
Evidence: timestamped, attributable, hard to alter after the fact

Judge any product on the second and third. The first is table stakes.

The Lifecycle, and Where It Leaks

Stage	What happens	Where it commonly leaks
Request	Someone asks for work	Arrives by phone or text and never becomes a record
Triage	Priority, scope, whether it is chargeable	Chargeability decided later, after the work, which is too late
Assign	Right person, right time, right kit	Assigned without checking parts, so the visit is wasted
Execute	The work, on site	Recorded on paper and typed up days later, badly
Verify	Evidence captured, customer sign-off	Photos on a personal phone, never attached to anything
Close	Outstanding items, follow-up raised	Follow-up mentioned verbally and forgotten
Bill	Invoice from the actual work	Rekeyed by hand, which loses hours and parts

Two leaks cost the most money. Work that never becomes a record cannot be billed, measured or learned from, and in most businesses this is a larger number than anyone expects. And chargeability decided after the fact is how goodwill work quietly becomes most of a month.

The assignment leak is the cheapest to fix and the most satisfying: checking parts availability before dispatch removes a whole class of wasted visit. That is where this connects to job scheduling software.

The Fields People Forget

Everyone captures customer, address, description and a completion tick. These are the ones that are missing when you need them, and each one exists because of a specific argument it prevents.

Asset, not just address. Which unit, which serial number. Without it you cannot see that the same boiler has failed four times, which is the single most useful thing maintenance history tells you
Reported fault and found fault, separately. What the customer said and what was actually wrong. Keeping both is how you learn that a reported symptom usually means something else
Arrival and departure times, captured on site. Not entered later from memory. This is what settles a billing dispute
Access problems and waiting time. Chargeable in many contracts and almost never recorded
Parts used, from stock. Tied to inventory so the van's stock is right tomorrow
Work not done, and why. The most valuable field on the form and the one most often absent. It is where the next job comes from
Who did the work, by name. Not the company, not the crew. Accountability and competence tracking both need the individual
Customer sign-off, with a name. A signature with no printed name is worth very little in a dispute

If you add one field to an existing system, add work not done and why. It captures follow-up revenue that currently evaporates, and it tells you which jobs are being scoped wrongly before they become complaints.

Offline Is Not an Edge Case

Work orders are completed in basements, plant rooms, lift shafts, rural properties and underground car parks. A system that needs connectivity to record a completed job will be worked around, and the workaround is paper and a phone camera.

Ask every vendor the same four questions and accept only specific answers.

1Can a work order be opened, completed and signed with no connection at all?
2Are photos stored locally and uploaded later, at full quality rather than a thumbnail?
3What happens if two people edit the same order while both are offline?
4What does the engineer see if the sync fails: a clear warning, or silence?

The third question catches a lot of products. Offline capture is common; offline conflict handling is not, and silently losing the second person's notes is worse than refusing the edit.

Have an idea like this?

Get a free, no-obligation quote for your project. It takes two minutes and there is no pressure.

Evidence That Survives a Dispute

Evidence is only useful if it is attributable and hard to alter afterwards. Three properties decide whether your records help you.

Timestamped at capture, not at upload. A photo stamped with the sync time proves nothing about when the work happened
Attributed to a person, through their own login rather than a shared device account
Append-only after close. Corrections recorded as additions with their own timestamp, never silent edits

The third is the one that distinguishes a records system from a notepad. If a closed work order can be edited and nothing records that it changed, then any of them could have been edited, and the whole set weakens. Ask whether closed orders are locked and how corrections are handled.

On photographs: agree a small standard and it will be followed, because it is less work than being asked for more later. Something like a wide shot showing context, a close shot of the fault, a shot of the completed work, and the serial plate. Four photos, every job, no debate on site.

Build or Buy

Buy if your work orders are ordinary. The products are mature, the mobile apps are the expensive part to build, and offline sync is genuinely hard engineering you should not take on without a reason.

Situation	Usually right	Why
Standard reactive and preventive work	Buy	Well served, and the mobile app alone justifies it
A regulated form you must produce exactly	Buy and extend, or build the form	Compliance documents rarely bend to a product's template
Work orders must drive an existing system you cannot replace	Build the integration	Cheaper than replacing either end
Your customers need a portal into their own work history	Buy plus build the portal	Customer-facing views are usually the weakest part of these products
Managing work is your product	Build	It is your differentiator

The regulated-form row is the most common genuine reason to build here. If an inspection certificate has to come out in a prescribed layout with prescribed fields, a product that nearly does it creates manual rework on every single job, and that cost compounds.

Rolling It Out Without Losing the Crews

Work order systems fail on adoption more than on features, and adoption is decided in the first fortnight. The people filling the forms in have to get something out of it.

1Start with one team and one job type, not everything at once
2Cut the form to the fields you will genuinely use. Every optional field is a tax on every job
3Let crews see their own history and their own completed work, so the data is theirs too
4Remove the paper equivalent on a named date, or both will run forever and neither will be complete
5Show the office using the data within the first month, so it is visibly not just extra typing
6Review the form after a month and delete whatever is being filled in with nonsense, because that is a field nobody needed

The last step is the one that keeps the data honest. A field that is always set to its default is not giving you information, it is costing you goodwill on every job.

We build work order systems and the integrations around them, including the offline mobile capture and the regulated forms that packaged products will not bend to. Tell us what your work orders have to prove and we will tell you whether a product can do it before you commit to anything.

Frequently asked questions

What is work order software?

Software that turns a request for work into an instruction, a record of what was done, and evidence you can bill and defend afterwards. Most systems handle the instruction well; the record and the evidence are where they differ.

What fields should a work order capture?

Beyond customer, address and description: the asset or serial number, reported fault and found fault separately, arrival and departure times captured on site, access problems and waiting time, parts used from stock, work not done and why, the individual who did it, and a signature with a printed name.

What is the single most useful field to add?

Work not done, and why. It captures follow-up revenue that otherwise evaporates and tells you which jobs are being scoped wrongly before they turn into complaints.

Does work order software need to work offline?

For most field work, yes. Basements, plant rooms and rural sites have no signal, and a system that needs connectivity gets worked around with paper and a phone camera. Ask specifically how it handles two people editing the same order offline.

How do we make records that stand up in a dispute?

Timestamp at capture rather than at upload, attribute to an individual through their own login rather than a shared device, and make closed orders append-only so corrections are recorded as additions rather than silent edits.

Should we build a custom work order system?

Usually buy, because offline mobile sync is hard engineering. Build when a regulated form must be produced in a prescribed layout, when work orders must drive a system you cannot replace, or when managing work is itself your product.

Keep reading

Software & Tools

Ready to get a number for your idea?

Tell us what you want to build. We reply within two hours with a clear, fixed-scope quote. It is free and there is no pressure.

Work order software: the fields that matter and the ones people forget