Immigration operations

From a document request to the next action

A practical handoff check for immigration teams

KORE Insights5 min read

A document request needs a clear next step. What should the client send? Who will check it? And what happens if the response does not resolve the issue? Before sending the next request, try making those answers explicit in the record your team already uses.

This practical exercise is for immigration lawyers, case managers and relocation coordinators. It follows one request from the client’s action to the team’s next decision. It is a proposed method to test with your team, illustrated with a fictional example.

Choose one request

Start with a request that has a clear purpose and a person responsible for responding. Keep the scope small enough to inspect: for example, supplying a replacement file for a specified work item. Do not try to redesign the whole case or combine several unrelated requests into one completion label.

Describe the action in terms the recipient can follow. If an action must happen before a file can be supplied, record those as separate steps. Record that an instruction was sent separately from whether the requested action was completed. Keep the requested action open until the agreed evidence has been checked.

Make five answers visible

  • Requested action: what should the recipient do, and who is expected to do it?
  • Expected evidence: what should come back so the assigned person can check this operational step?
  • Current record: where will the response and its version be recorded?
  • Check owner: who checks the response, against which specific question?
  • Next action: what follows a satisfactory check, and who handles an exception?
  1. 1Requested action
  2. 2Expected evidence
  3. 3Current record
  4. 4Check owner
  5. 5Next action
A proposed check for one document request. The example is fictional and professional review remains a separate task.

Put these answers beside the existing work item. A reference is enough when the source material is already stored in the right place. Avoid copying applicant names or documents into a separate planning sheet. If the information is already clear, the exercise may need no new field.

Separate receiving from checking

For this exercise, “received” means that a response is available and linked to the intended work item. “Operationally checked” means that an assigned person has answered the specific operational question and recorded the result, including an unresolved issue. For example: can the specified pages be read, and is this the version intended for the next review? Checked does not automatically mean satisfactory.

Keep any professional assessment separate from this operational check. Being able to read a file does not establish what it proves or whether it is sufficient for a particular case. Record the professional review question, responsible person and result where that assessment is needed. Agree these working definitions with the team before applying them to a live record.

Work through one fictional request

Consider fictional work item F17. The case record points to file A, and the coordinator requests a replacement because the assigned reader cannot read the relevant pages. The client supplies file B through the practice’s existing permitted channel. There is no real applicant or legal requirement in this example.

Illustrative F17 entry

Requested action
Client supplies a readable replacement for the specified work item.
Expected evidence
Replacement file B is available for the assigned operational check.
Current record
Existing F17 record links B and keeps the earlier reference to A.
Check owner
Named coordinator checks the specified pages for readability and records the result.
Next action
If satisfactory, the coordinator assigns any required professional review; the reviewer accepts that task. Otherwise record the gap and follow-up. Receipt alone does not mean review has begun.

If B can be opened but still does not answer the assigned question, record the exception and the next action. The coordinator can request clarification while keeping the review open. If B resolves the operational issue, a reviewer still records any substantive assessment required. Being able to read a file is different from deciding what it proves.

Keep an exception actionable

When the expected evidence is missing, name the specific gap and the person responsible for resolving it. Distinguish an action awaiting the client, a check awaiting the team and a dependency outside either person’s control. Each needs a next event or review point; none should acquire an invented completion date.

A short entry might say: “Replacement received; relevant page remains unreadable; coordinator to explain the specific issue and request another copy; check again when it arrives.” The team chooses its follow-up timing. This operational arrangement does not define or change a legal deadline.

If the assigned checker is unavailable, the coordinator retains the open action until a replacement accepts it. If another file arrives, keep the earlier observation attached to the version it addressed. Ask the responsible professional whether the change also requires a new substantive review.

Test the instruction and the record

Use a fictional example or a work item the team has permission to examine. First, ask a colleague to read the request as its recipient. Can they explain what action is expected and what evidence should come back? Record the exact ambiguity rather than guessing what a client would misunderstand.

Next, ask the person who would receive the response to identify the intended version, their check and the next owner from the current record. A clear request and a clear internal assignment are separate observations. Record each result, including an answer that the existing process already works.

Revise only the wording or field connected to the observed ambiguity, then repeat the check. If you later examine a real interaction, keep the professional’s account, permissions and context with the observation. One example cannot establish how often the issue occurs or whether a new tool would help.

Keep the change small

Review which information the exercise added and where it duplicated an existing record. Remove fields that do not help someone act. Before expanding the method, ask whether it fits the way the team already requests, stores and reviews material.

Use the exercise to answer a specific question: can each person identify the action, the evidence and the next decision? Keep changes that help someone act; remove additions that merely duplicate the existing record.

A worksheet for your next request

Copy these prompts into the permitted record you already use. Link to existing material instead of duplicating personal information. Leave irrelevant fields out.

Worksheet

Work item reference
[reference]
Requested action and recipient
[one specific action; responsible person]
Expected evidence
[what should come back]
Current record/version
[reference to the response]
Check owner and question
[person; exact question to answer]
Check result
[observation; satisfactory or unresolved]
Next action and owner
[what happens next; responsible person]
Follow-up trigger
[event or agreed review point]
Professional assessment, if needed
[question; assigned reviewer; result or pending status]

Try the worksheet on one fictional request first. If a colleague cannot identify the next action, revise that part before adding more fields.

For immigration practitioners: where would you test this first, and what evidence tells you that a request is complete?