The metric nobody watches until it hurts

Everyone measures how fast documents come back. Far fewer teams measure the number that actually decides whether a deal closes: the completion rate — the share of sent envelopes that reach every signature versus the ones that stall in limbo. A request that's opened, half-filled, and abandoned is not a small problem. It's a deal cooling, a credit already spent (remember: credits are decremented on send, not on completion), and a follow-up someone now has to chase by hand.

Completion rate is where turnaround, identity friction, and document design all cash out into a single number. This is a plain look at why signers drop off and the specific levers that move the number — a companion to reducing contract turnaround time, which covers the same problem from the speed angle.

Why signers actually drop off

Abandonment is rarely one dramatic failure. It's an accumulation of small frictions, each of which loses a slice of signers:

  • The request never arrived, or landed in spam. The single most common "the signer is ignoring me" case is one where the signer never received the email at all. If the invitation didn't land, no amount of good document design matters.
  • It's not clear what to do. A signer opens the document, doesn't see an obvious "start here," and closes the tab meaning to come back — and doesn't. Ambiguity is abandonment.
  • Too many required fields, or fields that don't apply. Every field the signer has to puzzle over is a chance to bail. A form that asks for data they don't have on hand stalls the whole thing.
  • Friction that isn't proportionate to the document. A routine form gated behind heavy identity verification reads as suspicious or annoying. Over-verifying a low-stakes document costs completions for no security gain.
  • It's not signable on the device they have. A signer reading email on their phone who can't sign on that phone will "do it later at my desk" — which often means never.
  • No deadline, so no urgency. Open-ended requests slide to the bottom of everyone's list. A request with no clock attached competes with everything else and usually loses.

Notice how few of these are the signer's fault. Completion is mostly something the sender designs for or against.

Lever one: make sure it lands and gets seen

Nothing else matters if the request doesn't arrive. Send from a recognizable, branded sender identity so the invitation looks legitimate rather than like phishing — which also heads off the "is this request legitimate?" hesitation that makes cautious signers freeze. Where a document is genuinely time-sensitive, deliver the link by text as well as email: an SMS signing link reaches a signer who never opens that inbox. And confirm delivery — the per-recipient delivery status tells a bounce from a silence, so you chase the right problem.

Lever two: design the document to be finishable

Once the signer is looking at the envelope, the document itself does the work:

  • Cut required fields to the genuine minimum. Every field you can pre-fill, you should. Merge fields that prefill the document before sending mean the signer confirms rather than composes.
  • Use conditional fields so signers only see what applies to them — hiding the branch that doesn't pertain removes a whole class of "do I fill this in?" stalls.
  • Place fields precisely and label them. Auto-placing signature and date fields from field tags puts the "sign here" exactly where it belongs, so nobody hunts for it.
  • Make the first action obvious. The signer should never wonder where to begin.

The discipline here is the same one that makes a good reusable template: a document you've tuned once for completion pays off on every send after.

Lever three: match friction to the stakes

Identity checks are insurance, and like all insurance they have a premium — paid in completions. The skill is proportionality. A routine internal form should ride on a plain emailed link. Reserve SMS one-time passcodes or KBA for the documents that genuinely carry the risk. Every unnecessary verification step is a place a signer stops. The audit chain and tamper-evident record give you defensibility without adding a single step the signer has to perform — that's the free security. Spend the friction budget where it buys real assurance, not everywhere.

Lever four: create a deadline, then follow up like a system

Urgency is a completion tool. Set a visible expiration so the request carries its own clock, and let automated reminders do the chasing on a cadence — a signer who meant to get to it gets a nudge instead of being forgotten. The point is to make follow-up a property of the system, not a task on someone's to-do list. Manual chasing is exactly the work that doesn't happen, and the envelope that isn't chased is the envelope that doesn't complete.

Lever five: watch the number and find the bottleneck

You can't improve what you don't look at. Watch completion rate the way you watch turnaround, and when a multi-signer envelope stalls, find which signer it's stuck on. The recipient progress and "waiting on" indicator turns "the deal is stuck" into "it's stuck on the third approver" — an actionable fact instead of a vague worry. On bulk sends, the per-batch signed/total rollup shows drop-off across a whole campaign, so you can remind the open ones in one motion rather than triaging by hand.

The takeaway

Completion rate is the number that decides whether a signature request becomes a closed deal or a stalled one, and almost every point of it is designed by the sender, not the signer. Make sure the request lands and looks legitimate; design the document to be finishable with the fewest required fields and precise "sign here" placement; match identity friction to the actual stakes; attach a deadline and automate the follow-up; and watch the number so you can find the exact bottleneck when an envelope stalls. Do those five things and the envelopes that used to die in limbo start crossing the line — faster turnaround, fewer wasted credits, and far less manual chasing.

This article is general product guidance. Your completion results depend on your document mix, audience, and how you configure each of these levers.