Complaint, cause, correction — plus the timestamped record of the customer saying go ahead, which is what ends the argument about the bill. $59, once.
Not a generic service form with a notes box at the bottom. The fields are the ones that matter on this job, and the document at the end is the one your customer expects.
VIN, plate, mileage, and everything you've ever done to it. Second visits get much faster.
What the customer said, in their words. Then what you found. Then what you did. Three fields, and they're the ones a court reads.
Estimate given, customer approved — by phone, by text, in person — with the time on it. Went over? New total, new approval, new timestamp.
Parts with numbers and condition, labour, signature, invoice with a payment link. Done at the kerb.
“Customer approved $840 by text at 2:14pm after the estimate came in at $520.” That single structured line wins chargebacks and small-claims hearings, and no generic invoicing app has anywhere to put it.
Vehicle identity and mileage · complaint, cause and correction · estimate and the time it was given · who authorised it, how and when · every revision with its own timestamp · parts with numbers and condition (new, used, rebuilt, customer-supplied) · labour · warranty terms · signature.
It doesn't decode VINs and it doesn't look up parts prices. It records the job and the permission, which is the part nobody else keeps properly.
Do the whole job offline — photos and all — and it syncs itself when you're back in range.
There's a button inside every work layer that sends me a message. I read all of them myself. When a fix ships because someone told me, it goes in the changelog with a thank-you.