15-minute scope leakage pilot
Run one real scope change through approval before your next invoice run.
If the workflow cannot produce a clearer record, a named decision, and a billing-ready export on one live change, it is not solving the leak yet.
One live request
One named decision
One billing export
1. Pick one live change
Use a request that would normally vanish into delivery.
- Choose a recent “can we also…” request from a real client.
- Use something with a clear amount, effort estimate, or commercial impact.
- Avoid synthetic demo data. The point is to test real workflow friction.
2. Run the path
Record it, send it, and capture the decision.
- Create the client and project baseline if they do not exist yet.
- Record the scope change with title, amount, and request date.
- Send one approval link and record the resulting yes or no.
If someone has to explain the context in Slack or email for the workflow to make sense, the process is still leaking.
3. Check the evidence
By the end, billing should not need your memory.
- The scope change should show the request, estimate, and status history.
- The approval record should include a named approver plus timestamp.
- The approved item should move into billing handoff and export cleanly.
Pass / fail signal
If one live change cannot survive the workflow cleanly, the leak is still there.
A successful pilot leaves you with a usable record, a decision trail, and a billing-ready export. A failed pilot tells you exactly where the handoff still breaks.
Record
Approve
Export