Agency Scope Change And Change Request Tracking: A Practical Workflow

Extra requests are accepted in calls and chat without a clear record of their effect on deliverables, time, fees, or deadlines. For small creative, design, and digital agencies, the useful goal is not to add another dashboard. It is to create a small, visible process that produces this outcome: every meaningful scope change is accepted, traded, deferred, or declined with its delivery impact visible.

Define the finish line first

Write the outcome in operational terms. A teammate should be able to look at one record and tell what happened, who owns the next action, and what is blocking completion. Use these rules as the boundary:

• Change is allowed; invisible change is not
• No extra work starts without a named decision owner
• Tradeoffs are offered alongside fees when useful
• The delivery plan and invoice evidence reflect the same decision

A practical end-to-end workflow

1. Capture the request verbatim

Record Client and project at this point, name the person responsible, and define the evidence that allows the work to move to the next step. The exit condition should be observable: either the team can compare it with agreed scope, or the record remains open with a reason and next action.

2. Compare it with agreed scope

Record Original deliverable at this point, name the person responsible, and define the evidence that allows the work to move to the next step. The exit condition should be observable: either the team can estimate impact and options, or the record remains open with a reason and next action.

3. Estimate impact and options

Record Requested change at this point, name the person responsible, and define the evidence that allows the work to move to the next step. The exit condition should be observable: either the team can obtain a client decision, or the record remains open with a reason and next action.

4. Obtain a client decision

Record Source and date at this point, name the person responsible, and define the evidence that allows the work to move to the next step. The exit condition should be observable: either the team can update delivery and billing records, or the record remains open with a reason and next action.

5. Update delivery and billing records

Record Impact on hours or fee at this point, name the person responsible, and define the evidence that allows the work to move to the next step. The exit condition should be observable: either the team can close the record and review the outcome, or the record remains open with a reason and next action.

Handle exceptions without hiding them

The process needs an explicit waiting state. Do not mark work complete because a reminder was sent or a form was opened. Keep the record open until the real exit condition is met. These events deserve a named exception path:

• a request alters an approved deliverable or acceptance criterion
• a revision exceeds the agreed round or source material changes
• the team begins work before a decision is recorded

For each exception, store the reason, the next review date, and the person who can unblock it. That makes a weekly review useful instead of turning it into a search across email, chat, and spreadsheets.

Start with one live cycle

Run the workflow for one client, location, role, order, or participant before standardizing it. At the end, remove fields nobody used, add evidence that was missing, and keep the status list short. The workflow is ready to scale when another person can operate it without asking the original owner what each row means.

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.