Designing a Signing Workflow: Sequential, Parallel, Quorum and Bulk, and When Each Is Right

Once a company moves past one-off e-signatures, the question becomes workflow design: who signs first, whether signers can act at the same time, what happens when one of five directors is travelling, and how to send 400 offer letters without creating 400 manual tasks. Each pattern has a use and a failure mode. This guide sets them out with HR and vendor-onboarding scenarios. Position as of October 2026.

The four patterns

Sequential. Signers act in a fixed order; each receives the document after the previous signer completes. Use when a later signature depends on an earlier one (the counterparty signs first, then your authorised signatory) or when internal approval must precede the external signature.

Parallel. All signers receive the document at once; the document completes when all have signed. Use when order does not matter and speed does (two co-founders signing a vendor agreement).

Quorum (group signing). A defined subset of a group must sign (any two of five directors). Use for board-level documents where the resolution authorises "any two directors". The workflow must record which members signed and stop accepting signatures once the quorum is met.

Bulk. One signer executes many separate documents in one session (an HR head signing 400 offer letters; a company signatory executing 50 vendor renewals). Each document is a separate electronic record with its own hash and audit trail; the convenience is in the session, not in merging the documents.

Two scenarios

Vendor onboarding (sequential, then obligations). Intake form captures the vendor's details and MSE status. The template is populated; the e-stamp certificate for the executing state is generated and attached. The vendor's authorised signatory signs first (Aadhaar eSign or DSC), then your signatory. On completion the obligations (payment terms, renewal date, insurance certificate) are extracted into the register. Sequential ordering matters because your signatory should sign the version the vendor accepted, not the other way round.

Annual increment letters (bulk). HR generates 400 letters from the HRMS. Each is a separate document with the employee's name, revised salary and effective date. The HR head signs all 400 in one bulk session with a DSC or Aadhaar eSign; each letter carries its own signature and audit trail. Employees acknowledge with a platform signature or OTP eSign in parallel. Nothing in this flow needs stamping in most states, but check the state schedule for employment-related instruments.

Stamping in batches

Stamp duty is per instrument. Section 17 of the Indian Stamp Act, 1899 requires each chargeable instrument to be stamped before or at execution. In a bulk run of 50 vendor renewals, that is 50 stamp certificates, one per agreement, each attached before its signature request goes out. A single stamp certificate attached to a batch does not cover the batch.

Keeping the audit trail intact

Whatever the pattern, each document needs its own evidence record: hash at signing, each signer's identity events, timestamps, IP and device, dispatch and completion events. Under section 63 of the Bharatiya Sakshya Adhiniyam, 2023, the certificate that admits the record must identify that record and the system that produced it; a batch log that cannot be separated per document is a weak record. For quorum signing, the record should also show the group rule and which members satisfied it.

Two mistakes that invalidate batch execution

1. Merging documents to save signatures. Combining 50 renewals into one PDF with one signature produces one instrument with 50 schedules, which is not what the parties intended and complicates stamping and later enforcement. Sign 50 documents in one session instead.
2. Signing before approval completes. In a sequential flow, if the internal approval step is bypassed "to save time", the company signatory executes a version that was never approved. Build the approval as a gate before the signature request, not a parallel notification.

Design checklist

• Which pattern per template, and why.
• Who is the authorised signatory for each value band (delegation of authority).
• Stamping step before dispatch, per instrument.
• Reminder cadence (24 and 72 hours) and escalation owner.
• Quorum rules recorded in the workflow, not in an email.
• Audit trail exportable per document.

Where Legatio fits. Legatio supports sequential, parallel, quorum and bulk signing per template, attaches stamp certificates per instrument, and stores a separate audit trail for every document in a batch. The workflow design decisions above are yours.

Position stated as of October 2026. General information, not legal advice.