Back to all articlesAgency customer operations

Decide When a Client Request Is a Scope Change

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A client asks for one more reporting breakdown. Then a second person needs a separate version. Soon, the agency is reconciling two reports and answering questions from both audiences every week. Each request looked small; together, they changed the service.

Decide whether a request changes scope by comparing it with the agreed service baseline—not by estimating how quickly someone can complete the first instance. A correction restores what was agreed. An included variation uses flexibility already allowed. A substitution replaces agreed work with an explicitly accepted alternative. Additional work expands the output, recurring effort, responsibility, or delivery conditions.

The practical question is: What obligation would the agency accept if it said yes? Answer that before promising a delivery date. The decision table below shows how to make that judgment visible without treating every client conversation as a dispute.

1. Establish the baseline you are comparing against

A deliverable name is rarely enough. “Monthly reporting” might mean sending an agreed summary, interpreting results in a meeting, or maintaining a live dashboard. Those are different responsibilities even when everyone calls them reporting.

Find the most recent explicitly agreed operating baseline. It may be recorded across a service description, delivery plan, meeting note, and accepted clarification. Consolidate the relevant facts into a short working record:

  • Output: What does the client receive, in what format, and for which audience?
  • Volume and cadence: How much work is included, and how often does it recur?
  • Included flexibility: Which revisions, topic changes, or format choices are already allowed?
  • Responsibility: Does the agency prepare, recommend, publish, monitor, respond, or resolve?
  • Inputs and dependencies: What must the client or another supplier provide, and when?
  • Delivery conditions: What turnaround, approval path, and support period have been agreed?

If a dimension is undocumented, mark it unknown. Do not turn an agency assumption into a client obligation, or a client assumption into an agency commitment. Clarify the missing point before using it to classify the request.

A useful baseline statement is specific enough that another delivery lead could reach the same decision. “Support with reports” is not. “Prepare one monthly summary from the supplied export, with one consolidated revision round” is much closer.

2. Classify the obligation, not the apparent size

Use four categories. The distinction matters because each calls for a different response.

Correction

The delivered work does not match an agreed requirement, or contains an agency-introduced error. Fixing it restores the baseline. Do not label it additional work merely because correction takes time.

However, a client changing its preference after approving an accurate deliverable is not automatically a correction. Identify the specific requirement that was missed rather than relying on the word “fix.”

Included variation

The request fits the baseline's existing flexibility and stays within its volume, revision allowance, responsibility, and delivery conditions. A different topic within an agreed content allocation can be an included variation.

Track any allowance it consumes. Included does not mean unlimited, and silently ignoring consumption makes the next decision harder.

Substitution

The client wants a different piece of work instead of something already planned. A substitution is valid only when the removed work is explicit and the replacement fits an accepted capacity and responsibility boundary.

Similar production time alone is not enough. Replacing a static asset with a live event could introduce attendance, moderation, and follow-up duties. That is not a straightforward exchange.

Additional work

The request adds an output, increases frequency or volume, introduces a new audience or dependency, changes turnaround, or transfers responsibility to the agency. It can be additional work even if the first task takes only a few minutes.

A request can contain more than one category. Correcting an inaccurate figure may be a correction; creating a new departmental report around that figure may be additional work. Separate the parts rather than assigning one label to the whole message.

3. Use this filled scope-change decision table

Fictional worked example: An agency delivers a monthly reporting and content service. All requests, quantities, and effort estimates below are hypothetical, not customer results or recommended service limits.

The agreed baseline is one monthly report from a client-supplied export, one review meeting, four static content assets, and one consolidated content revision round. The client supplies approved source information and handles incoming customer messages. The agency does not maintain the client's source data or provide continuous monitoring.

The following plain-text decision table can be copied into a shared delivery record. Each numbered block is one filled row; the same fields repeat so the comparison remains clear.

ROW A
Baseline: One monthly report using the agreed metric definitions.
Requested change: Correct a total calculated with the wrong formula.
Recurring effort: No new service; correct and recheck this report.
Dependencies: Agreed metric definition and original export.
Classification: Correction.
Client decision needed: None to restore the agreed output;
confirm receipt of the corrected version.

ROW B
Baseline: Four static assets; topics chosen before production.
Requested change: Use a product update instead of a planned tips post.
Recurring effort: No increase; remains four assets this month.
Dependencies: Approved product facts before production starts.
Classification: Included variation.
Client decision needed: Confirm topic and supply approved facts.

ROW C
Baseline: Four static assets; two remain unstarted this month.
Requested change: Replace two assets with one short document.
Recurring effort: Hypothetical estimate: three hours either way;
no new recurring obligation.
Dependencies: Existing approved copy and one consolidated review.
Classification: Substitution, subject to explicit acceptance.
Client decision needed: Confirm which two assets are removed
and accept the document's defined length and review boundary.

ROW D
Baseline: One monthly report for one review group.
Requested change: Send a tailored weekly version to sales managers.
Recurring effort: Hypothetical estimate: 45 minutes per issue,
plus a new recurring question-handling responsibility if accepted.
Dependencies: Weekly export, audience list, agreed metric definitions.
Classification: Additional work.
Client decision needed: Keep monthly reporting or authorise a
separately defined weekly service with an agreed question boundary.

ROW E
Baseline: Report from a client-supplied export; client owns data quality.
Requested change: Repair source records whenever totals disagree.
Recurring effort: Unknown; depends on errors and access required.
Dependencies: Source-system access, data owner, correction approval.
Classification: Additional work; not ready for commitment.
Client decision needed: Retain client-side cleanup or agree a
bounded investigation before defining any ongoing responsibility.

