Inspection findings on the RO
LiveCapture findings in the job context technicians already use.
DVI · trust · ARO
Digital vehicle inspection software that turns findings into approved work
Inspections are how modern shops earn trust and ARO. Workshop Wrench attaches inspection findings to the repair order, feeds estimate lines, supports customer decisioning via portal, and ships a findings gallery path (Live+) — with richer media templates and offline photo queues still expanding honestly.
Why this category matters
Profit levers behind the keyword
Category pages should not be synonym stuffing. Here is the operating rationale every serious shop platform must address.
- 01
Car count dies on missed calls, weak booking, and messy intake — the OS must own first contact through check-in.
- 02
ARO dies when findings never become priced, decided lines — DVI and portal approvals are margin features.
- 03
Throughput dies when AWAITING_AUTH and AWAITING_PARTS are invisible — board stages must mean something.
- 04
Cash dies when invoices are re-keyed and AR is a Friday spreadsheet — money path starts on the repair order.
Vehicle lifecycle
Complete vehicle service lifecycle
The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.
- 01Lead
- 02Customer
- 03Vehicle
- 04Booking
- 05Check-in
- 06Inspect
- 07Estimate
- 08Approve
- 09Parts
- 10Labour
- 11Produce
- 12Invoice
- 13Pay
- 14Release
- 15Retain
Shop day sequence
Six moments that protect cash
The same operational spine as the product board — detailed use cases live under Processes.
- 01
Book or walk in
Public booking or front desk intake with customer + vehicle first-class. Why: car count dies when first contact never becomes a system object.
- 02
Check in & board
Booking becomes a repair order; board shows stage, tech, and blockers. Why: WIP you cannot see is WIP you cannot manage.
- 03
Inspect with evidence
DVI findings with severity convert to estimate lines or deferred work. Why: verbal upsells without structure kill trust and ARO recovery.
- 04
Authorise work
Line-level approve / decline / defer via portal tokens. Why: silent scope expansion creates write-offs and disputes.
- 05
Parts & labour
Reserve stock, raise POs, clock labour on the RO. Why: authorised work without parts is fake progress; unbilled labour is pure waste.
- 06
Invoice & collect
GST invoice from approved lines, payments, AR visibility. Why: revenue is not cash until collected — money path stays on the RO.
Capabilities
What ships — with honest status
Live means in the multi-tenant product/demo. Integrations use Live / Stub / Dry-run / Planned — never Connected for stubs. Roadmap means not production-complete.
Convert to estimate lines
LiveRecommended work becomes priced lines with approval state.
Customer portal decide
LiveCustomers accept/decline lines without a desktop login.
Findings gallery
Live+Gallery projection and portal findings path ship Live+ after W4 N27.
Rich media templates / offline photo queue
PartialTemplate libraries and hardened offline capture continue to expand.
FAQ
Questions buyers actually ask
Structured for humans and search (FAQ schema). We update when ship status changes.
Why does DVI matter for shop software?+
Photo-backed findings increase approval rates and reduce “I didn’t authorize that” disputes. It is table stakes on modern shop platforms.
Is your DVI complete?+
Findings → lines → portal is live; gallery path is Live+. Full template polish and offline photo queues remain Partial — never marketed as a finished Shop-Ware clone.