How Migration Agents Collect Client Documents
A practical workflow for migration agencies: prepare the request, collect uploads, review and correct files, follow up on outstanding items, and finish the pack without living in email.
On Tuesday, a coordinator opens three threads for the same client. One has a passport photo from the weekend. Another has bank PDFs with no month labels. A chat message says the employment letter is coming later. Nobody can say, in one place, what has been reviewed and what still blocks the pack.
That is the usual document collection problem inside a migration agency. The work fails less often because staff do not know which documents exist, and more often because the request, the uploads, and the follow-ups live in different places.
This guide walks through an operational process you can adapt: prepare the request, send it clearly, collect uploads without losing context, review and correct files, follow up on open items, and finish the collection so the next stage does not start with an inbox search. It is not a visa eligibility guide and not a government document list.
Prepare the request before you ask for anything
Start from the matter in front of you. Confirm the pathway, the people who may need to provide evidence, and the date you need the pack ready. Copy your closest template, then edit it. Remove lines that do not apply. Add anything intake revealed, such as a prior name or a dependent who was not on the last similar matter.
Separate what is essential now from what depends on circumstances. Identity for each person on the matter usually belongs in the first wave. A second language certificate, an older address history, or a sponsor statement can wait until you know those people are involved. Asking for everything on day one often produces noise and late replacements.
Write each line so a client can finish it without guessing. Name the document, the person it belongs to, and what a usable copy looks like. A line that says "bank statements" invites random months. A line that says "Jordan, personal bank statements for the last six months, all pages, PDF or clear phone photos" gives staff something they can review against.
Put slow items early in the list when third parties or certificates will set the timetable. Clients often finish easy scans first and leave the hard items until someone asks again.
For adaptable category prompts and tracking fields, use the migration agent client document checklist. Keep this page focused on how the collection runs once you know what to ask for.
Send one clear request instead of a vague chase
A single organized request is easier to manage than attachments scattered across email and chat. When every file lives in a different thread, staff rebuild the outstanding list by memory each time a client asks whether they are done.
Tell the client which item each file belongs to, what format you can use, and when you need the first pass of uploads. Set a due date that matches your matter timeline, not an open-ended "when you can." A short covering note helps: what this request is for, that they can upload in more than one sitting, and that you will reply on specific items that need a better copy.
Clients should be able to see what remains outstanding. If they only receive a long original list every time you write, they will skim past the open items and ask whether they are done. The request itself should show accepted, open, and items waiting for replacement.
For sample wording patterns that work outside immigration work as well, learn how to request files from clients.
Collect documents without creating confusion
Clients rarely send everything on the first day. Plan for uploads that arrive in batches, and for matters where a partner, sponsor, or employer also provides files. Keep each submission tied to the checklist item it was meant for so a later employment letter does not get filed against an identity item by accident.
When more than one person uploads, put the owner on the line. If people should upload on separate checklists, send each person their own request link. ClientlyBase can hold more than one request for the same client; each person opens only the checklist in the link they receive.
Treat a new upload on an item as the current attempt for that item. Do not leave staff guessing which email attachment is the latest version. If a client uploads the wrong file, reject that item with a short note and leave the rest of the checklist alone. Moving the wrong file into a general "misc" folder without updating the item status is how packs look complete while the real evidence is still missing.
Review submissions properly
An uploaded file is not the same as an accepted file. Open each item against its instruction. Confirm the person, the document type, legibility, dates, and whether names match the rest of the pack.
- Uploaded means something arrived and still needs a human look.
- Accepted means the item meets the instruction for this matter.
- Needs replacement means the client should fix that item only.
- Outstanding means nothing usable has arrived yet.
Example: a skills letter that arrives as a photo of the first page only is uploaded, not accepted. A full PDF with the correct dates and letterhead can be accepted. A letter covering the wrong employment period needs replacement on that same line.
Review within a short, consistent window when you can. Waiting until every file arrives often means the client no longer has the original nearby when you ask for a better scan. Later specialist guidance can go deeper on review standards; for this workflow, the rule is simple: every upload gets a decision, and the decision sits on the item.
Handle incorrect and incomplete documents
Specific correction notes reduce repeated conversations. Name the item, say what is wrong in one sentence, and say what to send next on that same line. Leave accepted items out of the message.
If a bank export covers only three months when you asked for six, say so and ask for the missing months on that item. If a civil record belongs to a sibling instead of the applicant, name both people and ask for the correct file. If a reference letter is unsigned, ask for a signed copy rather than a vague "this is not enough."
When you need additional evidence that was not on the original request, add a new line instead of rewriting history in email. That keeps the outstanding view honest for the next person who opens the matter.
Follow up only on outstanding items
Track missing documents as a list of open items, not as a feeling that the client is "still working on it." Reminders should name what is still open. Repeating the whole original checklist trains clients to skim.
Choose a reminder cadence that matches the matter date, then stop reminding items that are already accepted. Keep the client's open list short enough to act on. If ten items are still open, send the list once and offer a short call to unblock the hardest two rather than sending daily noise on every line.
If a client goes quiet after several clear reminders, switch to a short call or a firmer note that still lists only the open lines. ClientlyBase supports scheduled or manual reminders for outstanding items. Use whatever cadence your agency can keep consistently.
When to remind, request a replacement, or wait
- Remind when the due date has passed, or a sensible gap has passed, and the item is still outstanding with no file waiting for review.
- Request a replacement when a file has been reviewed and fails the instruction. Do not send a general reminder for that item; send the correction note.
- Wait for review when a file is uploaded and a staff member has not opened it yet. Reminding the client in that window creates duplicate uploads and confusion.
- Stop chasing an item that is accepted or marked not needed, even if the client volunteers another copy.
Complete the collection before the next stage starts
Operational completion means the required items for this request are accepted, items that do not apply are marked not needed, and open questions about replacements are closed. Staff should be able to hand a clear pack to the next stage without reconstructing email threads.
A useful handoff note names the request, the date it closed, and any items that remain optional or intentionally deferred. The next person should not need to open five inboxes to learn what was accepted.
Completing document collection is not the same as a visa decision or a lodgement outcome. It only means your agency has the reviewed supporting files it asked for on this request.
Worked example: one request across one week
Sample scenario for an agency coordinator, Sam, and a primary applicant, Jordan, with a partner who also supplies one civil record. This is an operations story, not advice about any particular visa pathway.
Day 0. Sam edits a template for the matter, names owners on each line, sets a Friday due date, and sends one checklist link. The covering note tells Jordan they can upload in stages and that Sam will reply on specific items that need a better copy. Jordan confirms the email and starts uploading.
Day 1. Jordan's passport arrives and is accepted. The partner birth certificate is cropped on one edge. Sam rejects that item with a note asking for all seals and margins. The employment letter is still outstanding. Sam does not remind Jordan about the passport.
Day 3. Nothing new has arrived. Sam sends a reminder that names only the birth certificate replacement and the employment letter. Accepted passport stays out of the message.
Day 5. The replacement birth certificate is accepted. The employment letter arrives covering the wrong period and goes back with the date range restated. Jordan uploads a corrected letter the same afternoon. Sam reviews it before the end of day so the item does not sit in an uploaded limbo overnight.
Day 5 evening. Required items are accepted. Sam marks one unused optional item as not needed, closes the collection request, and leaves a short handoff note for the practitioner. The pack is ready for the next stage of work without an inbox search.
Common collection problems and what to do
| Problem | Practical response |
|---|---|
| Client sends one big email with mixed files | Ask them to upload each file against the named item. Confirm which item each attachment was meant for before you approve anything. |
| Upload is the wrong person or wrong year | Reject that item only. Name the person, the period, and what a usable file looks like. |
| Cropped scan hides a seal or page number | Send a short correction note on the same item. Ask for all edges and pages visible. |
| Partner and primary applicant both upload | Assign the owner on each line, or send separate requests when people should upload on different checklists. |
| Client says they are done while items are open | Reply with the outstanding list only. Do not restate accepted items. |
| Staff disagree on whether a file is good enough | Use one review standard for the matter and write the accept or reject note on the item so the next person can see the decision. |
Process checklist for the collection itself
Use this as an operational list for how the agency runs the request, not as a list of immigration documents.
- Confirm the matter type, people involved, and target date before the request goes out
- Edit a template so every line has an owner and a plain-language instruction
- Send one structured request instead of a vague email ask
- Review each upload against its instruction within a short, consistent window
- Reject unusable files with a specific replacement note on that item
- Remind only on outstanding items
- Mark items not needed as soon as they do not apply
- Close the collection when required items are accepted, then hand the pack to the next stage
Where ClientlyBase fits in this workflow
You can run much of this process in a careful spreadsheet. It breaks when several matters are open at once, clients reply across channels, and nobody shares one outstanding view. Structured requests help when you need named items, an upload link, item-level review, and follow-up on what is still missing.
ClientlyBase is built for that loop: checklist requests, client upload links, approve or reject with a reason, replacement on the same item, reminders for outstanding files, and reusable templates. Migration agencies can see the product framing in document collection for migration agents, or how teams collect documents from clients more generally. If you want to compare plans first, explore plans and pricing.
