A single jobcard can produce several different documents depending on who's reading them. They all share the same data underneath but the formatting differs: a technician needs the work, a customer needs the cost, a fitter signing off an inspection needs the checklist.
The four types
Customer-facing jobcard / estimate
Shown when you print or share a jobcard with the customer before invoicing. Includes garage branding, customer name, vehicle, the full list of jobs with their parts and labour, and the cost breakdown with VAT. For: the customer.
Invoice
A separate, formal document raised from the jobcard's Invoices tab — invoice number, issue and due dates, amount paid and balance, and your bank details. Locked once issued; print it from the invoice page (Print / PDF) or via the print dialog's Invoice Copy. For: the customer (for payment) and your records.
Technician work order / job sheet
A stripped-down printout for the workshop floor (the print dialog calls it the Workshop Copy). Registration, make/model, mileage, jobs, parts, labour. No customer name. No contact. The only date shown is the booked appointment date, and even that can be toggled off. See the PII rule for why. For: the technician doing the work.
Inspection report
Generated from an inspection submission linked to the jobcard. Carries garage branding and vehicle details, and shows the checklist results, condition ratings, photos, and any signature captured. Print it or export it as a PDF. For: the customer, plus an internal copy in your records.
Same data, different lens
Every jobcard document is generated from the live jobcard — change the labour rate on a job and the next print reflects it. The one exception is the invoice: its line items are snapshotted when the draft is created, and the document is frozen once issued. The difference between the jobcard document types is which fields are shown, not which fields exist.
Server-side filtering of financial fields
Users without payments.view get a jobcard payload from the API that already has rates, prices and unit costs removed. So a technician who somehow ended up viewing a jobcard JSON couldn't print a customer-style document by accident — the data isn't there to print.