Start a New QCDS Request from a Published Template

A normal QCDS signing transaction starts from a published Template. Choosing Use opens a temporary Request editor seeded from that exact published Template version, then lets you set transaction details, assign signers, review fields, and Send Now.

Confirm the Template Is Ready

The Template must have an available published version. A draft-only, unpublished, unavailable, or deleted Template cannot start the normal streamlined Request workflow. If Use is unavailable, return to the Template builder, correct validation issues, and publish the current version first.

Open the Request

  1. Open Templates in the QCDS sender workspace.
  2. Locate the published Template you want to use.
  3. Choose Use.
  4. QCDS opens Request Details for a new transient Request.

The Request starts from the published Template snapshot. QCDS also seeds current workspace/request defaults such as the title, expiration, reminder interval, time zone, and the sender's current Signer Invitation message source.

Set the Transaction Details

In Request Details, review the Title, Expires value, email subject, and invitation message. These edits apply to this Request only; they do not rewrite the saved Template or the reusable email template.

Choose Prepare & Send when the transaction details are correct.

Prepare the Signers and Fields

  • Assign every interactive field to the intended signer.
  • Use the signer strip to review field ownership and routing order.
  • Enter every Request Text value that belongs to this transaction.
  • Enable Identity Verification for eligible signers when that workflow is required and available.
  • Choose Everyone at once or Sign in order as appropriate for the Request.

Check and Send

  1. Choose Check.
  2. Correct every blocking field/assignment problem.
  3. Review the PDF and Request Details one final time.
  4. Choose Send Now.

Send Now is the transaction boundary. QCDS creates and freezes the immutable Request, performs the server-side authorization/validation path, and queues invitation delivery. After success, the browser returns to the Unsigned Requests view.

Do Not Confuse Delivery Trouble With Request Creation Failure

If QCDS reports that the Request was created but invitation delivery needs attention, preserve that Request and troubleshoot delivery. Do not immediately create a duplicate: the immutable Request may already exist even though one or more invitation emails need correction or retry.

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.