ROW F
Baseline: Client handles incoming customer messages.
Requested change: Agency checks messages twice daily and drafts replies.
Recurring effort: Hypothetical estimate: 30 minutes per working day;
volume and escalation handling remain unmeasured.
Dependencies: Authorised access, reply guidance, named escalation owner.
Classification: Additional work.
Client decision needed: Retain current ownership or define coverage,
reply authority, volume boundary, and escalation responsibilities.

Row D is not simply “another report.” It changes frequency and audience, and may create a new support obligation. Row E is more uncertain: an estimate made before examining the data would hide the very risk the decision process should expose.

Row C is deliberately conditional. Until the client accepts the removal and the agency accepts the replacement boundaries, it is a proposed substitution—not permission to deliver both.

4. Assess recurring effort and responsibility separately

For every request, examine the first delivery and the future pattern. A useful working estimate separates setup, effort per occurrence, frequency, coordination, and likely rework. State what remains unknown instead of disguising uncertainty with a precise total.

In a hypothetical example, a report adaptation taking 15 minutes each working day would consume five hours across 20 working days, before review or questions. The first 15 minutes is a poor basis for deciding whether the obligation fits the service.

Responsibility needs its own check because it does not always scale with production time:

  • Does “prepare” now mean “send without further approval”?
  • Does “send” now mean “watch for failures and resolve them”?
  • Does “summarise supplied information” now mean “verify the underlying records”?
  • Does “join a scheduled meeting” now mean “be available whenever stakeholders ask”?

Any of these can change scope without changing the visible deliverable. Record the boundary explicitly: who acts, who approves, who monitors, and who handles exceptions.

Do not reject work just because it introduces a dependency. Instead, identify whether that dependency already exists in the baseline and whether the agency is being asked to own it.

5. Turn the classification into a clear client choice

The agency should propose the classification; the client should not have to decode internal capacity concerns. Explain the difference from the baseline, then ask for the decision needed to proceed.

For the hypothetical weekly-report request, a useful response is:

The current service includes one monthly report for the review group. A weekly version for sales managers adds a recurring output and a separate audience. We can continue the monthly report as agreed, or define the weekly version as additional work. Before committing, we need to confirm the data source, the start date, and who handles follow-up questions. Which direction would you like us to develop?

For a substitution, name the displaced work just as clearly:

We can propose the short document in place of the two unstarted assets identified in the plan. The other two assets remain unchanged. Please confirm that those two planned assets are removed and that the document uses the approved copy with one consolidated review.

Acknowledge the request without implying acceptance. “We are checking the effect on delivery” is different from “We will get that done.” Record the decision, the person authorised to make it, and the resulting delivery boundary before scheduling changed work.

6. Handle ambiguity without freezing delivery

Not every request can be classified immediately. When the baseline is unclear or the work is unbounded, separate clarification from execution. Continue unaffected agreed work where practical, and identify exactly what is paused and why.

A bounded investigation can help when effort is unknown. Define what it will inspect, who must authorise access, what finding it will produce, and when the agency will stop to request another decision. Investigation should not quietly become ongoing maintenance.

There is a trade-off between control and administrative overhead. Requiring a meeting for every included variation slows delivery. Letting every staff member approve recurring obligations creates inconsistent commitments. A practical operating design is:

  • Delivery staff handle clear corrections and included variations within documented boundaries.
  • A named delivery owner reviews substitutions and ambiguous requests.
  • An authorised client contact decides whether to accept a changed service after its boundaries are clear.

These are recommended workflow roles, not product controls. Keep the decision record wherever the team reliably works; the important point is that the reasoning and authorisation remain visible.

7. Recover when extra work has already started

If staff have already accepted a request informally, first establish what happened. Record the work performed, how often it has recurred, what the client was told, and any immediate dependency on its continuation. Avoid blaming either the client or the individual who tried to help.

Then separate past assistance from the future service. An agency may choose to absorb completed effort as a service decision, but that does not resolve what happens next. Agree whether the work stops, replaces something else, or becomes a defined ongoing obligation.

Repeated exceptions deserve particular attention. If a request was described as temporary, record its end condition. Review it when that condition is reached rather than allowing repetition to become an unspoken baseline.

Also check for misclassification. If review shows that the original output failed an agreed requirement, reclassify the work as a correction. A sound process must catch agency errors as well as client additions.

8. Test the process on the next delivery cycle

Start with one active account. Write its baseline, review its open requests, and fill one decision-table row for each unresolved item. Prioritise requests that introduce recurrence, a new audience, monitoring, or ownership of client inputs.

As a hypothetical pilot, review the next ten non-routine requests. Track whether each had a stated baseline, a classification, a recorded client decision where needed, and a check of actual effort after delivery. Also count requests started before classification and substitutions where the original work was not removed.

Use the results to improve the baseline, not merely to count extra-work requests. Repeated uncertainty about the same revision allowance suggests that the allowance needs clarification. Repeated corrections suggest a delivery-quality issue. Repeated additional requests may justify discussing a different service boundary.

Your immediate next action is to take the latest “small” request and complete these fields before promising it: baseline, requested difference, recurring effort, dependencies, classification, and client decision needed. If the team cannot fill a field, that gap is the next question to resolve.

Agency operationsScope managementClient deliveryChange decisions

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications