Set the Request Title and Expiration

Use Request Details to give each QCDS transaction a clear Title and a future expiration date/time before you send it. Both values start from reusable defaults but belong to the specific Request once Send Now freezes the transaction.

Set a Clear Request Title

When you start from a published Template, QCDS seeds the Request Title from the Template title. Replace it when the transaction needs a more specific identifier—for example a customer name, agreement reference, project, or period.

The Title is required and the current Request Details field accepts up to 255 characters. It is also available to QCDS notification tokens such as {{request.title}}, so choose wording that will make sense in both the workspace and signer communications.

Understand the Default Expiration

QCDS seeds Expires from the workspace's Default expiration setting. If that setting has not been changed, the normal default is 30 days. The initial expiration is calculated in the workspace time zone for the configured number of days ahead at 11:59 PM local time.

Changing Expires in Request Details affects only the current Request. It does not alter the workspace default used by future Requests.

Choose the Expiration Carefully

  1. Open Request Details.
  2. Confirm or edit the Title.
  3. Use the Expires date/time control to choose the intended future local deadline.
  4. Continue to Prepare & Send and complete the remaining Request setup.
  5. Run Check, then use Send Now.

At send time, QCDS converts the local deadline using the workspace IANA time zone and freezes the exact UTC deadline into the Request. A deadline that is not later than activation is rejected.

Watch for Daylight-Saving Edge Cases

QCDS validates local wall-clock times against the selected time zone. A nonexistent time during a daylight-saving jump is rejected. An ambiguous repeated local time also requires an explicit earlier/later resolution in the underlying timing model; the streamlined Request Details screen does not expose that choice, so choose an unambiguous local time if the selected value is rejected.

What Happens at the Deadline

When a Request has a deadline, QCDS schedules the request-expiration action for that exact UTC instant. The deadline also informs secure signer-link lifetime. If an active nonterminal Request later needs more time, QCDS supports a guarded deadline extension that records the change in the timeline and updates still-usable invitation-link expiry instead of erasing the original history.

Verify Before Sending

  • The Title clearly identifies this transaction.
  • Expires is in the future and reflects the intended workspace-local date/time.
  • The email subject/message still make sense with the chosen Title.
  • After Send Now, Request Details shows the expected deadline and lifecycle state.

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.