How do you track every quote and report sent to a customer?
Summary
Tracking customer quotes, proposals and reports takes 4 steps: file by customer, group by document type, log version and send date, then attach emailed copies. The record works when every document that leaves the company, by email or any other route, lands in the customer's list with the file itself, not only a line saying it was sent.
ISO 9001:2026, the sixth edition, was published on 16 September 2026 and keeps clause 7.5.3 Control of documented information (ISO, 2026).
ISO 15489-1:2016 applies to the creation, capture and management of records regardless of structure or form, and ISO confirmed it as current in 2021 (ISO 15489-1:2016).
In the EU, when a safety data sheet is revised for new information on hazards or risk management measures, an authorisation decision or a restriction, the new version must go to every recipient supplied within the preceding 12 months (Regulation 1907/2006, Article 31).
EU distributors must keep the information they need for their REACH duties for at least 10 years after they last supplied the substance or mixture (Regulation 1907/2006, Article 36).
This method is for supplier sales and technical staff who send quotes, proposals, test plans, reports and product documents to industrial customers. It does not replace a contract management system, an ERP order record or a regulated document control system that a customer or authority requires.
Why do quotes and reports sent to customers get lost in email threads?
Quotes and reports sent to customers get lost in email threads because the email client files them by conversation and by sender, while the question later is usually about the customer and the document type: which quote did we last send this plant? The answer sits in someone's sent folder, under a subject line nobody remembers.
Three things make it worse. A document often goes out several times, as a draft, a revision and a final, each in a different thread. A colleague may send the next version from their own mailbox. And when the account changes hands, the history leaves with the person: the UK National Archives tells organizations that "leavers file any emails of corporate value" before accounts are deleted (The National Archives, UK).
The same guidance names the cost of missing mail: "Lost emails can prevent work from being carried out, create unnecessary duplicated effort or cause damage to the organisation" (The National Archives, UK). For a supplier, duplicated effort means rewriting a quote that already exists, and damage means quoting a customer a different price or lead time from the one they hold. It also warns that email archiving systems "do not manage email, they only store them" (The National Archives, UK), so an archive does not answer the customer and document type question either.
Which document types should you track for each customer account?
You should track every document type for each customer account that the customer may act on or quote back to you: quotes, proposals, test plans, test and visit reports, and the product documents you supplied. A useful test is whether someone will later ask "which version did they get?"
A working list for an industrial supplier:
Quotes and price offers, with their validity date.
Proposals and technical recommendations.
Test plans and trial protocols agreed with the customer.
Reports: trial results, service visit reports, complaint and corrective action reports.
Product documents: technical data sheets, safety data sheets, certificates of analysis and declarations.
Product documents matter for a regulatory reason as well as a commercial one. In the EU, when a safety data sheet is revised for one of the reasons listed in Article 31(9), the new version goes to all recipients supplied within the preceding 12 months (Regulation 1907/2006, Article 31). A per-customer record of which sheet revision each customer received makes that mailing list a lookup instead of a search through sent mail.
Leave out routine correspondence that carries no decision. Records guidance makes the same cut for email: an organization should "define clearly which emails need to be kept for business or historical value" (The National Archives, UK).
Is a sales quote tracking spreadsheet enough for proposals and reports?
A sales quote tracking spreadsheet is enough for proposals and reports only if it holds a link to the sent file for every row and someone fills it in at the moment of sending; without the file, it shows that a document went out but not what it said.
Spreadsheets are where most teams start. A 2014 post by a proposal software maker describes businesses using a basic CRM or "an Excel spreadsheet or something similar" to organize sent quotes, and advises avoiding spreadsheets "at all costs" (Better Proposals, 2014). That advice comes from a vendor selling tracking software, but the weak points it names are real: a spreadsheet does not remind anyone, and it holds no document unless someone attaches one.
The test is the same for any tool:
Can you find every document sent to one customer, grouped by type, without opening email?
Does each entry open the exact file the customer received?
Does it show which version is the latest?
In Lubinpla, each customer's deliverables list stacks quotes, proposals, test plans and reports by document type, but only documents created on or uploaded to the platform are stacked, and attachments sent by email are not linked to the customer automatically. Whatever tool holds the record, emailed attachments still need a deliberate step to reach it.
What should a sent-document log record for each quote or report?
A sent-document log should record seven fields for each quote or report: customer and site, document type, title, version, send date, recipient, and the file itself. With those seven, anyone on the team can say what the customer holds and whether it is the latest version.
Customer and site: the customer's legal or account name and the plant, so two sites of one group stay apart.
Document type: from a fixed list, such as quote, proposal, test plan, report, product document.
Title: the document's own title, not the email subject.
Version: a number or letter that increases with each issue, for example Rev 2 (illustrative).
Send date: in YYYY-MM-DD form, which removes the doubt in a date such as 01/05/22 (ISO 8601-1:2019; ISO date format guide).
Recipient: the named person and their role at the customer.
File: the exact file sent, stored with the entry, or a link that opens it.
Add the validity date for quotes and the superseded version for any revision. ISO 9001:2026 keeps a clause on control of documented information, clause 7.5.3 (ISO, 2026), and a log that cannot open the sent file cannot show which version the customer holds.
How do you set up a customer document record step by step?
You set up a customer document record in four steps, each one a single action that the team can repeat for every customer.
File by customer. Create one record per customer, with sites under it. Use the customer name exactly as it appears on your account list, so search finds it.
Group by document type. Inside each customer, keep one list per document type from your fixed list. A new quote goes under quotes, never under "misc".
Log version and send date. For each document sent, add an entry with the fields from the previous section. Fill it in when you send, not at month end.
Attach emailed copies. For a document that left as an email attachment, save the attached file into the entry, along with the email itself if it holds terms the file does not. The UK National Archives advises keeping "emails with related digital information in a shared corporate information management system" (The National Archives, UK).
Then backfill. Search each team member's sent mail for the last 12 months (illustrative period) of attachments to the customer, and add the latest version of each document type first. Older versions can follow; the latest quote and the latest safety data sheet revision matter most.
How do you check that a customer's document record is complete?
You check that a customer's document record is complete by comparing the record against the team's sent mail for that customer and running five checks on what you find: coverage, file, version, date and recipient.
The table below decides whether a customer's record holds every quote, proposal, test plan and report that was sent.
Check | Pass | Fail and what to do |
|---|---|---|
Coverage | Every attachment found in sent mail has an entry | Attachment with no entry: add it under the right document type |
File | Each entry opens the exact file sent | Entry with no file: save the attachment from sent mail into the entry |
Version | Latest version marked, older ones kept and labeled superseded | Two entries both look current: compare dates and mark the older superseded |
Send date | YYYY-MM-DD on every entry | Missing or ambiguous date: take it from the email header |
Recipient | Named person and role | "Purchasing" only: add the person's name from the email |
The coverage row matters most: a document that left only as an email attachment and has no entry is invisible to anyone who looks at the customer record.
Run the comparison per customer when an account changes hands, before a quarterly review, and after any safety data sheet revision. Record the date of the last check on the customer record so the next person knows where to start. Ask each person who sent documents to that customer to search their own sent folder, since a shared mailbox or another colleague's account will not show what they sent. Close the check only when every attachment found has an entry or a written reason for leaving it out.
Frequently asked questions
Should the email itself be saved, or only the attachment?
Save the attachment in every case, and the email too when its body carries terms the file does not, such as a changed delivery date or a condition on the price. Records guidance says a kept email should still show its full content and open its attachments for any user (The National Archives, UK).
Who should keep the customer document record?
The person who sends the document makes the entry, because they hold the file and know the version. The account owner checks the record for completeness at handover and before reviews, so gaps are caught while the sender can still fill them.
How long should sent customer documents be kept?
Keep them for the longest period that applies: your contract terms, your quality system rules and the law. For safety data sheets and other REACH information in the EU, REACH requires each manufacturer, importer, downstream user and distributor to keep the information needed for its duties for at least 10 years after it last manufactured, imported, supplied or used the substance or mixture (Regulation 1907/2006, Article 36).
What about documents sent through a customer portal?
Treat a portal upload like an email: save the uploaded file and the upload confirmation into the customer's record under the right document type. A portal holds the customer's copy, not yours, and access can end when the account or the portal changes.