Job card
Job card explained: the record that travels with the work
A job card is the shop-floor record of a single job: the sheet or screen that travels with the work and captures what the technician actually found, did, fitted and timed. It is the technician-facing document, as distinct from the work order that authorises the job in the first place.
For field service
Know what the job needs before the van rolls
Venta Capture, a product of VentaVid, lets the customer show you the fault first, so the engineer arrives with the right part or does not need to arrive at all.
Written as job card, jobcard, or job sheet depending on the trade and the country. In North American workshops the same role is filled by the repair order, usually shortened to RO.
What does a job card contain?
The contents vary by industry, but the spine is consistent:
- Job and asset identity. Job number, customer, asset or vehicle details, mileage or running hours.
- The requested work, carried over from the authorising document.
- Diagnosis. What the technician found, in their own words, including what was ruled out.
- Work performed, in sequence, with the parts and consumables actually used.
- Time. Clock-on and clock-off, or booked hours against the flat-rate time.
- Additional work found, flagged for authorisation rather than quietly carried out.
- Technician sign-off, plus quality check or road test where the process requires one.
The two fields that decide whether a job card is useful are diagnosis and additional work found. Those are the ones that get one-word answers when the workshop is busy, and the ones every later question depends on.
Job card and work order: which document does what
The distinction is worth holding onto even where one document does both jobs.
The work order is the authorising document. It says the work is approved, defines its scope, and carries the commercial agreement. Anything about who authorised what, and how the scope was agreed, belongs to that document.
The job card is the execution record. It exists to capture reality: what was actually wrong, what was actually done, how long it actually took. Where the two disagree, that gap is the interesting part, and it is why additional work needs a fresh authorisation rather than a new line on the card.
In small reactive workshops the terms are used interchangeably and little is lost by it. In a planned maintenance environment with cost codes, approval stages and asset histories, keeping them separate is what makes the history readable.
The job card in an automotive workshop
Automotive is where the job card has the most developed form. The repair order plays this role in North America, and dealer service departments run their whole workshop day on it: it opens at write-up, follows the vehicle through dispatch and technician allocation, absorbs the inspection results and the parts picks, and becomes the invoice at cashier.
Warranty work adds a documentation standard on top. Manufacturers expect the technician's narrative to record the complaint, the cause and the correction, the three Cs, in enough detail for an auditor to follow the reasoning. A card that says "replaced under warranty" without a cause is the kind of entry that turns into a chargeback at audit. That is also why warranty claim inspection practice leans so heavily on evidence captured while the vehicle is still on the ramp.
How a job card moves through a day: a worked example
A van arrives for an intermittent charging fault. The job card opens with the customer's description and two hours of diagnostic time authorised. The technician records battery voltage under load, an alternator output reading and a corroded earth strap as the cause. Because the strap sits outside the authorised scope, the card flags it as additional work, service calls the customer, and the approval is added before the spanner moves. Everything after that, part number, time, retest reading, lands on the same card.
Where job cards cost money
Thin diagnosis. "Found faulty, replaced" gives the next technician nothing and gives a warranty auditor a reason to say no.
Unrecorded additional work. Carried out to be helpful, invoiced later, disputed at the counter.
Time written up once the shift is over. Estimated hours drift, and productivity reporting built on them drifts with them.
Cards that never inform the next visit. The asset history is the reason to keep them. If nobody reads the last three cards before starting the fourth job, the record is only a billing artefact, and repeat faults keep repeating.
Cleaner job cards start earlier than the workshop. What the customer describes at booking, captured properly at digital service intake, is what stops the diagnosis field from starting empty, and it is one of the quiet levers on first-time fix rate.
