Sign This, Dammit!

Live Free, Sign Hard

ad slot · header · set NEXT_PUBLIC_ADSENSE_CLIENT

2026-04-19

Sequential vs parallel signing when several people must sign

If several people must sign, the choice is parallel or sequential — not whose squiggle looks nicest. Parallel is fast when everyone is equal. Sequence is when someone's yes only makes sense after someone else's. What wrecks it is sending parallel and then asking people to wait anyway.

When is parallel the adult choice?

Two parties who have finished negotiating. A board that already debated in a meeting and only needs to confirm the minutes. Three equal founders. A customer and a vendor who both saw the last draft in email already.

Then it is dishonest to pretend A must 'approve' before B may look. You fake a hierarchy you do not have, and you lose days. Send to everyone, set a deadline, send one nudge.

Parallel does not mean they see different files. They should see the same PDF. If you are still editing after the first send, you do not have a signing problem. You have a draft problem.

The calendar is part of choosing a mode. Three board members in a cabin with no signal is an argument for parallel with a long deadline, not for pretending sequence helps.

When does it have to be sequential?

Guarantor after the principal. Internal counsel before the CEO, because counsel should stop nonsense before the company's name is on it. An auditor who only attests after management signed the numbers. Public flows defined as steps.

Sequence is a brake. Use it on purpose. Each extra step is a chance someone is in a cabin with no signal.

Say in the email who is waiting on whom. The tool shows it, but humans read sentences. 'You get the link when Kari is done' cuts three support calls.

An informed party who still gets a signer field can bind the company without you meaning to. Roles are power. Not decoration.

What about hybrid without making porridge?

Company first (one person with signing authority), then all board members in parallel. Or vendor first, then customer in parallel with an internal approver as copy, not as signer. Copy is not a signature. Do not fake it.

Draw the flow in three boxes on paper before you click. If you cannot draw it, the tool cannot save you.

Hybrid goes wrong when 'approver' is really a signer, or the reverse. Roles are not decoration. They control who gets fields and who gets the finished file.

If the tool cannot do hybrid, split into two jobs on purpose and write that in the email. Two clean tracks beat one porridge.

How does this affect evidence and a fight?

In sequence, B can say: I signed the version A had already bound themselves to. That is the point. In parallel, someone can say: I did not know C had objections. Then the document was poorly explained, or you should have waited to send.

The log should show timestamps. If the tool pretends everyone signed 'at once' with no clock, that is a bad trail. SES needs time, not theatre.

PAdES in the final file covers the final bytes. It does not by itself tell the story of order. That story sits in the evidence pack. Download it.

What do you do when one person hangs?

One nudge. Then a phone call. Then drop or void if it is dead. Leaving a job glowing 'waiting on Per' for eight weeks teaches the team that status means nothing.

If Per is in sequence and everyone behind him waits, the cost is visible. Easier to escalate. In parallel you do not always see that three others are done and annoyed. Say it.

Change the email if Per never reads work mail. Do not send three addresses for the same human as three signers. Then you get three yeses from one person and a ridiculous trail.

Can you switch tracks mid-flight?

Rarely cleanly. Usual path: void, explain why, send again in the right mode. People who already signed often have to sign again. That is annoying and more honest than gluing on a fourth person in secret.

Some products have 'correct'. Use it only if you understand what happens to the hash and to people who are done. If you do not understand that, void.

Plan the mode as if you cannot change it. That makes you kinder to the other side and to future you who has to explain the trail.

What about board minutes, spouses, and suretyship in practice?

Board: often parallel after the meeting has happened. Sequence before the meeting is theatre — then the text should not have been sent. Spouses on a lease: parallel, same file, both fields. Suretyship: principal first, then guarantor. Not the reverse because the guarantor had time on Tuesday.

If counsel must look, they are an approver or a signer. If they only need a copy, they are copy. Three roles, three outcomes in the log.

Do not invent a fourth role called needs to know. Either a field, or copy, or Slack outside the tool. Mixing is how the evidence becomes a novella.

FAQ

What if number two refuses in a sequential flow?

Number three should not have a 'done' file. The job stops. You fix the text or void. Do not blast a parallel copy 'just to hurry'.

Can I change the order after someone has signed?

Often you must void and resend, or the trail lies. Some tools let you 'correct' recipients. Read what happens to people who already tagged.

Is parallel less 'valid'?

No. Validity is each party saying yes to the text they saw. Order is process, not an eIDAS level.

Pick parallel when you are done fighting about the text. Pick sequence when someone's yes presupposes someone else's. Say it in the email, not only in a setting.

If you just need a PDF signed without a subscription, that’s what STD is built for.

Norsk