Back to all articlesQuotes and proposals

Keep One Current Quote When Buyers Have Several Versions

Alactic Editorial10 min read

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

A buyer approves the price in one attachment while their operations colleague reviews the scope in another. Both files came from your team, both look credible, and neither says clearly whether it has been replaced. The problem is not simply too many files. It is the absence of a shared rule for identifying which issued quote is current.

To manage sales quote versions, give each proposal a stable quote ID, assign a new version to every externally issued revision, and maintain one register showing which version is current. Whenever you replace an issue, name the old and new versions, explain what changed, and ask active reviewers to use the replacement. Keep previous issues as history rather than silently overwriting them.

The practical test is simple: can a buyer, approver, or colleague identify the current quote without asking the salesperson to reconstruct an email thread? The protocol below is designed to make that possible.

1. Decide what counts as the same quote

Start with a stable identifier for the commercial proposal. Keep that identifier through revisions to the same buying decision. Add a separate version number for each externally issued revision.

For example, in a hypothetical sale, Q-0264 identifies the quote family and Q-0264-v03 identifies one specific issue. The filename might be Q-0264-v03-Northbank-Packaging-Line.pdf. The customer name helps people recognise the file; the quote ID and version distinguish it from its predecessors.

Use a new quote family when the buyer is considering a genuinely separate purchase or an independently selectable option. Otherwise, two valid proposals can accidentally be treated as competing versions of one document.

  • Revision: The buyer requests a different quantity for the same project. Retain the quote ID and issue a new version.
  • Separate proposal: The buyer requests an unrelated project with its own approval. Create a new quote ID.
  • Alternative: The buyer wants to compare two configurations. Label the alternatives explicitly rather than calling one a newer version of the other.

Put the full issue identifier inside the document, not just in the filename. Forwarding, downloading, or renaming a file can strip away the context around it. A practical header includes the quote ID, version, issue date, and page number. Identify any scope schedules or pricing attachments by version too.

2. Separate working drafts from issued proposals

A file being edited is not yet the proposal a buyer should review. Keep internal drafting separate from external issue status so that an unfinished revision does not displace a usable quote.

A small team can work with these states:

  • Draft: In preparation; not issued for buyer review.
  • Current issued: The version the seller is presenting for the defined decision.
  • Superseded: Previously issued, now replaced by a named version.
  • Withdrawn: No longer offered, with no current replacement.

Track buyer response separately. Acknowledged, under review, and approved describe what the buyer has done; they do not identify which file is current. Likewise, a quote's validity date is a separate field. A quote can be the latest issue yet no longer be available for acceptance without rechecking its terms.

Do not label several files “current” within the same quote family and decision scope. If a revised proposal is still awaiting internal checks, keep it as a draft. If the existing issue must no longer be used, withdraw it explicitly rather than leaving reviewers to guess.

Once a document has been issued externally, preserve that exact issue. Even a small correction should produce a new version if it changes the file buyers receive. Reusing the old identifier for different contents makes it impossible to establish what a reviewer actually saw.

3. Keep a register that records issue history, not just filenames

The register is the practical artifact at the centre of this process. It can be a shared record or a controlled list; it does not need elaborate software. It does need an owner and a predictable place where colleagues can find it.

Record the full issue identifier, issue date, status, replacement relationship, change summary, recipients, and location of the preserved issue. Record enough recipient detail to reconnect the review chain when a revision is sent. An address list alone may miss the person who is actually approving scope or price.

Fictional worked example: a filled version register

All organisations, people, identifiers, dates, quantities, and prices in this example are hypothetical. Northbank Foods is reviewing a packaging-line proposal. All prices below are hypothetical USD amounts. The register is shown as it stands on 14 April 2026.

Quote family: Q-0264
Decision scope: Packaging-line supply, installation, and operator training
Register owner and issue coordinator: Maya Chen, seller account lead
Current issue: Q-0264-v03, issued 14 April 2026
Current preserved file: Issued quotes / Q-0264 / Q-0264-v03-Northbank-Packaging-Line.pdf

  • Document identifier: Q-0264-v01
    Issue date: 7 April 2026
    Supersession status: Superseded by Q-0264-v02 on 10 April 2026
    Issued contents: Two packing stations, installation, one training session; USD 48,000 total
    Recipients: Elena Ruiz, buyer procurement lead; Tom Reed, buyer operations lead
    Preserved file: Issued quotes / Q-0264 / Q-0264-v01-Northbank-Packaging-Line.pdf
  • Document identifier: Q-0264-v02
    Issue date: 10 April 2026
    Supersession status: Superseded by Q-0264-v03 on 14 April 2026
    Changes from v01: Added a third packing station; total changed to USD 61,000; installation and one training session retained
    Recipients: Elena Ruiz, procurement; Tom Reed, operations; Priya Shah, buyer finance reviewer
    Preserved file: Issued quotes / Q-0264 / Q-0264-v02-Northbank-Packaging-Line.pdf
  • Document identifier: Q-0264-v03
    Issue date: 14 April 2026
    Supersession status: Current issued; replaces Q-0264-v02 and is the current reference for the Q-0264 quote family
    Changes from v02: Three packing stations retained; added a second training session; total changed to USD 62,500; installation scope unchanged
    Recipients: Elena Ruiz, procurement; Tom Reed, operations; Priya Shah, finance; Noah Patel, buyer project sponsor
    Preserved file: Issued quotes / Q-0264 / Q-0264-v03-Northbank-Packaging-Line.pdf
    Buyer acknowledgment: Elena confirmed receipt and forwarding to all named reviewers on 14 April; individual review status remains unconfirmed

