Proposal versions, delivery and verified signatures
Select an authorised recipient, upload immutable proposal PDFs, resend or download versions and complete signature verification through native CRM proposals.
Guides in this workflow
Follow the guide that matches the exact action, filter, menu change or issue.
Check proposal workflow readiness
Verify that required core proposal and file tables/fields are available before using the workflow.
List eligible proposal contacts
Load active contacts belonging to the case client and containing a valid email address.
Select the verified proposal signatory
Choose the exact active client contact who must receive and sign the proposal.
Review the selected proposal recipient
Confirm name and email before upload or resend.
Confirm portfolio completion before upload
Ensure portfolio review is Completed or Not required and the journey has reached stage 5.
Upload a proposal PDF
Upload one real PDF file through the proposal panel.
Understand proposal PDF validation
Use a valid PDF no larger than 15 MB; non-PDF content is rejected.
Understand immutable proposal hashing
Recognise that each uploaded PDF receives a SHA-256 hash for version evidence.
Create a new proposal version
Upload a replacement as a new immutable version rather than overwriting accepted evidence.
Understand proposal supersession
Recognise that a replacement marks the previous active version and document as superseded and requires a fresh signature.
Understand native CRM proposal creation
Recognise that the module creates and links a native CRM proposal for delivery and acceptance.
Send the proposal to the client
Deliver the exact PDF and secure proposal/signature link to the selected recipient.
Understand Awaiting client signature
Recognise the active version state after successful client delivery.
Resolve Email delivery failed
Correct SMTP or recipient issues and use Resend where the version remains eligible.
Resend a proposal version
Use Resend on an eligible non-accepted, non-verification-failed version.
Download an immutable proposal version
Open the exact stored PDF associated with a proposal version.
Complete proposal identity confirmation
Require the client to provide identity details on linked native proposal acceptance pages.
Understand signature verification
Verify accepted status, signature file, first name, last name, email, date and IP against the selected recipient.
Complete accepted-proposal onboarding
Mark the proposal/document accepted, advance journey to stage 6 and add onboarding timeline/audit evidence.
Resolve Signature verification failed
Review mismatched or incomplete signer evidence; onboarding remains incomplete until corrected by an authorised workflow.
Process a declined proposal
Record the declined version/document, timeline event, landlord action and professional notifications.
Reconcile linked native proposals
Allow the case view to reconcile current native proposal states before displaying versions.
Review all proposal versions
Inspect status, version, recipient, hashes and timestamps without losing superseded evidence.