Tracking signature status
The eSignatures page gives you four places to check where a request stands: the metrics cards at the top, the status tabs, the Status column in the table, and a per-recipient breakdown inside "Details & audit trail" on each row's menu.
The metrics cards
Three cards sit above the table:
The tabs
Below the cards, four tabs filter the table: "All", "Awaiting", "Signed", "Drafts". "Awaiting" includes requests with status "awaiting", "sent", or "expiring". A badge only shows on a tab when it has at least one matching request.
Status badges in the table
A declined request shows the signer's reason directly beneath its badge, and a voided request shows the reason your firm gave when voiding (if one was entered). "Sent" and "awaiting" share the same blue "Awaiting" badge; on multi-signer requests, the "Signed by N of M" line beneath the badge adds a "Next:" marker naming whoever the request is currently waiting on.
Per-recipient detail
Open "Details & audit trail" from any request's "..." menu (any status, not just signed) to see every recipient with their own state: Waiting (not yet their turn), Invited, Viewed (they opened the document), Signed, Declined (with their reason), Voided or Expired, each timestamped. CC recipients are listed too, marked as receiving the completed copy only. The full audit trail follows underneath.
Viewing is tracked from the moment a signer opens the document after verifying their identity, so "Invited" versus "Viewed" tells you whether a chaser is needed because they haven't looked at it, or because they looked and stalled.
Searching
The search box ("Search agreements or clients…") matches against the document name and client name only. It won't find a request by signer email, status text, or date.
The "Due" date
The Action/Details column shows the request's real expiry date (set in Step 1) or "No expiry set". After the expiry passes, the request auto-expires, the outstanding signers' links stop working, and your firm is emailed that it expired unsigned.
Staying current without refreshing
The page updates live: if a teammate sends or voids a request, or a client signs remotely, the table and counts refresh automatically without you needing to reload the page.