Track each issued quote as a separate version and connect customer approval to a specific revision. Adding “final” to a filename does not establish which scope and price were accepted.
The first version includes installation, the second adds training and the third changes delivery. A salesperson may send the newest PDF while the customer replies to an older email. The problem is often version ambiguity rather than a new negotiation.
Separate the quote ID from its revisions
For example, T-204 could identify the main quote, with R01 and R02 identifying versions. These are example codes only. Keep the customer, project and conversation under the main record while preserving each version's scope. Retain issued documents rather than overwriting them.
Record the essentials for each revision
- Revision number and creation date.
- Author and reviewer where needed.
- Changes to scope, quantity or delivery conditions.
- Validity period and relevant commercial terms.
- Recipient, channel and sending time.
- A clear state such as current, withdrawn or superseded.
Your CRM may not provide all these fields. Define missing items as requirements rather than assuming they exist. If a temporary process is needed, agree on one authoritative record.
Describe the change concretely
A note such as “Training increased from two sessions to three; other items remain unchanged” is more useful than “updated.” This is an example of wording, not a service commitment. A precise summary saves both teams from comparing the entire document again.
Which version did the customer approve?
Keep the revision number, date and approval communication together. If a customer replies to an old version, do not silently treat it as acceptance of the newest one. Have the authorized parties clarify the agreement. The resulting order or work instruction should reference the accepted version.
Test the process internally
- Create two revisions of a sample quote.
- Check that the first document and its sending information remain available.
- Ask a colleague to identify what changed in the latest revision.
- Test the step that prevents approval of an old version from creating the wrong order.
When discussing a CRM project with BE Soft, describe this scenario without sharing real customer information. Explaining the relationship between versions, sending and approval produces a clearer requirement than simply requesting a quotation module.
