How to Close a Work Order So It Survives an Audit

Why this matters

An institutional audit does not ask whether you did good work. It asks whether a person who was not there can reconstruct, from the record alone, that authorized work was performed by a qualified person and billed at the agreed rate. That is a different test than completeness, and a thoroughly written ticket routinely fails it while a shorter one passes. What the auditor follows is the chain between documents: authorization to labor, labor to invoice, parts to receipt, person to credential. Break any link and the whole line is disallowed, sometimes a year later, sometimes across every ticket that shared the defect. A shop that has closed 300 tickets the same wrong way finds out about all 300 at once.

A note on scope before the steps. Capturing the work in the field, what you did and what you used, is its own procedure and a sibling article covers it. This one starts after that and deals only with what makes the closed record hold up to a third party.

The rule this article runs on

A closed ticket survives an audit when every claim on the invoice traces to a document created by someone other than the person being paid, or to a timestamped record created at the moment of the work. That is the whole gate. Read the two halves as an OR, not an AND: a third-party document satisfies it, and so does a contemporaneous record, and most tickets need a mix. The unit of analysis is the individual line on the invoice, not the ticket as a whole, which is why partial disallowances are more common than total ones.

Below, that single rule is run against two tickets from the same account and the same month. One survives. One does not, and it is the better-written of the two.

Ticket A: a chiller repair, 11.5 labor hours, two technicians

What the record held. The facility's ticket, opened by their engineer, priority 2, with a charge account. A dispatch timestamp from the shop's system. Two technicians' time recorded by clock-in and clock-out at the site badge desk, which is the facility's system, not the shop's. A parts requisition against the shop's stock with a supplier packing slip attached. A completion note naming the asset tag, the failed component, the reading that condemned it, and the reading after repair. A signature from the facility engineer on completion. An invoice quoting the ticket number and the two technicians' names against the labor category in the agreement.

Run the rule, line by line. Labor traces to the badge system, which the shop does not control, so the contemporaneous half and the third-party half are both satisfied. Parts trace to a supplier document. The technician's rate category traces to the agreement plus the named technician, whose credential is on file with the facility's vendor portal. Authorization traces to a ticket the shop did not open.

Where it would have failed. If the two technicians had been recorded as a single line of 11.5 hours with no names, the rate category could not be verified against the agreement, and the whole labor line becomes disputable at the auditor's discretion. Naming people is not bureaucratic courtesy; it is what connects an hour to a rate.

Ticket B: an emergency drain call, 3.0 labor hours, one technician

This ticket has better prose. The completion note runs to two paragraphs, describes the diagnosis clearly, and reads like someone who knew what they were doing. It fails anyway.

What the record held. No ticket at the time of the work, because the call came at 22:40 from a building supervisor by phone. The technician's own time entry in the shop's system. A photo of the cleared line, undated in the record. A materials line for consumables carried on the truck. An invoice raised nine days later quoting a ticket number the facility issued retroactively.

Run the rule. Authorization: the retroactive ticket exists, but nothing ties the 22:40 call to it except the shop's own assertion, and the supervisor who called is not on the facility's list of people who can commit funds. Labor: recorded in the shop's own system by the person being paid, with no badge record because after-hours entry was through a door that does not log. Materials: truck stock with no requisition and no supplier document for that specific job.

Every line depends on the shop's own word. That is the definition of a failed audit trail, and the quality of the writing is irrelevant to it.

What would have saved it, at the time, in about four minutes. A text message to the facility's on-call engineer at 22:45 stating the location, the condition and that work was starting, which creates a timestamped record on a system the shop does not own. A photo taken with location and time metadata intact rather than exported through a channel that strips it. A truck-stock consumption entry made on site rather than the next morning. None of that is more paperwork; it is the same paperwork, created at a moment that gives it evidentiary weight.

The five links an auditor follows

