Back to Blog

How to Measure Electronic Signature Completion Rates and Find Drop Off Points

BulkSigner  ·   ·  3 min read

How to Measure Electronic Signature Completion Rates and Find Drop Off Points

Your team sends 100 agreements, but only 60 reach completion. Before changing the signing process, check which requests you counted, how long recipients had to respond and where the remaining agreements stopped.

An e-signature completion rate measures the share of eligible signing requests that reach your defined completion point within a stated period. A consistent calculation helps operations teams investigate delays and compare changes fairly.

Define the group before calculating the rate

Start with a group of requests sent during the same period. Analysts call this a cohort. You might group all requests first sent from 1 to 7 October and give each request seven days from its send time to complete.

Wait until every request has had those seven days before finalising the comparison. Counting a request sent yesterday alongside one sent a week ago gives recipients different opportunities to finish.

Decide how you will handle tests, duplicates and cancellations. Exclude clearly identified test requests and duplicate sends under a documented rule. Keep genuine requests that recipients later cancel in the main denominator and report their outcome separately. Apply the same rules to every comparison.

Calculate completion at the request level

Use this formula for your defined group and observation window.

Completion rate = completed eligible requests ÷ all eligible requests × 100

Consider a fictional reporting example. Your team sends 120 requests. After excluding 10 tests and 10 duplicate sends, 100 eligible requests remain. Sixty complete within seven days, giving a completion rate of 60%.

If eight genuine requests were cancelled, keep those eight visible in the results. Removing them simply to improve the percentage would change what the rate measures. Record the remaining 32 requests as incomplete at the seven-day cutoff, with their available statuses.

Count each request once. Record reminders as follow-up events under the original request reference.

Separate agreements from individual signers

An agreement that needs two signatures remains incomplete when only one person has signed. Track request completion and individual signer completion separately so your report explains both progress and unfinished work.

Define completion against the actual workflow. If required approvals form part of that workflow, include them in your definition. A signed field alone may not represent the finished process.

Find the stage that needs attention

Where reliable event records exist, review delivery, opening, verification and signing. Keep stage counts at a consistent level, such as unique signer invitations, and explain exactly what reaching each stage means.

Mark unavailable data as unknown. An unopened invitation could involve a delivery problem, an absent recipient or a request waiting for an earlier signer. Follow up before assigning a reason.

Group incomplete requests by document type and signer group. Check device patterns where reliable data exists, and show how many requests lack device information. An open event may identify the device used to access a document without explaining why signing stopped.

Combine the records with support feedback. For example, repeated questions about a mandatory field give your team a specific issue to investigate.

Keep a small reporting record

The following template uses the fictional example above.

Reporting fieldEntry
GroupRequests first sent from 1 to 7 October 2026
Observation windowSeven days from each request’s send time
Completed requests60 within the observation window
Eligible requests100 after documented exclusions
Completion rate60%
Cancelled requests8, included in the denominator
Other incomplete requests32 at the cutoff
Data sourceRequest records and checked event history

If your platform lacks the required report, maintain a controlled spreadsheet with one row per request. Record its reference, send time, completion time, cutoff status and exclusion reason where applicable. Use available records or manual checks to verify each entry.

Test one change and compare fairly

Try a focused improvement, such as clearer instructions or removing an unnecessary field after approval. Keep the document group, eligibility rules and observation window comparable.

Measure completion alongside turnaround time. For completed requests, calculate the median time from sending to completion and state that scope. Show incomplete requests separately so fast completions cannot hide a growing queue.

SignuluOne offers electronic signing, approval workflows and signing audit trails. Explore the available records with your team when planning workflow measurement. Visit SignuluOne.

Prefer a live walkthrough?

We will show the flows behind these articles on your own documents.