Designing a signing flow people finish

01 · Send one clear PDF

Send one clear PDF

Upload the file counsel has already adapted. Do not ask someone to sign a web page, a slide, or a draft that still has open brackets. The signer sees the PDF you sent. If the words are wrong, fix the PDF and send it again.

02 · Place only the fields you need

Place only the fields you need

Put a signature field and a date field on the person who must sign. Extra fields that nobody will use add noise. Each field belongs to one person, so the record can show who was asked to complete it.

People finish the request when the next action is obvious and the document in front of them is the document counsel approved.

03 · Write the email as an instruction

Write the email as an instruction

The invitation should say what the document is and what the person is asked to do. Email delivery and reminders are included on every plan. A reminder is a nudge, not a new agreement.

• ✓Is the PDF the final text?
• ✓Does each signer have the fields they must complete?
• ✓Does the email say what the document is?
• ✓Do we know where the completed file will be stored?

04 · Add identity only for a reason

Add identity only for a reason

A one-time code by SMS or WhatsApp, WhatsApp signing, and KYC are optional add-ons and are priced separately. Use one when the risk of the document calls for it. Do not turn every request into an identity check because the button exists.

05 · Stop when the file is done

Stop when the file is done

When everyone has signed, download the completed PDF and the completion record. The record includes a SHA-256 hash of the final file. That pair is the end of the flow, not a second homepage and not a legal opinion.