Common Agency Scope Change And Change Request Tracking Mistakes and How to Prevent Them

Extra requests are accepted in calls and chat without a clear record of their effect on deliverables, time, fees, or deadlines. The recurring failures are usually process-design problems rather than motivation problems. For small creative, design, and digital agencies, these are the mistakes worth finding before buying or building software.

1. Calling a request small before estimating it

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Original deliverable at the point of work and enforce this guardrail: No extra work starts without a named decision owner When the exception occurs, keep it visible instead of repairing it privately in email.

2. Letting work begin while approval is ambiguous

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Requested change at the point of work and enforce this guardrail: Tradeoffs are offered alongside fees when useful When the exception occurs, keep it visible instead of repairing it privately in email.

3. Recording price impact but not schedule impact

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Source and date at the point of work and enforce this guardrail: The delivery plan and invoice evidence reflect the same decision When the exception occurs, keep it visible instead of repairing it privately in email.

4. Hiding agency-added gold plating inside client scope

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Impact on hours or fee at the point of work and enforce this guardrail: Change is allowed; invisible change is not When the exception occurs, keep it visible instead of repairing it privately in email.

Audit five recent records

Pick five completed or abandoned examples and ask:

• Can we reconstruct client and project without asking the original owner?
• Can we reconstruct original deliverable without asking the original owner?
• Can we reconstruct requested change without asking the original owner?
• Can we reconstruct source and date without asking the original owner?
• Can we reconstruct impact on hours or fee without asking the original owner?

If the answer is no, improve the capture point rather than adding a later reporting step. Reports cannot recover decisions that were never recorded.

Use mistakes as software requirements

Turn every frequent failure into a testable requirement. “Better visibility” is vague; “show every record with no owner or next date” can be tested. “More automation” is vague; “stop reminders after the completion condition is recorded” can be tested.

Next step

Explore the Scope Change Ledger workflow concept and record whether this is painful enough to justify a focused tool.

For the adjacent workflow, see Client Asset Chaser.