Person 1 → Person 2 → Person 3. The order you define.
Sequential signing ensures documents are signed in the exact order you specify. Person 1 signs first, then Person 2, then Person 3 — each receiving an email notification only when the previous signer completes their part.
When creating an envelope, add recipients with an assigned order number (1, 2, 3, ...).
The envelope starts in 'draft' status, then transitions to 'pending' when sent.
An invitation email is sent ONLY to the recipient with order = 1.
After signer 1 completes, the envelope status updates to 'partially_signed' and signer 2 is notified.
This continues until the last signer completes — then the envelope becomes 'completed'.
All parties receive a completion email with the final signed PDF and Certificate of Completion.
Signing order is enforced at the database level — the signing endpoint rejects any attempt to sign out of order.
Each envelope has a current_signer_order field updated atomically via SQL transactions.
Race condition protection: concurrent signing attempts are serialized via SQLite's row-level locking.
If a signer declines, the envelope transitions to 'changes_requested' and all pending notifications are paused.
Most platforms offer parallel signing (everyone signs simultaneously). IUSign exclusively uses sequential signing because it matches real-world workflows: a manager must approve before HR signs; a witness must sign before the notary; a spouse must consent before the primary signer.
Each signer sees the document as it currently exists — with all previously applied signatures, timestamps, and annotations. They cannot see future signers' identities unless the sender chooses to disclose them.
If signer 3 tries to access the document while signer 1 is still pending, they receive a clear 'Not Your Turn' message with the current signer's identity and expected timeline.
Create your free account and send your first document in under 3 minutes.
Get Started Free