A workshop without a system produces two things reliably: a pile of job slips, and an argument at the end of the year about which vehicles are costing money. The parts went somewhere. The labour was done by someone. Neither is attached to the unit that consumed them.

The fix is not a bigger spreadsheet. It is making the job card the thing that controls the work, rather than a record written up afterwards.

What the job card has to carry

A job card that only records what was done is a diary. A job card that controls the work has five states, and nothing moves between them informally.

Fault reported
Who raised it, when, and the symptom — not the presumed cause. Recording "brake problem" rather than "needs brake pads" preserves the information that matters when the same fault recurs.
Work authorised
Someone with authority approves the scope before parts move. This is the control that stops a routine service becoming an overhaul.
Parts issued
Against the job card, drawing down real stock. A store that issues on a verbal request cannot reconcile, and will not.
Labour booked
Technician time against the job. Compare it with standard times where you have them; the gap is where either training or estimating needs attention.
Released
The vehicle returns to service and the card closes. Until then it is off road, and that matters for reasons below.

Preventive work has to be raised, not remembered

Every workshop intends to do preventive maintenance. Most do it when someone notices, which means it happens late on the vehicles that are busiest — exactly the ones where failure is most expensive.

A schedule attached to the vehicle, triggering by distance or elapsed time, removes the remembering. The service is due because the unit has run its interval, and it appears on a list rather than in someone's head.

The discipline this requires is accurate odometer capture, which brings us back to the gate. Readings taken at the barrier on entry and exit, with the system rejecting anything lower than the last, is the cheapest reliable source you will find.

External bills belong on the same card

Few operations do all their own work. The moment some repairs go to an outside workshop, maintenance cost splits across two systems and stops being comparable.

External bills should import against the job card they belong to, be matched before approval, and carry the same vehicle reference as in-house work. Otherwise you have a per-vehicle cost that quietly excludes the expensive repairs, which is worse than no figure at all because it looks authoritative.

Why downtime is a workshop output

A vehicle in the workshop earns nothing and still accrues fixed cost. If the time off road is not recorded with a reason, that cost spreads silently across the vehicles that were working — flattering the broken unit and penalising the rest.

This is the practical argument for the workshop and the fleet register sharing one vehicle master. When a job card opens, the unit becomes unavailable for allocation and its downtime is recorded without anyone doing anything. The cost per kilometre then reflects reality, and the availability figure means something.

What to ask a vendor

Most workshop software demos well. These questions find the gaps.

Can parts be issued without an authorised job card?
If yes, the control is advisory. Ask whether it can be configured to no.
How do external workshop bills get in?
Bulk import matched to job cards, or manual entry? At any volume the answer determines whether it gets done.
Does the fleet side see downtime automatically?
If the two systems need reconciling, you will be reconciling them monthly, forever.
Can I see lifetime cost for one vehicle?
Parts, labour, external bills and downtime, across its whole life — not just the current financial year. This is the figure a replace-or-keep decision needs.
Does it handle warranty?
Work covered under warranty should be flagged so it is claimed rather than absorbed. Most operations lose money here quietly.

Common questions

What should a vehicle job card include?

Fault as reported, authorisation before parts move, parts issued against the card, labour booked by technician, and a release step that closes it. Each state should be stamped, so the history is reconstructable.

Should preventive maintenance trigger by distance or by date?

Both, whichever comes first. A vehicle covering high mileage needs servicing by distance; one sitting idle still needs it by elapsed time. Systems offering only one will under-service part of your fleet.

How do we stop losing warranty claims?

Flag warranty-covered work on the job card at the point it is raised, not at month end. If the flag depends on someone remembering the purchase date, it will be missed.

Can workshop software work for an in-house plant workshop rather than a commercial garage?

It should, but most products on the market are built for commercial garages invoicing customers. A plant workshop needs cost allocation to cost centres and integration with the fleet register, not customer billing.