How to Write a Repair Line

Why the 3 Cs matter

A repair line is the core of every work order and invoice. It tells the customer what they are paying for, tells the next technician what was done, and becomes part of the unit's history. Fleets rely on those records. Under 49 CFR 396.3, motor carriers must keep records of inspection, repair and maintenance for each vehicle they control. A vague line like "fixed brakes" is a poor record. A clear 3C line is a good one. See 3 Cs: complaint, cause, correction.

Some states also have rules about how repairs are described. California's Write It Right guidance says invoices must describe work and parts so the customer can understand what was purchased, and discourages shorthand such as "R&R".

The complaint

The complaint is the problem that brought the vehicle in, or a problem found during inspection.

Write it as:

• What the driver or fleet reported, in their words when useful.
• Or what was found, with where and how it was found.

Good: "Driver reports air pressure drops when parked overnight." Weak: "Air problem."

For inspection findings: "Found during annual inspection: right front steer tire tread depth below limit." See annual inspection.

The cause

The cause is what the technician found was actually wrong. It shows the diagnosis was done.

Include:

• The failed component and location.
• How it was confirmed: test, measurement, code or visual check.
• The reading against the limit where there is one.

Good: "Leak test found air leak at rear service brake chamber, left side drive axle. Diaphragm leaking." Weak: "Bad chamber."

If the cause cannot be found, say so and what was checked. That is still useful information.

The correction

The correction is exactly what was done.

Include:

• What was replaced, repaired or adjusted.
• Key steps such as adjustment, torque or programming.
• How the repair was verified.

Good: "Replaced left drive axle service brake chamber. Adjusted brake. Leak tested system, no leaks found. Checked pushrod stroke within limit." Weak: "Replaced."

See brake chamber and slack adjuster.

Parts and labor under the line

Under each repair line, list:

• Each parts line with description, part number, quantity and price, and whether new, used or rebuilt.
• Labor hours, and whether billed at actual time or a standard time. See book time.
• Any core charge on its own line.

Keeping parts and labor tied to the repair line shows the customer what each part was for.

One line per problem

Do not combine unrelated problems into one line. If a truck came in for an air leak and the technician also found a burned-out marker lamp, those are two lines. Separate lines:

• Let the customer approve or decline each item.
• Show the cost of each problem.
• Make the unit history searchable.

Full examples

These examples are invented for illustration.

Example 1: road call

• Complaint: Driver reports truck will not start at customer site.
• Cause: Battery test found two of four batteries failed load test. Cables and terminals corroded.
• Correction: Replaced two batteries. Cleaned and protected terminals. Load tested all batteries, passed. Started and ran engine, charging voltage normal.

Example 2: PM finding

• Complaint: Found during PM service: oil seep at oil pan gasket.
• Cause: Visual inspection shows light seep at rear of oil pan. No drips. Oil level normal.
• Correction: No repair today per customer. Recommend monitoring and repair at next PM.

Declined or deferred items still deserve a 3C line, because they warn the fleet and protect the shop. See PM service.

Words to avoid

• "R&R" or "R/R" without explanation.
• "Checked" with no result.
• "As needed" or "misc."
• Internal codes the customer will not know.
• Blame or opinions about the driver.

Codes and standards

Many fleets classify repairs with VMRS codes from the ATA Technology and Maintenance Council. If a fleet customer asks for VMRS codes, add them to each line. See VMRS codes.

From shorthand to a clean line

Technicians are not writers, and they are often typing on a phone with dirty hands. A practical approach:

1. Technicians record short notes, photos and readings as they work.
2. The service writer or software turns the notes into full 3C lines.
3. The technician checks that the line matches what was done.
4. The line goes on the estimate or invoice.

What matters is that the final line is accurate and in plain words, and that the technician's findings are not lost.

Writing lines for inspections

Inspection work produces many small findings. For each failed or flagged item, write a separate 3C line that names the inspection item, the finding and the measurement, and the correction or the recommendation. For items that passed, the inspection form itself is the record. Under 49 CFR 396.21, the person doing a periodic inspection must prepare a report that identifies the vehicle and the components inspected, among other items. A repair line for each defect that was corrected ties the repair to the report. See inspection failure.

Writing lines for diagnosis only

Sometimes the shop only diagnoses and the customer takes the truck elsewhere or decides later. The line still follows the 3 Cs:

• Complaint: what was reported.
• Cause: what was found, with codes and readings.
• Correction: "Diagnosis only. Recommend" followed by the repair recommended.

Bill the diagnostic time on that line. A clear diagnostic line is often what wins the repair later, because the customer can see the work behind the recommendation.

Lines for fleet customers

Fleet customers often ask for more on each line than a walk-in customer does: the unit number, the odometer or engine hours, a purchase order number, and sometimes VMRS codes. Put the unit details at the top of the work order and the codes on each line. Ask a new fleet account what they need before the first job, so lines do not have to be rewritten later. See unit number and odometer reading.

Training new technicians

New technicians learn the 3 Cs fastest from examples. Keep a short set of good lines from the shop's own jobs, covering common work such as brakes, electrical, tires and PM findings, and review a few of each new technician's lines every week in their first months. Point out what was missing rather than rewriting the line for them. Over time the lines get better without anyone needing to be a writer.

Review checklist

• Could a fleet manager who was not there understand it?
• Does the cause show how the problem was confirmed?
• Does the correction show how the repair was verified?
• Are measurements and codes included?
• Is each problem on its own line?
• Are parts and labor listed under the right line?

How good lines pay off

• Faster approvals. Customers approve what they understand. See how to send estimates customers approve.
• Fewer disputes. The invoice explains itself.
• Fewer comebacks. The next technician knows what was done. See comeback.
• Better records. Fleets can search their unit history.

How MetaFleet helps

MetaFleet's AI invoicing writes repair lines from technician shorthand with suggested labor hours, keeping the technician's words, and the shop adds the parts. MetaFleet also supports work orders, digital inspections and estimates. Get a walkthrough.