Use Check to Validate a QCDS Request Before Send Now

Use Check as the field-level preflight for the current Prepare & Send state. It catches preventable builder problems before submission, but it is not the final server authorization performed by Send Now.

Run Check After the Request Is Prepared

  1. Finish the transaction-specific field placement and assignment work.
  2. Enter required Request Text values and review any Signed Date links.
  3. Choose the routing mode and signer order.
  4. Select Check.
  5. Use the inline issue indicators and Unassigned signer-strip item to correct every reported field problem.
  6. Run Check again until QCDS reports that the current fields are ready to send.

What Check Examines

In the current streamlined browser-only Request flow, Check first makes sure the displayed PDFs can be prepared, then evaluates the current field snapshot. It catches problems such as:

  • a retired or unsupported field type;
  • a field that extends outside the PDF page;
  • Document Text or Request Text with no text value;
  • a signer-controlled field with no concrete signer/contact assignment;
  • a Signed Date with no valid Signature/Initials link; and
  • a Signed Date whose linked signing field still has no concrete assignment.

What Check Does Not Prove

A clean Check result does not mean the Request has already passed Send Now. The streamlined Check action does not contact QuantaCade for the monthly Request allowance, does not consume an allowance, does not create an immutable Request, and does not send invitations.

Request Details such as the title, email subject, and active invitation message are checked separately when you press Send Now. The server then performs its own complete validation, including documents, participants, routing, deadline, Identity Verification availability, and frozen email/message state.

Use the Error Location to Fix the Right Thing

Field issues are tied back to the affected builder item whenever possible. Open that field's options, correct the assignment, link, content, or placement, then rerun Check. Avoid changing unrelated Template or entitlement settings to solve a local field error.

Treat Check as Preflight, Not Authorization

The safest sequence is: finish the builder, run Check until clean, review Request Details, then press Send Now. If Send Now still stops, read that server message separately; it may identify a participant, timing, Identity Verification, allowance, entitlement, or central-authorization problem that the browser Check is not designed to decide.

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.