Filling immigration forms from client documents

An immigration file asks for the same values again and again: the client’s name, date of birth, passport number, registration number, addresses going back years. The reliable way to fill it is to extract each value from the source documents once, verify it once, and let software carry it into every field that needs it.

Why do repeated fields cause the most trouble?

Because a value typed five times is five chances to type it differently, and internal consistency is exactly what a filing gets checked for. The forms are long. Form I-485 alone runs to well over a dozen pages in the version published on uscis.gov (uscis.gov/i-485), and a filing usually bundles several forms, with the same identifiers repeating across most pages of each.

• The name must match the passport exactly, and it repeats in headers, family sections and signature blocks.
• Registration numbers and passport numbers are long strings with no internal pattern a reader can check by eye.
• Dates appear in more than one convention: one form wants MM/DD/YYYY while the source document prints DD.MM.YYYY.
• Address history repeats across forms, and a gap or overlap between two copies of it raises questions.

A mismatch between two of your own pages is the cheapest error to prevent and one of the more expensive ones to explain after filing.

What the source documents already contain

Almost everything the forms ask for exists in the papers the client hands over. The work is transfer, not authorship. Three kinds of sources cover most fields.

• The passport bio page: the name as officially transliterated, the passport number, nationality, dates of issue and expiry.
• The national ID or residence card: the personal number and, on many cards, the registered address.
• Prior applications, receipts and notices: the registration number, receipt numbers, and the exact spellings and dates already declared to the authority.

Prior applications deserve particular respect. They are the record of what has already been stated. If the new filing spells a name or dates an entry differently, someone will eventually have to explain why. Treat the old application as a source with the same authority as the passport, and treat any disagreement between the two as a finding to resolve with the client, not a detail to smooth over.

A workflow that extracts each value once

• Collect the sources for the case: passport photos, ID scans, prior application PDFs, the client’s emails.
• Extract every needed value into a single set: one name, one birth date, one number of each kind, one address history.
• Verify each value against its source once. Long numbers get checked digit by digit, here and nowhere else.
• Fill every document from the verified set. Never from memory, and never by copying from another form.

The verification step is the whole point. When a value is checked against its source once, every field it flows into inherits that check. When values are typed per form, every form needs its own proofread, and the proofreads are never equally careful.

For the Word documents in the file, Run Done runs this workflow directly: cover letters, declarations, representation agreements, and any forms your office keeps in Word format. You upload the .doc or .docx you already use, unchanged, and add the client’s materials: photos, scans, PDFs, pasted text, even dictated details. The software reads the materials and enters the values in the right places. Values come only from what you supplied; a value that cannot be found leaves the field empty, and nothing is invented. You review every entered value, correct anything, then download the finished Word file. A document you produce for every client can be saved and refilled in seconds.

The short version

Immigration forms repeat the same identifiers across dozens of pages, so consistency matters more than speed. Extract each value from the passport, the ID and the prior applications once, verify it against the source once, and fill everything from that verified set. Mismatches with prior filings are findings to resolve, not noise. The review at the end is a short list, not a re-read of the whole file.