What document requests solve
Tax intakes, onboarding packs, and recurring collections often die in inbox chaos — or stall after a first upload that needs corrections. Document Requests replace ad-hoc attachments with a structured checklist and one secure link. Explore the capability on Document requests on Capabilities or the document collection solution.
Recipients do not need an Opcilo account. They open the link, complete checklist items, and upload. You stay in control of review inside your workspace — including asking for corrected files when something is wrong.
The trustworthy collection lifecycle
From creating a request through final confirmation:
Create the request
List each document you need. Optionally attach blank forms or templates per item so clients know exactly what to return.
Share a secure link
Send the request link (or invite) to your client. The link is the collection surface — no portal signup wall for the recipient.
Receive submissions
Clients upload completed files against checklist items. New files enter a Received state awaiting your review.
Review each item
Mark each received file Verified or Rejected (with a reason). This is requester review — it is not the same as sealing Document integrity or checking a person’s identity.
Send a review response
When review of the latest submission is complete, send one summary response. Rejected items reopen so the recipient can fix them; verified items stay locked.
Resubmit rejected items only
The recipient returns via a private link, replaces only rejected files, and submits again. Corrections do not consume an extra MaxSubmissions slot.
Final confirmation
When required items are Verified, the request reaches completion. You can then seal accepted files in your normal sealing workflow when you need a public verification code. After you seal or share, accepted files can also land in Business Inbox (/app/inbox) for the receiving workspace.
- 1
Create request
- 2
Share secure link
- 3
Recipient submits
Safe path - 4
Review: verify or reject
Safe path - 5
Send review response
- 6
Resubmit rejected only
Risk point - 7
Final confirmation
Safe path
Review can repeat after a resubmit until required items are confirmed.
Who document requests are for
- Accountants collecting tax packs without endless “please resend” email threads.
- Client-facing teams running onboarding document lists with a clear correction path.
- Operations teams that need a repeatable checklist instead of ad-hoc attachments.
Plans and availability
Frequently asked questions
Do recipients need an Opcilo account?
No. They open the secure upload link, complete the checklist, and upload without creating an account.
What happens if I reject a document?
You provide a reason, then send a review response. The recipient can resubmit only the rejected items; verified items stay locked.
Does verifying a request item seal the file?
No. Request-item Verified is your review decision. Sealing for a public verification code is a separate step when you choose to seal an accepted file.
Can I attach blank forms to checklist items?
Yes. Optional blank forms or templates per item help clients return the right completed files.
Which plan includes document requests?
Pro and Team. It is a Pro capability for intake and client collections.
How are clients notified about a request or review response?
You can deliver the request via Email, SMS, or WhatsApp when those channels are enabled. Review responses use the same notification channels. Details are in multi-channel notifications.