ClientlyBase LogoClientlyBase
ClientlyBase LogoClientlyBase
Blog·Guide

Review and Replace Migration Client Documents

How migration agents and immigration consultants review uploaded client documents, spot quality problems, request clear replacements, and keep accepted items closed.

Tomas Novak uploads three files after a consultation. One identity scan is crisp and complete. One employment letter belongs to his sister Katarina by mistake. One status record is cut off at the bottom edge, so the expiry date is missing. The question for the migration practice is not whether anything arrived. It is which files can be accepted for the requested items, and what Tomas needs to replace.

This guide focuses on that review-and-replace stage: what staff should check, how to decide the next action, how to ask for a corrected file, and how to keep the rest of the collection moving. For the broader end-to-end workflow, see how migration agents collect client documents. For organizing evidence readiness before professional review, see immigration supporting evidence collection.

Before you open the file

Review starts with the request, not the attachment. Confirm which checklist item the upload belongs to, which person it should cover, and any date range or instruction the client was given. If an earlier version already exists on that item, know whether you are comparing a replacement or looking at a first attempt.

Without that context, staff often accept a clean-looking file that answers the wrong ask, or reject a usable document because nobody remembered what was requested. Named checklist items make this matching step faster than searching through a mixed email thread.

Document review checklist

Use these checks on each uploaded item. They support operational review for your collection request. They do not replace a practitioner's professional judgment about whether the file is sufficient for a particular matter.

Copies the checklist as plain text.
  1. Requested document name matches the checklist item
  2. Correct person or entity (applicant, partner, sponsor, employer)
  3. Correct date, period, or version where the request specified one
  4. All expected pages present
  5. Edges and key details readable (names, dates, seals, reference numbers)
  6. File is the document category that was asked for, not a lookalike
  7. Not an obvious duplicate of another open item
  8. Outcome recorded: accept, replace, clarify, or leave outstanding

If you are still building the original ask, start from a clear category list such as the migration agent client document checklist, then apply this review list once uploads begin.

Decide what happens next

An upload is not the same as an accepted document. After the checklist, choose one clear outcome for that item:

  • Accept when the file matches the request and is readable enough for your team to use.
  • Ask for a replacement when the problem is specific and the client can fix it.
  • Ask for clarification when you are not sure what the client intended to send.
  • Leave outstanding when nothing usable has arrived yet, including when a third party still holds the record.
  • Flag for professional review when the file looks complete for collection but still needs the migration agent or consultant to judge the next step.

Record the outcome on the item. That habit prevents a second staff member from treating every upload as finished work.

Correction decision table

Different problems need different client instructions. Use the table as a starting point, then adjust to the matter.

ProblemReview decisionWhat to tell the clientWhat happens next
Cropped edges or unreadable detailAsk for replacementName the missing edge, seal, or fieldKeep other accepted items closed
Wrong person on the documentAsk for replacementName who the item was for and who appeared insteadDo not treat the wrong-person file as that item
Wrong date range or outdated versionAsk for replacementRestate the required period or current versionLeave the item outstanding until the matching file arrives
Missing page in a multi-page scanAsk for replacementSay which page is missing and how to send a complete scanReject only that checklist item
Looks plausible but needs practitioner judgmentAccept for collection, flag for professional reviewNo client action unless the practitioner asks for moreDo not call the collection stage complete if review is still open
Client uploaded a note instead of the documentClarify, then replaceAcknowledge the note, restate the actual document neededKeep the item outstanding

Write a useful correction request

Vague: "Please resend your documents. Some of them are not clear."

Specific: "Please replace only Tomas's status record. The current scan is cut off at the bottom, so the expiry date is not readable. Upload a full-page scan with all edges visible to the same checklist item. Katarina's accepted identity document does not need to be sent again."

A useful correction names the item, states what was wrong, describes the replacement, points to the upload link, and confirms whether other accepted items stay closed. Ready-to-adapt wording lives in migration agent document request email templates.

Receive and review replacements

When the corrected file arrives, review it against the same requirement that failed the first time. Keep the replacement tied to the original checklist item so staff are not hunting across threads for "the new version."

Do not reopen unrelated accepted items just because one file needed another attempt. If the second upload still fails, say so clearly and keep the count of attempts visible in your notes so the next coordinator is not starting from zero. ClientlyBase supports reject with a reason and replace on the same item. Do not invent broader version-history claims beyond that replace loop.

When an employer or institution must issue the corrected letter, brief the client on the details that letter must include, then leave that one item outstanding until the usable file lands. For general request craft outside migration work, learn how to request files from clients.

Worked replacement scenario

Sample matter for Northbridge Migration. Coordinator Elena Vargas is collecting supporting documents for Tomas Novak. This is an operations example, not a required evidence list.

  1. Upload: Tomas uploads a status record against the correct checklist item.
  2. Review: Elena applies the checklist. Pages are present, but the bottom edge is cropped and the expiry date is unreadable.
  3. Decision: She rejects that item only, with a reason naming the missing expiry date. Tomas's accepted identity document stays closed.
  4. Replacement: Tomas uploads a full-page scan to the same item. Elena rechecks readability and accepts it.
  5. Result: The collection request moves forward without restarting unrelated items or asking Tomas to resend the whole pack.

Multiple people and outstanding items

Review gets harder when more than one person owns documents. Tomas may have an accepted identity item while Katarina still needs a clearer civil record, and an employer letter waits on a third-party office. Keep each person's items on separate checklist lines so a replacement for one person does not reopen another person's accepted file.

When several items need different actions, list them by outcome rather than by inbox order: accepted, awaiting replacement, awaiting third party, uploaded but not reviewed. That picture helps staff decide whether to send one focused correction, wait for an employer, or escalate a cluster of open items to the migration agent. Repeated corrections on the same item should stay on that item, with the latest reason visible, so clients are not asked to restart the whole request every time one scan fails.

Staff handoff summary

When another coordinator or the migration agent picks up the file, a short summary prevents rework:

  • Items accepted for this request (name the person on each)
  • Items awaiting replacement, with the reason in one sentence
  • Items waiting on a third party (employer, school, sponsor office)
  • Items uploaded but not yet reviewed by staff
  • Open questions for the migration agent or consultant

That handoff is especially useful when partners, sponsors, and employers each own different outstanding items. For a commercial overview of structured collection across a practice, see document collection for migration agents.

When a correction is resolved

Keep four statuses distinct in everyday language:

  • Uploaded means a new file arrived.
  • Reviewed means staff looked at it against the request.
  • Accepted for this item means the file meets the collection requirement you asked for.
  • No outstanding collection actions means every checklist item for this request is accepted or marked not applicable.

Resolving a document request is not the same as a government decision on the immigration matter. Say that distinction once when clients ask "does this mean we are approved," then return to the practical next step your practice actually controls.

Where ClientlyBase helps with review and replace

Email can carry a clear correction once. It struggles when several items sit in different states, partners reply on separate threads, and nobody can see which files are already accepted. ClientlyBase helps migration practices keep each document on its own checklist line, share an upload link, track outstanding items, review submissions, reject with a reason, receive a replacement on the same item, send reminders, and reuse request templates.

That is the review-and-replace loop in one place. See the broader overview of how teams collect documents from clients, or explore plans and pricing.

You might also find these useful

Fix incorrect documents without restarting the whole request

Review each upload against its checklist item, reject with a clear reason, receive a replacement on the same item, and keep accepted files closed while outstanding ones stay visible.

Get started free