The anxious gap between "sent" and "signed"

You send a contract for signature and then... silence. Did they get it? Did it land in spam? Are they reading it, ignoring it, or stuck on a field they cannot figure out? Without visibility, the only tools you have are a nagging gut feeling and a follow-up email that risks being annoying. The whole value of sending documents electronically is that you do not have to guess — every request carries a live status, and learning to read it turns that anxious gap into a calm, informed wait.

This is about how to track a signature request from the sender's side: the statuses a document moves through, what each one tells you, and how to react to where a document is actually stuck instead of chasing it blindly.

The statuses a request moves through

A signature request isn't simply "out" or "back." It moves through a sequence of states, and a good dashboard shows you exactly which one each document is in:

  • Sent / delivered — the request reached the signer's email. Delivered specifically means the email server accepted it, which is your first reassurance it didn't bounce.
  • Viewed / opened — the signer clicked the link and opened the document. This is the most useful single signal: it separates "they haven't seen it" from "they've seen it and haven't acted."
  • In progress — on a multi-document or multi-field packet, the signer started but hasn't finished.
  • Signed / completed — the signer applied their signature. On a multi-recipient routing order, this may mean one party is done and the document has moved to the next signer.
  • Completed (all parties) — everyone has signed and the document is final and sealed.
  • Declined — the signer actively declined to sign. That is information, not failure: it tells you to pick up the phone rather than keep waiting.
  • Voided / expired — you cancelled the request, or it hit its expiration date before completion.

Each status answers a different question, which is why "is it signed yet?" is the wrong way to check. The right question is which status, because the status tells you what to do next.

Reading "viewed but not signed"

The single most actionable status is viewed but not signed. It rules out the most common worry — that the email never arrived or sat in spam, the failure mode covered in the signer says they never got the email — and tells you the signer has the document in front of them and simply hasn't finished. That changes your move entirely. You don't resend; you gently surface whether something is blocking them: a clause they want to discuss, a missing piece of information, or just a busy week.

Contrast that with sent but never viewed after a couple of days, which points back at delivery — wrong address, spam folder, an out-of-office signer — and warrants a different fix. Same lack of a signature, two completely different causes, and the status is what lets you tell them apart.

Let the system chase, and watch the trail

Tracking is not a job you should do by manually refreshing. Two things do it for you:

  • Automatic reminders. Rather than monitoring a stalled request yourself, set reminders and an expiration so the platform nudges a viewed-but-unsigned signer on a schedule and closes the request if it goes cold. You intervene only when the automated cadence isn't enough.
  • The audit trail. Every status change — sent, opened, signed, declined — is recorded with a timestamp in the audit trail. That is both your live tracking view and, later, your evidence: it shows not just where the document is now, but the full timeline of how it got there.

For a sender managing many documents at once, this is the difference between a dashboard that tells you exactly which three requests need a human touch today and an inbox you have to reconstruct by hand.

Tracking at scale and after completion

If you send the same document to many signers — a policy update, an onboarding form — you track the batch the same way, watching the completion rate climb and zeroing in on the handful still outstanding rather than the whole list. And when you need tracking to drive something downstream automatically, an envelope.completed webhook lets the "done" status itself trigger the next step — file the document, update your CRM, kick off fulfillment — so completion isn't just visible, it is actionable without anyone watching the dashboard.

Once a document hits completed, tracking hands off to retention: the sealed file and its audit certificate get stored for the long term, so the record you tracked to completion is the record you can still produce years later.

The takeaway

You never have to wonder where a signature request stands. Every document moves through a clear sequence — sent, viewed, signed, completed, or declined and expired — and reading the specific status tells you exactly what to do: resend a never-viewed request, gently follow up a viewed-but-unsigned one, call a signer who declined. Let automatic reminders chase the stalled ones and the audit trail record every step, and you trade inbox anxiety for a calm, accurate picture of every document in flight. Send your first tracked request and watch it move from sent to done.

This article is general guidance, not legal advice.