Agency Scope Change And Change Request Tracking Template: Fields, Statuses, and Rules

The most useful agency scope change and change request tracking template is a small operating record. It should answer what is happening, who owns it, what evidence exists, and when the next decision occurs. This structure works in a spreadsheet, database, or focused application.

Recommended record fields

| Field | Why it exists | Update point | |---|---|---| | Client and project | Prevents the record from depending on memory or an inbox search | Capture the request verbatim | | Original deliverable | Prevents the record from depending on memory or an inbox search | Compare it with agreed scope | | Requested change | Prevents the record from depending on memory or an inbox search | Estimate impact and options | | Source and date | Prevents the record from depending on memory or an inbox search | Obtain a client decision | | Impact on hours or fee | Prevents the record from depending on memory or an inbox search | Update delivery and billing records | | Impact on timeline | Prevents the record from depending on memory or an inbox search | Capture the request verbatim | | Tradeoff option | Prevents the record from depending on memory or an inbox search | Compare it with agreed scope | | Decision | Prevents the record from depending on memory or an inbox search | Estimate impact and options | | Approver | Prevents the record from depending on memory or an inbox search | Obtain a client decision |

Suggested statuses

Use workflow statuses that describe reality: Capture The Request Verbatim → Compare It With Agreed Scope → Estimate Impact And Options → Obtain A Client Decision → Update Delivery And Billing Records. Add Waiting only when you also capture a waiting reason and review date. Add Closed—Not Completed when an item legitimately ends without the desired outcome.

Follow-up rules

• When a request alters an approved deliverable or acceptance criterion, assign a next action and review date.
• When a revision exceeds the agreed round or source material changes, assign a next action and review date.
• When the team begins work before a decision is recorded, assign a next action and review date.

Avoid reminders with no stop condition. A rule should say when it starts, who receives it, what counts as a response, and when a person should take over.

Example records

• A client asks for a new landing page during a status call
• Late brand assets force the agency to redo approved layouts
• An account lead offers an extra revision to preserve the relationship

For each example, write the current status, next action, owner, and supporting evidence. This makes the template testable with real work rather than idealized sample data.

Quality-control rules

• 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

Before adding automation, run the template manually for a week. Remove ambiguous fields and confirm that two different users classify the same situation the same way. Consistency matters more than having a long form.

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.