Signing Analytics
E-SignSeal's analytics help you understand how efficiently your team executes contracts and where the friction points are. The Dashboard surfaces the key metrics described on this page, enabling data-informed decisions about your contract workflow.
Dashboard cycle-time chart with bottleneck signers panel side by side
Metrics reference
Active contracts
What it is: The count of contracts currently in In progress status across your entire workspace.
How to use it: A rising active-contract count with a flat or declining completed count suggests that contracts are being sent but not completing — investigate the bottleneck-signers panel and the needs-attention table.
Completed (90 days)
What it is: The count of contracts that reached Completed status in the rolling 90-day window.
How to use it: Track this number week over week as a measure of contracting throughput. A drop may indicate signer bottlenecks, an increase in declines, or more contracts expiring before completion.
What it is: The median number of days from contract send to the last signature, calculated across all contracts completed in the last 90 days.
Why median, not average: A single outlier contract (for example, a deal that took 60 days because a signer was on leave) can skew the mean significantly. The median gives a more representative read of typical signing speed.
How to use it: Compare the overall median cycle time against individual template averages (in the cycle-time bar chart) to identify which agreement types take longest to execute. Use that insight to investigate whether the issue is in the terms, the signer set, or the document length.
Expiring ≤ 3 days
What it is: The count of in-progress contracts whose expiry date falls within the next 72 hours.
How to use it: This is a leading indicator of potential expirations. Select the card to jump to the needs-attention table filtered by expiring contracts. For each expiring contract, send a manual reminder to the pending signer(s) immediately.
Declined
What it is: The count of contracts that entered Declined status in the last 90 days.
How to use it: A higher-than-expected decline rate often means the contract terms are being circulated too early (before terms are agreed), or that the wrong signer is being added. Review decline reasons from the Audit tab of each declined contract to identify patterns.
Cycle-time bar chart by template
The bar chart breaks cycle time down by template, showing you where signing speed varies across contract types.
Reading the chart: Each bar represents one published template. Bar height = average days from send to completion for contracts from that template in the last 90 days. Templates with fewer than 3 completed contracts show a dashed bar to indicate the sample size is too small for reliable benchmarking.
What to look for:
Templates with consistently long cycle times may benefit from content simplification (shorter documents are read and signed faster).
Templates with short cycle times despite complex terms may indicate signers are not reading carefully — worth reviewing the consent audit logs.
Bottleneck signers
The bottleneck signers panel identifies the individuals whose pending signatures are holding up the most contracts.
How the ranking works: Signers are ranked by the number of contracts currently awaiting their signature. Ties are broken by the age of the oldest pending contract (longest wait first).
What to do: If the same person appears week after week, consider:
Checking whether they are aware of the contracts pending their signature (send a manual reminder)
Discussing with their manager whether delegation is appropriate
Reviewing whether they were added as signers correctly or if a different person should sign
Data scope and permissions
Workspace Admins see metrics across all contracts in the workspace.
Template Managers see metrics across all contracts.
Senders see metrics scoped to contracts they sent.
All metrics use the data E-SignSeal has stored within your Atlassian site. No analytics data is sent to external services.
Next steps