Business admin for UK trades

Quote Document Version Control for a Small Trade Business

Files named “quote final”, “quote final new” and “quote final 2” make a simple customer question harder to answer. Give the document a stable identity and keep an issue history. The aim is to know which proposal was sent and discussed, not to decide whether a document creates a binding agreement.

Separate the latest draft, the issued document and the recorded customer decision.
Separate the latest draft, the issued document and the recorded customer decision. MMD process illustration.

Use a reference that survives a revision

Connect the quote to the job or enquiry reference, then add a version identifier that changes when the proposal is revised. For example, an illustrative filename is A104-quote-v03-draft.pdf. The filename helps retrieval, but the document itself and the job record should also show the relevant reference and position.

Choose a simple convention that the team can apply. Avoid customer personal details in filenames where those names could appear in shared folders, links or notifications. A descriptive reference is more useful than a long filename containing every detail.

Keep document states distinct

  • Draft: still being prepared or checked.
  • Ready for issue: the responsible person has completed the agreed review.
  • Issued: sent through the recorded route on a known date.
  • Superseded: replaced in the current process by a later issue.
  • Customer decision: recorded separately against the relevant version.

Saving a new draft does not mean the customer has received it. Nor does issuing a document show that its contents have been accepted. Use factual labels and retain the evidence needed to explain the sequence.

Record what was actually sent

Keep the issued file or supported system record, its version, recipient and issue date connected to the job. If the business sends a link to a live document, check how the chosen tool records the version visible at the time. Do not assume a link preserves an unchanged copy.

Make the current working reference easy for staff to find while keeping older issues distinguishable. Restrict editing to appropriate people and follow the business’s retention arrangements. This guide does not prescribe a universal retention period or replace advice about contractual documents.

Resolve a version mismatch before changing the work

Illustrative exchange: “Customer refers to quote v02, while the office has prepared v03. Office checks the issue record, confirms which document the customer is discussing and refers any scope or price difference to the owner before updating the job.”

Do not quietly overwrite v02 and make it appear the customer always had v03. A document-control check should expose the mismatch; the authorised person then decides how to resolve the underlying business question.

Check the document tools already available

Microsoft documents restoring earlier SharePoint file versions where version tracking is available. That can help recover an edit, but file history alone does not prove which proposal was sent to a customer or approved. Keep the issue record and communication context too.

Test your current quote system with a fictional revision: can staff retrieve both issues, identify the latest issued version and find the decision? If it already does this, use its supported workflow rather than another register. If not, start with a controlled reference list and review a real mismatch before commissioning custom automation.

Download the working checklist

Download the blank worksheet (CSV). Use fictional details for a trial, then adapt the fields in the system you already maintain. Do not keep a separate spreadsheet just to duplicate a working process. Protect real customer details and share only what the person handling the task needs.

Sources and review

Reviewed 27 October 2026. Microsoft: SharePoint version history and restoration.

Source material supports the specific examples referenced. The checklists, worksheets and illustrative scenarios are MMD's suggested business-admin processes, not customer results. Product workflows can change; check current documentation for the software you use.

Contact us

Tell us what you need help with. We’ll reply by email to discuss the next step.

We’ll use your details to reply. This won’t subscribe you to marketing.

How we handle your details

Your enquiry is stored securely and may be emailed to our support inbox. Only authorised staff and our hosting and email providers have access. We keep it only as long as needed to respond and meet record-keeping obligations. To ask about access, correction or deletion, email support@mmd-solutions.co.uk. This form does not subscribe you to marketing.

Or email support@mmd-solutions.co.uk

Help shape MMD

Start with a free 15-minute conversation about the admin taking up your evenings. If there is a fit, choose Callback alone or add enquiry, quote and payment follow-up.

Discuss a paid pilot

From £49 for 30 days + £49 standard setup (£98 first payment), before any applicable VAT. Starts on activation. Continuing after day 30 needs your explicit agreement. No obligation to buy or join a mailing list.

Read the pilot details and allowances

Optional analytics

Chat on WhatsApp