Tracking USCIS delays — the work that happens before a mandamus is ever discussed.

By the time a client calls to ask why nothing has happened in fourteen months, the information that would have answered them existed months earlier and nobody was looking at it. Monitoring pending agency matters is ordinary paralegal work, it is entirely on the correct side of the non-attorney line, and it is one of the few things a support role can do that changes case outcomes rather than just case administration.

The call nobody wants

Every immigration practice has had this conversation. A client who filed nearly two years ago calls, upset, wanting to know why their case is still pending and what the firm has done about it. The attorney takes the call cold. The file has to be pulled while the client is on the line. And the honest answer, more often than anyone would like, is that the case had drifted past the point where something could have been done and nobody noticed, because noticing is nobody's assigned job.

That is an operations failure, not a legal one. Which means it is fixable by the support side of the practice, which is where I sit.

The premise of everything below is simple: whether a delay justifies going to federal court is a legal judgment that belongs to the attorney, and I never make it. But whether a case has crossed the agency's own published threshold is a matter of arithmetic, and putting that arithmetic on the attorney's desk on time is a support task like any other.

What "outside normal processing time" actually means

USCIS publishes a processing time for each form at each office, expressed as the time within which it completes eighty per cent of cases. That figure gets quoted a great deal and it is the less useful of the two numbers on the page.

The useful one is the case inquiry date. Alongside the processing time, each office publishes a date and a rule attached to it: if the receipt date on your notice falls before that date, your case is outside normal processing time and you may submit a formal inquiry about it. That is the agency's own line, published by the agency, applied by comparing two dates.

This matters for a support role specifically because of what it is not. Deciding that a delay is unreasonable is legal analysis. Observing that a receipt date is earlier than a published inquiry date is reading a calendar. The first is not mine to do; the second is exactly the kind of thing a firm should have somebody doing systematically, and most firms do it ad hoc or not at all.

My job is not to decide that a case has waited too long. It is to make sure that when it has, the attorney knows before the client does.

What I keep in the tracker

One row per pending matter, in whatever case management system the firm already runs — Clio, MyCase, PracticePanther, a spreadsheet if that is genuinely what the practice uses. The system matters far less than the discipline. The fields I keep are:

  • Receipt number, form type, and the office or service center handling it.
  • Receipt date — the one date everything else is measured against.
  • The processing time published for that form and office when the case was filed, and the one published now. Both, because the movement between them is information.
  • The current case inquiry date for that form and office.
  • Last action on the file: biometrics, RFE issued, RFE answered, interview scheduled, transfer to another office.
  • Date of the last case status check, and what it said.
  • Date of any inquiry already submitted, and the response received — including the non-responses, which are their own kind of record.
  • Any hard date in the client's life that the delay is running against.

That last field is the one people leave out, and on some matters it is the whole file. A child who ages out of a benefit on a birthday, a work authorization expiring against a job offer, a consular appointment that has to be rebooked from abroad — a delay that is merely annoying on one file is terminal on another, and the tracker is where that difference becomes visible.

Why the numbers have to be watched, not looked up

Here is the part that trips up otherwise well-run practices. The published figures are not stable, and they are not archived.

USCIS revises processing times roughly once a month. It does so without notice, and the page it publishes them on shows only the current values — the previous month's numbers are simply gone, with no public record of what changed. Across the whole system that is a lot of quiet movement: forty-three forms across ninety-six offices, close to five hundred form-and-office combinations, and at a typical revision a large share of them move.

The practical consequence is that a threshold can be crossed by the agency rather than by the file. An office shortens its inquiry date in a revision, and a case that was inside normal processing time on Friday is outside it on Monday — without a single thing happening to the case itself. If the only time anyone looks is when a client complains, that crossing is invisible for however many weeks it takes the client to get annoyed enough to call.

So I don't look the numbers up. I watch them. The processing-time monitor I keep open when I do the status round compares each USCIS revision against the one before it, shows what moved at the last update, and preserves the history the agency does not — and it will email when a specific form changes, which turns a monthly manual sweep into a notification I act on. Whatever tool a firm prefers, the requirement is the same: somebody has to be holding the previous month's numbers, or the changes are unobservable.

The flag memo — one page, facts only

When a matter crosses the line, what reaches the attorney is a single page. Not an email thread, not a note in the file that will be read eventually, and emphatically not a recommendation. It contains:

  • Client, matter, form, receipt number, office.
  • Receipt date, today's date, and the elapsed time stated in months.
  • The currently published processing time for that form and office, and the elapsed time expressed against it.
  • The current case inquiry date, and the date on which the receipt date fell behind it.
  • Whether the published time for that office has been rising or falling over recent revisions.
  • Every inquiry already submitted, with dates and the text of what came back.
  • Anything on the file that would explain the delay innocently — an outstanding RFE, a missed biometrics appointment, a transfer, a name variation.
  • The client-side deadline the delay is running against, if there is one.

That last-but-one line is there deliberately. A flag that omits the innocent explanation wastes the attorney's time and, worse, trains them to stop trusting the flags. If the case is stalled because an RFE went unanswered, that belongs at the top of the page, not left for the attorney to discover.

The memo ends where my part ends. The attorney reads it and decides what the delay means, whether a further inquiry, a congressional liaison request, or a federal court filing is warranted, and whether it is worth raising with the client at all. Sometimes the answer is that the case is fine and the client simply needs to be told so in their own language — which is also work I can do, once the attorney has decided that is the message.

What I don't do

This is worth stating plainly, because delay work sits closer to the line than most support tasks and immigration is the field where that line is abused most often.

I do not tell a client that their case is taking too long, that they have grounds to sue, or that a mandamus petition is an option — that is legal advice, and it is the attorney's to give or withhold. I do not assess whether a delay is legally unreasonable. I do not quote what litigation would cost or how likely it is to work. I do not contact an agency or a client on a substantive point without the attorney's review and approval, and I do not sign anything on the firm's behalf.

What I do is narrower and, done consistently, more valuable than any of that: I keep the record complete, I apply the agency's own published thresholds as a matter of arithmetic, and I make sure that the moment a file crosses one, it is in front of the person licensed to decide what to do about it. The same boundary is set out at more length in the companion piece on working with overseas trilingual paralegals.

Cadence

Three rhythms, and they are unremarkable by design:

  • Weekly — case status checked on every pending matter, tracker updated, anything that moved noted with its date.
  • At every USCIS revision — the published times and inquiry dates refreshed for each form and office on the list, and every receipt date re-tested against the new inquiry dates.
  • Immediately — a flag memo the day a receipt date falls behind an inquiry date, and the day an office's published time jumps against a file with a hard client-side deadline.

None of this requires judgment I am not entitled to exercise. It requires somebody to own it, every week, without being asked — which is precisely what a firm is buying when it engages support. If that is the gap in your practice, the virtual legal assistant page sets out how I structure the engagement, and the practice areas page covers the matter types I work across.


This essay describes administrative monitoring practices for pending immigration matters from the perspective of non-attorney support. It is general information about legal-operations workflow, not legal advice about any case, and nothing here should be read as an opinion on whether any particular delay warrants legal action.

Nobody watching the pending files? Email Carol.

Tell me roughly how many matters are pending, which forms and offices they sit with, and what your practice uses to track them. We can start with a single sweep of the current caseload before committing to anything ongoing.

Email Carol