Sequential against parallel signing

The dependency test

Ask whether any signer needs to see another signature before making their own decision. A finance director signing after a project lead has committed, a witness attesting a signature they must observe, a guarantor signing once the principal has: those are genuine dependencies and the order exists for them. Two companies signing a mutual agreement have no dependency at all, and neither does a set of shareholders approving the same resolution. Where there is no dependency, sequencing converts a one day task into a five day one for no benefit.

What sequencing costs

Time, mostly, and it compounds. Each hop adds the recipient's own delay, which for a busy person is measured in days rather than hours, so a four party sequential document routinely takes a fortnight. It also concentrates risk: one person on leave stops everybody behind them, and nobody later in the order even knows the document exists yet. Where an order is genuinely needed for only one pair of signers, consider whether the rest can be positioned together rather than strung out behind them.

What parallel signing gives up

Control over what each person sees. In a parallel arrangement everybody receives the document as it was sent, so a party who would have wanted to see the other side's signature before committing does not get that. It also produces the occasional awkward case where somebody signs a document the other party then declines, which is untidy but rarely harmful. For most commercial agreements those costs are trivial next to the days saved, which is why parallel is the better default.

Mixed requirements

The setting applies to the envelope rather than to individual recipients, so a document is either sequential or it is not. Where two people belong at the same stage, giving them the same position in the order lets them be invited together while still sitting behind an earlier signer. Where the workflow genuinely needs a mixture that the ordering cannot express, that is usually a sign the transaction is two documents: an internal approval and an external agreement, each with its own recipients.

Enforcement is not cosmetic

With ordering on, the invitation is only issued to the lowest outstanding position, and every signing route checks that it is that recipient's turn before doing anything. Somebody who obtained a link early cannot sign ahead of their turn, because the check happens on the server rather than in the interface. That matters for documents where the sequence carries meaning, since an order enforced only by not sending an email would be no order at all.

Setting it, and one thing to watch

The choice is a switch on the envelope before sending, and it cannot be changed afterwards along with everything else about a sent envelope. Note that a newly created envelope has ordering enabled in the underlying record while the preparation screen shows the switch as off, so the safe habit is to set it deliberately either way rather than trusting the default. The definition of the setting itself, and what turning it on means for invitations, is covered on the signing order page. It is worth agreeing the arrangement with the other side before sending anything complicated. A quick message saying who signs first, and why, prevents the common exchange where one party waits for an invitation that was never coming because they sit third in an order nobody told them about. For a document with more than two parties, listing the sequence in the covering email costs one line and saves several rounds of chasing. Where the parties disagree about who goes last, that disagreement is usually about the commercial position rather than the software, and it is better surfaced before the document goes out than discovered halfway through. That conversation takes a minute, and it is often the difference between a document signed this week and one signed next month.

Questions people ask