View Rejected Documents in signNow

What view rejected documents means
View rejected documents means opening and reviewing files that a signer declined, returned, or could not complete in signNow. In practice, the document stays in the workflow history with its status, rejection reason, timestamps, and related audit data. Teams use it to understand where the signing process stopped, correct errors, resend the file, or keep a record for compliance and dispute review. The feature supports a clear chain of custody and helps users trace the full transaction without losing the original document state.
Why rejected document review matters
It helps teams resolve signing issues faster, preserve evidence, and document signer intent. Under ESIGN and UETA, rejected records can still support enforceability when the workflow history, consent, and audit trail are retained accurately.

Frequent rejection workflow issues
Users may not know why the signer rejected the document, which slows correction and resend steps. Missing timestamps or audit details can make it harder to explain the rejection in a dispute. Teams sometimes confuse a rejection with a completed decline, which affects follow-up and recordkeeping. Poor access controls can expose rejected files to people who should only see final records.
Who reviews rejected documents
Document teams
Legal, finance, healthcare, and real estate teams review rejected files to fix errors and preserve records.
Use cases
They use rejected lease forms, consent forms, approvals, and agreements that need correction or evidence.
People who benefit most
A director of NetSuite operations at Xerox may review rejected contract packets to keep approval flows aligned with ERP records, correct routing issues, and preserve a clear history for internal controls and downstream reporting. A COO at a real estate or venture-backed services firm may use rejected document history to identify signer friction, resend corrected forms, and maintain evidence for audit-ready transactions across mobile and desktop workflows.
- Best ROI. Our customers achieve an average 7x ROI within the first six months.
- Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
- Intuitive UI and API. Sign and send documents from your apps in minutes.
Core features for rejection review
Rejected document review gives teams a clearer record of what happened, why it stopped, and how to move forward.
Status visibility
Shows the rejection status, reason, and related activity in one place, so teams can correct issues without searching across separate systems.
Record integrity
Keeps the original document and its history intact, which helps preserve evidence for internal review and later disputes.
Audit context
Captures timestamps and signer actions, giving compliance teams a reliable timeline for rejected transactions.
Workflow recovery
Supports faster resend decisions by showing where the signing process stopped and what needs to change.
Clear follow-up
Reduces back-and-forth by making rejection details visible to the people who manage the document.
Document control
Helps teams keep rejected files organized alongside completed records for retention and review.
How rejection review works
The workflow records the rejection first, then lets users inspect the file history and decide what to do next.
Rejection occurs: The signer declines, returns, or cannot complete the document. History updates: signNow records the status and related activity details. Review details: Users open the rejected file and review the reason. Take next step: Teams correct the document, resend it, or archive it.
Quick steps to review rejection
Use a short review process to identify the issue, confirm the record, and decide whether to resend.
Find the file:
Open the document history and find the rejected file. Read the reason:
Check the signer note or rejection reason. Inspect the record:
Review timestamps and related activity details. Fix and resend:
Correct the file and resend it if needed.
Recommended review settings
Use controls that preserve rejection evidence, support access review, and fit U.S. compliance needs.
| Setting | Recommendation |
|---|---|
| Authentication method | SMS OTP |
| Signature type | SES |
| Audit trail | Enabled |
| Document retention | 6 years (HIPAA 45 CFR 164.530(j)(2)) |
| Encryption | AES-256 at rest |
Browser and device support
signNow works in modern browsers and mobile operating systems, with secure TLS-based access for review and signing tasks.
Desktop browsers Chrome, Firefox, Safari, Edge Desktop systems Windows 11, macOS 14 Mobile systems iOS 17, Android 14
For regulated workflows, managed Windows and macOS devices, current iOS and Android versions, and up-to-date browsers help preserve access controls, session stability, and audit consistency. Mobile apps can support review on the move, while desktop browsers remain the most practical option for document history and export tasks.
Security and compliance safeguards
Transport security:
Stored data:
Control reporting:
Security management:
Healthcare use:
Legal framework:
Real-world review examples
Customer stories show how rejected document history helps teams keep workflows moving while preserving evidence and context.
Xerox operations
A Xerox operations leader needed tighter routing control across NetSuite-connected workflows. Rejected documents stayed visible with their history, so teams could correct routing issues without losing the record.
- Rejected files stayed tied to ERP records.
- Teams corrected routing without losing history.
The workflow kept rejection evidence available for internal review, while the NetSuite connection helped preserve document context across systems and reduce manual follow-up.
Real estate founder
A real estate founder managing mobile closings needed a clear way to inspect declined lease and agreement packets. Rejected files remained organized, making it easier to fix errors and resend documents.
- Mobile review kept records organized.
- Corrected files could be resent quickly.
The review process supported faster correction cycles and preserved a usable record of what happened, which is important for lease packets, approvals, and other transaction files.
Best practices for rejection review
A consistent review process helps teams handle rejected documents without losing evidence, access control, or workflow clarity.
Keep reasons visible
Limit review access
Preserve the audit trail
Control resend steps
FAQ for rejected document review
These answers focus on plan limits, compliance questions, and access issues that affect rejected document review in signNow.
In signNow Business, rejected files remain in the document history with status details. If the reason is missing, check whether the signer left a note or whether the workflow was completed outside the standard signing path.
If a HIPAA workflow is involved, confirm that your account has a signed BAA and that the document retention and access settings match 45 CFR 164.312 and 164.530(j)(2).
If audit details are incomplete, verify that the document was sent through signNow rather than uploaded after signing. The audit trail records signer activity, timestamps, and document history for supported workflows.
The Business plan includes templates, mobile apps, and audit trails, while Business Premium adds bulk send. If you need advanced signer authentication or SSO, review Enterprise or Site License options.
For ESIGN and UETA enforceability, keep consent, signer intent, and the full audit trail together. A rejected document can still be useful evidence if the record shows who acted, when, and why.
If a file will not open on mobile, update the signNow app and use Chrome, Safari, Firefox, or Edge on a current iOS or Android device. Browser and app versions affect access to history and exports.
Vendor comparison for rejection review
The table compares core review-related capabilities across leading eSignature vendors using verified baseline information.
| signNow | DocuSign | Adobe Sign | PandaDoc |
|---|---|---|---|
| Audit trail | Yes | Yes | Yes |
| HIPAA support | Yes | Yes | Yes |
| Starting price | $8/user/mo | $15/user/mo | $14/user/mo |
| Envelope cap | No cap | 100/year | Not verified |
Rollout and retention timeline
This timeline combines rollout milestones with retention and policy facts that affect rejected document records.
Day 1:
Day 2:
Week 1:
7-day trial:
HIPAA retention:
ESIGN baseline:
UETA coverage:
Enterprise rollout:
Risks of poor rejection handling
Evidence gap
Attribution risk
PHI exposure
Enforceability issue
Inside the audit trail
The audit trail records each action on the rejected document so teams can verify what happened and when.
Authentication check:
Timestamp capture:
Document hashing:
Seal the record:
Audit logging:
Retrieval and export:
Pricing and feature snapshot
The comparison uses verified entry-level pricing and plan notes for annual billing, with unknowns marked as not verified.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting price | $8/user/mo, annual | $15/user/mo, annual | $14/user/mo, annual | $19/user/mo, annual | $15/user/mo, annual |
| Free trial | 7 days | Not verified | Not verified | Not verified | Not verified |
| Bulk send | Business Premium | Not verified | Not verified | Not verified | Not verified |
| Audit trail | Included | Included | Included | Included | Included |
| HIPAA compliance | BAA required | Available | Available | Not verified | Not verified |
Key performance indicators that demonstrate SignNow's proven track record.