Voiding a sent document
3 min read
Updated Apr 12, 2026
Voiding is the right move when a sent package should no longer stay actionable. It prevents further signing on that workflow and records the action in the audit history.
Before you begin
A sent, in-progress, or otherwise active package
A clear reason the package should stop
A decision on whether a corrected version needs to be created afterward
Use void for real workflow changes
Void when the document content changed, the recipient list is wrong, or the package should not remain executable.
If the issue is only recipient timing, reminders or resend are usually the better choice.
Record the reason
When you confirm a void, include a concise reason if one is available.
That reason helps teammates and later reviewers understand why the workflow ended early.
Plan the next version
After voiding, decide whether you need to start a corrected draft or reopen an existing draft version.
Avoid sending a replacement package until you are confident the underlying problem is fixed.
Pro Tips
Void quickly if the wrong document or wrong recipients were used.
Keep void reasons factual and short.
If a document was already completed, treat follow-up as a new package instead of trying to revive the old one.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.
Need more help?
Our support team is here to assist you.