The real reason documents don't get signed

Ask anyone who sends agreements for a living why a document is still open and the honest answer is rarely "they refused." It's that the email got buried, the signer meant to do it after lunch, and then a week passed. Most signing delay is silence, not rejection. The signature is a thirty-second task competing with a full inbox, and it loses.

The instinct is to fix this with willpower: a reminder note in your calendar, a "just circling back" email you write by hand. That doesn't scale past a handful of envelopes, and it puts the burden on the busiest person in the loop — you. The platform should do the chasing. Two settings handle almost all of it: automatic reminders and a hard expiration.

Automatic reminders: chase on a cadence, not on a whim

A reminder is a re-send of the signing invitation to the recipients who still have action pending. Done by hand it's awkward and inconsistent; done automatically it's a quiet, predictable cadence that recovers days per agreement.

Hosting Sign sends reminders on a schedule you set — say day 2, day 5, and day 9 after the envelope goes out. The mechanics that make this work in practice:

  • Only the people who are holding things up get pinged. In a sequential routing order, a reminder goes to whoever's turn it currently is, not to signers who already finished or aren't up yet. Nobody gets nagged for someone else's delay.
  • The reminder uses your branding and copy. Custom email body templates let you override the reminder wording per organization, so the nudge reads like it came from you, not a generic robot.
  • Every reminder is recorded. Each send is written to the envelope's audit trail as its own event, so the history shows exactly how many times a signer was contacted and when.

The goal of a good cadence is to be persistent without being annoying. Three reminders over nine days is usually enough; a daily barrage trains people to ignore you.

Expiration: a deadline that actually closes the loop

Reminders push a document forward. Expiration stops it from drifting forever. An expiration date is a hard cutoff after which the signing link no longer works and the envelope is marked expired.

This matters for two reasons that have nothing to do with being pushy:

  1. Stale signatures are a problem. A compliance acknowledgment signed three months late and quietly counted as on-time is worse than an unsigned one — it creates a false record. A hard expiration means a document either gets signed inside the window or it visibly didn't.
  2. A deadline focuses attention. "Please sign when you get a chance" drifts. "This expires Friday" gets done. The cutoff is a forcing function, and pairing it with reminders ("expires in 2 days") turns the last nudge into a real prompt.

When an envelope expires, the sender is notified and the envelope's final state is recorded — so an expired document is a clear, auditable outcome, not a mystery.

A note on credits

One billing detail worth planning around: credits are consumed when an envelope is sent, not when it completes. Reminders don't cost extra credits — they're re-sends of an envelope you already paid to send. But an envelope that expires unsigned still consumed its credit on send. That's not a reason to skip expirations; it's a reason to set a sensible window and let reminders do their job inside it, so the credit you spent actually turns into a finished signature.

Putting it together

A workflow that finishes itself looks like this:

  1. Send the envelope (from a template, ideally, so setup is instant).
  2. Set reminders on a cadence — day 2, day 5, day 9.
  3. Set an expiration that gives a real but finite window — often 7 to 14 days.
  4. Watch per-recipient status to see who's outstanding, and let the reminders do the chasing.
  5. Wire an envelope.completed webhook so the moment the last signer finishes, the signed document files itself downstream.

You set it once and the system handles the follow-up. The deals that would have died in silence get closed — not because anyone nagged harder, but because the chasing stopped depending on a human remembering to do it.