Order matters.
Sequences, parallel signing, roles and approvals.
On paper, the order of signatures took care of itself: the document moved from desk to desk and each person signed when it reached them. In the digital world, order is a design decision. It can be made well or badly, and that choice has legal, technical and practical consequences worth understanding before setting up the first workflow.
Sequential or parallel
There are two basic ways to order signers, and most real processes combine both.
- Sequential. Each person receives the document once the previous one has finished. It is slower, but each signer sees what the earlier ones signed, and the order is fixed.
- Parallel. Everyone receives the document at the same time. It is faster and works when the signatures are independent of one another, as when the members of a board approve the minutes.
Why order matters
For legal reasons
Whoever signs a contract first is usually making an offer; whoever signs afterward is accepting it. Many organizations prefer the counterparty to sign first, so that they are not bound by a document the other side may still decline. Likewise, an internal approval makes sense before the legal representative signs, not after.
For technical reasons
In a PDF, each new signature is added as an incremental update to the file and covers everything that came before, including earlier signatures. The first signature can also determine which changes are permitted afterward, such as filling in certain fields or adding more signatures, through the certification and field locking mechanisms defined in the ISO 32000 standard. A poorly planned order can cause a later signature to invalidate an earlier one in the eyes of the validator.
For practical reasons
If the hardest signer to reach sits at the end of a long sequence, the document can stall for weeks. Putting first the person most likely to request changes spares everyone else from having to sign twice.
Roles beyond the signer
| Role | What they do | What must be recorded |
|---|---|---|
| Signer | Becomes bound by their signature. | Identity, version viewed, acceptance and time. |
| Approver | Authorizes the document to proceed, without becoming personally bound. | What they approved and when. |
| Reviewer | Can request changes before the signatures. | The versions and the changes requested. |
| Form filler | Fills in missing data, such as a number or a date. | Which fields they completed. |
| Copied recipient | Receives the final result. | That it was delivered to them. |
What else needs to be decided
- Deadlines and reminders. How much time each person has, and what happens if they do not respond.
- Rejections. If someone declines, whether the workflow returns to the start, stops, or moves on to someone else.
- Substitutions. Who may delegate their signature, to whom, and with what record.
- Changes midway. If the document changes after a signature, every earlier signature must be repeated.
No one should sign a different version from the one everyone else signed. If the content changes, the workflow starts over, and the record explains why.
The order of signatures is a design decision with legal, technical and practical effects. It pays to distinguish signers from approvers, reviewers and recipients, to decide in advance what happens with deadlines, rejections and changes, and to record each step in the order in which it occurred.