Keep the note, bill, rate, and finding tied to the job.
For diesel repair shops
Close out a job in minutes. You still approve every invoice.
DieselOS pulls technician notes, vendor bills, and your rates into a ready-to-review draft—nothing gets billed until your team signs off.
We assemble one job with you. You keep the draft. We agree a secure intake before any job records are shared.
Every billed line has a reason.
Read the short answer first. Open the source only when someone needs the detail.
The repair record is ready when the customer asks.
What was done. What supports it. What still needs approval—fewer calls back to the bay asking what changed and why.
TruckDiag reads the arrival scan. Your technician makes the call.
Available on its own or with DieselOS, TruckDiag captures source ECU, SPN/FMI, lamps, occurrence count, and capture quality when the truck is connected.
When the evidence supports a useful hypothesis, it names the next verification test. When it does not, it says so.
Explore TruckDiagTruckDiag · arrival scan
Offline-validated workflowArrival scan captured
Engine #1 reported SPN 3936 / FMI 18 with an amber lamp. Capture complete.
Four steps. No invented certainty.
See what supports a line and what only provides context.
Leave missing rules open until a person defines their value and scope.
Approve a named draft version. Any later edit returns it to review.
In beta
Source-backed invoice drafts, evidence review, unresolved decisions, and explicit approval.
Designed to expand into
Full repair decision records, customer-ready approvals, and verified system handoffs.
Before you start.
Do we have to replace our current system?
No. This beta is a review surface for a job draft. It does not claim to replace accounting, diagnostics, or shop management software.
What counts as evidence?
A technician note, supplied rate, vendor bill, attached record, or an explicit policy. The draft labels each one separately.
What happens when a price rule is missing?
It stays open. A reviewer defines the value, tax treatment, scope, and invoice impact before it can affect the draft.
Will technicians need another app?
The beta is designed around the records already created during a job. The workflow should make those records useful at closeout, not create duplicate paperwork.
Bring one unfinished job to a working session.
We’ll assemble a review draft with you, and you keep the result. This form starts the conversation only; we agree a secure intake before any job records are shared.