Conditional signature routing — when signer B depends on signer A

Conditional routing activates different signers based on document content or earlier decisions.

Common patterns

### High-value requires extra approval "If contract value > $50K, route to CFO. Otherwise, route to department head."

### Optional signers "If spouse listed, require spouse signature. Otherwise, skip."

### Jurisdiction-specific "If employee in Massachusetts, include non-compete clause + additional signature. Otherwise, standard flow."

### Rejection routing "If signer 1 rejects, route back to sender. If signer 1 accepts, proceed to signer 2."

Platform support

Conditional routing is an advanced feature. Support varies:

• DocuSign — supported on Business Pro+
• HelloSign — limited support
• PandaDoc — strong support with content-based rules
• SignBolt — supported on Business tier via API; UI coming Q4 2026

Implementation via API

SignBolt's API supports conditional routing via post-signing webhooks:

`` POST /api/v1/envelopes {...} → on signer 1 completion webhook → evaluate condition → POST /api/v1/envelopes/{id}/route with next signer ``

When to avoid

Conditional routing adds complexity. For most workflows, a linear sequential flow is clearer and easier to debug.

Next

• E-signature workflows
• SignBolt API conditional logic