Skip to content
Workshop Wrench

Authorisation · margin protection

Live

Line-level estimate approval that protects margin and trust

Shops lose money two ways: unapproved work that becomes write-offs, and weak ARO because recommended work was never decided. Line state is the control plane.

Primary persona: Service advisor + customer

The problem

What breaks without this process

Whole-job “OK” signatures hide which lines were declined; variations expand silently; invoicing becomes negotiation.

Why it matters

Rationale — profit, risk, and shop floor truth

  1. 01

    PENDING → APPROVED | DECLINED | DEFERRED is explicit and auditable.

  2. 02

    Only approved lines should become billable invoice content.

  3. 03

    Deferred work is a first-class opportunity, not a lost sticky note.

  4. 04

    Portal tokens remove desktop login friction for customers on-site or at work.

Proof from the live demo

Real UI — not a pitch mockup

Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.

live demo capture
Repair order detail with estimate lines and status
RO detail — estimates, findings, labour, and stage transitions on one job
live demo capture
Customer portal estimate line approval on mobile web
Customer portal — approve or decline lines without a staff login

Stage sequence

Step-by-step use case

Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.

  1. 01

    Build the estimate

    Action

    Add labour and parts lines from menus, DVI conversion, or advisor pricing.

    Why this stage

    Speed to estimate is speed to authorisation — bays wait on decisions.

    Surface: Quotes / ROOutcome: Estimate ready
  2. 02

    Share for decision

    Action

    Generate portal link; dispatch via SMS/email adapters (deep link to token).

    Why this stage

    Customers decide on the phone they already hold — higher response rates.

    Surface: Portal + commsOutcome: Customer notified
  3. 03

    Line decisions land

    Action

    Customer sets approve/decline/defer; board reflects AWAITING_AUTH clearance.

    Why this stage

    Floor starts only what is paid for; advisor coaching targets declined lines.

    Surface: Portal → BoardOutcome: Scope locked
  4. 04

    Handle variations

    Action

    New discovery returns to estimate/auth rather than silent expansion.

    Why this stage

    Trust and legal posture require re-authorisation of material changes.

    Surface: RO statusOutcome: Honest variation

Related search intent

  • SMS estimate approval auto repair
  • estimate approval portal
  • line item approval workshop

Run this flow in Workshop Wrench

Start a trial or open the seeded multi-tenant demo — same processes, real data.