Void vs expire on an e-signature request

Voiding is a decision with a reason

A sender voids when the document is wrong, the deal changed, the wrong person was invited, or the transaction is dead. Because it is deliberate, the interface offers a reason field, and using it is worth the ten seconds: the reason is the only part of the record that explains why a document that was sent never completed. A void is refused only where there is nothing left to withdraw, meaning a completed envelope or one already voided. Declined, sent, partially signed, expired and failed envelopes all accept it.

Expiry is the absence of a decision

Every envelope carries a thirty day life from creation, and no screen offers a different date. A nightly sweep finds outstanding envelopes past that point, marks the remaining recipients as expired, marks the envelope expired and records the event. Nothing is emailed, because there is nothing to say beyond the passage of time. The effect on a recipient is that their link, which worked yesterday, now returns a message saying the request has expired, with no explanation of what they should do next.

What each looks like to a recipient

Both produce a plain page rather than a signing screen, and the wording is the only difference the recipient sees. A withdrawn document says it was withdrawn by the sender, which at least implies somebody made a choice and can be contacted. An expired one says the request has expired, which invites the recipient to assume they missed a deadline. Neither page tells them what to do, so a sender who voids something a counterparty was expecting should send an email explaining it rather than relying on the page.

Partly signed documents

The awkward case is an envelope where somebody has already signed. Voiding it does not unsign anything: the record of that person's signature stays in the trail and the intermediate stamped file remains stored. What ends is the process, so the document never becomes a completed agreement. The person who signed is not notified that their signature came to nothing unless they still held a live link, which is a good reason to tell them directly if the document mattered to them.

Choosing between waiting and withdrawing

If the document is still wanted, chase rather than void, because a fresh envelope restarts the identity checks and asks people who already signed to sign again. If the document is wrong or dead, void promptly rather than letting it expire, since a withdrawn document with a stated reason reads far better in a file than one that simply ran out of time. Letting things expire quietly is how businesses end up unable to say whether a deal was declined or forgotten.

What the record keeps either way

Nothing is deleted. The envelope remains with its status, the audit trail keeps every event that occurred before the end, and any intermediate stamped versions stay retrievable. Only drafts can be deleted, which is deliberate: once a document has been sent to somebody, the fact that it was sent is part of the history. That is why the status list distinguishes voided, expired, declined and failed rather than collapsing them into one closed state. A short weekly habit keeps the list honest. Filter for anything still awaiting signature, chase what is genuinely live, and void what is not, with a reason written in plain words. Ten minutes of that a week prevents the situation most businesses eventually find themselves in, where the outstanding list is thirty documents long and nobody can say which three still matter. It also means the record of each dead transaction says why it died, which is the part that helps a year later when somebody asks what happened to a deal that was almost signed. The same review is the moment to notice a document sent to the wrong address, since an envelope sitting untouched for a week with no opening recorded is usually a delivery problem rather than a slow signer.

Questions people ask