When a Small Customer Request Becomes Ongoing Scope
Use a scope-impact note to distinguish a one-time favor from recurring work, with clear options to clarify, include or separately agree the change.
10/24/20263 min read
A supplier creates an extra report once to help a customer through a difficult week. The next month, the customer reasonably expects the report again. By the third request, one team calls it standard service while another calls it unpaid scope. The problem is not necessarily bad intent. The original favor had no recorded boundary.
A scope-impact note makes the emerging commitment visible without blaming the customer for asking. It records the request, the work required, the current agreement and the choices available. It should help both parties decide what happens next, not manufacture a surprise invoice for work already performed.
Describe the work before debating the label
Avoid starting with “out of scope.” First specify what the customer needs and how it differs from the current delivery pattern. Frequency, data sources, review responsibilities, turnaround and maintenance can change the impact even when the output looks almost identical.
Keep the original request and later modifications traceable. W3C's PROV overview explains provenance through the entities, activities and people involved in producing information. The practical lesson here is to preserve where the scope description came from. The worksheet below is an editorial method, not a W3C contract standard.
Locate the actual agreement or approved change record. If it is ambiguous, say so. Do not infer the customer's legal obligations from a task tracker, and do not present your internal cost estimate as proof that additional payment is owed.
Worked scope-impact note
In this fictional example, a service includes a monthly summary of approved lead-research work. A customer asks for a weekly breakdown by business unit after receiving one exceptional breakdown during an internal review.
Existing documented delivery: one monthly aggregate summary; the cited agreement does not explicitly address business-unit reporting.
New requested pattern: weekly business-unit breakdown, with corrected mappings when the customer's organizational structure changes.
Work introduced: maintain unit definitions, resolve unmapped records, run the additional report and obtain a review before distribution.
Previous exception: one breakdown supplied for a particular review; no recurring schedule was confirmed in the accompanying message.
Uncertainty: customer and supplier may have understood that exception differently. Confirm rather than assign fault.
Current service protection: continue the agreed monthly summary while the additional reporting request is resolved, unless the parties agree otherwise.
Decision owner: supplier delivery lead discusses feasibility; the customer's authorized commercial contact considers any proposed change.
The note does not claim that the extra report takes a particular number of hours unless someone has actually assessed the work. “Effort not yet estimated” is more useful than an invented figure that later becomes an anchor in negotiation.
Offer three honest routes
Clarify: the request may already be covered by the agreement. Have the appropriate owner resolve that interpretation, using legal advice where needed. A salesperson should not settle a contractual dispute by declaring what the contract must mean.
Include: the supplier may choose to absorb a bounded change. State exactly what is included, its frequency and the review point. “We can include this week's breakdown” is different from “We now provide weekly breakdowns.” Make the distinction explicit without making the customer parse hidden qualifications.
Separately agree: describe a proposed additional service with its deliverables, dependencies, pricing process and approval route. Do not begin recurring chargeable work merely because the customer said the idea sounded useful. Confirm the actual authorization through the normal commercial process.
Close the ambiguity, not the relationship
After the decision, update the delivery instructions and tell the people who receive requests. A perfect change note is ineffective if the service desk continues accepting the recurring work as routine. Preserve the history rather than rewriting the original request to make one side look unreasonable.
Contract interpretation, payment rights and enforceability depend on the agreement and jurisdiction; this is an operational guide, not legal advice. Where that uncertainty matters, pause the disputed extension and involve the authorized reviewers. The immediate goal is a shared understanding of future work, not a retrospective argument disguised as project administration.
Sources and scope
The worksheet and fictional example are original editorial proposals. References support only the stated research, data or product context, not endorsement or proof of results. Verify any product capability against the actual subscription.