Back to all articlesQuotes and proposals

Price a Scope Change Without Hiding Its Timing Impact

Alactic Editorial10 min read

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

A buyer asks for an additional approval step. Your revised quote adds a charge but leaves the original delivery date untouched. The buyer reasonably reads that as an offer to deliver the expanded scope on the old timetable—even if your team needs new inputs, a different build sequence, and another review slot.

Assess a scope change as a replacement offer, not just an extra invoice line. Show the work added and removed, the pricing basis, the timing effect, the buyer’s responsibilities, and any existing commitments that would be displaced. Then seek confirmation of that whole package before authorising changed work.

The worksheet below connects those decisions. Its purpose is not detailed project scheduling. It is to give the buyer enough information to choose between a changed scope, a changed date, or a smaller alternative without discovering the trade-off after approval.

1. Establish the baseline before pricing the difference

A change has no reliable price or timing impact until you identify what it changes. Start with the currently accepted offer and the actual work position, not an earlier sales conversation or someone’s memory of the brief.

Record the accepted deliverable, exclusions, price, delivery target, buyer inputs, and review assumptions. Then separate completed work, work in progress, and work not yet started. This distinction determines what can genuinely be removed.

Deleting a deliverable does not necessarily release its entire original allowance. Some work may already be complete; some may remain useful to the revised solution. Explain the treatment rather than presenting an unexplained credit or charging for the same activity again.

  • Retained: Work still required and already included in the accepted price.
  • Removed: Work no longer required, with the remaining effort and commercial credit stated separately.
  • Added: New work needed to meet the revised requirement.
  • Reworked: Existing work that must be changed or repeated because of the request.

If the parties disagree about whether something is new scope, resolve that question before presenting the adjustment as settled. A disputed baseline cannot support a clear revised offer.

2. Trace the request beyond the visible feature

Describe the requested outcome in terms the buyer can verify. “Add approvals” is incomplete. Who submits, who decides, what happens after rejection, and what evidence will demonstrate that the result meets the agreed requirement?

Then trace the consequences. A visible addition can require discovery, revised configuration, changed instructions, new test cases, and another buyer review. These are not automatically chargeable extras; they are work to assess against the baseline.

Use a short chain: requested outcome → affected work → prerequisite → review → handover. At each link, ask what must exist before the next activity can begin.

For buyer inputs, name an owner and define a usable submission. “Send the approval rules” is weaker than “The operations lead supplies one consolidated decision matrix naming each request type, approver, and rejection outcome.” A file arriving on time does not help if contradictory versions prevent work from starting.

Keep unresolved choices visible. If the buyer has not decided whether approvals are sequential or parallel, either price a clearly stated assumption or complete a separately authorised assessment first. Do not hide an unresolved design decision inside a confident fixed total.

3. Filled hypothetical change-impact worksheet

Fictional worked example: All names, amounts, hours, dates, capacity arrangements, and outcomes in this example are hypothetical. Days are business days counted from project start. This is a standalone service engagement, not a description of any product’s capabilities.

Baseline and request

  • Project: Configure a buyer’s internal request portal and provide handover instructions.
  • Accepted offer: $12,000 fixed price, including a static onboarding checklist, with handover targeted for Day 20 under the original assumptions.
  • Assessment point: Day 7. The checklist work has not started. Other accepted work remains required.
  • Requested change: Replace the static checklist with a sequential approval workflow using two named approver roles, including rejection and resubmission.
  • Acceptance evidence: Buyer-observed test cases demonstrate submission, approval in the agreed order, rejection, and resubmission. Revised instructions explain those paths.

Work and pricing assessment

  • Retained work: Existing request intake, core configuration, and original handover activities remain included. No additional charge is applied to those unchanged activities.
  • Removed work: Eight unstarted hours allocated to the static checklist. Proposed credit: $800.
  • Added work: Eight hours to confirm and map approval rules; ten hours to configure the revised workflow; six hours for additional test cases and validation; four hours to revise instructions and prepare the changed handover. Total: 28 hours.
  • Pricing basis: For this change only, both the removed-work credit and added-work estimate use a hypothetical agreed rate of $100 per hour.
  • Added-work amount: 28 × $100 = $2,800.
  • Net adjustment: $2,800 added work less $800 removed work = $2,000 increase.
  • Revised project price: $12,000 + $2,000 = $14,000, proposed as a fixed revised total for the stated scope and assumptions.
  • Excluded: Additional approver roles, parallel approval paths, historical data migration, and further workflow variants.

Timing, dependencies, and displaced commitments

  • Buyer input: The operations lead provides one consolidated approval matrix, named reviewers, and agreed test examples by Day 10.
  • Input check: The delivery lead confirms whether those materials are complete enough to use. Missing or conflicting rules trigger reassessment rather than silent assumptions.
  • Sequence effect: Rule confirmation must precede workflow configuration; configuration must precede the added validation. The original checklist validation slot cannot accommodate that sequence.
  • Capacity effect: Removing checklist work releases effort but does not create an earlier validation slot. The next suitable validation window is Days 16–19, provisionally available subject to change confirmation by Day 8.
  • Buyer review: Consolidated acceptance feedback is needed by Day 22.
  • Existing commitment: The team has another booked engagement on Days 23–24. This offer preserves it rather than assuming those days can be reassigned.
  • Revised handover target: Day 25, replacing Day 20, conditional on timely confirmation, usable buyer inputs, and the stated review turnaround.
  • Displaced baseline commitment: The original Day 20 handover is no longer offered for the expanded scope. Other accepted project work remains included.

