Can I control the order people sign a document in?

Yes. Sequential routing emails signers one at a time in the order you set, and the next invitation only goes out when the previous person finishes. An out-of-turn signature is refused by the server, not merely hidden in the interface. Parallel routing emails everyone at once instead.

Can MostlySign chase signers automatically?

Yes. Automatic reminders nudge signers who have not acted, and each reminder rotates the signing link so an old forwarded email stops working. You can also set an expiry between 1 and 90 days, after which outstanding links stop working and the document is marked expired.

Signing order

Signed in the right order.

Q: Can I require a code before someone sees the document?

Yes. Any signer can be gated behind an access code that you share out of band. The document is not shown until it is entered and a wrong code on submission is refused. MostlySign stores only a hash of the code and never emails it.

Some documents only make sense signed in sequence — the candidate before the hiring manager, the tenant before the landlord, every partner before the chair. Set the order and MostlySign enforces it, rather than trusting everyone to wait their turn.

Build a signing order See pricing →

Two routings.

Chosen per document, so a workflow that needs both can have both across two envelopes.

Sequential

Signers are emailed one at a time, in your order. The next invitation goes out only when the previous person finishes, so nobody sees a half-signed document before their turn — and an out-of-turn attempt is refused by the server, not merely discouraged by the UI.

Parallel

Everyone is emailed at once and can sign in any order. Signatures accumulate on a working copy, so each person sees the ones already collected. The document completes when the last signature lands.

What runs the workflow while you get on with your day.

Automatic reminders. Signers who have not acted are nudged on a schedule rather than by you remembering. Reminders rotate the signing link each time, so an old forwarded email stops working.

Expiry. Set a window between one and ninety days. When it passes, outstanding links stop working and the document is marked expired instead of hanging open indefinitely.

Access codes. Any signer can be gated behind a short code you share out of band. The document is not shown until it is entered, and a wrong code on submission is refused. We store only a hash of it and never email it.

Webhooks, if you want them. Point an envelope at an HTTPS endpoint and every transition — sent, viewed, signed, completed, declined, voided — is POSTed to it, HMAC-signed so you can verify it came from us. Available with the signing API on Business.

Everything is on the record.

Every step is timestamped

Each transition is written the moment it happens — never inferred afterwards — with the actor and the originating IP.

The order is provable

The certificate of completion shows who signed when, so the sequence itself is part of the evidence and not just an intention.

Sealed at the end

When the last signature lands, the document is PAdES-sealed and RFC 3161 timestamped. How that works.

Set the order once.

Then let it run — reminders, expiry and all. Unlimited documents on Pro at $12 a month.

Build a signing order