4 min read
Updated Apr 12, 2026
Signing order changes how recipients receive access and how long a workflow can take. Sequential routes create tighter control, while parallel routes usually reduce turnaround time.
A draft with recipients already added
A decision about whether recipients must act in sequence
Awareness of any approval dependencies in the document
Sequential routing is best when a later signer should not act until an earlier signer or approver has completed their step.
This keeps review order explicit but can extend total completion time.
Parallel routing sends access to all relevant recipients right away.
That works well when signers are independent and do not need to wait on each other.
Routing affects reminders, recipient expectations, and status interpretation in Sent and Pending.
If you change routing late in the workflow, review recipients again before you send.
If just one person must approve first, use sequential routing and keep everyone else after that gate.
Explain the order in your custom message when recipients might be confused about why they cannot access the document yet.
Use parallel routing for straightforward acknowledgements or independent signer groups.
Use this as a quick signal while the public knowledge base is static.