Confirmation and open conditions

  • Buyer confirmation: Authorised commercial contact accepts the replacement scope, $14,000 total, Day 25 target, exclusions, input ownership, and review requirements.
  • Supplier confirmation: Delivery lead confirms the stated capacity remains available before the revised offer is accepted.
  • Decision point: Confirmation is requested by Day 8. Later acceptance requires a fresh capacity and timing check.
  • Until confirmed: Changed work is not authorised. The delivery lead identifies any affected baseline activity that should pause and explains the consequence; unaffected work continues only where it remains useful.

4. Explain why effort and elapsed time differ

The worksheet shows a net increase of 20 hours and a five-business-day movement in the handover target. Those figures describe different things. Effort measures work; elapsed time also includes prerequisites, availability, waiting, and review.

Do not divide the extra hours by a nominal working day and treat the result as the date adjustment. That ignores who must perform the work and whether the necessary inputs and review capacity are available in sequence.

Equally, avoid adding a vague timing buffer without explanation. A buyer should be able to identify the main reason the date moves. In the hypothetical example, the new approval rules must be settled before configuration, validation moves to another available window, and an existing engagement remains protected.

Show dependency uncertainty differently from committed work. If the buyer input date is unknown, a conditional sequence may be more credible than a calendar target. State what event will allow you to confirm the target. If the buyer needs an earlier date, assess a narrower deliverable or another feasible arrangement; do not imply that a higher fee automatically removes dependencies.

5. Present a coherent revised offer

The buyer should not have to reconstruct the decision from a worksheet, an email about dates, and a separate price attachment. Put the commercial choice in one summary and identify which baseline terms remain unchanged.

Hypothetical revised-offer summary:

Replace the unstarted static onboarding checklist with the agreed sequential approval workflow for two approver roles, including rejection, resubmission, validation, and updated instructions. Other accepted deliverables remain unchanged.

The revised fixed project total is $14,000: the original $12,000, plus $2,800 of added work, less an $800 credit for the removed checklist work. The change calculation uses the hypothetical $100 hourly basis described in the assessment.

The proposed handover target moves from Day 20 to Day 25. It depends on confirmation by Day 8, a complete approval matrix and test examples by Day 10, and consolidated buyer feedback by Day 22. Capacity must be reconfirmed if acceptance is later.

Please confirm the revised scope, total, target, exclusions, and buyer responsibilities together. Confirmation of price alone does not authorise the change. No changed work will begin before the agreed authorisation is recorded.

This is an operational summary, not a substitute for the organisation’s established approval process. Name the person who can approve the commercial change and the person responsible for supplying inputs; they may be different people.

6. Offer alternatives that expose the trade-off

A buyer who cannot accept the revised date needs a choice, not repeated reassurance. Offer alternatives only after checking their feasibility.

  • Keep the original scope: Assess whether the baseline remains deliverable under its original conditions, including any disruption already caused by the request.
  • Accept the expanded scope: Use the revised price and conditional target as one package.
  • Stage the change: Deliver a useful baseline first and assess the approval workflow separately. Identify any duplicated testing, instructions, or handover effort before presenting this as cheaper.
  • Reduce the addition: Agree a smaller outcome and reassess both price and timing. Do not assume removing one feature removes its dependencies proportionately.

If an earlier target would displace another commitment, make that an explicit internal decision before offering it. Do not silently spend capacity already promised elsewhere. The buyer needs a credible offer, not private details about another customer.

7. Recover when the assumptions fail

A complete revised quote can still become outdated. Define the response to the most likely failures before work starts.

Inputs arrive incomplete: Identify the missing decisions, name the owner, and explain which activity is blocked. Reassess the target once usable inputs and capacity are known rather than automatically moving it by the number of late days.

The buyer approves only the amount: Ask for confirmation of scope, timing, and responsibilities before treating the change as authorised. Do not infer acceptance from a message that addresses only price.

Work starts prematurely: Record what has been done, what remains, and what can still be stopped. Present the current position honestly instead of backdating approval or disguising completed work as a future estimate.

Another requirement emerges: Compare it with the newly accepted baseline. Do not fold it invisibly into the current adjustment. Reassess only the affected work and dependencies, while keeping unchanged commitments clear.

8. Use the worksheet on the next live request

Before sending your next revised quote, ask someone outside the estimating conversation to find five things: the replacement deliverable, the price calculation, the changed target, the buyer’s required inputs, and the authorisation needed. If they cannot find them without asking, the offer is not ready.

For that request, record whether every timing dependency has an owner and whether the accepted offer contains both a price and a schedule position. After the change is completed, compare the assumed input and review dates with what actually happened. That gives the next assessment a concrete improvement point: a missing dependency, an unrealistic review assumption, or an unclear approval—not merely a larger contingency.

Scope changesQuotes and proposalsCommercial operationsProject handoffs

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