Send a QCDS Request in Signing Order

Choose Sign in order when each signer must wait for the preceding signer to finish. QCDS freezes the signer-strip sequence into a chain of routing stages and activates the next signer only after the current stage is satisfied.

Set the Sequence Before Sending

  1. Assign every signer-controlled field to the correct signer.
  2. Set Routing to Sign in order.
  3. Use the signer strip’s up/down controls or drag-and-drop ordering to arrange Signer #1, Signer #2, and the remaining signers.
  4. Click each signer and verify the correct fields highlight.
  5. Run Check, then review the order once more before Send Now.

How QCDS Freezes Sequential Routing

At Send Now, QCDS builds the concrete participant list from the used signer roles in their saved sort order. Sequential routing creates one stage for each actionable participant and connects each stage to the next.

The first stage has no incoming dependency, so it is the root stage. QCDS activates that participant and queues the first invitation while later participants remain pending.

How the Next Signer Becomes Active

When the active participant completes the frozen required action, QCDS marks that stage completed. The routing progression service then activates the successor stage, marks its participant available, and queues that signer’s invitation. The same process repeats until the final routing stage is complete.

This is why the signer order must be correct before Send Now. The sequence becomes part of the immutable Request routing rather than a cosmetic list that can be casually rearranged afterward.

Do Not Expect Later Signers to Receive an Immediate Invitation

In a sequential Request, later signers are intentionally not active at the start. If Signer #2 has not received an invitation while Signer #1 is still incomplete, that is normal routing behavior rather than a delivery failure.

Verify the Live Request

  • Request Details shows Sign in order.
  • Only the current stage’s participant is available to act.
  • The timeline records routing-stage activation/completion as the Request advances.
  • After a signer completes, the next signer becomes available and the next invitation is queued.
  • Final completion waits until the required sequential stages are satisfied.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.