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.
Full Compliance Applications
Open guide →GuideCheck proposal workflow readiness
Verify that required core proposal and file tables/fields are available before using the workflow.
Open guide →GuideList eligible proposal contacts
Load active contacts belonging to the case client and containing a valid email address.
Open guide →GuideSelect the verified proposal signatory
Choose the exact active client contact who must receive and sign the proposal.
Open guide →GuideReview the selected proposal recipient
Confirm name and email before upload or resend.
Open guide →GuideConfirm portfolio completion before upload
Ensure portfolio review is Completed or Not required and the journey has reached stage 5.
Open guide →GuideUpload a proposal PDF
Upload one real PDF file through the proposal panel.
Open guide →GuideUnderstand proposal PDF validation
Use a valid PDF no larger than 15 MB; non-PDF content is rejected.
Open guide →GuideUnderstand immutable proposal hashing
Recognise that each uploaded PDF receives a SHA-256 hash for version evidence.
Open guide →GuideCreate a new proposal version
Upload a replacement as a new immutable version rather than overwriting accepted evidence.
Open guide →GuideUnderstand proposal supersession
Recognise that a replacement marks the previous active version and document as superseded and requires a fresh signature.
Open guide →GuideUnderstand native CRM proposal creation
Recognise that the module creates and links a native CRM proposal for delivery and acceptance.
Open guide →GuideSend the proposal to the client
Deliver the exact PDF and secure proposal/signature link to the selected recipient.
Open guide →GuideUnderstand Awaiting client signature
Recognise the active version state after successful client delivery.
Open guide →GuideResolve Email delivery failed
Correct SMTP or recipient issues and use Resend where the version remains eligible.
Open guide →GuideResend a proposal version
Use Resend on an eligible non-accepted, non-verification-failed version.
Open guide →GuideDownload an immutable proposal version
Open the exact stored PDF associated with a proposal version.
Open guide →GuideComplete proposal identity confirmation
Require the client to provide identity details on linked native proposal acceptance pages.
Open guide →GuideUnderstand signature verification
Verify accepted status, signature file, first name, last name, email, date and IP against the selected recipient.
Open guide →GuideComplete accepted-proposal onboarding
Mark the proposal/document accepted, advance journey to stage 6 and add onboarding timeline/audit evidence.
Open guide →GuideResolve Signature verification failed
Review mismatched or incomplete signer evidence; onboarding remains incomplete until corrected by an authorised workflow.
Open guide →GuideProcess a declined proposal
Record the declined version/document, timeline event, landlord action and professional notifications.
Open guide →GuideReconcile linked native proposals
Allow the case view to reconcile current native proposal states before displaying versions.
Open guide →GuideReview all proposal versions
Inspect status, version, recipient, hashes and timestamps without losing superseded evidence.
Open guide →