Agency Scope Change And Change Request Tracking Examples: Three Workflow Scenarios

Examples make agency scope change and change request tracking easier to design because they reveal where a neat diagram meets messy work. The scenarios below are not claims about a particular company; they are test cases small creative, design, and digital agencies can run against a template or software trial.

Scenario 1: A client asks for a new landing page during a status call

Create the record before the first follow-up. Capture Client and project, Original deliverable, Requested change, then move it through capture the request verbatim and compare it with agreed scope. If a request alters an approved deliverable or acceptance criterion, do not improvise in a private message; assign the exception, set a review date, and preserve the evidence needed for the next decision. Close with an explicit outcome and reason. ### Scenario 2: Late brand assets force the agency to redo approved layouts

Create the record before the first follow-up. Capture Original deliverable, Requested change, Source and date, then move it through capture the request verbatim and compare it with agreed scope. If a revision exceeds the agreed round or source material changes, do not improvise in a private message; assign the exception, set a review date, and preserve the evidence needed for the next decision. Close with an explicit outcome and reason. ### Scenario 3: An account lead offers an extra revision to preserve the relationship

Create the record before the first follow-up. Capture Requested change, Source and date, Impact on hours or fee, then move it through capture the request verbatim and compare it with agreed scope. If the team begins work before a decision is recorded, do not improvise in a private message; assign the exception, set a review date, and preserve the evidence needed for the next decision. Close with an explicit outcome and reason.

Debrief each scenario

After running a scenario, ask:

• Did the record make change is allowed; invisible change is not?
• Did the record make no extra work starts without a named decision owner?
• Did the record make tradeoffs are offered alongside fees when useful?
• Did the record make the delivery plan and invoice evidence reflect the same decision?

Also check whether a new teammate could identify the owner, next action, and finish condition without opening another system.

Convert scenarios into acceptance tests

Use the normal case, waiting case, and closed-without-completion case in every software demo. Require the vendor—or your own prototype—to show the full workflow rather than isolated feature screens. Export the resulting records and verify that the status history remains understandable.

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.