The work order is a record, not a throwaway printout: labour lines with hours, parts with numbers, external services, a status chain with timestamps, and a cost total derived from the line items rather than typed into the header.
Operations that run their own workshop have to answer years later what was done to a vehicle and what it cost. That is why the printout here is a rendering of the order and not the artefact itself. External workshops are the same partners that receipts and contracts already bill against — name and address are copied onto the order so a later rename does not rewrite a closed job.
Labour, parts, external services and other as line types. Labour lines without their own price use the order's hourly rate; hours are counted even without a configured rate, so an in-house workshop can document its working time.
Labour, material, external and total cost are recomputed on save. The total never comes from the client — that is exactly the path along which header and line sums otherwise drift apart.
Draft, released, in progress, completed, invoiced, cancelled — every transition with timestamp, person and an optional note. Going backwards is allowed, because workshops report 'done' and then find the next defect; invoiced and cancelled are terminal.
In KPIs and in the vehicle file, completed and invoiced orders count. A draft is a plan, and a cancelled order cost nothing.
Maintenance, repair, inspection, tyre change, accident repair or other, each as internal or external work, with normal, high or urgent priority.
A workshop, inspection, tyre or handover appointment is its own record with subject, location, order number, cost centre and a start/end odometer pair — and an optional driver, because a car sitting in the workshop often belongs to nobody those days.
A new workshop appointment proposes subject, assigned driver, odometer and the workshop from the last order — and says where that proposal came from instead of inventing it.
The order as a PDF for the workbench. Fleet-wide, the 'vehicle and workshop appointments' report answers the weekly planning question — including the inspection dates from the vehicle file, with Excel, PDF and CSV export.
For order and cost documentation, yes: orders with labour, parts and external line items, an hourly rate, status chain, history and printout. What is not modelled yet is who did the hours. There is no per-mechanic time tracking and no role-based hourly rates — the order carries hours, not a name behind them.
No. Invoiced is a status transition today, not a document generator. The order's costs appear on the workshop card of the vehicle file and in the workshop KPIs; an invoice to a third party is still written in your billing system.
No. The appointment shows in the vehicle's calendar but does not enter the booking availability check. To take a vehicle out for its workshop stay you block it through dispatch today.
Maintenance planning says what is due when; the work order records what was actually done and what it cost. An order can reference a maintenance record or a damage case. That link is one-way today: the order knows the case, the case does not yet display the order.
Maintenance templates, plans by time or mileage, service history and reminders.
Tyre sets, tread measurements per wheel position, two thresholds and the seasonal change campaign.
Every vehicle with technical data, registration, plate history, tyres, due dates and costs in one file.
Workshops, suppliers, insurers and authorities with contacts and a communication trail.
30 minutes, no sales pressure: we show the module in the context of your fleet — self-hosted in your data centre, GDPR-compliant, made in Germany.