What is a repair order? Fields and a shop handoff
Learn how a repair order connects estimate revisions, separate approval decisions, findings, and completed work without rewriting the record.
A repair order is the working record for one vehicle visit. It connects the customer’s concern, each estimate, each approval decision, the technician’s findings, and the work completed.
The exact legal meaning and required fields vary by location. Treat this as a record method, then check the estimate and authorization rules that apply to your shop.
Keep the estimate and decisions with the visit
An estimate shows proposed work and prices. An approval records what the customer accepted or declined. The repair order gives the shop one place to follow those records as the visit changes.
A shop may keep them as separate documents or connected parts of one record. California, for example, defines a work order as a paper or electronic document containing requested repairs, the authorized estimate, and the vehicle’s odometer reading. The state’s Write It Right guide was updated in January 2026. This California guidance does not set a national rule.
Assign one repair order number to the visit. Use it on each estimate revision, approval record, finding, and completion note. This makes the repair order an index to the retained records instead of a second copy of every detail.
Start with intake fields
The first section should establish who, what, and why. Capture:
- Repair order number and opening date
- Customer name and preferred contact details
- Person allowed to approve work, if different
- Vehicle year, make, model, VIN, plate, and mileage in
- Customer concern in the customer’s own words
- Requested service or authorized assessment
- Promised update time, if one was agreed
- Vehicle location and key location for internal use
Do not turn the customer’s concern into a diagnosis at intake. “Scraping sound during a low-speed stop” preserves what the customer reported. “Needs front brakes” states a conclusion the shop may not have reached.
For covered written estimates, Washington law lists customer, shop, vehicle, odometer, and reported-problem fields. The statute has a dollar threshold and exceptions. Other states use different terms, limits, and notices.
Link every decision to approved scope
A clear repair order has a visible estimate and approval block. For each decision, record:
| Field | What it should answer |
|---|---|
| Job ID | Which job or jobs does this decision cover? |
| Description | What work can the technician understand and the customer recognize? |
| Estimate revision | Which retained version did the customer review? |
| Jobs and prices | Which proposed jobs and presented prices were on that version? |
| Decision | Approved, declined, or still waiting? |
| Approved estimate | Which estimate revision, jobs, and prices does this decision accept? |
| Authorization record | Who decided, when, and through what recorded contact? |
| Scope limit | What must not start without another decision? |
Make clear which jobs each approval covers. If the customer approves one job and declines another, record those decisions separately.
California’s guide defines “specific job” as all repair work in one transaction, as listed on the estimate. It does not mean each estimate line is a separate legal job. California also specifies what written, oral, and electronic authorization records contain. Those rules are specific to California. The practical method here is to preserve each decision and show exactly which proposed work it covers.
Give the technician a bounded handoff
The handoff should tell the technician what can happen next. Keep it short enough to scan before touching the vehicle.
- Confirm the vehicle, mileage, repair order number, and key location.
- Read the customer concern without rewriting it as a finding.
- Review each decision and its approved estimate reference.
- Confirm the assigned technician, due date, and current status.
- Point to relevant photos, notes, or measurements already attached.
- State the stop point. New findings return for review before added work begins.
A status such as “In progress” does not expand the approved scope. A due date does not do that either. They organize work. The retained decision record shows what the customer accepted.
The first handoff can fit in a small block:
Start: Job A, the authorized inspection. Do not start: Job C, the declined shop-proposed maintenance. Return for review when: the inspection is recorded, it cannot be completed, or another repair is proposed.
Job B does not exist at intake. It enters the record only after a finding supports a new proposal.
Add findings and revise the estimate
Keep the original customer concern. Add findings in a separate section with the date, technician, note, and attached evidence. This preserves the difference between what the customer reported and what the shop observed.
A finding is not authorization. If it leads to added work, add the proposed job to a new estimate revision. Record the customer’s decision before assigning that work. California’s guidance says to prepare a revised work order, provide the added parts, labor, and revised cost, and obtain authorization before additional repairs or charges. See California BAR’s additional authorization guidance.
Use a simple chain:
Concern → authorized check → finding → revised estimate → decision → assignment
Every step should leave a dated record. Do not erase the earlier state when the job changes.
Compare requested, authorized, and completed work
This worked example shows one visit without repair details or prices. The authorization references point to retained records with the estimate revision, scope, prices, approver, time, and contact method. Those records are intentionally omitted from this teaching extract. No price should be invented to fill the gap.
| Job | Requested | Authorized | Completed |
|---|---|---|---|
| A | Customer reported a scraping sound. Shop proposed an inspection. | Inspection authorized at 8:15 a.m. Reference A links to the initial estimate and decision record. | Inspection performed. Finding F1 recorded at 10:20 a.m. |
| B | Shop proposed added work after finding F1. | Pending at 10:20 a.m. Revised estimate authorized at 10:50 a.m. Reference B links to the revision and decision record. | Approved added work performed. Actual result recorded. |
| C | Shop proposed a separate maintenance item at intake. | Declined at 8:16 a.m. Reference C links to the initial estimate and decision record. | Not performed. Declined item remains recorded in history. |
The columns do not need to agree at every moment. At 10:20 a.m., Job B is proposed but still pending. The technician must not start Job B until its approval is recorded and handed back. That pending decision does not revoke approval for other work.
Do not rewrite history to make the columns agree. Keep the pending state, then add the 10:50 a.m. decision. A declined proposal also stays visible instead of becoming a customer request or disappearing.
Write completion notes that support review
For each completed job, name the work performed, the check made, the actual result, and any unresolved concern. Record who completed it and when. “Done” does not tell the counter whether the work matched the approved estimate.
Compare the completion note with the retained decision before closing the handoff. If completed work falls outside the approved scope, stop and review the record. Do not edit the earlier request or approval to hide the mismatch.
For the billing step, follow the estimate-to-invoice worked example. It traces approved work through final charges, a deposit, and partial payments.
Keep the repair order tied to its approval records
A useful repair order preserves the concern, estimate revisions, separate decisions, findings, and completion facts. It shows what changed and when without turning a finding or status into approval.
Use the auto repair order template to inspect a printable field set. See repair order software and job tracking for connected assignment and status. Neither resource replaces a review of the rules for your location.
