Show What Changed Between Proposal Versions
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A buyer opens your revised proposal and sees a higher total. Was the increase caused by more work, a different rate, or an error? If the covering message only says “updated as discussed,” the buyer has to reconstruct the answer from two documents.
Send a concise change summary alongside the revised proposal. Name the exact versions being compared, state the material changes first, and separate price, scope, timing, assumptions, and unchanged elements. For each revision, show the previous position, the new position, the reason, and the practical effect. Then tell the buyer which points need renewed attention.
The summary is a navigation aid, not a replacement for the proposal. Its job is to make differences visible without asking the buyer to trust a vague assurance that everything else remains the same.
1. Give the reader a clear comparison boundary
A useful summary starts by answering a basic question: changed compared with what?
Identify the proposal reference, the previous issued version, and the revised issued version. Compare against the version the buyer actually received, not an internal working draft. Otherwise, you may describe edits the buyer has never seen while missing differences from the document they are reviewing.
Use a stable heading such as Change summary: Proposal P-214, version 2 to version 3. These identifiers are hypothetical. The important feature is that both documents can be distinguished without opening them.
Place the summary near the start of the revised proposal, or send it as a clearly labelled companion document. A short covering message should point to it. Keep the previous issued version available in your own records rather than silently overwriting it.
Before writing, establish a single comparison pair. If different reviewers received different versions, say which baseline the summary uses and provide a separate comparison where needed. One summary cannot reliably explain several different starting points.
2. Sort changes by buyer consequence, not editing order
The order in which a proposal was edited rarely matches the order in which a buyer needs to review it. A title correction may have happened last, but a new dependency that shifts completion deserves more attention.
Use five categories to make the review predictable:
- Price: changes to the total, line items, recurring charges, discounts, or payment amounts.
- Scope: deliverables added, removed, reduced, or expanded, including changes to quantities and limits.
- Timing: changes to duration, milestones, start conditions, or completion expectations.
- Assumptions: changes to what the buyer must provide or what must be true for the offer to hold.
- Unchanged elements: important boundaries and terms checked against the previous version and confirmed unchanged.
Do not force every edit into a separate line. Group related changes when they have one cause, but keep distinct consequences visible. Adding a deliverable may change both price and timing; showing only the new fee hides part of the revision.
Distinguish substantive changes from presentation edits. A spelling correction can sit in a brief housekeeping note. A corrected quantity that changes the work is not housekeeping, even if the seller considers the original quantity a typo.
3. Filled hypothetical example: proposal comparison
Fictional worked example: Every name, identifier, amount, duration, and commercial detail below is hypothetical. This example concerns an operations documentation project, not an Alactic product offer or customer result.
Buyer: Northbridge Services
Proposal: P-214, Operations Handover Pack
Comparison: issued version 2 to issued version 3
Currency: USD; all amounts below exclude tax, with tax treatment unchanged
Headline: Version 3 increases the fixed project fee from $12,000 to $13,800, a net increase of $1,800. It adds a second team’s handover pack, removes the live training workshop, and extends delivery from four to five weeks after the agreed start conditions are met. It also allows more time for buyer feedback.
Price: show the bridge to the new total
- Before: $12,000 fixed project fee.
- After: $13,800 fixed project fee.
- Reason: Add $2,400 for the second team’s handover pack and deduct $600 for removing the live training workshop.
- Commercial effect: Net increase of $1,800. This is a scope-driven price change, not a general rate increase.
- Proposal location: Section “Fees and payment,” with corresponding deliverables in “Included work.”
Price reconciliation: $12,000 + $2,400 − $600 = $13,800. There are no other fee changes in this hypothetical revision.
Scope: identify both additions and removals
- Before: One handover pack for the customer support team, plus one live training workshop.
- After: One handover pack for customer support and one for the scheduling team. The live training workshop is removed.
- Reason: The buyer requested coverage for scheduling and chose to brief staff internally rather than hold the workshop.
- Commercial effect: The buyer receives an additional team-specific deliverable but no supplier-led live training. The buyer must arrange its own staff briefing.
- Proposal location: Sections “Included work” and “Exclusions.”
Timing: state the duration and its starting point
- Before: Four weeks from the agreed start, following receipt of the listed source materials.
- After: Five weeks from the agreed start, following receipt of the same listed source materials.
- Reason: The additional handover pack requires more drafting and review time; the feedback allowance also increases.
- Commercial effect: The planned completion point moves one week later relative to the same start. No calendar completion date is confirmed by this revision.
- Proposal location: Section “Delivery schedule.”
Assumptions: make changed buyer inputs visible
- Before: The buyer returns one consolidated feedback response within two business days of receiving each draft.
- After: The buyer returns one consolidated feedback response within five business days of receiving each draft.
- Reason: Feedback must now include both teams.
- Commercial effect: The longer feedback allowance is included in the revised five-week schedule. Feedback received later than that allowance would require the delivery schedule to be revisited; the fee has not increased simply because the feedback allowance changed.
- Proposal location: Sections “Buyer inputs” and “Delivery schedule.”
Unchanged: name the items actually checked
- Revision allowance: One consolidated revision round per handover pack remains included. The allowance per pack is unchanged; the number of packs has increased.
- Payment split: 50% at project start and 50% at completion remains unchanged. Because the total increases, each instalment changes from $6,000 to $6,900.
- Source materials: The requirement to provide the listed process notes and existing reference documents before the agreed start remains unchanged.
- Exclusions: Software configuration and ongoing operational support remain excluded. The removed live workshop is now also explicitly excluded.
- Tax treatment: Fees remain stated exclusive of tax.
Renewed attention requested: Review the revised total and instalment amounts, the added scheduling pack, the removed workshop, the five-week duration, and the five-business-day feedback assumption.
4. Explain the effect, not just the edit
A before-and-after pair tells the buyer what words or figures changed. The effect tells them why the difference matters to their review.
In the fictional example, “payment split unchanged” is accurate but incomplete. The split remains the same while the cash amount at each milestone increases. Likewise, “revision allowance unchanged” could suggest the total revision effort is identical unless the summary explains that the allowance applies to each pack.
For every material change, ask:
- Does the buyer pay more, less, earlier, or later?
- Does the buyer receive something different, or take on work previously included?
- Does delivery move, or depend on a different input?
- Does an unchanged percentage or allowance produce a different practical result?
Keep reasons neutral and verifiable. “Buyer requested a second team’s pack” explains the scope addition. “Improved solution” does not explain what changed or why it costs more. If the reason is a seller correction, label it as a correction rather than attributing it to a buyer request.
5. Send a covering message that directs attention
The covering message should be shorter than the comparison. Lead with the material revisions, identify the attachment, and ask a focused question. Do not make the buyer search an attachment to discover that the total or delivery duration changed.
Fictional covering message for the example above:
Subject: P-214 version 3 — revised scope, fee, and delivery duration
Hello Morgan,
Attached is version 3 of the Operations Handover Pack proposal, with a change summary comparing it against the version 2 previously sent.
The main changes are the added scheduling-team pack and removal of the live training workshop. Together, these increase the fixed fee from $12,000 to $13,800, excluding tax. Delivery changes from four to five weeks after the agreed start conditions are met, and the feedback allowance increases from two to five business days.
Please give renewed attention to “Included work,” “Fees and payment,” “Delivery schedule,” and “Buyer inputs.” The payment split remains 50/50, but each instalment is now $6,900.
Could you confirm whether the revised scope and timing reflect your request, or identify anything we have misunderstood? The summary also lists the important items checked as unchanged.
Regards,
Alex
This message requests confirmation of understanding without treating silence as agreement. It also avoids describing the revision as “minor” when price, scope, and timing have all changed.
6. Check the summary against the issued document
The biggest weakness of a manual summary is drift: someone updates the proposal after the summary has been written. Make the comparison a final release check, not an early drafting task.
- Confirm the baseline. Open the previous issued document and the intended revised document.
- Check every substantive difference. Include removals, changed quantities, assumptions, exclusions, and corrections—not just additions.
- Reconcile the money. Check that line-item changes equal the total difference and that related payment amounts agree.
- Trace dependencies. Check whether new scope affects timing, inputs, revision allowances, or buyer responsibilities.
- Verify unchanged statements. Name only items you have compared. Avoid “all other terms unchanged” unless that statement has actually been checked.
- Match the outgoing files. Confirm the version label, summary, covering message, and attached proposal all describe the same revision.
A file comparison can help find omissions, but it will also surface formatting noise. Use it as a completeness check; write the buyer-facing summary around consequences rather than every detected edit.
7. Recover clearly when a revision goes wrong
If the buyer discovers an omitted change, acknowledge the omission specifically. Issue a corrected summary tied to the same document if the proposal itself is unchanged. State what the earlier summary missed and whether the omission affects price, work, timing, or assumptions.
If the proposal also needs correction, issue a new version and identify the document it replaces. Do not leave the buyer to infer which attachment is current. Where review is already underway, explicitly flag the affected points for another look.
If the buyer says “this was not agreed,” separate the record of the revision from the discussion about whether to retain it. Explain what the issued version contains and ask what needs to be corrected. A change summary should describe the proposal accurately; it should not present a disputed request as settled.
The detail level is a trade-off. Too little leaves buyers comparing documents themselves; too much hides consequential changes in editing history. Keep routine presentation edits brief, and give price, deliverables, dependencies, and timing enough space to be understood.
8. Use the next revision as a completeness test
For your next revised proposal, add the five category headings before drafting the covering message. Fill each with a change or a checked unchanged statement, reconcile the total, and link each material revision to a named proposal section.
Use a simple release measure: every material difference found in the final comparison has a matching summary entry. Record any omission caught before sending. After sending, note questions that reveal an unclear explanation, such as a buyer asking why the total increased or whether a removed service is still included.
Those questions identify where the summary needs improvement. The immediate goal is concrete: the buyer can locate each material revision, understand its consequence, and see exactly which parts need fresh attention.
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