SOP Template: Change Management for Agencies & Consultancies
Free change management SOP template for agencies. Step-by-step scope change requests, client approvals, timeline adjustments, and contract amendments.
Purpose
Define how scope changes are requested, evaluated, approved, and implemented so the agency protects its margins while keeping clients informed. This SOP covers scope change identification, timeline impact assessment, client approval workflow, contract amendment, and internal team communication.
Scope
Covers any change to project scope, timeline, budget, or deliverables after the initial SOW has been signed. Does not cover internal process changes, tool migrations, or organizational restructuring.
Prerequisites
- Signed statement of work (SOW) with clearly defined scope, deliverables, and timeline
- Change request form template accessible in Google Drive
- Agency pricing guide with hourly rates and common add-on costs
- Client approval authority documented (who can sign off on changes and up to what dollar amount)
Roles & Responsibilities
Account Manager
- Identify scope changes during client calls and document them immediately in Asana
- Present the change request to the client with cost and timeline impact
- Secure written client approval before any work begins on the changed scope
Project Manager
- Assess the timeline and resource impact of the requested change within 24 hours
- Update the Asana project plan to reflect approved changes
- Communicate adjusted deadlines to all affected team members
Agency Owner / Director
- Approve or reject change requests that exceed $5,000 or extend timelines by more than 2 weeks
- Review the monthly change request report for patterns that indicate SOW scoping problems
- Authorize contract amendments for approved changes
Procedure
When a client requests something outside the original SOW — a new deliverable, additional revisions beyond the agreed limit, a shifted timeline, or a change in target audience — the AM documents it immediately. Do not agree to the change on the call.
- aOpen the change request template in Google Drive > Templates > Change Management
- bFill in: client name, date, description of the requested change, who requested it, and which SOW clause it affects
- cLog the request as a task in the client's Asana project under the 'Change Requests' section
- dTag the project manager for impact assessment
Completion Checklist
Key Performance Indicators
Change request documentation rate
100% of scope changes documented before work begins
Client approval turnaround time
Under 3 business days from request to signed approval
Change request profitability
Actual hours within 10% of estimated hours
Undocumented scope changes per month
Zero — every change goes through the formal process
SOW amendment completion rate
100% of approved changes over $1,000 have signed amendments
Why This Matters for Agencies & Consultancies
Undocumented scope changes are the single biggest threat to agency profitability. When an AM says 'sure, we can add that' on a client call without logging the change, the agency absorbs hours that were never budgeted. Over a quarter, these absorbed hours can turn a profitable account into a loss-making one. A formal change management process protects margins without damaging client relationships — most clients respect agencies that have clear processes for handling changes.
Common Mistakes
- ×AMs agreeing to scope changes on client calls without checking the timeline impact first
- ×Treating small changes as 'not worth documenting,' which compounds into significant untracked work over months
- ×Skipping the SOW amendment step, leaving the agency with no legal basis to invoice for additional work
- ×Not tracking actual hours against change request estimates, making it impossible to improve scoping accuracy
- ×Presenting change requests apologetically instead of professionally, which trains clients to push back on legitimate scope protections
Agencies & Consultancies-Specific Notes
Agency change management differs from internal corporate change management because every change directly affects a client relationship and a revenue line. The process must be fast (clients will not wait a week for an answer), transparent (clients should understand the cost/timeline trade-off), and documented (the agency needs a paper trail for billing disputes). Agencies using Asana or Monday.com can automate much of the tracking by creating a dedicated 'Change Requests' section in every client project board.
Frequently Asked Questions
Learn More About Change Management
For a deeper look at building onboarding documentation, see our complete guide.