You send a proposal, revise it after feedback, and the client eventually says “yes.” By then, the thread contains two prices and three versions of the scope. Learn how to prepare and preserve the proposal so both the client and your team know exactly what was accepted.
Chill&AutomateUpdated September 27, 2026
untangle → move on
✓
When this guide helps
Use this guide if any of these situations sound familiar:
You revise proposals several times and risk starting work from an outdated version.
The client agrees in general, but it is unclear which price, schedule, and scope they accepted.
You want a teammate to take over without searching every earlier message.
Record the proposal, its version, and the client’s reply. Use the message template to clarify an ambiguous acceptance. This helps the team understand the agreement; it does not replace a contract or determine its legal effect.
The approach
Every proposal needs a traceable version and acceptance tied to it. Before handing work over, establish what the client accepted, what remains open and who can approve a change in price or scope.
Check off steps as you finish them. Progress stays in this browser; reset it below when you start again.
Lead with a concrete outcome
State what the client receives, its scope and what they must supply. Separate deliverables from activities: “designs for five pages” means more than “website design.” Define revision rounds, what counts as a scope change and how late materials affect the work. Use the commitments in your actual offer.
Assign an ID and version before sending, such as P-01 v2. Preserve the sent version so editing the working document cannot alter it. Record recipient, date and expiry if you set one. Attachments and links should all correspond to that version.
Clarify an ambiguous yes
If two options are circulating and the client only says “yes,” clarify the exact version. A practical message: “Thank you. Please confirm that you mean proposal P-01 v2 dated [date], covering [deliverables]. We can then arrange the handover.” Do not mark an ambiguous reply as approved internally.
Keep the acceptance reference and the person who checked it. A material scope or price change needs a new version and decision. A signing app can simplify document handling, but it cannot replace a sound proposal or the parties’ authority.
What the record establishes
The record helps the team trace agreed work. It is not a contract template and does not determine the legal effect of an email or signature. Use appropriate contractual terms for the transaction and keep this sheet as its operating record.
Filled example
Fictional example to explain the process, not a real client record.
Example: P-01 v1 covers three pages; v2 adds two more. The client replies “go ahead” to the old email. The owner keeps the status as clarify version instead of handing over a five-page job. Once clarified, acceptance is linked to the correct version.
Client / job / decision maker
Fictional client Studio A; JOB-01; client contact confirms scope and Alex approves the offer internally.
ID, version and sent document
P-01 v1: three pages. P-01 v2: five pages. Both sent versions are stored separately.
Deliverables, exclusions and client inputs
V2: five page designs, two revision rounds. Client supplies copy; new copywriting is excluded.
Price, currency and payment terms from the proposal
Fictional V2: $1,200 before applicable taxes; payment terms are in the proposal. This is not a market price recommendation or an invoice template.
Sending approval and expiry
Alex approved sending V2 on September 28; fictional expiry October 5.
Acceptance: reference, version, date and review
Client replied “go ahead” to the V1 thread on September 29. Alex keeps the status as clarify version and requests confirmation of V2.
Changes / open questions / handover
Do not hand off the five-page project yet. Next: Alex clarifies scope with the client by September 30 and links the reply to the right version.
Take the worksheet with you
A proposal, acceptance and scope-change control sheet.
Expand the blank template below, select the text, and paste it into your document. Replace the brackets with your own information, using the filled example above for guidance. Keep a separate copy for each job. You can also download the text. No sign-up required.
For a few proposals, start with a versioned document and traceable acceptance. Use SignWell when you need a separate signing process; if the team already has Pipedrive Premium, evaluate its included document features first.
Prices and terms checked September 27, 2026, in the currency shown by the vendor. Quotes may vary by country; confirm your currency, tax and commitment before buying. Example budgets exclude any additional tax.
Budget for this job
Five proposals sent for signature per month exceed the three-document free allowance. One Light sender has a public rate of USD 12 billed monthly or USD 120/year. Do not add a signing subscription if your agreed acceptance process already works without a separate signature.
Keep the exact proposal the client received and their reply. A teammate can then find the price, scope, and terms without reconstructing the agreement from several versions.
What can go wrong
If a client replies “go ahead” to an old email, the intended version may be unclear. Clarify it before handing a particular scope to the team as agreed.
✓
How to check it works
The handoff links to the sent version and its corresponding acceptance. A teammate can distinguish what was agreed from what still needs an answer.
Where to start today
Give your next proposal a version and preserve a fixed copy before sending. Link the client’s decision to that specific version.