The contract that sat still for nine days
A supply agreement between three companies. Six people had to sign it: two board members on each side, plus a technical lead and a finance approver.
It went out as a single PDF attached to an email. Nine days later it had four signatures, two of them on different versions of the file, and nobody could say which copy was authoritative. The commercial terms had been agreed in a forty minute call. The paperwork took longer than the negotiation.
This is not a signature problem. It is a signing order problem, and it has two possible answers.
Parallel: everyone at once
All signatories receive the document at the same time. Each signs when they can. The envelope closes when the last one is done.
This is the faster option, and for most commercial contracts it is the right one. If six people each take two days to get around to it, parallel signing finishes in two days. Sequential finishes in twelve.
Use it when the signatories are peers. Two companies signing a mutual NDA. Co-owners selling a property. Board members approving the same resolution. Nobody's signature depends on anybody else's.
Sequential: one after another
Each signatory is notified only when the previous one has finished. The order is fixed when the envelope is created.
This is slower by design, and sometimes the design is the point.
Use it when the order carries meaning:
Approval chains. The technical lead confirms scope before finance commits budget. Finance commits before the board signs. Sending it to the board first would ask them to approve something not yet checked.
Counterparty then internal. Many organisations want the other side committed before their own directors sign. Sequential signing makes that structural rather than a matter of trust.
Delegated authority. Where one signature authorises another, the sequence is part of the legal reasoning, not an administrative preference.
Choosing between them
| Situation | Order |
|---|---|
| Signatories are peers, no dependency | Parallel |
| Internal approval must precede commitment | Sequential |
| You want the counterparty committed first | Sequential |
| Speed matters more than sequence | Parallel |
| Six or more signatories, no hierarchy | Parallel, or the contract will crawl |
There is a middle option that gets overlooked. Group the signatories: the two people from Company A sign in parallel with each other, but only after Company B has finished. You keep the meaningful ordering without forcing six people into a queue.
The part most platforms do not handle
Not every signatory on a contract needs the same kind of signature.
Consider that supply agreement again. The board members are committing the company to a multi year obligation, and their national law may require written form for it. The technical lead is confirming a scope annex. The finance approver is acknowledging a budget line.
Requiring the strongest signature level from all six means putting all six through identity verification. That is friction applied where it buys nothing, and friction is what made the contract take nine days.
The alternative is a mixed envelope: qualified signatures where the law or the value demands them, simpler signatures where they do not. One document, one workflow, different assurance levels per signatory.
This needs care rather than enthusiasm. Mixing signature levels within a single document is not universally accepted, and the answer depends on the governing law and on what each signature is doing. A qualified signature on the binding commitment and a simpler one on an internal acknowledgement is a defensible structure. Downgrading a signature that the law requires to be qualified is not.
Working out which level each signatory needs is the part worth getting right before the envelope goes out, and it depends on the contract, the jurisdiction and who is signing for what.
What a multi-party workflow needs to do
Beyond the order itself, a few things separate a workflow that holds up from one that generates chasing emails.
One document, one version. The moment a contract exists as attachments in six inboxes, you have lost track of which file is authoritative. Everyone should be signing the same object.
Visible state. Anyone coordinating the contract should be able to see who has signed and who has not, without asking. Most of the delay in multi-party signing comes from people not knowing it is their turn.
Positions fixed in advance. Six signature fields placed once, on a template, rather than dragged onto the page each time. Recurring contracts should not be reassembled from scratch.
Reminders that go to the right person. In a sequential envelope, only the current signatory is blocking. A reminder sent to all six is noise.
One audit trail for the whole envelope. Not six separate records to reconcile later. When the contract is questioned, the evidence should be a single document, not an archaeology project.
Where this shows up
Banking and financial services. Facility agreements, guarantees, mandates. Multiple internal approvals before the client ever sees the document.
Construction. Contracts and variation orders with the client, the main contractor and subcontractors. The order tends to be genuinely hierarchical.
Energy and utilities. Supply agreements with volume commitments, signed by commercial, legal and technical roles on both sides.
Telecoms. Enterprise service agreements with annexes, each needing a different approver.
The common shape is the same: several people, different roles, one document, and an order that is not accidental.
Doing this through your own systems
If contracts originate in a CRM or an ERP, the signing workflow should start there rather than in a separate tool nobody remembers to open.
Through an API, the sequence becomes part of the process: the system creates the envelope, sets the signatory order, applies the field positions from a template, and receives a callback when the state changes. The people involved stay in the system they already use, and the contract state stays visible where the deal is managed.
That is usually the difference between a signing process that people follow and one they work around.
Frequently asked questions
What is the difference between sequential and parallel signing? In parallel signing all signatories receive the document at once and can sign in any order. In sequential signing each person is notified only after the previous signatory has completed, following an order set when the envelope is created.
Which is faster for a contract with many signatories? Parallel, in almost every case. With six signatories each taking two days, parallel completes in about two days while sequential takes around twelve. Choose sequential when the order carries meaning, not by default.
Can different signatories use different signature levels on the same contract? Technically yes, and it is often sensible: a qualified signature where the law or the value requires it, a simpler one for an internal acknowledgement. It needs checking against the governing law, because mixing levels in a single document is not universally accepted and depends on what each signature is doing.
Do all signatories need to be in the same country? No. A qualified electronic signature issued by an EU Qualified Trust Service Provider is recognised in every Member State, and signatories outside the EU can obtain qualified certificates through remote identity verification. One envelope can cover signatories in several countries.
How do we keep track of who has signed? The envelope should carry its own state, visible to whoever is coordinating, with a single audit trail covering all signatories. Chasing by email is what makes multi-party contracts slow, and it is avoidable.
Can this run from our own CRM? Yes, through an API. The envelope is created from your system with the signatory order and field positions already set, and your system receives callbacks as the state changes. Users stay in the tool they already work in.
Coordinating contracts across several companies and approval levels? Talk to us.