E-signature

Contracts stay attached to the application record.

SponsorPlat's v1 e-signature flow is designed around organizer-uploaded PDFs, embedded signing, webhook verification, and archived signed PDFs.

Dropbox Sign primaryDocuSign fallback flagLegal review needed
Signature packetLegal review needed
1

Organizer sends PDF

Contract packet starts only after the application is approved.

2

Sponsor signs

Dropbox Sign embedded signing is the primary v1 path.

3

Organizer countersigns

Fully signed webhook archives the PDF and moves the application to Signed.

Flow summary

Upload PDF

Organizer creates a draft contract packet after an application is approved.

Send for signature

Dropbox Sign creates an embedded request with sponsor then organizer signer order.

Archive signed PDF

The completed PDF is stored in the contracts container and linked back to the application.

Review posture

Legal review needed

Contract language and e-sign consent are drafts

This site describes product workflow only. It does not say a particular template is legally sufficient or that a signature is enforceable in every circumstance.