Stage kanban
LiveEvery open RO visible by stage so advisors can see the floor at a glance without walking bays or chasing techs — which means blockers surface in seconds, not after a ten-minute walkabout.
Loading
Loading
How it works
The job board tracks every RO through each stage — no sticky notes, no 'how's that Hilux going?' across the bay.
Customer arrives, advisor opens a new RO (Repair Order), selects vehicle, adds services.
Job appears on the board in "New" stage — assign to a tech, who sees it immediately on their tablet.
Tech moves the job stage as work is done — domain rules stop skipping required steps.
Job reaches "Ready to Invoice" stage — advisor finalises, customer receives a portal link.
Floor operations
Monday morning, 7 bays, and you can't see which car is waiting on parts and which is ready to pull out. The job board changes that — every vehicle's stage, technician, and block reason on one screen. Workshop Wrench runs each repair order through a real state machine: Inspection, Awaiting Auth, Waiting on Parts, In Progress, Ready for Collection. No free-text guessing, no sticky notes, no "how's that Hilux going?" across the workshop. If it is on the board, it is real.
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.
Every open RO visible by stage so advisors can see the floor at a glance without walking bays or chasing techs — which means blockers surface in seconds, not after a ten-minute walkabout.
A job cannot move to In Progress until it has authorisation. Illegal stage jumps are blocked at the API — so the board stays honest even on a busy Friday when shortcuts are tempting.
Techs see only their assigned jobs on a tablet — no advisor noise, no CRM clutter, just the work in front of them. Less time navigating the system means more time on the hoist.
My Day badges a job that is waiting on a part so techs and advisors know it is blocked before someone walks to the shelf and finds nothing there. Heuristic overlay — not a new RO status, just earlier visibility.
FAQ
Structured for humans and search (FAQ schema). We update when ship status changes.
A board shows WIP and bottlenecks at a glance — which column is jammed, which bay is free. A list is for search and history. Good shop software offers both. We lead with board stages that match how shop floors actually talk.
No. It is a My Day overlay when a job is waiting on a part. The RO state machine is unchanged — this is visibility, not a new workflow step.