A client asks for one more tax form, a cleanup project expands, or a monthly engagement quietly picks up another recurring deliverable. If the extra work stays in email, your team can end up doing it before anyone agrees on the terms or how it will be billed.
A scope change request is a clear record of what the client wants added or changed. Why it is needed, when it applies, and what happens to the agreement, fee, timeline, and invoice. It gives both sides a practical checkpoint before approved work begins.
For accounting, tax, and professional-services firms, the goal is not to make every client request feel like a contract negotiation. It is to turn a reasonable request into a clean handoff: clarify the work, capture approval, update the terms, and make sure collections follow the agreement. Start with what this request actually means and why the distinction matters.
What is a scope change request?
A scope change request is a written record of work a client wants that is not clearly included in the current engagement. In an accounting or tax firm, that might be a request to prepare an additional return. Clean up historical books, respond to a taxing authority, or add recurring advisory support. In another professional-services firm, it could be a new deliverable, expanded research, or a faster deadline.
The important distinction is simple: a request is not approval. A client asking, "Can you also handle this?" starts a conversation. It does not automatically change the agreement, authorize the work, or establish how the additional service will be billed. Treating a casual request as approved work is how a helpful favor quietly becomes an unplanned project.
A request describes the change, not just the problem
A useful scope change request identifies the exact work being considered. It should connect the request to the existing engagement, state what will be added, and make exclusions visible. For example, "Prepare the 2025 federal and state returns" is more useful than "Take care of the tax issue." Include the relevant entity. Tax year, forms or deliverables, client responsibilities, expected timing, and any assumptions about the records the client will provide.
That level of detail gives the firm something practical to evaluate. The team can determine whether the request fits existing capacity, whether it affects a deadline, and whether it requires a different fee method or a separate agreement. Sample CPA engagement letters commonly limit services to specified returns or tasks and require other requested work to be documented in a separate written agreement. A sample engagement letter illustrates how specific those boundaries can be.
Approval turns the request into authorized work
Once the firm and client agree on the change, record the decision in writing before work begins. The approval should identify the revised deliverable, fee or billing method, effective date, responsibilities, and any updated deadline. For material changes, a signed amendment may be appropriate. One business tax engagement letter states that material additions become effective only through a written amendment signed by all parties. And that services do not begin until the executed agreement is received. That approval model keeps the request separate from the authorization.
This is not about making every client interaction feel like a legal negotiation. It is about giving both sides the same reference point. Clear documentation protects margin because the team knows what work is included and how it will be handled. It also protects trust because the client can see what changed, when it changed, and what to expect next.
What should a scope change request include?
A useful scope change request gives everyone the same answer to a simple question: what is changing, and what happens next? For an accounting, tax, or professional-services firm, it should be specific enough to guide delivery, approval, and billing without reading like a contract written by a robot.
Use the template below when a client asks for extra cleanup, an additional tax filing. A new reporting package, or a recurring service that was not part of the original engagement.
Scope change request
- Client and current agreement: Identify the client, entity, engagement name, and the agreement or proposal this request changes. Include the relevant tax year, service period, or project phase. Sample CPA engagement letters often define the exact year and forms covered, which prevents a request for one return from quietly becoming a request for several.
- Requested work: Describe the new service in plain language. Name the deliverable, affected accounts or entities, forms, reports, cleanup period, or advisory topic. "Additional tax work" is too vague to approve. "prepare the state return for the new entity" gives the team something usable.
- Reason for the change: Record what triggered the request. It might be a new entity, incomplete records, an acquisition, a change in filing position, or a client priority. This context helps the firm assess the work instead of treating every request as an emergency.
- Deliverables and exclusions: State what the client will receive and what remains outside the request. For example, a cleanup may include reconciliations for a defined period but exclude historical years, audit procedures, or tax representation. Clear exclusions are not unfriendly. They are how both sides avoid filling gaps with assumptions.
- Assumptions and client responsibilities: List the records, access, decisions, approvals, and information the client must provide. Include any required format or cutoff date. Engagement terms commonly place responsibility on the client to furnish complete information, so make that responsibility visible here.
- Timing: Add the proposed start date, client input deadline, milestone dates, and expected completion date. If the schedule depends on records arriving by a certain date, say so directly. A deadline without dependencies is just optimism wearing a calendar.
- Fee method: Explain how the added work will be billed, such as a fixed fee, hourly work, recurring line item, or another approved method. You do not need to insert a price before the scope is understood, but you do need to make the billing method clear.
- Effective date: Specify when the approved change begins and whether it affects work already underway, future work, or both. This avoids billing a new service from the wrong period.
- Approval owner: Name the person at the firm who can approve the change and the client representative who must accept it. Material changes should be documented in a written amendment signed by all parties. And some engagement terms state that work will not begin until the executed agreement is received. Review a sample engagement provision on written amendments.
- Next action: End with one concrete action, such as "Client approves the amendment by Friday" or "Firm sends the revised proposal for signature." Once approved. Update the work queue, agreement record, and billing setup so the request does not live only in an email thread.
After approval, keep the request with the agreement and supporting records. Payment controls generally work best when the amount, allowable service, and payment are supported by documentation that was approved and retained. That record gives the delivery team a reliable brief and gives the client a clear reference if a question comes up later. For firms connecting engagement terms to billing, the goal is simple: the approved change should be visible in the work. The invoice, and the payment workflow, not just remembered by the person who received the original request.
How do you get a scope change approved without friction?
Approval gets easier when the client can quickly see what is changing, why it matters, and what happens next. Use this five-step workflow to turn an unexpected request into a clear decision instead of a long email thread. The aim is not to add ceremony. It is to make the commercial decision easy to understand before the team commits time.
- Pause and clarify the request. Before promising a deadline, write down the exact additional work. Is the client asking for another tax year, extra forms, cleanup outside the recurring engagement, or a new advisory deliverable? Note what is included, what remains excluded, the reason for the request, and any information the client must provide. This gives the firm and client one version of the request to review.
- Assess the impact. Review the effect on timing, team capacity, deliverables, client responsibilities, and billing. You do not need a legal memo. You do need enough information to explain whether the change affects the fee method, payment terms, effective date, or existing deadlines. If the request depends on missing records or a revised client deadline, say so plainly.
- Present practical options. Give the client a small number of workable paths, such as adding the work now, moving it to a later phase, or keeping the original engagement unchanged. For each option, show the deliverable, timing, assumptions, and commercial effect. Clear choices reduce back-and-forth and make the conversation feel practical rather than confrontational.
- Capture written approval. For a material change, use written updated terms that identify the revised deliverable, fee or billing method, effective date, responsibilities, and any updated deadline. A sample business tax engagement letter states that material changes become effective through a written amendment signed by all parties. And that services do not begin until the executed agreement is received. Use the approval method required by your own engagement terms and applicable professional guidance.
- Update the work queue. Once approval is complete, update the client record, task owner, deliverables, due dates, assumptions, and billing instructions. Make the approved version visible to everyone doing the work. A change that lives only in an email is easy to miss, especially during tax season. Connecting the agreement to the next operational step helps your team work from the same source of truth.
The best approval process is clear enough for the client to answer quickly and complete enough for the firm to act confidently. When the request, approval, and billing instruction travel together, the team can deliver the new work without guessing what was promised.
How should an approved change flow into billing?
Approval is not the finish line for a scope change request. It is the point where the new work needs to become operational. If the signed amendment stays in an email thread while the billing record remains unchanged. Your team still has to remember what changed, when it starts, and how to charge for it. That is how approved work quietly becomes unbilled work.
A cleaner handoff treats the amended agreement as the source of truth. First, record the approved deliverable, effective date, billing method, payment terms, and any client responsibilities. Then update the engagement or agreement itself, not just a task note. A change log gives your team and the client a shared record of what was accepted. For a deeper look at this model, see how to connect engagement terms to billing.
| Handoff stage | Disconnected process | Connected approved-change process |
|---|---|---|
| Agreement | Approval sits in an email, document, or chat thread. | The amendment records the updated work, terms, and effective date. |
| Billing setup | Someone manually remembers to change a spreadsheet or invoice template. | The billing record reflects the amended agreement and its schedule. |
| Invoice | The invoice may omit the added work or carry outdated details. | The invoice includes the agreed description, date, amount, and payment terms. |
| Payment and reconciliation | Staff track payment separately and match it by hand. | Payment follows the accepted terms and is connected to the accounting record. |
Move from approval to an accurate billing record
Once all parties approve the change, update the billing record before the additional work begins, where the engagement terms require that sequence. The record should make clear what is being billed, whether it is recurring or one-time, when it starts, and which agreement supports it. Payment controls generally work best when charges match the agreement's allowable services and terms, and when approval documentation is retained for the record.
Next, generate the invoice from the updated record. At minimum, the client-facing invoice should identify its unique number, issue date, due date, amount, and description. Those details give the client enough context to recognize the change and give your team a reliable reference if a question comes up. Avoid burying the added service in a vague line item.
Let payment and reconciliation follow
After the amended agreement is live, payment should follow the terms the client accepted. Reconciliation then closes the loop by matching the payment to the right client, invoice, and accounting record. Anchor connects agreements, invoicing, payments, and reconciliation so the team does not have to recreate the same information at every stage. Its invoices can be generated from agreements and scheduled recurring or one-time billing, while payment details are collected when the client accepts the proposal.
This is the practical difference between a signed change and a completed billing workflow. For the broader accountant proposal-to-payment workflow, the same principle applies: carry approved terms forward instead of retyping them. You can also review how automated billing works across agreement, invoice, payment, and reconciliation stages.
Examples for accounting and tax firms
The best way to test a scope change request is to follow it through a real client moment. The client asks for something different, the firm records the change, everyone approves the new terms. And the billing record reflects the work without anyone having to reconstruct the decision later.
Tax return expansion
A business tax client asks your firm to prepare an additional state filing alongside the return already covered by the engagement. The request record should identify the client, tax year, specific filing, reason for the addition, information required, target deadline, fee method, effective date, and person responsible for approval. That level of detail matters because sample engagement letters often define the tax year and exact forms covered, while treating other requested services as separate written work. See a sample engagement letter defining specific tax deliverables.
The approval moment is the client's written acceptance of the added filing and its terms, ideally before preparation begins. Once approved, add the agreed one-time service to the billing record with its description and payment terms. The original return remains easy to identify, and the additional filing does not disappear inside a vague catch-all line.
Cleanup project
A bookkeeping client discovers several months of unreconciled transactions and asks your team to clean them up before a reporting deadline. Capture the affected period, accounts involved, expected deliverable, client-provided information, timing, assumptions, fee method, and approval owner. If the work depends on records the client has not supplied, note that dependency rather than treating the cleanup as already underway.
Approval happens when the client accepts the documented cleanup scope and the firm confirms the work can begin. A sample business tax engagement letter similarly says the firm will advise the client in writing before necessary accounting or bookkeeping work is performed. Review an example of written notice for additional accounting work. The invoice effect may be a separate project line or a documented adjustment to the engagement. It should identify the cleanup work rather than silently blending it into recurring services.
Recurring advisory add-on
A tax client wants a monthly advisory meeting added to an annual compliance engagement. Record the meeting cadence, intended outcomes, start date, participants, client responsibilities, and whether the service is recurring or limited to a defined period. Approval occurs when the client accepts the amended recurring terms in writing. Material additions should be reflected in a written amendment signed by the parties before the new service starts, as described in this sample business engagement letter.
The invoice effect is a new recurring line tied to the approved effective date, with the agreed description and payment terms. Anchor can generate invoices from agreements and scheduled recurring or one-time billing, so the request-to-billing handoff can remain connected instead of relying on a spreadsheet reminder. The client sees what changed, the team knows what to deliver, and the invoice reflects the decision that was approved.
How Anchor keeps approved changes from getting lost
An approved change should not end as a note in an email thread that nobody remembers to revisit. It should update the agreement, the billing plan, and the record of what the client accepted. That connection matters when a one-time request becomes recurring work, when an engagement expands, or when a new service needs to be billed alongside the original scope.
Anchor makes the agreement the working source of truth. Once the change is approved, the updated terms can stay connected to the invoices they produce. That gives your team a clearer line from the agreed work to scheduled recurring or one-time invoices. Rather than asking someone to re-enter the same information in another system. It also gives the client a more consistent experience because the billing reflects the terms they accepted.
Payment setup is part of that handoff, too. When a client accepts a proposal, Anchor collects their payment details so the payment method is connected before billing begins. When the amended terms call for a new charge or a different schedule, the billing workflow has the information it needs to follow those terms. Your team does not have to reopen the conversation every time an invoice is due.
This is autonomous billing and collections, not a reminder campaign. Anchor does not send payment reminders, and it does not require the client to take action on reminders. Instead, clients are charged according to the agreed terms. That distinction keeps the process focused on clear authorization and predictable execution. While your team spends less time checking whether a scope change made it from approval to invoice.
The final piece is reconciliation. Payments and their related billing records remain connected through the revenue workflow, helping your team match what was charged and collected to the agreement that created it. For a broader look at reducing manual receivables work, read about automating accounting firm receivables. You can also explore these billing and collections practices for building a smoother process from agreement through payment.
Frequently Asked Questions
What does a scope change mean?
A scope change means the requested work no longer fits the services, deliverables, timing, or responsibilities in the current agreement. Treat the request as proposed work until the client approves the updated terms in writing.
What is a formal scope change request?
A formal scope change request is a written record that turns an informal ask into something the firm can assess and the client can approve. It describes the requested work, its impact on timing and fees, and the approval needed before work begins.
What should a scope change request include?
Include the client, current agreement, requested deliverable, reason, deadline, assumptions, exclusions, fee method, effective date, approval owner, client responsibilities, and invoice effect.
What are some examples of scope changes?
Examples include adding a state tax return, expanding a cleanup project, preparing an amended filing, or adding recurring advisory work to a monthly engagement. In each case, document the new deliverable, timing, responsibilities, fee approach, and invoice effect.
Ready to connect approved changes to billing?
A clear scope change request is easier to manage when the approved work, updated agreement, invoice, and collection process stay connected. Anchor helps your firm move from client approval to autonomous billing and collections without adding another manual handoff. Sign up for Anchor to connect approved engagement changes with billing and collections.