Signing workspace

eSign

Route signatures from document context, assign the right signers, follow pending requests, and keep signoff traceable from creation to verification.

Signature command center
Request routing Select documents, signers, due dates, and reasons from one flow.
Status visibility Track requests by me, to me, pending, completed, and due soon.
Verification Support trust in signed outputs with a verification workspace.
Designed from the codebase outward

A signing layer grounded in the documents teams already manage

eSign is not a disconnected add-on. It sits alongside document discovery and uses the same operational context to make signoff easier to request, review, and complete.

Request creation

Choose files and signers in one flow

Users can search documents, search signers, select both, and send signature requests with reason and due-date context.

Work queue visibility

Monitor the requests that matter to each user

Separate views for requests sent by me, assigned to me, still pending, and already completed make the workload more actionable.

Operational signals

See due-soon counts and pending volume at a glance

Summary metrics surface the health of signature throughput without requiring teams to manually reconcile multiple inboxes or trackers.

Compliance confidence

Verification supports trust in signed records

Signed outputs remain part of a governed operational process, not just a file that disappears after execution.

Next module

Move from signoff into live study execution

See how Study Hub connects sites, contacts, portals, subjects, and visit progress.