Bottom line
An authorized agency owner prices and reviews a material change against the current accepted scope.
Best for
Agencies with governed agreements, projects, approvals, access, billing, campaign-readiness, and vendor records.
Use when
Only after the project, service, account, and exception records are current and match.
Watch for
Unversioned deliverables, ambiguous authority, unsupported performance claims, or informal credential sharing.
How to Use This Email
When to use this
An authorized agency owner prices and reviews a material change against the current accepted scope.
What’s on their mind
The client may believe the request was included or may not see how it changes fees, timing, capacity, and dependencies.
What this email should do
A reviewed change to an agency engagement is ready for client decision.
Best sender
Finance owner
Read the Finished Email
Review the message as a recipient would see it. The names and business details are fictional.
Subject
Please review change REF-1042 for REF-1042Hi Jordan,
You asked us to the current details. We outlined that request as change REF-1042 for REF-1042.
Here is what would change:
- Current scope: the current details
- Proposed change: the current details
- Fee or credit: $240
- Schedule change: 2:00–4:00 p.m.
- What each team needs to provide: the current details
- Assumptions and exclusions: the current details
Review version the current details and choose an option: https://example.com/next-step
You can approve it, request a revision, defer it, or decline it. Until then, we'll follow the current details. An informal reply does not approve the change when the agreement requires signed approval.
Questions about the scope or price can go to Alex Morgan at (555) 014-0182.
Alex Morgan
the current details
Template to copy
Subject
Please review change [Change number] for [Project reference]Hi [First name],
You asked us to [Request or condition]. We outlined that request as change [Change number] for [Project reference].
Here is what would change:
- Current scope: [Baseline scope]
- Proposed change: [Changed scope]
- Fee or credit: [Price effect]
- Schedule change: [Timeline effect]
- What each team needs to provide: [Dependency effect]
- Assumptions and exclusions: [Assumptions]
Review version [Change version] and choose an option: [Decision link]
You can approve it, request a revision, defer it, or decline it. Until then, we'll follow [Interim work rule]. An informal reply does not approve the change when the agreement requires signed approval.
Questions about the scope or price can go to [Project owner] at [Phone number].
[Project owner]
[Agency name]
Subject Line Variations
- Scope decision for [Project reference] change [Change number]
References the actual operating record or decision.
- Agency Scope Change Approval: [Reference number]
Direct operational alternative.
- Update from [Company name] about [Reference number]
Use with a recognized business and valid reference.
Best for
- Agencies with governed agreements, projects, approvals, access, billing, campaign-readiness, and vendor records.
- Client operational communication with explicit owners, branches, evidence, and stop conditions.
- Teams able to separate agency, client, platform, vendor, media-spend, legal, and financial responsibilities.
Don’t send this if
- Unversioned deliverables, ambiguous authority, unsupported performance claims, or informal credential sharing.
- Records with unresolved agreement, billing, access, rights, data, budget, platform, or decision conflicts.
- Any workflow that cannot stop when a client replies, disputes, changes scope, or enters human handling.
When to Send It
Trigger
An authorized agency owner prices and reviews a material change against the current accepted scope.
Timing
Only after the project, service, account, and exception records are current and match.
Frequency
Once for each valid event or confirmed update; reminders must retain the same verified obligation or decision.
Timing note
Use only a real operational deadline, safety escalation, weather window, or live allocation window.
Make This Email Yours
- Use the current agreement, project, account, platform, and decision-log facts.
- Insert claims, rights, data, access, budget, results, and platform language only when supported for the exact workstream.
- Pause automation and assign replies, disputes, access concerns, security events, and delivery exceptions to the declared owner.
Before You Use This Email
Why This Approach Works
Platform Setup Steps
Trigger
An authorized agency owner prices and reviews a material change against the current accepted scope.
Segment
Authorized client decision-makers with a reviewed material scope change.
Delay
Send after the record is reconciled and before the next dependent operational action.
Reply owner: Agency project or account owner responsible for baseline, pricing, capacity, dependencies, revisions, and client authority.
- Verify client authority, agreement and version, workstream owner, dependencies, access or data boundary, and the applicable commercial and risk state.
- Send the minimum necessary evidence and one clear decision or completion path.
- Record the decision, stop conflicting automation, and update project, access, billing, vendor, and launch records.
Stop conditions
- Approval, revision, deferral, or decline.
- A superseding change version.
- Agreement cancellation, formal dispute, or active owner handling.
Mistakes To Avoid
- Treating discussion, dashboard data, email replies, payment, or platform status as universal client approval
Different versions, scopes, budgets, rights, claims, and launch decisions require different evidence.
Use instead: Bind every decision to its named record, authority, scope, version, and decision path.
- Collecting credentials or moving client data through ordinary email
It weakens access control, auditability, revocation, privacy, and incident response.
Use instead: Use named identities, native delegated access, secure workspaces, minimum data, and an access register.
Sequence Placement
Use inside the governed client-delivery lifecycle at the verified operational event; suppress when the record is stale, superseded, resolved, disputed, insecure, or under human control.
Related Email Platform Guidance
teams running behavior-based nurture with branching, scoring, and segmentation
Not best for: teams whose requirements stop at newsletters and a short welcome series
View ActiveCampaignPaid linkagencies standardizing lead-response systems across multiple accounts
Not best for: teams expecting a native field-service or legal practice-management system
View GoHighLevelPaid linkB2B organizations aligning marketing, sales, and service around shared CRM data
Not best for: small teams needing only broadcasts and a simple welcome sequence
View HubSpotsmall businesses connecting leads, pipeline activity, appointments, and follow-up
Not best for: organizations needing native field-service, legal, or ecommerce operations
View KeapPaid link
Disclosure
Some platform links on this page are paid links. If you choose a platform through one of them, EmailCampaigns.io may earn a commission. That does not change our recommendations. We include best for and not best for notes so you can decide based on fit, not payout.