Who this checklist is for
Teams collecting a defined packet of documents from clients, applicants or suppliers.
Free template · 10 checklist items
Turn “please send your documents” into a request a client can finish. This document collection checklist helps your team agree on the exact file, who provides it and what counts as a usable submission.
No signup required. Edit the CSV in Excel, Google Sheets or another spreadsheet.
Teams collecting a defined packet of documents from clients, applicants or suppliers.
Replace each example with a named document. “Bank statements for January to March, all pages” is clearer than “financial documents”. Decide which items are essential before you mark them required.
These are starting points to adapt, not universal requirements. The CSV contains the same items and instructions as this preview.
| Section | Item | Format | Provided by | When to request | Instructions |
|---|---|---|---|---|---|
| Request plan | Case or project reference | Internal note | Request owner | Before sending | Give this request a name that distinguishes it from other work for the same client. |
| Request plan | Purpose and requested date | Internal note | Request owner | Before sending | Explain why these files are needed and choose a realistic due date. |
| Example request | Registration certificate | File request | Company contact | If company registration is relevant | Ask for the certificate showing the legal entity name and registration number. |
| Example request | Statements for the specified period | Multiple file request | Record owner | If needed for this case | Replace this with exact start and end dates and ask for all pages. |
| Example request | Current certificate or policy | File request | Policy owner | If your process requires it | Name the type of certificate and the dates it must cover. |
| Example request | Other supporting evidence | File request | Named contributor | If needed for this case | Use one request per document type instead of a single miscellaneous upload. |
| Instructions | Accepted file types and file count | Internal note | Request owner | For each file request | Tell the client which formats are accepted and whether several files are expected. |
| Review | Readable and complete | Reviewer check | Reviewer | After upload | Check legibility, missing pages and whether the file matches the request. |
| Review | Correct person or company and period | Reviewer check | Reviewer | After upload | Do not accept a clear file that belongs to a different entity or year. |
| Correction | Replacement instructions | Review note | Reviewer | If an item needs fixing | Name the problem and the replacement needed. Keep accepted items unchanged. |
Use each document row to configure a file request, with the period and acceptance instructions in its description. Allow multiple files where a statement pack needs them. Reviewer checks belong in your review process, not in questions the client must answer.
After setup, share your application link. Applicants access their own checklist through an email link with no password to create. Your team reviews the submitted answers and files and requests corrections on the items that need them.
Create your workspace, adapt the questions and file requests, and collect the answers in one place.
Create your workspace14-day free trial · No card needed