How it works
Six chapters, in the order a garage lives them. Every rule below is enforced by the system, not by remembering, which is the difference between a process and a poster.
Find the owner before you create one.
Search by phone, email or name. If nothing matches, create the customer and the vehicle without leaving the form. Record who actually brought the car in, often not the owner, and both of them can be told it arrived.
Evidence first, opinion second.
Technicians log findings against areas of the vehicle with a severity and a recommendation, and can be required to attach a photo before flagging something. Diagnosis then names the root cause and the work it calls for.
Work nobody agreed to is work nobody pays for.
Recommended items go to the customer as approvals they answer from their tracking link. Approving above a threshold you set asks for the last four digits of the phone on file; declining never asks.
Parts come off a real shelf.
Procedure checklists are copied onto the job so a change to the template never rewrites a car already in the bay. Parts are drawn from the branch holding them, and every movement is recorded against the stock it came from.
The last look, by someone else.
Quality control is a stage like any other, and you decide whether a supervisor has to sign it off. A failed check returns the job with a note rather than quietly reopening it.
A bill that matches the job.
Estimates build from the services and parts on the job, become an issued bill, and settle line by line as payments land. A stage can require its charge to be paid before the vehicle goes any further.
And around it
Every visit keeps the customer, prices and workflow it ran on. Editing a template or a price list later cannot rewrite what already happened.
Throughput, turnaround, revenue, technician load and stock movement, over any range up to a year, with the slowest visits named.
One row per part with its branch breakdown, reorder levels, and a purchase list you can hand to a supplier.
Invite by email with a role and the branches they work at. Suspend someone without deleting their history.
Stock, jobs, access and reporting are all branch-aware. Staff see where they work; owners see everything.
A car wash and a gearbox rebuild follow different paths. Build each one, attach it to the services that use it, and publish.
Setting up takes a few minutes, and the first vehicle can go through the same day.