Void after a partial sign

One signature on a multi-signer envelope is not completion. Status stays sent. The document list still shows sent. Envelope admin Void envelope, Correct recipient, and Resend signing email stay available. Void stops every remaining signing and embed link. The person who already signed does not get an email. Their mark stays in the audit as signed. The envelope becomes voided. That is partial-void honesty: you can stop the deal after a partial sign, and you cannot pretend the first mark never happened.

The three verbs on a sent id are when to void, correct, or resend an envelope. The signer’s verb is correct, void, or decline an envelope. How several people share one envelope is send one envelope to multiple signers and sequential vs parallel signing. Desk help is Docs. This guide is the moment after someone has signed and the rest have not.

The FAQ says completed envelopes cannot be voided. Features names the same limit under envelope admin. Ask Inkpacket for void after a partial sign to open this article. Ask how to void an envelope to open help. Those phrases stay on the product screens. This article is the public version of why sent-with-a-signature is still in-flight.

Sent is still in-flight

• Sequential: the first signer finished. Later orders may still be waiting.
• Parallel: one of several invited people signed. The others are still outstanding.
• The badge is sent, not completed. Completed is everyone required.
• Only SENT envelopes can void, correct, or resend.

A later sequential signer who opens early sees This envelope is waiting for an earlier signer — first-signer waiting message. That wait is not a void and not a decline. If the deal dies during the wait, void the sent envelope. Do not wait for the next person to decline it for you.

What void does after a mark

• Marks the envelope voided. Every token dies. Reminders stop.
• Keeps the same envelope id. Webhooks can fire voided on that id.
• Does not email the signer. Tell outstanding people out of band.
• Does not erase the signed event. The audit still shows signed, then voided.

The filed stamped PDF is not the completed object you wanted. Completion never happened. If the work still needs a signature, send a new envelope from the PDF or template. That new send is a new envelope toward the monthly cap. Do not expect void to mint a replacement.

What you cannot do

• Correct the person who already signed. Correct updates an outstanding signer only.
• Un-sign. There is no “remove that mark and keep the envelope.”
• Void after completed. The API returns Completed envelopes cannot be changed.
• Void after expired or declined. Those closes already stopped signing.

If the outstanding email is wrong and someone already signed, correct the outstanding recipient — not the one who finished. If the PDF itself is wrong after a partial sign, void and start over. Fields and routing are locked once the envelope is sent. Do not treat the editor as a way to rewrite a sent envelope. Assign fields to each signer is placement, not an undo.

Decline is still the signer

An outstanding signer can still decline with a reason. One decline closes the whole envelope, including the person who already signed. That is the signer’s verb, not yours. Void is yours when the agreement is off and you do not want to wait for a refusal. The signed mark remains in the trail either way.

The click-path

1. Open the sent document at /desk/documents/:id. Read who signed.
2. If the deal is off, Void envelope. Record a reason if you want it on the audit.
3. Tell outstanding people the link will die. The product will not email them.
4. If only the next email is wrong, Correct that outstanding signer.
5. If the work still needs a signature, send a new envelope. Count it.

Public API: POST /api/v1/packets/:id/void on that sent id. The same 409s apply: completed, already voided, declined, expired, or not sent. Public API lists the routes.

Caps and what is not open yet

Void is not a send. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not un-void an envelope or complete a partial sign. The FAQ and envelope admin on Features use completed envelopes cannot be voided in the same words.

Stop the deal on the same id. File the audit as signed-then-voided if that is what happened. Then send the next envelope only if the work still needs a mark. Open a workspace on Free — see published pricing — and run a two-signer throwaway so partial-then-void is a pair you have watched.