You send an estimate to paint two rooms. The customer asks about adding the hallway, so you change the document and send it again. A few days later, a message arrives: "Looks good." Meanwhile, the crew has a printed copy of the first estimate.
Picture a small interior painting business serving Orlando and nearby neighborhoods. This is a fictional example. Before the crew leaves, someone needs to settle a basic question: does this job include the hallway? The latest draft alone won't answer it.
You can start with the files and messages you already use. Give each sent estimate a clear revision, preserve that copy and connect the customer's response to it.
Keep a record of what you actually sent
Choose a job reference that stays the same throughout the conversation. Add a revision number when you send a changed proposal: Estimate-104-v1, then Estimate-104-v2. Put the reference, revision and issue date inside the document as well as in its filename. A printed page needs to identify itself.
Keep three things easy to find: the working draft, the copies sent to the customer and the record of the customer's response. For a small operation, start with a job folder in your existing business storage. Give one person responsibility for issuing revisions so two employees don't send different files with the same number.
Once you've sent a copy, preserve it as sent. Make the next revision from a separate draft. Avoid replacing an old attachment or changing a shared document while expecting the customer to remember what it used to say.
If you already prepare estimates in Word for the web, Microsoft's PDF export instructions show how to download a copy with or without comments. Export the customer copy without internal comments, then open it and check the scope, price and revision before sending. A PDF gives you a separate copy to retain; it isn't tamper-proof or evidence of acceptance by itself.
Explain the change before asking for a decision
In the painting example, the second message should say that revision 2 adds the hallway and identify any change to the price or planned duration. Keep exclusions visible too. If ceilings remain outside the proposed work, don't leave that detail buried in an earlier email.
Ask the customer to confirm the specific revision. For example: "Please confirm whether you'd like to proceed with Estimate 104, revision 2, including the hallway." If their reply could refer to either version, clarify before scheduling the disputed work.
Save the response with the exact estimate it concerns and note who confirmed it and when. Use your existing contract or change-approval process where one applies. This filing routine helps coordinate the work; it doesn't establish that an email meets every contractual requirement.
If the customer had already approved revision 1 before asking about the hallway, record revision 2 as a proposed change. Keep the original agreement identifiable until the change is resolved. Don't silently treat a question about extra work as approval to perform it.
Give the crew the agreed scope
A later edit date doesn't tell the crew whether a proposal was accepted. In the job record, identify the revision approved for the work and link to the retained copy. List any open change separately so it can't be mistaken for an instruction.
Before dispatch, the person coordinating the job should confirm that the crew has the applicable scope. If an approved change arrives after a brief was printed, replace the outdated brief and get acknowledgment from the crew lead. Keep internal costing notes out of the customer copy, and avoid giving the crew unrelated customer records.
For a business already using OneDrive, Microsoft's sharing guide describes access for specific people and view versus edit permissions. Share the individual customer copy with the intended recipient, with viewing access when editing isn't needed. Recipient access can depend on account and administrator settings, so test the link before relying on it. Check existing access too: a new restricted link doesn't remove permissions someone already has. View access also doesn't guarantee that a recipient cannot retain or forward a downloaded copy.
Use version history as a fallback
OneDrive can show and restore earlier file versions. Microsoft notes that work-account administrators may disable versioning. Check your actual setup and retention settings before depending on it.
That history may help recover an overwritten draft. It doesn't explain which attachment a customer received or which proposal they accepted. Keep the sent copy and the response together even when file history is available.
If your estimating system already stores issued revisions and customer approvals, use those records instead of creating a parallel folder routine. This approach doesn't require buying an add-on: start with the document export, storage and communication tools your business already has. Check that the people involved can actually access the chosen records.
Try one fictional job with an original estimate, a requested addition and an ambiguous reply. Ask someone else to find the agreed scope without asking you. If they open the newest draft by mistake, fix the labels and handoff before adding automation.
The request and quote tracking example shows how revisions and next actions could fit into a focused project. Bring the steps you use to send and revise an estimate; we can discuss where the approved scope gets lost along the way.