This record distinguishes sending from acknowledgment and acknowledgment from review. It also explains why a price changed without forcing someone to compare every page. It does not claim that every recipient has opened or approved the latest issue.

4. Issue each revision as a controlled handover

Assign one person to coordinate each external issue, even if several people contribute pricing and scope. That person checks that the document, register, and outgoing message all describe the same revision.

  1. Prepare the candidate issue. Check prices, quantities, scope, exclusions, and the identifiers on associated attachments.
  2. Resolve internal comments. Do not send a document containing unresolved alternatives or drafting notes as the current proposal.
  3. Assign the version and issue date. Use the same full identifier in the document, filename, register, and message.
  4. Preserve the issued copy. Retain the exact file being sent, not merely an editable source that may later change.
  5. Record the replacement relationship. Name the prior issue being superseded and identify the new current issue.
  6. Send and record the handover. Note the actual recipients and send date. If sending fails, record that the intended recipient has not received the replacement.

Keep these steps close together. Updating the register days before distribution creates a gap in which the seller calls one version current while the buyer still has another. Preparing the issue packet first makes that gap easier to manage.

If you use a stable link to a current-copy location, keep the issue identifier visible at the destination and retain separately identifiable historical issues. A convenient link does not tell you which version somebody downloaded last week. Check that intended recipients can access the replacement before relying on it.

5. Send a replacement message that names the current version

“Please see the updated quote” is not enough. It gives recipients no reliable way to distinguish the attachment from another update already in their inbox. Name the current issue, identify what it replaces, summarise the changes, and specify the next review action.

The following replacement message continues the fictional worked example.

Subject: Q-0264-v03 is the current Northbank packaging-line quote

Hello Elena, Tom, Priya, and Noah,

Please use Q-0264-v03, issued 14 April 2026, for the packaging-line review. The attached file is Q-0264-v03-Northbank-Packaging-Line.pdf.

This issue replaces Q-0264-v02, issued 10 April. Q-0264-v01 is also superseded. Please keep those earlier copies for reference only, not for the current approval.

Compared with v02, v03 adds a second operator-training session and changes the total from USD 61,000 to USD 62,500. The three packing stations and installation scope are unchanged.

Please confirm that your review is using Q-0264-v03. If an earlier issue has already been forwarded for approval, please send this replacement to that reviewer and let me know who else needs a copy. If approval has already been recorded against an earlier version, please flag that before we proceed.

Thank you,
Maya

Send the replacement to everyone actively reviewing the quote, not only the person who requested the change. Ask the buyer's coordinator about additional internal recipients, while recognising that you may not have visibility into every forwarded copy.

Use a permitted communication channel and respect recipients' contact preferences. The operating rule is channel-independent: a short chat notification should still name the current version rather than merely announce that an update exists.

6. Preserve history without making old issues look current

Deleting older files removes useful evidence of what changed and what people were discussing. Leaving them beside the current copy with no status information invites reuse. Preserve the originals, but make their status clear wherever people retrieve them.

A practical arrangement separates the current issue from historical issues and labels each historical entry with its replacement. Preserve the originally sent file unchanged. If you create a visibly marked reference copy, distinguish it from that original rather than silently altering the historical record.

Include a concise change summary with every new issue. State both the changes and the important areas that remain unchanged. However, make the complete current document the review reference; the summary is a navigation aid, not a substitute for the proposal.

There is a trade-off between detail and upkeep. A paragraph describing every punctuation change can obscure the commercial differences. A summary saying only “updated pricing” conceals too much. Prioritise changes affecting the buying decision: price, quantities, deliverables, exclusions, timing assumptions, and included attachments.

7. Recover when someone uses the wrong version

When a buyer cites an outdated amount, first establish the exact issue they are using. Ask for the identifier or the file itself. Do not assume that a matching filename means matching contents, especially if files have previously been overwritten.

  • An old quote is in an approval chain. Identify the issue in that chain, send the current replacement, and ask the buyer's coordinator to redirect the review. Record which reviewer still needs the update.
  • Approval references a superseded issue. Flag the mismatch and obtain clarification against the intended current issue before treating it as approval of the new scope or price. Do not silently transfer the approval.
  • Two different files share one identifier. Preserve both, record the discrepancy, and issue a newly numbered, checked replacement. Tell recipients that the duplicate identifier was ambiguous.
  • A replacement was not received. Keep the new issue status and the recipient's receipt status separate. Re-establish contact through an appropriate channel and record the unresolved handover.
  • The seller wants to restore an earlier offer. Recheck it and issue a new version explaining the restoration. Do not simply relabel an old attachment as current.

If nobody can establish which version a reviewer saw, record that uncertainty. A transparent correction is more useful than a reconstructed history presented as fact.

8. Test the protocol on one active quote

Choose one live proposal with multiple attachments or revisions. Gather the issued files, assign unambiguous identifiers where needed, and build the register before sending another update. Resolve any conflicting current copies with the account owner.

Then ask a colleague who was not involved in drafting to find three things: the current issue, the issue it replaced, and the people who received the replacement. If they need to search a private inbox or ask the salesperson, improve the record.

For the next review period, track observable exceptions rather than assuming the process works:

  • How many quote families have more than one file presented as current?
  • How many issued revisions lack a recipient record or replacement message?
  • How often do buyers reference a superseded issue during review?
  • How many replacement handovers still have unconfirmed receipt?

Your next action is concrete: complete one version register and send one replacement message that names the current issue. Success is not the disappearance of every old attachment. It is the ability to identify the right proposal, explain its history, and correct a mistaken reference without restarting the negotiation.

Sales quotesVersion controlSales operationsProposal management

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