When quotation requests are scattered across inboxes and personal Excel files, nobody can tell who owns a request or whether it was answered. This article explains, stage by stage, how to get to a state where you can follow them in one place.
The approach is simple. Rather than choosing a quote-management system straight away, move one stage at a time — ledger → notifications → assignment → history → CRM — and stop at the stage where today's problem goes away. Few companies need all five.
If you want to automate one Excel chore, read how to automate manual Excel work; if you want to choose which small improvement to try first, read choosing small DX improvements. This article covers the flow of a single business process: the quotation request.
What is going on with quote requests
Quoting runs from intake to answer to a won or lost deal over days or weeks, with several people involved. Run it on email and Excel and four problems pile up.
| Symptom | Where it happens | Result |
|---|---|---|
| Replies are missed | A request lands in one person's inbox and stalls during leave or a transfer | The customer asks a competitor |
| Two people handle it | Two people separately pick up a request sent to the main address | Quotes go out with different prices |
| Past quotes can't be found | "quote_final_v3.xlsx" is scattered across PCs | The same customer gets different terms from last time |
| Confidential data spreads | Costs, discount rates and other companies' drawings are copied through shared folders and email | People who should not see them can |
The first two are problems of things being invisible; the last two are problems of keeping too much and too little. Centralising fixes both at once.
Losing track of quote requests?
One ledger from quote intake through to assignment
The five stages, and when to stop
| Stage | What to do | Problem it removes | Sign to move on | Fine to stop here when |
|---|---|---|---|---|
| 1. Ledger | Register every quote request in one shared ledger | "Nobody knows who has it" | Requests miss the ledger, updates lag | Two or three handlers who all look at the ledger daily |
| 2. Notifications | Alert the owner to new requests and approaching deadlines | Missed replies, missed deadlines | Disputes or imbalance over who handles what | Few requests and fixed owners |
| 3. Assignment | Decide assignment rules (product, region, rotation) and let the system assign | Duplicate handling, imbalance | Time spent hunting for "what did we quote last time?" | Few repeat requests from the same customers |
| 4. History | Record quote versions, reasons for changes, when and to whom it was sent | Lost past terms, "he said, she said" | You want win rates per customer or a view of all sales activity | Quotes are one-offs and continuing deals need no analysis |
| 5. CRM | Combine customers, deals, quotes and orders in one customer-management system | Sales status lives in individuals' heads | — | — |
Decide the stopping point in advance because every stage adds cost and operating effort. If the ledger alone ends missed replies, that is the right answer.
Stage 1: design the ledger columns so they don't hurt later
You can build the ledger in shared online Excel, a spreadsheet, or a no-code tool such as kintone. What matters is not the tool but the column design. The columns below are shaped so they migrate cleanly to later stages.
| Column | Content | Why it is needed |
|---|---|---|
| Reference number | A sequence such as Q-2026-0001 | Ties email and ledger together even when subjects change |
| Received date | The day the request came in | Measures deadlines and response speed |
| Counterparty | Company name (consistent spelling) | A search field under the Electronic Books Preservation Act; inconsistent names cannot be searched |
| Channel | Email / form / phone / fax | Shows which channel leaks |
| Owner | Exactly one person | "Everyone's job" is nobody's job |
| Reply deadline | The date promised to the customer | Used at the notification stage |
| Status | Received / checking / answered / won / lost / declined | A fixed choice, not free text |
| Quote date | The day the quotation was sent | A search field under the Act (transaction date or other date) |
| Quote amount | Agree company-wide on tax-exclusive or tax-inclusive | A search field under the Act (transaction amount) |
| Quotation file | Stored file name or link | Links ledger and data |
| Confidentiality | Includes drawings / price only, etc. | Used in permission design |
Status is a fixed choice because once "answered", "replied" and "done" are mixed, neither totals nor notifications work.
Stage 2: trigger notifications on owner and deadline
At this stage notifications can often be built from a shared intake address and tool rules. Limit the triggers to two.
- A new request has been in the ledger for a set time with no owner
- The day before the reply deadline, the status is not yet "answered" or later
Notify on every update and soon nobody reads them. Notify only when a person has to act.
Stages 3 and 4: custom work starts with assignment and history
Automatic assignment by rule (product, region, rotation) and keeping the reason for each quote version become fragile in a shared spreadsheet. When someone re-sorts columns or deletes rows, the history is simply gone. From this stage, a database-style tool that keeps a change record, or development fitted to the work, becomes the candidate.
Stage 5: CRM is for when you want to see beyond the quote
A CRM (customer relationship management system) covers not just quotes but deal progress and post-order trading. It is usually too big to install just to fix missed replies; consider it once the sales team grows and the organisation needs to share each customer's situation.
How to prevent mis-sent quotations
A quotation carries prices, terms, the contact's name and details, and sometimes drawings. Sending one to the wrong place loses a partner's trust and can also be a leak of personal data. Do not rely on one measure; layer them.
| Layer | Method | What I confirmed (primary sources) | Limit |
|---|---|---|---|
| Before sending | Review address autocomplete, warn on external recipients | — | Attention fades with habit |
| Right after sending | Delay sending | In classic Outlook for Windows, a rule can delay all outgoing mail by up to 120 minutes; scheduling an individual message also works in new Outlook (Microsoft Support). Gmail lets you choose an undo-send period of 5, 10, 20 or 30 seconds (Gmail Help) | Useless if nobody notices during the delay |
| How it is sent | An expiring, revocable share link instead of an attachment | — | Cannot be revoked once opened |
| Organisational controls | DLP (data loss prevention) to warn on or stop mail containing sensitive data | Microsoft Purview DLP covers Exchange and other locations and can show policy tips or block sharing (Microsoft Learn) | Needs the licence and rule tuning |
| Operations | For priced quotes, two people check recipients only for large amounts or new partners | — | Becomes a formality at high volume |
For a small business, the best balance of effect and effort is delayed sending and switching from attachments to links. Both can usually start at no extra cost.
Deciding what to do after a mis-send
The Personal Information Protection Commission's guidelines give mis-sending an email containing personal data to a third party as an example of a leak, and require internal reporting and limiting damage, investigating the facts and cause, identifying the scope of impact, and measures against recurrence.
Reporting to the Commission and notifying the individuals become mandatory when the leak involves sensitive personal information, risks financial damage, is suspected to result from a wrongful act, or affects more than 1,000 people. In quoting work, attaching a customer-list file by mistake or an inbox read through unauthorised access could qualify. Reporting is in two steps: a preliminary report (roughly 3 to 5 days from becoming aware) and a final report (within 30 days, or 60 where a wrongful purpose is suspected). Check the procedure and forms on the Commission's page on responding to leaks (Japanese).
An amended Act on the Protection of Personal Information was promulgated on 17 July 2026 and, apart from some provisions, takes effect on a date set by cabinet order within two years. Reporting rules may change, so check the Commission's latest guidance when you respond, and consult a professional for individual cases. (This is Japanese law; readers elsewhere should check their own jurisdiction.)
Mis-sending confidential information that is not personal data, such as prices or drawings, is not covered by this reporting duty, but it can breach a non-disclosure agreement. Check the notice obligations in your contracts.
Separate prices and drawings by location, not by file
A quote ledger tends to hold, side by side, the amount shown to customers and the costs, discount rates and margins only insiders should see. A common mistake is hiding them with Excel sheet protection or hidden cells. Microsoft explains that worksheet protection is not intended as a security feature; it only prevents changes to locked cells.
| Information | Who may see it | Where it belongs |
|---|---|---|
| Request details, status, deadline | Sales, quoting staff, managers | The shared ledger |
| Quote amount shown to the customer | Sales, quoting staff, managers | The shared ledger |
| Cost, discount rate, margin | Quoting staff, managers | A separate place with restricted permissions |
| Drawings received from partners | The staff on that project | A per-project folder with restricted viewers |
Permission design is cheapest when decided at the first ledger stage. Try to separate things after the ledger has grown and you cannot recall the files already copied. Designing the entry point for receiving drawings is covered in receiving drawings and NDAs for manufacturers and B2B firms.
Japan's Electronic Books Preservation Act: keep emailed quotations as data
Japan's Electronic Books Preservation Act requires businesses to keep tax-relevant documents exchanged electronically as electronic data. The points of the National Tax Agency's "Electronic Books Preservation Act Q&A [Electronic transactions]" (July 2026 edition) that matter for quoting are these.
| Point | How the Q&A puts it |
|---|---|
| Scope | "Transaction information" in electronic transactions includes items normally written on quotations, and exchange by email (including attachments) is an electronic transaction. Rough drafts before a formal quotation and quotations sent unilaterally by companies wanting to trade need not be kept (Q2) |
| What to keep | The email if the transaction information is in its body; the attachment if exchanged as a file (Q4, Q6) |
| Requirements | An anti-tampering measure (such as establishing and operating internal rules) and search by date, amount and counterparty (Q18, Q48) |
| With no dedicated system | An Excel or similar index listing date, amount and counterparty, matched to the files, is considered to meet the search requirement (Q50) |
| Retention period | For corporations, documents are generally kept 7 years (table under Q17) |
The Q&A also covers when the search requirement is waived, such as for businesses with sales of 50 million yen or less, and how to handle quotes with no fixed amount. Check the National Tax Agency Q&A (PDF, Japanese).
The stage 1 ledger has quote date (transaction date), quote amount, counterparty and quotation file columns precisely to bring it close to the Q50 index. A ledger alone does not meet every requirement, though. You still have to choose an anti-tampering measure and run things so stored files are never deleted or overwritten. Decide which method to adopt with your tax accountant.
Use tools for the ledger and notifications; build from assignment and history
What you can do in-house (about two weeks)
- Pull the last month's quote requests out of the inbox and write them into the ledger columns
- Decide the status options and the rule that assigns exactly one owner
- Route quote requests to a shared address rather than individuals
- Turn on delayed sending for everyone who sends quotes
- Decide where cost-bearing files live and who may see them
- Confirm with your tax accountant how electronic transaction data is retained
When ready-made tools are enough: stages 1 and 2 can nearly always be done by configuring a shared spreadsheet, a no-code tool or an enquiry-management service. Stage 5, the CRM, is also mostly ready-made services.
When custom work fits: when you must show each partner different information, want quote generation linked to existing price lists or production management, or want fax and phone requests on the same flow, configuring ready-made tools stops being enough. In the lumber-distribution DX case study, which I developed single-handedly, ordering moved onto one web-based system that limits what each partner role can see and generates documents such as quotations. The overall approach to moving off Excel is in when Excel hits its limits and how to move off it.
What drives cost
Rates vary widely with conditions, so here are the factors that set cost.
| Factor | Direction that raises cost |
|---|---|
| Intake channels | Email only → forms, fax and phone into the same ledger |
| Users and sites | A few people → across departments and sites |
| Permission design | Everyone sees the same → visibility split by role or partner |
| Integration | Standalone → data linked to accounting, sales or production management |
| Quote generation | Manual → generated automatically from price lists |
| Migrating past data | New requests only → several years of Excel and email imported |
| Approach to the Electronic Books Preservation Act | An index plus internal rules → storage in a system that meets the requirements |
| Maintenance | Done at launch → ongoing user support and changes |
If you outsource, decide first which stage you are asking for. Scope and how costs are set are on routine work automation.
Write last week's quote requests into the ledger
The first thing you can do today is pull every quote request that arrived last week out of the inbox and write them into the ledger columns above. Any row where "owner" and "status" cannot be filled is a request slipping through right now.