Loading
How it works
Tech inspects on any device, advisor prices the findings, customer approves by phone, job moves forward.
No paper form. Tech works through the checklist on a tablet or phone — each item: Pass / Concern / Fail, with a photo and note field.
Inspection submits automatically. Advisor reviews findings, prices the recommended lines, and sends an estimate to the customer.
Customer receives a portal link — no login. They see findings, photos, prices. Approve or decline each line individually.
Approved lines convert to the RO. Declined lines go to deferred-work queue for follow-up. Board updates in real-time.
DVI · trust · ARO
Tech captures → advisor reviews → customer approves in the portal. Every finding documented, every approval timestamped. The old workflow: tech writes findings on a paper RO, advisor transcribes them, someone prints a PDF, customer says "just do what you think." Nobody wins and nothing is documented. Workshop Wrench closes the loop: findings on the repair order, priced estimate lines in one step, a portal link the customer opens on their phone to approve or decline each item. No re-keying, no missing context, no "I didn't know that was on the list." Findings gallery is Live+; richer media templates and offline photo queues continue to expand honestly.
Why this category matters
Category pages should not be synonym stuffing. Here is the operating rationale every serious shop platform must address.
Car count dies on missed calls, weak booking, and messy intake — the OS must own first contact through check-in.
ARO dies when findings never become priced, decided lines — DVI and portal approvals are margin features.
Throughput dies when AWAITING_AUTH and AWAITING_PARTS are invisible — board stages must mean something.
Cash dies when invoices are re-keyed and AR is a Friday spreadsheet — money path starts on the repair order.
Vehicle lifecycle
The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.
Capabilities
Live means in the multi-tenant product/demo. Integrations use Live / Stub / Dry-run / Planned — never Connected for stubs. Roadmap means not production-complete.
Tech logs findings in the job context they already work in — not a separate inspection app that never connects to the job card. Findings stay attached to the job, so nothing falls out of the conversation between the pit and the counter.
Recommended work becomes a priced line with approval state in one step — so the advisor stops re-typing what the tech already captured, and the customer sees the finding before deciding, not a paraphrased summary.
Customer receives a token link, opens it on their phone, and approves or declines each line individually — no shop login, no back-and-forth calls, and every decision is timestamped so there is no "I didn't authorise that" conversation at pickup.
Gallery and portal findings path live — customers see what was found, which builds the trust that turns a "maybe next time" into an approved line. Richer contextual views continuing to ship.
Structured inspection templates and hardened offline photo capture continue to expand — honest about where it sits relative to a full US-class media suite, expanding with each sprint.
FAQ
Structured for humans and search (FAQ schema). We update when ship status changes.
Photo-backed findings with line-level approval remove the "I did not authorise that" conversation at pickup. More importantly, they lift ARO — customers who see the finding and the photo approve at a higher rate than customers who hear it second-hand from an advisor.
Findings to estimate lines to portal approve is live. Findings gallery is Live+. Full template polish and offline photo queues remain Partial — we never market this as a finished US-class media suite.
Estimates & Approvals
Convert DVI findings to priced lines the customer approves by phone.
→Customer Portal
Line-level approvals from the customer's phone — no login required.
→Job Board
DVI findings visible on the board card alongside job stage.
→Deferred Work
Declined DVI lines flow straight into the recovery queue.
→