Assign Every Interactive Field Before Sending a QCDS Request

Before Send Now, every signer-controlled field in the QCDS Request must resolve to a concrete signer. Assign fields directly to a saved Contact/signer choice or inherit assignment from another field where the field relationship supports it.

Which Fields Need a Signer

Interactive signer fields—such as Signature, Initials, signer information, text/date choices, checkbox/dropdown, and attachment fields—must resolve to a concrete signer before the Request can be sent. Creator-controlled document content such as Document Text/Request Text is handled separately and is not a signer assignment.

QCDS treats a signer as concrete when the role resolves to an actual saved Contact/current sender or another already-resolved participant identity in the Request snapshot. A generic placeholder role is not enough for the final send.

Assign Fields Efficiently

  1. In Prepare & Send, use Field Assignment to choose the signer.
  2. Use Assign selected for a subset, Assign unassigned to fill only unresolved signer fields, or Assign all when every eligible field belongs to the same signer.
  3. For precise control, select/right-click an individual field and change its assignment in Field Options.
  4. Use the signer strip and field colors/highlighting to confirm ownership on the PDF.

The signer search supports the signer choices already available in the current Request, including saved Contact details used by the assignment roles.

Understand Inherited Assignment

A field can store an assignment link to another field. QCDS follows that link to resolve the effective signer and rejects missing or circular links. The most visible example is Signed Date: it links to a specific Signature or Initials field and inherits that signer. If the parent signing field has no concrete signer, the linked date is also blocked.

Recognize Assignment Blockers

QCDS marks unresolved signer fields as Unassigned and shows an Unassigned count in the signer strip. Check reports field-specific fixes. Send Now refuses to proceed while assignment errors remain, and the server performs its own assignment/routing validation as the Request is frozen.

Do not “fix” a blocker by assigning a field to the wrong person just to make the warning disappear. Field ownership becomes part of the immutable Request evidence.

Verify Before Send Now

  • Every signer-controlled field highlights under the intended signer.
  • No Unassigned pill remains.
  • Linked Signed Date fields point to the correct Signature/Initials parent.
  • Routing order still makes sense after assignments are finalized.
  • Check passes before Send Now.

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.