Loading
Loading
Workshop manager · floor control
LiveWIP only improves when stages mean the same thing to advisors, techs, and owners. Domain-enforced transitions stop “just move it to ready” shortcuts that hide missing parts or unapproved work.
Primary persona: Workshop manager / advisor
The problem
Spreadsheets and free-text statuses let jobs leapfrog authorisation and parts readiness — cash and rework both suffer.
Why it matters
Columns for inspection, awaiting auth, waiting parts, in progress, ready mirror shop language — training time drops.
Illegal transitions are blocked by shared domain rules used by API and UI.
Blockers (auth, parts) stay visible so managers coach throughput instead of hunting tickets.
Owner attention widgets feed from the same board state — one source of operational truth.
Proof from the live demo
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.


Stage sequence
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
Action
Open Job Board; every non-terminal RO appears in stage columns.
Why this stage
Managers cannot balance bays from a list buried in email.
Action
Open RO, assign tech intent, note customer promise time and concern.
Why this stage
Clear ownership reduces idle techs and “whose job is this?” dead time.
Action
Move NEW → INSPECTION → ESTIMATE → AWAITING_AUTH / PARTS → IN_PROGRESS → READY…
Why this stage
State machine protects profit rules (e.g. produce after auth/parts readiness).
Action
Park on AWAITING_AUTH or AWAITING_PARTS until portal decision or stock arrives.
Why this stage
False “in progress” destroys utilisation metrics and customer ETAs.
Related search intent