Before treating an AI preparation task as complete, open the destination matter and reconcile what arrived against what was expected. Check the matter identity, document versions, unresolved issues and review status. If only part of the work returned, assign an owner and verify what is already saved before retrying. A generated draft and a completed handoff are separate milestones.
Your preparation tool says the draft is ready. The attorney opens the case-management system and finds an older letter, no evidence index and a task marked complete.
The draft may be useful. The handoff is still unfinished.
When immigration firms evaluate AI, they often watch document import and drafting closely. The return trip deserves the same attention. Your team needs to know where each output went, which version to review and what remains open.
This checklist focuses on that return trip. It is a suggested internal process for preparation and review, not a filing procedure or a promise that every product automates each step.
1. Agree on what should return
Write a short list of expected outputs before running the test. Depending on the agreed workflow, that might include draft forms, a support letter, an evidence index and a note identifying unresolved questions.
Separate three kinds of actions:
- Document return: saving a draft or packet to the matter.
- Record update: changing a field or status in the case system.
- Review handoff: identifying who should check the returned work.
A connection may support one action without supporting the others. Ask the vendor to demonstrate each action included in your proposed configuration. Record manual steps too.
For a broader evaluation, start with the immigration AI pilot scorecard. Use this checklist when the test reaches the destination matter.
2. Confirm the destination before returning work
Use the case system's stable matter identifier where available. A client's name alone may not distinguish an extension from a change-of-employer matter or a separate family member's case.
Check the intended client, petitioner or household member, case type and matter identifier together. Confirm the folder or document category as well.
In a test environment, use two clearly fictional matters with similar display names. Ask the operator to show why the selected record is the correct destination. The test should expose ambiguity before any real client work is moved.
For multi-person matters, confirm which outputs belong to the principal and which belong to each dependent. Keeping documents in one household folder does not make their case records interchangeable.
3. Keep a small transfer manifest
A transfer manifest is simply a list of what the team expected to save and what it actually found. It can be a note in the matter or a row in an existing review worksheet. It does not require a new application.
| Item | What to record |
|---|---|
| Destination | Matter identifier and intended folder or category |
| Preparation run | A reference that distinguishes this attempt from an earlier one |
| Expected outputs | Each file or record update included in scope |
| Source output | The version prepared for return, with a creation time or other usable identifier |
| Destination result | Saved document link or identifier, or confirmation of the field update |
| Exception | Missing item, failed action or unexpected change |
| Ownership | Person resolving exceptions and person reviewing the draft |
Keep the note proportionate. Its purpose is to let someone verify the result without replaying the entire workflow. Follow firm policy for access and retention, and avoid copying unnecessary client information into a separate log.
4. Open the saved files from the CMS
Do not stop at the preparation tool's success message. Open each expected output from the actual destination matter.
Check that it is readable, belongs to the right case and matches the version intended for review. A familiar filename is not enough. Open the document and inspect a distinguishing detail, such as its version label and the corrected paragraph used in the test.
If an assembled packet is part of the return, inspect its contents and references in the saved export. If the workflow returns only separate drafts, record that boundary rather than treating packet assembly as completed.
Include a person with the ordinary reviewer's permissions. A file visible to the integration administrator may still be inaccessible to the attorney assigned to the matter.
5. Test a partial return before trusting a retry
Use an authorized test environment or a vendor-supported simulation. Suppose the expected return contains three items: a draft form, a support letter and an evidence index.
In this fictional test, the form saves successfully, the support-letter upload fails and the index remains pending. A single green completion label would hide unfinished work.
The handoff note should instead identify the result:
Test matter DEMO-204: draft form v2 is saved and opens correctly. Support letter v2 has not returned. Evidence index v1 is pending. Preparation is complete, but the CMS handoff is incomplete. Assigned preparer will reconcile the saved files before retrying the missing items. Attorney review has not started.
Before rerunning, check whether any failed-looking action actually succeeded at the destination. A lost confirmation can make a saved document look missing.
Then observe the supported recovery process. Does the retry create a duplicate, overwrite an existing file or save a new version? If the software cannot retry individual items, record the manual reconciliation needed after a full rerun.
The goal is not to demand a particular architecture. It is to make recovery understandable to the team that will perform it.
6. Keep transfer status separate from legal review
Agree on status meanings before mapping them between systems. A vendor's “completed” may mean processing finished, while your firm's “complete” may mean attorney review finished.
Use a distinction your team can maintain:
| State | Meaning in this suggested workflow |
|---|---|
| Prepared | The scoped output has been generated |
| Returned | Expected outputs have been checked in the destination matter |
| Awaiting review | The reviewer has access to the intended version and knows the open questions |
| Reviewed | The designated reviewer has recorded a decision on that version |
These are example labels, not required product settings. If the CMS has fewer status options, use a task or note to preserve the distinction.
Returning a document should not, by itself, mark it approved or authorize filing. Attorneys retain legal judgment, final review and filing decisions.
7. Finish with a reviewer handoff
Send the reviewer a concise note pointing to the saved outputs. Include the unresolved questions and the work still required. Avoid a vague “AI done” message.
A useful note identifies the matter, draft version, document location, missing items and next owner. The reviewer should be able to open the work from that note and know whether it is ready for their assigned review step.
For the review itself, use the immigration review QA workflow. This handoff check establishes where the work is and what state it is in. It does not establish that the underlying facts or legal analysis are correct.
A short test sheet for your next demonstration
Ask the vendor to walk through these tests using fictional records and agreed permissions:
| Test | Evidence to keep |
|---|---|
| Two similar matter names | The identifier used to select the correct destination |
| Return the agreed output set | Manifest showing each expected and saved item |
| Return a revised draft | What happened to the earlier version and any reviewed edits |
| Interrupt one return action | Visible exception, owner and recovery steps |
| Repeat the same run | Duplicate, overwrite or new-version behavior, plus cleanup required |
| Open as the assigned reviewer | Accessible files, correct version and open questions |
Mark each result as demonstrated, manual, unsupported or not tested. Do not turn “not tested” into a pass. Record the system configuration and test date because supported behavior can change.
Frequently asked questions
Does a CMS integration mean documents and case fields both sync?
No. Document import, document return and structured field updates are separate actions. Confirm exactly what is supported for your case system, account permissions and configuration.
Should returned drafts overwrite the existing documents?
Agree on the firm's version policy first. Test how the connection handles an existing file and a reviewed draft. Preserve enough history to identify what changed and which version the reviewer approved.
What should staff do when a transfer fails?
Check the destination before retrying, identify what was already saved and assign recovery to a named owner. Use the supported recovery procedure and reconcile the results afterward.
Can a manual upload still be a workable handoff?
Yes. A documented manual step can be workable when the file, destination and owner are clear. Include its effort in the evaluation instead of counting it as automated work.
Does this checklist prove an AI draft is ready to file?
No. It tests the transfer and review handoff. The attorney still determines whether the materials meet the requirements of the matter and whether filing is authorized.
See the complete workflow before choosing a connection
Infinity by InceptionAI is an AI immigration case-preparation platform for US immigration law firms. Its MyCase integration overview describes starting preparation from a matter and returning a draft. Confirm the specific documents, field updates, permissions and review steps for your configuration during a walkthrough.
Book a case-preparation workflow review. Bring a fictional matter and the output list your team expects to find back in the case record.