Treat a translated questionnaire as the start of a fact review, not as a filing-ready form. Keep the client’s original answer with the English working version, check names and dates against source documents, mark uncertain answers, and trace each approved fact into every prepared output. If a foreign-language document will be submitted to USCIS, handle its full English translation and translator certification as a separate filing requirement.
A client may answer a questionnaire in the language they know best. The firm then has to use those answers in English forms, letters and case notes. Several different jobs sit inside that handoff: translating a question, interpreting a response, resolving conflicting facts, populating form fields and reviewing the finished work.
A demo can make all of this look like one button. For a law firm, the useful question is what the reviewer can see when a name, date or answer changes along the way.
This checklist is a suggested evaluation workflow. It does not certify a vendor, replace a competent translator or tell counsel what a specific case requires.
Separate three kinds of translation
Ask a vendor to show each of these tasks separately:
| Task | What the firm needs to check |
|---|---|
| Questionnaire language | Can the client read the exact questions, instructions and follow-ups in the intended language, including custom questions? |
| Working answer translation | Can staff see the client’s original response beside the English version used for case preparation? How are corrections recorded? |
| Supporting-document translation | If the firm submits a foreign-language document to USCIS, who supplies the full English translation and the required translator certification? |
These are different capabilities. A tool that translates intake questions has not necessarily translated a birth certificate. A tool that drafts an English summary of a document has not, by that fact alone, supplied a certified translation for submission.
Under 8 CFR 103.2(b)(3), a foreign-language document submitted to USCIS must have a full English translation certified as complete and accurate, with the translator certifying competence to translate into English. This regulation was checked against the eCFR version current through November 9, 2026. Confirm the current rule and any form-specific instructions when preparing a filing.
Test the client’s actual language path
Use a fictional matter in an authorized demo. Pick a language your clients actually use and a form workflow the firm would really run. Do not settle for a language count on a product page.
Send the same questionnaire a client would receive. Inspect the invitation, instructions, standard questions, custom questions, upload requests, error messages and follow-up prompts. If a client pauses and returns, check what remains visible and in which language.
Give the test client one short free-text answer, one date and one answer that needs clarification. The staff reviewer should be able to see the original wording and ask a follow-up without silently converting uncertainty into a confirmed English fact.
Questions worth asking during the demo:
- Which parts are translated by the product, and which require the firm to supply language-specific text?
- Does an edited question change every version of the questionnaire, or only future sends?
- Can the reviewer compare the original answer and the English working version before approving a field?
- Where does the system show that a translation or interpretation is uncertain?
- If the client corrects an answer, which downstream fields and drafts are marked for recheck?
Record the product version, language, case type and configuration tested. A successful Spanish demo, for example, does not establish the same behavior for every other language or custom question.
Reconcile facts before form population
Suppose a fictional client enters a birth date as 04/05/1992. Without an agreed date format, that may mean April 5 or May 4. An uploaded identity document may settle the matter, or it may create another question. The form should not inherit a guess merely because the answer passed through translation.
Use a small review record:
| Item | Example entry |
|---|---|
| Original answer | The exact client response and its questionnaire language |
| English working version | The proposed meaning used in preparation |
| Supporting source | Document name and page, or a recorded client clarification |
| Difference or uncertainty | Ambiguous date format, alternate spelling or conflicting address |
| Resolution | Approved value, reviewer and date, or an open question |
| Affected outputs | Form fields, letter paragraphs and case notes requiring recheck |
Keep the record inside the firm’s approved case system where possible. The point is traceability, not another spreadsheet containing unnecessary client data.
Names deserve their own check. Compare the original-script name, any romanized spelling in the passport, prior filings and the version proposed for forms. Do not normalize a spelling merely because two versions look similar. Counsel or the designated reviewer should decide which value belongs in each output and whether an explanation is needed.
The same principle applies to employment dates, addresses, travel history and family relationships. When source records disagree, show the disagreement and route it to the right person. A blank or contested value should not become a confident form answer.
Check the return trip into every output
After the firm approves a fact, inspect the prepared form and any related letter or evidence list. Compare the actual saved output with the approved record. If the client revises an answer later, repeat the check for affected outputs and preserve the prior version for review.
For a short demo, choose two forms or a form and a letter that reuse one fact. Correct that fact once. Ask the demonstrator to show what updates automatically, what remains manual and what alerts the reviewer. Then open the destination matter in the case system, if a return workflow is part of the proposed configuration.
The forms automation guide covers the broader intake-to-packet path. The CMS draft-handoff checklist helps verify saved versions and exceptions after preparation. This checklist concentrates on the language and fact decisions before that handoff.
Use a simple pass, question or fail record
Do not score a polished screen as a complete workflow. For each test, record what was demonstrated:
| Test | Evidence to keep |
|---|---|
| Client sees the intended language | Screens of standard and custom questions, instructions and follow-ups |
| Reviewer sees the original answer | Original response beside its English working version |
| Ambiguity stays open | A date, name or free-text answer flagged for clarification |
| Approved correction reaches outputs | The corrected value in every scoped form and letter |
| Foreign-language exhibit is handled separately | Owner for full translation and certification, when needed for filing |
| Attorney review remains visible | Reviewer, output version and open questions before filing decisions |
Mark each row demonstrated, manual, unsupported or not tested. A manual step can be acceptable if the firm can assign and verify it. “Not tested” should stay visible when comparing vendors.
Frequently asked questions
Does a multilingual questionnaire mean the filed forms are translated?
No. The client-facing questions, the client’s responses, the English working record and the filed form are separate artifacts. Ask to see how information moves between them in the case type and language you plan to use.
Can an AI summary replace a certified translation of a foreign-language exhibit?
For a foreign-language document submitted to USCIS, 8 CFR 103.2(b)(3) requires a full English translation and the translator’s certification of completeness, accuracy and competence. A working summary does not satisfy that stated requirement. Counsel should check the applicable instructions for the filing.
What if a client’s translated answer conflicts with a passport or prior form?
Keep both sources visible, mark the affected fields as unresolved and ask the appropriate reviewer to decide the next step. Do not let the software choose silently. After resolution, check every output that used the earlier value.
Should the firm replace its case-management system to use AI preparation?
That depends on the existing system and the required handoffs. Evaluate the intake language workflow, fact review, preparation outputs and return to the matter separately. Ask each vendor to demonstrate the exact configuration the firm would use.
See where Infinity fits in your existing workflow
Infinity is InceptionAI’s AI case-preparation software for US immigration law firms. Its public intake automation overview describes structured intake, document tracking and review handoffs. This article does not claim Infinity translates questionnaires or provides certified document translations. If your firm already handles multilingual intake in another system, ask for a walkthrough of how reviewed English facts and source documents would move into the preparation workflow you are considering.
Book a case-preparation workflow review. Bring a fictional multilingual intake, one conflicting fact and the outputs your team needs to review.