Sales proposal control record

Keep the current proposal, open questions, and approved send path in one place.

Use this log when a sales proposal has been revised, reviewed, or returned with questions. Record the source version, what changed, who needs to review it, and which version, if any, is approved for sending.

This is a preparation and tracking record, not authority to make a commercial decision. Assistants may collect version references, note visible changes, prepare a neutral draft, and route questions. They must not set or change pricing, scope, terms, legal wording, discounts, or proposal commitments. They must not negotiate, approve a version, send a proposal, or imply that a proposal is final. The named sales owner, commercial approver, legal reviewer where required, and authorized sender control those actions.

Six checks

A version history is useful only when the decision path is clear.

A file name and a date are not approval. Keep the current source, visible change, open question, reviewer, and send status together so a proposal does not move forward by accident.

Record field

Proposal reference, current version, and approved source

Record the safe opportunity reference, current version, dated approved source, file location, and sales owner. A draft attachment, comment, or email is not the current version until the owner confirms it.

Record field

Changed section and source of the request

Name the visible section, slide, appendix, or safe document anchor that changed and link the approved request or review note. Do not paste confidential prospect material into this public-facing template.

Record field

Approved facts and held commercial claim

Separate approved facts from pricing, discounts, scope, terms, delivery, outcome, legal wording, or other customer claims that still need an owner decision.

Record field

Sales owner, commercial reviewer, and legal route

Name the sales owner and the commercial or legal review route when needed. A preparer may collect references and draft a neutral note, not negotiate, decide, or commit.

Record field

Approved version, authorized sender, and channel

Record the approved version location, send decision reference, authorized sender, and permitted channel. A file name, tracked change, meeting note, or draft email is not permission to send.

Record field

Evidence, superseded version, and next check

Keep safe evidence references, the superseded-version status, stop condition, and next owner check together so a proposal does not move forward by accident.

Fictional examples

A discovery proposal and a renewal proposal both need an owner review route.

Every company, person, request, document, date, review route, and outcome below is fictional. These examples do not set pricing, scope, terms, review standards, response times, negotiation positions, legal conclusions, or send authority. On smaller screens, scroll the table sideways to read every field.

Fictional records that keep a visible draft change separate from commercial review, approval, and sending.
Fictional recordCurrent sourceVisible changeHeld itemsOwner and review routeSend statusEvidence and next check
Fictional discovery proposalFictional proposal v3 in an approved sales folder and a fictional discovery-note reference.The implementation-timeline section was revised after a customer question.No delivery date, scope expansion, fee, discount, or customer commitment is approved by this log.A fictional sales owner checks the response; commercial and legal reviewers handle any pricing, scope, or wording question.Draft only. No assistant may send it.Safe source, review reference, superseded-version note, and next owner check before any customer reply.
Fictional renewal proposalFictional proposal v2 and a linked fictional customer request note in approved storage.The reporting section was clarified; a request for additional dashboard work remains open.Extra work, revised price, service terms, discount, legal wording, and contractual commitment remain undecided.A fictional sales owner routes the question to the commercial owner; legal wording follows the approved legal route.No approved customer-facing version is recorded.Safe source, decision reference when available, authorized-sender check, and recheck date.
Copy-ready version-control log

Use safe references, not prospect or contract text.

Copy this into the business's approved system. Keep confidential prospect material, contract text, credentials, personal data, and restricted records in the approved location.

SALES PROPOSAL VERSION-CONTROL LOG

LOG CONTROL
Safe opportunity or proposal reference:
Current proposal version, date, and approved storage location:
Approved request, review note, or source reference:
Preparers:
Named sales owner:
Commercial reviewer and legal-review route when needed:
Authorized sender and permitted channel after approval:
Next check owner and date:

VERSION CHANGE
Changed section, slide, appendix, or safe document location:
Visible change summary:
Approved facts carried forward:
Missing fact or owner question:
Superseded version and status:

HELD ITEMS
Pricing, discount, scope, term, delivery, outcome, legal wording, customer promise, or other held claim:
Owner decision needed:
Review reference:
Approved version location:
Send decision reference:
Stop condition:

EVIDENCE
Safe source reference:
Approved review or decision location:
Authorized sent-version reference, if applicable:
Next check and outcome reference:

Use safe references to approved records. Do not paste confidential prospect material, contract text, credentials, personal data, security material, or other restricted records into this log. Completing this log does not set price, discounts, scope, terms, delivery, legal wording, or customer commitments. It does not negotiate, approve, accept, send, or authorize a proposal. Named sales owners, commercial and legal reviewers, and authorized senders control those actions.

The full log stays visible and selectable. Nothing is uploaded or saved.

Review steps

Prepare the record without deciding the offer.

A draft, comment, or customer request does not approve a commercial claim or a send. The named owner and reviewer decide what may go out.

  1. Open the owner-confirmed current proposal version and the approved request or review reference before preparing a log.
  2. Record one visible change and its safe document location. Keep prospect details and restricted files in the approved system.
  3. Separate approved facts from open pricing, discounts, scope, terms, delivery, outcome, legal wording, and customer-promise questions.
  4. Name the sales owner and commercial or legal review route. Keep any missing fact as an owner question instead of guessing.
  5. Record the approved version, permitted sender, and allowed channel only after the named owner provides a decision reference. Send nothing before then.
  6. Save the safe evidence reference, superseded-version status, stop condition, and next owner check for the next reviewer.
Stop and escalate

A draft is not a decision.

Hold the work when the current version, owner, review route, approved wording, permitted sender, or safe evidence location is unclear.

  • The current version, approved request, sales owner, reviewer route, decision reference, permitted sender, or safe evidence location is missing or conflicts with another record.
  • A preparer is asked to set price, discount, scope, terms, delivery, legal wording, a customer promise, or a negotiation position.
  • A comment, tracked change, meeting note, draft email, file name, or customer request is treated as approval, acceptance, commitment, or permission to send.
  • The proposed change could affect price, discount, scope, term, payment, service level, delivery, security, privacy, legal position, contract, or a customer outcome.
  • Someone asks the preparer to negotiate, approve a version, send a proposal, communicate a commercial or legal position, or promise an outcome without explicit authorization.
  • Confidential prospect material, contract text, credentials, personal data, security material, or another restricted record is pasted into this public-facing template instead of safely referenced.
Before a proposal goes out

Confirm the version, the decision, and the sender.

A clean log can show what changed and who needs to act. It cannot approve pricing, scope, terms, legal wording, discounts, or a customer commitment, and it does not give an assistant permission to send.