Proposals and estimates · Workflow guide

Proposal Acceptance & Digital Signature Checks

Use the proposal’s supported acceptance workflow with the correct version and recipient. Treat signature evidence as part of a controlled record, not as a status that staff should casually set on a customer’s behalf.

Audience: Authorised staffPermission-awareReviewed 16 November 2026

Where to start

Open the intended proposal and review its client-facing acceptance options and Status / Activity.

Before you start

Availability depends on the enabled proposal or compliance workflow and its configuration. Confirm the intended acceptance method and the authority of the recipient before sending.

Follow these steps

  1. Review the proposal reference, related customer or lead, currency, scope, terms and validity dates. Confirm which version is being issued.
  2. Preview the client-facing document and check the recipient and available acceptance or signature controls. Do not assume every proposal uses the same signing method.
  3. Send the approved proposal through the authorised communication workflow. Keep confidential links limited to the intended recipient.
  4. Allow the authorised recipient to complete the required review and acceptance. Do not imitate their signature or record an unsupported acceptance.
  5. Review the saved status, activity and available signature or acceptance evidence. Investigate incomplete or conflicting evidence before proceeding.
  6. Preserve the accepted version and follow the separate conversion, billing or delivery process only when the agreed conditions are satisfied.

Preserve the meaning of acceptance

A workflow label, staff update and customer signature can represent different events. Keep the evidence needed to understand who acted, on which document and through which process.

A signature does not establish payment or completion of the work. Legal effect and required assurance depend on the circumstances; the organisation should obtain appropriate advice for its agreements.

Check the result

  • The issued version and recipient are correct.
  • The acceptance evidence is retained and consistent with the status.
  • No invoice, receipt or delivery milestone is assumed solely from acceptance.
Access and data safety

Use your own authorised account. Review the intended customer, record and visibility before making a change. Never bypass permissions or treat a saved status as proof of payment, signature or delivery.