A salesperson prepares a quote, the customer asks for a change and a colleague updates the pricing. An earlier attachment remains in the email thread. The customer later replies “approved” to that old message, while the sales team believes the latest version has been accepted.
The mistake may stay hidden until an invoice is raised or delivery begins. By then, scope, price and expectations can already be different. What looked like a document problem has become a customer and operational problem.
Proposal version control does not need to be complicated. It needs one visible record, clear status and a reliable link between the document sent and the customer’s response.
Keep one proposal record for the opportunity
Start with a single working record linked to the customer and opportunity. Keep the quote or proposal history there rather than treating each attachment as an unrelated file.
Capture the owner, customer contact, opportunity, current value, currency, scope summary, commercial terms, expected decision date and internal approver where one is required. The record should make the current position visible without asking the team to search several inboxes.
Give every version a clear identity
Use a consistent version number or revision label, creation date and owner. The document itself should show enough information for a colleague to distinguish it from an earlier version.
Do not rely only on filenames such as “final”, “final new” or “latest”. Those names become ambiguous as soon as another change is made. A useful version trail shows what changed, why, who made the change and which earlier version it replaced.
Separate draft, approved and sent
A document can be complete enough for review without being authorised for the customer. Use statuses that describe the real position, such as draft, internal review, changes required, approved to send, sent to customer, revision requested, accepted, declined or expired.
Only one version should hold the current “approved to send” or equivalent status. If a later revision is approved, the earlier version should be marked as superseded rather than left looking active.
Control the approval handover
Define which changes require approval and who can give it. Pricing, discounts, payment terms, delivery commitments, scope exclusions or unusual conditions may need different reviewers according to the organisation’s rules.
The approver should receive the complete version and a concise summary of changes. Approval should identify the exact revision, not simply say “looks good” in a thread containing several attachments.
Keep working comments out of the customer copy
Internal notes, margin discussions, alternative pricing and unresolved questions belong in the working process, not in the document sent externally. Generate or select a clean customer copy only after internal review is complete.
Before sending, check the customer name, contact, scope, quantities, pricing, tax treatment where applicable, currency, validity period, payment terms, delivery assumptions and included or excluded items. The check should use the approved record, not memory.
Record exactly what was sent
Link the sent email or communication to the exact proposal version. Record the recipient, date, sender and channel. Where several customer contacts are involved, make it clear who is expected to approve and whether another person must be copied or consulted.
If the customer requests a revision, create the next version from the current record. Do not silently replace the file that was already sent, because the team still needs to know what the customer originally received.
A practical example
A service company sends a quote for a three-month engagement. The customer asks for a six-month option and a revised payment schedule. Sales updates the proposal, but the earlier three-month PDF remains attached to the original email thread.
A manager internally approves the six-month version. Before sales sends it, the customer replies to the first email and writes “approved, please proceed”. Operations receives a note saying that the deal is won, but the team cannot tell which term the customer accepted.
With version control, the three-month proposal is recorded as sent but superseded after the revision request. The six-month version receives a new revision number and explicit internal approval. The customer’s response to the old message is treated as clarification required, not final acceptance. Sales sends the current proposal and asks the customer to confirm that exact revision.
Once the customer accepts, the response is linked to the approved version and the opportunity status can move forward with a clear basis.
Handle superseded documents actively
When practical, tell the customer that an earlier quote has been replaced and identify the current version. If a portal or shared location is used, ensure that old versions cannot easily be mistaken for the active document.
Internally, keep historical versions for the agreed retention period, but remove them from the team’s normal sending path. History should support accountability without increasing the chance of another mistake.
Connect acceptance to delivery
Customer acceptance should identify the version, accepted value, scope, terms, date and authorised contact. If the reply is unclear, resolve it before treating the opportunity as won.
The handover to operations or delivery should include the accepted proposal, not merely the newest-looking file. Confirm that quotes, orders, invoices and delivery instructions are based on the same agreed revision.
Review the workflow, not only the error
Track cases where customers receive the wrong version, approvals cannot be matched or delivery starts with unclear terms. Look for causes such as personal file storage, inconsistent names, unclear approval authority or manual copying between systems.
MyTalent Business CRM gives sales and operations teams a shared view of customers, opportunities and the work ahead, including leads and sales, quotes and invoices. Explore Business CRM or talk to our team about the capabilities available for your business.
The standard is simple: when a customer approves a quote, everyone should know exactly which version they approved and what happens next.