Work backwards from the invoice, because that is what the auditor holds first.

  1. Invoice line to ticket number. Exact string match, including prefixes. A reformatted number is treated as a missing number.
  2. Ticket to authorization. Who opened it, and were they authorized to commit that charge account. Retroactive tickets need the authorizing person named, not just the ticket.
  3. Labor hours to a time record not created by the biller. Badge logs, gate logs, the facility's own sign-in sheet, a dispatch record with a timestamp, a customer signature carrying a time.
  4. Labor rate to a named person and a credential. The agreement prices categories; the ticket has to say which category, and the person's licence or certification has to be current on the date of the work, not the date of the audit.
  5. Materials to a document from outside your shop. A packing slip, a supplier invoice, or a facility-issued requisition. Truck stock is the weak point and needs a consumption record made at the time.

Retention: how long the record has to last

Set your retention to the longest clock that touches the work, not the shortest. Three separate clocks commonly run at once, and they are not the same length.

  • The agreement's own audit window, frequently stated as a number of years after final payment, with a right to examine records. This is contractual and you agreed to it.
  • The statute of repose for construction defect claims in your jurisdiction, which clusters roughly in the 6 to 10 year range and runs from substantial completion rather than from the ticket.
  • Employee exposure and medical records where the work involved a regulated exposure, which under 29 CFR 1910.1020(d)(1) run duration of employment plus 30 years for medical records and 30 years for exposure records. That clock is far longer than the other two and is not negotiable by contract.

The practical consequence is that a purge policy written around the shortest of these will destroy records you are still required to hold. Where the work touched a regulated exposure, the exposure record is separated from the job file and kept on its own schedule.

Worked example: what a defect costs when it repeats

The shop above closed 214 tickets on the account over a year. An audit sampled 25 and disallowed 3, all for the same defect: labor recorded only in the shop's own system with no independent time record, on after-hours calls where the badge desk was unstaffed.

The sample rate is 3 of 25, or 12 percent. Auditors commonly extrapolate a sample finding across the population, so the exposure is not 3 tickets but roughly 12 percent of 214, about 26 tickets. If those tickets average 3.5 labor hours, the exposure is on the order of 91 labor hours, against a total year of 214 tickets at an average 2.8 hours, which is about 599 hours. So a defect present on one in eight sampled tickets puts roughly 15 percent of the year's labor hours at risk, and the shop's defense is limited to whatever independent evidence it can retrieve after the fact.

Now the correction, and note it does not touch price or headcount. The shop's after-hours process gained one step: a text to the facility's on-call line at start and at finish, from the technician's phone. That created a timestamped third-party record on 100 percent of after-hours calls at a cost of roughly 2 minutes per call. Against 26 after-hours calls a year, that is about 0.9 hours of annual effort protecting roughly 91 hours of billing.

Do not read the last figure as a return multiple. The 0.9 is unbilled administrative effort the shop absorbs; the 91 is gross billed labor that still costs technician time and travel to deliver. What the comparison shows is that the protective step is cheap relative to the exposure, not that the shop earns a hundred times its effort.

Also note what the extrapolation assumes. It assumes the sampled 25 are representative. If your after-hours calls are 12 percent of tickets and the auditor's sample happened to overweight them, the true exposure is lower, and saying so with your own ticket-type counts is a legitimate response. Bring the counts, not the argument.

How to verify a ticket before you close it

Take a closed ticket at random each week and hand it to your office manager with one instruction: bill this from the record alone, without asking anyone what happened. If they can produce the invoice, name the technician, price the labor category and cite the parts source without a phone call, the ticket survives. If they have to ask you anything, that question is the exact gap an auditor will find, and it is cheaper to find it in the same week than in the following year.

Run the same test on one after-hours ticket per quarter specifically. After-hours work fails this test far more often than day work, for a structural reason: the systems that create independent records, badge desks, receiving docks, requisition counters, are all staffed during the day.

References

  • 29 CFR 1910.1020(d)(1), retention periods for employee exposure and medical records
  • See related: How to Close Out a Work Order in the Field
  • See related: The Work Order System and Why the Ticket Is Your Only Record
  • See related: How to Assemble a Closeout Package