Agency Scope Change And Change Request Tracking Checklist for Small Creative, Design, And Digital Agencies

A checklist for agency scope change and change request tracking should prevent missing decisions, not merely prove that somebody clicked boxes. The checklist below is designed for small creative, design, and digital agencies and centers on one result: every meaningful scope change is accepted, traded, deferred, or declined with its delivery impact visible.

Before the work starts

• Confirm Client and project
• Confirm Original deliverable
• Confirm Requested change
• Confirm Source and date

Also name the owner and the expected completion condition. If either is unknown, the work is not ready to enter the active queue.

While the work is moving

• Update Capture the request verbatim
• Update Compare it with agreed scope
• Update Estimate impact and options
• Update Obtain a client decision
• Update Update delivery and billing records

Every update should change a decision. Notes such as “followed up” are weak unless they also include the channel, result, next date, and owner.

Before marking it complete

• Verify Impact on hours or fee
• Verify Impact on timeline
• Verify Tradeoff option
• Verify Decision
• Verify Approver

Confirm that the actual outcome—not just an activity—has been recorded. If the process ended early, use a closed reason rather than deleting the record.

Copy-and-paste weekly review

• [ ] Review records where a request alters an approved deliverable or acceptance criterion

• [ ] Review records where a revision exceeds the agreed round or source material changes

• [ ] Review records where the team begins work before a decision is recorded

• [ ] Check for calling a request small before estimating it

• [ ] Check for letting work begin while approval is ambiguous

• [ ] Check for recording price impact but not schedule impact

• [ ] Check for hiding agency-added gold plating inside client scope

Make the checklist measurable

Choose one metric before the next cycle. Good options for this workflow are Unapproved change exposure, Change decision time, Estimate variance by change. A checklist that never changes a metric or prevents a known failure mode is probably administrative overhead.

Assign ownership and escalation

Put one role—not a group—next to every item that can remain open. Define a backup owner and an escalation time for work that affects a customer, client, participant, or delivery promise. During review, separate not started, waiting on someone, and failed validation; those states need different actions. If a checklist item repeatedly waits on the same dependency, redesign the intake or handoff instead of adding more reminder boxes.

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.