Immigration client documents into Clio: building the matter file from what clients send

Most practice areas generate their documents: pleadings get drafted, contracts get negotiated, discovery gets produced. Immigration practice is different in degree — applications are document-heavy, and a large share of the file is collected rather than created. The client supplies identity documents, civil records, prior filings, and evidence; the firm assembles those into an application. A family-based or naturalization matter — the kind built around forms like an I-130, an N-400, or an I-485 — can involve dozens of client-supplied documents before any form is filled in.

That changes what the document-management problem looks like. The hard part isn't version control on documents the firm drafted; it's intake at volume from people who aren't document professionals. Documents arrive over weeks, in fragments, through whatever channel the client finds easiest, and the matter can't move until specific items are in hand. The file is only as complete as the collection process.

So the practice problem has two halves: getting every document a client sends into the Clio matter — whatever channel it arrived through — and keeping the status of the collection visible, so anyone on the team can see what's received and what's still outstanding. The rest of this guide takes those in turn, then covers the form-prep handoff and the filing conventions that keep the assembled file navigable.

Whatever the channel, the endpoint is the same: filed into the Clio matter, named to convention, reflected on the checklist.

Collection without tracking is how matters stall quietly. Every immigration matter needs an answer, at any moment, to "what are we still waiting on from the client?" — and the answer has to live somewhere the whole team can see it, not in one paralegal's memory.

Clio's own immigration practice marketing pitches its task tooling at exactly this: "Create Task Lists to keep track of what documents clients have given you and what's still outstanding," and "Track different types of tasks and individual task statuses with Advanced Tasks, so you know when you can proceed with filing." It's telling where that pitch points — collection and tracking is where immigration document work concentrates, and a per-document checklist with statuses is the offered mechanism.

The checklist discipline, whatever the tool. A task list, a spreadsheet, or a shared template all work if the practice around them holds. Create the checklist when the matter opens — one per application, not one per client, since a matter covering multiple family members needs each applicant's documents tracked separately. Give each item a status worth more than a checkbox: requested, received, filed — and, where it applies, needs translation or needs better copy.

And give the checklist one owner. A checklist everyone is responsible for is one nobody updates. The practical move is to make the checklist update part of the filing step itself — the same person who files the document into the matter marks it received — so the checklist's accuracy rides on a habit that's already happening rather than on a separate chore that competes with everything else.

A collection-heavy matter punishes loose filing faster than most. Sixty client-supplied files with camera-default names in a flat folder is a matter nobody can navigate. The conventions that hold up are ordinary ones, applied consistently from day one.

Folders. A small, fixed skeleton per matter — for example: identity documents, civil records, evidence, forms and filings, correspondence — created when the matter opens. For matters covering multiple family members, add per-applicant subfolders inside each category (or per-applicant top-level folders with the categories inside; pick one and keep it). The general design principles are covered in the folder structure guide.

Filenames. A date prefix, the applicant, the document type: something like 2026-06-10 - Maria - birth certificate (translation).pdf sorts chronologically, reads at a glance, and distinguishes original from translation without opening the file. Rename at filing time — the moment the phone photo or attachment goes into the matter — because nobody comes back later to rename IMG_4032.jpg. Naming discipline earns its keep on retrieval: Clio's global search bar produces results by searching both document names and the full-text of documents on higher-tier plans, but that full-text search relies on an extractable text layer — an image-only phone-photo scan is not confirmed to be auto-OCR'd — so for the picture documents that dominate an immigration file, a descriptive filename stays the reliable way to find something later. The fuller system is in the naming conventions guide.

These are practice suggestions, not requirements from anyone — the test of a convention is whether the second-newest person at the firm can find a specific client's translated marriage record in under a minute. If they can, the convention is working; if they have to ask, tighten it.