When a recipient decides to reject a document within an envelope, the platform immediately halts that specific document's progress and sends an email notification to all parties involved. However, what happens to the rest of the transaction depends entirely on whether they rejected the entire package or just a single file.

The Rejection Process: Step-by-Step

1. Reason for Rejection: When a signer clicks the reject button, the platform prompts them to type in a brief explanation of why they are declining to sign.

2. Instant Notifications: As soon as the rejection is submitted, an automated email is sent to the sender and all other recipients on the envelope, keeping everyone transparently informed.

Partial Rejection vs. Total Rejection

The Verified platform handles multi-document envelopes intelligently. If your envelope contains more than one file, a rejection operates on a file-by-file basis:

1. Partial Rejection (Some documents are rejected)

If an envelope contains multiple distinct documents and the recipient only rejects one or two of them, the transaction isn't entirely dead.

• The Outcome: The remaining approved documents will continue moving forward through the signing workflow as normal. Only the specific file that was flagged will be set aside.

2. Total Rejection (All documents are rejected)

If the recipient rejects every single document inside the envelope, the platform flags the transaction as compromised or completely declined.

• The Outcome: The entire envelope workflow is automatically aborted and permanently locked. The invitation links become completely inactive, and none of the documents within that envelope can be signed by anyone.

💡 What should the sender do next?
Check the automated notification email to read the recipient's feedback. If you need to make changes, correct the errors on your original desktop files, create a brand-new envelope, and send the updated documents out for a fresh round of signatures.