All articles

    Guide

    Proposal management in a CRM: from draft to signed

    Track the current proposal, the next review date, and the people who need to approve it.

    Oksana Tkachenko
    Oksana T.
    Writer · Updated 17 September 2026

    What should a CRM track for each proposal?

    Keep one deal linked to the current proposal version, its owner, the buyer contacts, the amount, and the next agreed action. Record document status separately from deal stage so a file view does not move a deal to won.

    Keep a usable proposal record

    Start with fields that someone can check before a buyer call. Use the document tool for the proposal itself and link its current version from the deal.

    • Owner and people

      Name the person responsible for follow-up. List the buyer, the person approving the budget, and any required signers. Confirm these roles with the buyer.

    • Version and commercial terms

      Keep the document link, version date, amount, currency, scope, and expiry date together. Mark an old version as replaced when terms change.

    • Next action

      Record who will do what and by when. Add the question or decision needed, such as confirming scope or arranging a review with procurement.

    Separate document status from the sales decision

    Choose clear stage rules for your team. Check the source document before changing a deal stage, especially when several people must approve it.

    • Draft and internal review

      Check scope, price, delivery dates, and approval needs before sending. Keep internal notes out of the client copy.

    • Sent and under review

      A delivery or view event records activity. Ask the buyer to confirm receipt and the planned review date. Record requested changes against the right version.

    • Completed, declined, or expired

      PandaDoc defines Completed as completion by all signers. It tracks payment separately. Check your own provider's status rules, then record the deal outcome and any remaining handoff steps.

    Set follow-up around an agreed date

    Ask when the buyer expects to review the proposal and whether other people need to be involved. Use that date for the next task. If no date is agreed, choose one based on the stated deadline and record that it is your own reminder.

    Example follow-up note
Proposal: Website support, version 3
Owner: Maya
Buyer review: 24 September
Open question: Include weekend cover?
Next action: Maya to send the revised scope on 22 September
Decision needed: Buyer to confirm scope and approver

    • When a review slips

      Ask what is blocking the decision and agree on a new action. Keep the old date in the history so a moved deadline remains visible.

    • When there is no reply

      Check the contact and document link, then ask whether the proposal is still being considered. Set a review point for pausing or closing the deal using your team's policy.

    Test the path from proposal to delivery

    Use a sample proposal in a CRM trial. Walk it through a revision, a missed review date, completion, and a handoff. Check each step on the plan you would buy.

    • Verify what syncs

      Check whether document links, versions, signer status, and tasks update automatically or need manual entry. Test a failed sync and confirm that the owner can spot it.

    • Make the accepted version clear

      Link the final document and record the agreed scope, start date, delivery owner, and any open conditions. Keep payment tracking separate where needed.

    • Keep the outcome useful

      For a lost or paused deal, record the buyer's stated reason and any agreed return date. Avoid guessing why they declined.

    Frequently asked questions

    Check whether your CRM covers the document editing, approvals, signatures, and version history you need. If a separate tool handles those steps, test its connection to the CRM before choosing a plan.

    Use the review date agreed with the buyer. If there is no agreed date, set a reminder based on the buying deadline and ask when a review would be useful. There is no single deadline for every proposal.

    A view event shows that the document was opened. Confirm the required approvals, final terms, and completion steps before marking the deal won.

    Keep the current version linked to the deal and mark earlier versions as replaced. Record the requested change, the person responsible, and the next review date.

    Sources

    Provider documentation checked on 17 September 2026. Features and report options depend on the tool and plan.

    Related guides

    Try the full workspace free for 30 days. No credit card required.