SECURINOS · Requests
Ask once. See what is still missing.
Turn a list of required documents into a clear collection process for you and the person sending them.
Organise your records · Collect what is missing · Share with purpose
The review checklist
Submission is a step, not a decision.
Missing
Submitted
Accepted
Accepted reflects your review of the record. Explain what needs correcting when asking for a replacement.
THE DETAILS THAT MAKE IT USEFUL
A useful checklist makes the work visible.
Create a useful checklist
Name the documents you need and explain what an acceptable submission looks like. Keep requests specific enough for the recipient to act without guessing.
A useful request tells the sender what to supply and why. Specify the record or period and describe an acceptable submission in plain language. A clear instruction reduces avoidable back-and-forth.
Give the recipient a browser link
The client opens an upload invitation and submits the requested documents without installing an application. They do not need to purchase a subscription.
Send the invitation through the communication channel you already use. The browser upload route lets the recipient respond to the document request without purchasing a staff subscription.
Track each item
Missing means no acceptable submission is available. Submitted means the file awaits review. Accepted means it has passed your review.
Use the three statuses to understand the work remaining. Missing identifies an outstanding item, Submitted identifies material to check and Accepted records your review outcome.
Request a replacement
If a scan is unreadable or a page is missing, explain the issue and ask for a corrected file. Acceptance remains the reviewer’s decision.
Be specific when asking for a corrected submission. Point out an unreadable scan, missing page or wrong period rather than simply saying the document was rejected.
Follow up clearly
Use reminders for outstanding items and keep the request in its client space. Reminders should explain what is still needed.
A follow-up is more useful when it names the outstanding item. Keep it connected to the checklist so the recipient can understand what remains rather than reconstructing the request from several messages.
An accounting example
Request a bank statement, invoices and receipts for a reporting period. Accept the complete files and return the statement for a clearer scan.
Review each record against the purpose of the collection. A complete set of invoices does not compensate for a bank statement that cannot be read; each item needs its own decision.
DOCUMENT WORK, WITH PEOPLE IN MIND
Make the next action clear to the sender.
A document request works best when the checklist is specific. Identify the record, relevant period and requirement so a recipient can act with confidence.
An unreadable or incomplete submission needs an explanation. A reason connected to the item is more useful than a general follow-up asking for documents again.
Keep collection separate from review. Submitted records still need checking; Accepted records reflect your own decision about whether the material meets the request.
ClientsA WORKSPACE WITH USEFUL CONTEXT
A useful request makes the review clearer too.
The sender needs a specific checklist and the reviewer needs an understandable outcome. Keep the status of each item connected to the actual record that was supplied.
When a replacement is needed, explain the issue. Missing pages, an unreadable scan and the wrong period are different corrections, and a useful message should make that distinction clear.
Reminders
SECURINOS, A WILLFRED PRODUCT
Give the next request a clear path forward.
Explore the document workflow and choose the package that fits the people doing the work.