How Time Zone, Reminder Interval, and Default Expiration Affect Requests

QCDS workspace timing settings are defaults for new Request drafts, not permanent rules that every Request must share. The workspace time zone, reminder interval, and expiration period are copied into the new transaction so the sender can review or override the Request-specific timing before it is sent.

What a New Request Receives

When QCDS creates a new Request draft, it reads the current workspace defaults and seeds three important values:

  • Time zone: copied into the Request timing data.
  • Unsigned request reminder: copied into the Request policy as the reminder interval.
  • Default expiration: used to calculate the draft's initial local deadline.

These values belong to the draft after creation. Later edits to workspace Settings are not a substitute for reviewing the actual Request you are about to send.

How the Default Deadline Is Calculated

QCDS resolves the saved workspace time zone, takes the current local date/time in that zone, adds the configured expiration days, and seeds the deadline for 23:59 local time on that resulting day.

For example, with a 30-day default expiration, a new draft receives a deadline 30 days ahead at 11:59 PM in the workspace time zone. QCDS later resolves the local timing to UTC for scheduled processing.

Review Exact Timing Before Send

During Request preparation, the Exact timing section lets the sender review or change:

  • Send mode — immediate or an exact future scheduled time.
  • IANA time zone.
  • Deadline local date and time.
  • Deadline warning offsets.
  • DST resolution when a local time is ambiguous.

Use Validate and Save Timing after making a Request-specific change. That override affects the draft/Request; it does not alter the workspace default for future work.

How the Reminder Interval Works

The workspace reminder interval is copied into the new Request policy. QCDS normally constrains it to 1–30 days. Once the Request is sent, the transaction keeps its own frozen policy rather than continuously rereading the workspace setting.

Automatic reminders are not generated merely because a number is saved. The Automatic Reminders Scheduled Task must remain enabled and must actually execute on schedule.

Changing the Workspace Default Later

A later Settings change affects newly created work and applicable fallback behavior. It does not rewrite the policy/timing evidence already frozen into sent Requests.

If an active Request needs more time after send, use the Request's supported deadline-extension workflow. QCDS records the extension in the Request history and reschedules the relevant expiration/deadline work rather than silently changing the original record.

One More Time-Zone Effect

The Dashboard's Requests used this month card also uses the workspace time zone to determine the current calendar-month boundaries for the signed-in account. A time-zone change near a month boundary can therefore change which sent Requests fall into the displayed month.

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.