Distinguish a Scope Clarification From a Chargeable Change
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
In a hypothetical reporting project, a buyer asks whether the quoted report can show results by branch. The salesperson hears a clarification. The delivery lead hears another report. Finance hears unpriced work. Each interpretation sounds plausible until someone checks what the proposal actually promises.
The distinction between scope clarification and scope change is whether the request explains an existing commitment or alters it. Effort alone cannot answer that question: difficult work may already be included, while an easy addition may expand the agreed output.
This method separates scope classification from the commercial decision. It helps teams explain what changed and decide what to offer; it does not determine legal entitlement to payment.
1. Establish the issued baseline
Start with the proposal the buyer received, including its version, issue date, and subsequent written revisions. Internal estimates explain how the team built a price, but do not establish that the buyer saw a limitation.
Build a short baseline record covering:
- Deliverables: named outputs and responsibilities.
- Boundaries: quantities, formats, audiences, locations, and service limits.
- Assumptions: required buyer inputs and their expected condition.
- Exclusions: activities or outputs expressly left out.
- Acceptance evidence: how completion will be demonstrated.
If documents conflict, preserve both interpretations. Do not quietly select whichever supports a fee. Likewise, an expectation that never appeared in issued material should not be presented as an explicit boundary.
The critical distinction is between a missing task and a missing commitment. If an issued proposal promises an outcome but the estimator omitted a necessary task, that is a planning or estimating problem. If the proposal never clearly commits to the outcome, inclusion remains uncertain unless other issued evidence establishes it.
2. Use four classifications and an unresolved status
Clarification
The buyer asks what an existing commitment means or how an included outcome will work. The answer does not introduce another deliverable, quantity, service level, or responsibility. Checking the answer can still take effort.
Correction of an omission
The issued baseline already promises the outcome, but necessary work is missing from the estimate or delivery plan. Restoring that work restores the baseline. Record whether the gap concerns estimating or planning, and identify the evidence establishing the commitment.
Ambiguous or absent proposal wording is not automatically this kind of omission. Mark the request unresolved unless another issued document establishes the promised outcome.
Substitution
The buyer replaces an included item with a different one. Record what leaves and what enters. Equal quantities do not prove equal impact: different inputs, discarded preparation, or new acceptance requirements can change the work.
Additional work
The request adds an outcome, quantity, responsibility, or condition beyond the baseline. This classification supports a commercial decision; it does not authorise work or automatically trigger an invoice.
Unresolved is a temporary status when evidence is insufficient, not a fifth category. Give it an owner, a specific missing question, and a review point. Otherwise it becomes a holding label that conceals an unanswered decision.
3. Test scope before assessing delivery impact
Use a separate record for each requested outcome. One buyer message may contain a clarification, an outstanding correction, and a new addition.
- Restate the outcome. Replace vague wording such as “improve reporting” with the requested file, view, audience, or behaviour.
- Identify baseline evidence. Record the proposal version and relevant section, paraphrasing its meaning.
- Describe the difference. What is being explained, restored, removed, or added?
- Assess impact. Consider effort, dependencies, sequencing, rework, and acceptance checks.
- Classify with confidence. Explain the reasoning and what could change it.
- Assign the next decision. Name the owner and the conversation or evidence needed.
Use high confidence for explicit, consistent evidence; medium for a supported interpretation with an important condition; and low when a material question remains unanswered. Confidence describes the evidence, not the reviewer's seniority.
Two challenge questions help expose effort-based reasoning: would this still change the promise if it took almost no work? Could it remain included even if it took substantial work?
4. Worked example: a filled classification worksheet
All details below are hypothetical. This fictional worksheet is a reusable operating artifact, not a customer result. Copy the field structure for your own requests.
Baseline: Proposal P-17, revision B, covers a monthly sales-reporting spreadsheet pack. Section 2 includes a company summary and separate worksheets for three named branches. Section 3 includes a branch lookup using the buyer's supplied list. Section 4 includes one review round with consolidated feedback. Section 5 assumes one source file matching the supplied sample, with branch codes populated; data repair is excluded. Section 6 excludes dashboards and recurring production after handover.
A1: Confirm where branch results appear
- Request: Confirm that each named branch has its own worksheet.
- Evidence and difference: Section 2 explicitly includes those worksheets. No output is added.
- Impact: Explain the pack structure; no new production task identified.
- Classification and confidence: Clarification; high. The question concerns an explicit output.
- Owner and next conversation: Proposal owner confirms inclusion and records the answer before the reporting walkthrough.
A2: Confirm reconciliation behaviour
- Request: Confirm whether branch totals reconcile to the company summary.
- Evidence and difference: Section 2 includes both outputs but does not explain treatment of unassigned transactions or company-level adjustments.
- Impact: Depends on the intended rules; do not estimate or promise a reconciliation process yet.
- Status and confidence: Unresolved; low confidence in any final classification because the required behaviour is undefined.
- Owner and missing question: Delivery lead asks whether the summary should equal only the named branches or also include other records, and how differences should appear.
- Review point and next conversation: Resolve at the reporting walkthrough before confirming report logic. If no issued evidence settles the question, agree the intended behaviour and commercial treatment explicitly.
Splitting A1 from A2 prevents a clear inclusion answer from accidentally promising undefined behaviour. The buyer receives one confirmed answer and one precise question, rather than a blanket inclusion or rejection.
B: Restore the promised lookup
- Request: Include the branch lookup missing from the delivery checklist.
- Evidence and difference: Section 3 explicitly includes it; the internal plan omitted the task.
- Impact: Add preparation and checking tasks; assess any handover-date consequence.
- Classification and confidence: Correction of an omission; high. An issued commitment establishes inclusion.
- Owner and next conversation: Delivery lead corrects the plan before scheduling approval. Proposal owner confirms inclusion and explains any timing issue separately.
C: Exchange one branch worksheet
- Request: Replace East with Central before report construction starts.
- Evidence and difference: Section 2 names East; remove East and introduce Central.
- Impact: Check Central's source fields and update mapping and acceptance checks. No completed worksheet is discarded in this example.
- Classification and confidence: Substitution; high for classification, with delivery impact pending input inspection.
- Owner and next conversation: Delivery reviewer checks Central's sample before the commercial owner confirms price and timing. Record East's removal explicitly.
D: Add an interactive dashboard
- Request: Supply a dashboard alongside the spreadsheet.
- Evidence and difference: Section 6 excludes dashboards. This introduces another output.
- Impact: Define views, access expectations, refresh arrangements, and acceptance criteria before estimating.
- Classification and confidence: Additional work; high because the exclusion is explicit.
- Owner and next conversation: Commercial owner asks whether the buyer wants an addition or a replacement option. Obtain approval for a defined option before starting it.
E: Repair missing branch codes
- Request: Infer missing codes from transaction descriptions.
- Evidence and difference: Section 5 assumes populated codes and excludes data repair.
- Impact: Define repair rules, exceptions, and buyer confirmation of uncertain mappings.
- Classification and confidence: Additional work; high under this baseline.
- Owner and next conversation: Proposal owner offers a corrected buyer-supplied file or separately defined repair work. Delivery lead explains each path's scheduling dependencies before processing begins.
F: Check an outstanding correction
- Request: Review the revised pack because previously submitted feedback remains unaddressed.
- Evidence and difference: Section 4 includes a review round. The feedback record shows this correction was raised within it.
- Impact: Verify the outstanding item and demonstrate its correction.
- Classification and confidence: Correction of an omission; medium until the delivery reviewer confirms the item was an agreed correction rather than a new preference.
- Owner and next conversation: Delivery reviewer checks the feedback record before responding. Confirm the correction as included if supported; classify any new preferences separately.
5. Turn the classification into a commercial choice
The response should state the requested outcome, its treatment, any delivery consequence, and the decision needed. Avoid sending a worksheet without a clear recommendation.
For a substitution, show both sides of the exchange. For additional work, offer a defined choice: add it, replace something, defer it, or retain the existing scope. An unresolved request needs a question and review point, not a premature price.
A commercial owner may absorb an addition to preserve momentum. Record that as a deliberate concession, including its boundaries, rather than relabelling it as originally included. Otherwise the next reviewer may mistake the concession for baseline evidence.
Similarly, a price-neutral substitution still needs a record of what changed. “No price change” does not mean “no scope change.” Keep pricing approval and permission to begin work explicit.
6. Handle ambiguity and earlier answers without erasing them
When reviewers disagree, have each identify the evidence and the exact difference in outcome. If neither can support a classification, gather evidence rather than escalating the strength of the pricing argument.
If proposal wording is ambiguous, document the competing interpretations and ask the buyer about the intended outcome. Acknowledge uncertainty instead of describing an unstated boundary as explicit.
If a salesperson already confirmed inclusion, preserve that communication. The commercial owner should review what was said, the authority behind it, and any work already started before presenting a revised position. A later worksheet must not silently erase an earlier assurance.
If work began without a decision, distinguish completed activity from the remaining request. The delivery lead identifies what can safely pause; the commercial owner handles the outstanding choice. Continuing quietly while expecting a later invoice to resolve uncertainty compounds the problem.
7. Assign ownership and test the method
Give the proposal owner responsibility for maintaining the baseline, the delivery reviewer responsibility for impact assessment, and the commercial owner responsibility for concessions or revised offers. One person may hold multiple roles, but each decision should have a named owner.
For a hypothetical trial of ten requests, have the proposal owner and delivery reviewer classify each independently before comparing answers. Use disagreement to identify unclear evidence, not to reward the person who labels more work chargeable.
Track observable measures: records with baseline evidence, classifications changed after review, unresolved items still open at their review point, and commercial responses issued before work starts. Also note whether buyer messages were split into distinct outcomes when necessary.
Review recurring uncertainty by proposal section. Repeated questions about inputs may call for clearer assumptions; repeated substitution disputes may call for named outputs and acceptance checks. Improve the next issued proposal rather than retroactively tightening the current one.
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