Approval Flow

Client Approval for Extra Work

The business problem is not just documentation. It is getting a clear yes before scope expands. This page focuses on the approval layer that keeps small contractors from eating surprise work.

Preview client approval Open the full workflow

Field capture

Log the change while the crew is standing in front of the issue.

Client clarity

Show the scope delta and price impact in one simple approval view.

Billing backup

Hand the office an invoice-ready summary instead of scattered proof.

Why this matters

Clients see the exact change, the price delta, and the reason it matters before they approve.

Field teams stop relying on verbal go-aheads that disappear when the invoice lands.

The office gets a timestamped decision and client note alongside the change record.

What teams actually need

Simple enough to sign from a phone

Detailed enough to avoid billing ambiguity

Connected directly to the final documentation packet

Core Positioning

Purpose-built for scope changes, not everything else.

The PRD is explicit about the wedge: this should not drift into generic CRM, generic quoting, or generic invoicing. The product earns attention by being the cleanest route from field surprise to approved documentation.

Mobile web speed

Fewer clicks and clearer typography than broad service software.

Client-facing clarity

One summary view that reduces confusion and billing pushback.

Back-office readiness

Exportable, printable documentation instead of forensic reconstruction.

Trade-specific fit

Designed around the exact workflow small plumbing and AV shops described.