What the signer sees

Signers need no login, no account and no software. This page describes what they experience, so you can answer a signer’s question without having to send yourself a test envelope.

1. An email naming the document and the sender, with a signing button, the expiry, and an anti-phishing footer.
2. Identity verification. Before a signer proves who they are, the page names only the act of signing. It does not name the document, and it does not name or hint at the signer. What it does carry is your organisation’s logo and accent colour, the same ones the invitation email showed, because the one thing somebody needs before trusting a code is knowing whose page they are on. They enter a one-time code emailed to their address, and everything else appears once it is accepted. The code expires in minutes, allows a limited number of attempts, with the last one counted correctly in every language, and has a cooldown between re-issues.
3. Consent. A consent statement they accept before signing. It records their intent to sign electronically, and it tells any signer whose document needs a higher form of signature not to sign and to ask the sender instead. The exact wording each signer accepted is captured at the moment they were invited, so editing your consent text later never changes what an old certificate reprints.
4. The document. A long document tells the signer it is being prepared, with a count and a bar reading “Preparing your document, page 3 of 24”, and Start becomes available as soon as the first page is drawn, so they can begin reading while the rest catch up. Jumping to a page that has not been drawn yet waits with that same message rather than scrolling to blank paper. Signers page through every document in the request, are moved on to the next one still needing something from them, and see only the fields belonging to what is on screen. In a sequential request, marks already made by earlier signers are shown.
5. The signing screen. A sticky bar across the top carries the envelope name, progress and the primary action, so what to do next is never below the fold. A notices strip sits directly beneath it. On a desktop a rail down the side lists each page with what is still owed on it; on a phone the same list opens as a bottom sheet. The document sits in a framed well of its own, so it always reads as the document rather than as part of the page around it.
6. Signing. A Start action begins their walk through everything they have to complete. Previous field and Next field move between what is left, a running count (“3 of 7 required”) tracks progress, and it reads All required fields complete once nothing remains outstanding. Add your signature opens the signature pad, with Draw and Type tabs to choose between drawing a mark and typing one. The single binding action is Sign: pressing it commits the signature, and the signer watches it land on the page.
7. Finishing. Finish in the top bar raises the finish step. It signs nothing on its own: it is where the consent statement, the submit, and every reason the submit is being held are shown together, so a signer never has to hunt for what is stopping them.
8. Dates. Any date a signer types or picks is shown, stored, and inked into the signed document in the same form, 2026-08-04, at every moment. A date picker is one tap on every platform, and a typed date is checked as a real day.
9. Their copy. They can download the signed documents and the Certificate of Completion, either as one archive or as separate files, once they have verified their identity.

The whole signing surface is available in ten languages alongside English, so each signer reads it in their own language with nothing for you to configure. See Languages.

If a signer cannot open a document, they are told so in plain words, the request refuses rather than silently wedging, and the problem is reported back to you on the record. See Tracking and managing a request.