For migration agents and immigration consultants
Document collection for migration agents
A client sends five requested files. Two are fine. One is missing a page, another is unreadable, and the last one never arrives. The matter does not stall because the team forgot a passport exists. It stalls because the work of asking, receiving, checking, and correcting is scattered across email and chat.
ClientlyBase gives your team a checklist for the matter, a simple upload link for the client, and one place to see what is still missing, what needs review, and what was sent back for a replacement. You approve good files, reject the rest with a clear reason, and follow up only on the open items.
Where collection usually breaks down
Most teams already know what they need. The list lives in the last careful email, or in a spreadsheet the client never sees. The reply mixes questions, apologies, and files. A week later someone rebuilds the matter from attachments named IMG_4412.
A file in the inbox only proves that something was sent. It does not prove you can read the expiry date, that the months match, or that the document belongs to the person on the item. A reminder that says "just checking on the documents" makes the same mistake. Name the open items. Leave the accepted ones alone.
An example request clients can follow
This sample uses a fictional couple, Aisha Hassan and her partner Daniel Okonkwo, to show how a clear request looks in practice. It is not a real client matter and not a complete document list for every immigration case. Start from the requirements for the matter you are handling, then keep only what this case needs. A usable line names the document, the person, what must be visible, and what to do if they cannot get it yet.
- 01Sent back
Passport bio page, Aisha Hassan
Color photo or scan of the full page. All four corners, the document number, and the expiry date must be readable. Do not crop the page down to the portrait.
- 02Approved
Passport bio page, Daniel Okonkwo
Same standard as above. Upload Daniel's passport on this item, not in the same file as Aisha's.
- 03Sent back
Evidence of living together, March 2024 to February 2025
Lease, joint bills, or dated photos that cover the period named above. Label the month. A single weekend of photos does not cover a year.
- 04Outstanding
Police certificate, Aisha Hassan
The certificate for the country named in your matter notes. If the authority has not issued it yet, leave this item open and reply on the item with the date you applied.
- 05Uploaded
Identity document, Daniel Okonkwo (sponsor)
Photo of the full identity document, front and back if there is a back. The name must be readable. A photo of a card on a bench, with glare across the name, will be sent back.
The next morning, the folder looks busy and the matter is not ready. Daniel's passport is a full page and can be accepted. Aisha's passport is a close crop of the portrait, so the expiry date is gone. The relationship photos arrived as one unnamed bundle, with no months. Daniel's identity document is a photo of a card on a kitchen bench, and the glare covers his surname. The police certificate has not arrived. Five items were requested. One is actually done.
If both passports are marked complete just because they arrived, the missing expiry date shows up again when someone assembles the pack. With ClientlyBase, the team can keep the approved file, send Aisha's passport and the photo bundle back with instructions, and leave the police certificate on the outstanding list.
How document collection works in ClientlyBase
You can start a request in ClientlyBase, or from a monday.com board if that is where the matter already lives. The same collection steps apply either way.
- 01
Build a checklist for this matter
List the documents this matter needs, with a short instruction on each one. Save a template for a shape of matter you see often, then edit it before you send. Templates save setup time. Someone on the team still reviews the list against the current requirements for this client.
- 02
Send one upload link
The client opens a checklist page from the email and does not create a password. The link may ask them to confirm their email. Each file goes against its own item, so a passport and a pile of photos do not arrive as twelve unnamed attachments.
- 03
Keep outstanding items visible
The client can see what is still open, including an item you sent back. If a sponsor and an applicant should not see each other's evidence, send two requests. ClientlyBase can hold more than one request for the same client.
- 04
Review each file before marking it done
Open the upload against the instruction. Approve it, or reject it with a reason. The client replaces that item and does not resend the documents you have already accepted.
- 05
Remind only for open items
Reminders can be scheduled, or sent when you choose. They should name the open items. A reminder that repeats the whole original list teaches the client to skim.
- 06
Close the request when every item is approved
When every required item is approved, this collection request is finished. Your team can move on to the next stage of the matter with a clear pack of accepted files.
For the same approach outside migration work, learn how to request files from clients.
Why uploaded and approved are different
Teams lose time when every received file is treated as finished. Keep these states separate so the whole practice can see what still needs a person.
01
Outstanding
Nothing usable is on the item yet. Reminders should name these items.
02
Uploaded
A file has arrived and is waiting for review. It can still be the wrong document.
03
Sent back
A reviewer rejected the item with a reason. The client replaces the file on the same item.
04
Approved
Someone checked the file against the instruction and accepted it. This is the only state that means the item is done.
Sent back is the return path, not the step after approval. The replacement lands on the same item and stays in Uploaded until someone accepts it.
What to check before you accept a file
Use this as a review habit when you open an upload. It helps the team catch the problems that usually force a second round of follow-up.
Right document, right person
A birth certificate uploaded against a passport item is not progress. Neither is the sponsor's passport sitting on the applicant's item. Read the name before you open the next file.
The whole page, and readable
Edges, dates, and document numbers are the usual failures. A dark photo, a thumb over a corner, or a scan that cuts the expiry date has to go back, even if the rest looks familiar.
The period you asked for
If the item says March 2024 to February 2025, a statement for January 2026 does not satisfy it. Say which months are still missing instead of asking them to send the documents again.
One item, one clear copy
Forty photos in one email are not a finished item. Ask for date order, or one PDF with a date on each page, on the item those photos belong to.
Two corrections written as instructions
The reason on a rejected item should tell the client what to do next. These are sample notes a reviewer could put on Aisha's passport and on the photo bundle.
The photo is cropped, so the expiry date is missing. Please take a new photo of the full bio page, including all four corners. Check that the expiry date and the document number are readable, then upload it on this same item.
These photos arrived as one bundle, with no dates. Please upload them on this item in date order, or as one PDF with a date on each page. The item asks for March 2024 to February 2025. Photos from a single weekend do not cover that period.
Keep the accepted passport out of the message. The client should not have to guess which file you are talking about.
Choosing how to collect documents
A clear list and a shared view of open items matter more than the brand on the software. Some practices already get that inside their case tools. Others still chase supporting files in email. Use the comparison to see which approach matches the work you do every week.
Email and chat
Works well forA familiar client is sending one or two files you already discussed on a call.
Document collection in practiceThreads mix questions and attachments. The current version is whichever file someone opened last, and nobody has a shared view of what is still open.
A shared folder
Works well forClients reliably name files and put them in the folder you created, with little follow-up.
Document collection in practiceA wrong upload looks the same as a finished one. There is no checklist status, so reminders and corrections still happen outside the folder.
Practice software
Works well forYou want matters, agreements, billing, and case work in the system that already runs the practice.
Document collection in practiceMany practices still collect supporting files by email. If the product already covers checklist requests, review, and reminders, you may not need another tool.
ClientlyBase
Works well forYou want a named checklist, one upload link, a clear view of outstanding items, reminders, and a way to approve or send back each file.
Document collection in practiceBuilt for the document request and review loop, so it can sit beside the practice tools you already use for the rest of the matter.
If the matter already lives in monday.com
You do not have to change how you manage the rest of the case in order to collect the files. From a monday.com board, ClientlyBase can send the checklist using the email column on the item, a saved template, a request name, a due date, a reminder setting, and a short note to the client. The client still uploads through the link, sees what is pending, and replaces a file you reject. Statuses can sync back to the item as Pending, Uploaded, Approved, Rejected, and Not Applicable.
That connection is optional. The same request can be created in ClientlyBase on its own. See how to collect client documents from monday.com, or explore plans and pricing.
Questions practices ask before they try it
Does the client need an account?
No. They open the checklist from a link in the email and do not create a password. The link may ask them to confirm their email address before the page opens.
What happens when the file is wrong?
You reject that item and write the reason. The client uploads a replacement on the same item. Files you have already approved stay approved.
Can we reuse a checklist?
Yes. Save a request as a template and edit the items before you send the next one. Someone on the team should still check that the list matches the current requirements for that matter.
Can this sit beside our practice software?
Yes. ClientlyBase is built for checklist requests, uploads, review, and follow-up. Many practices keep their case tools for the rest of the matter and use this workflow for the document pack.
We already have practice software. Is this still useful?
If that system already shows outstanding items and lets you send one file back with a reason, you may not need another tool. If supporting files still arrive in email and chat, this workflow can sit beside what you already use.
Can we start from monday.com?
Yes. You can send the checklist from a monday.com board item, or create the same request in ClientlyBase on its own. Statuses can sync back to the board for Pending, Uploaded, Approved, Rejected, and Not Applicable.
Spend less time chasing client documents
Keep every document request, upload, and follow-up in one place. Review submissions, request corrections, and see what's still missing without digging through emails or messages. See how ClientlyBase helps teams collect documents.
Get started free