Two backlogs, two different numbers
The most common error in coverage of this is treating USCIS and the immigration courts as one queue. They are separate systems with separate figures, and conflating them is the fastest way to lose credibility with anyone who works in the field.
USCIS held 11.3 million pending cases at the end of FY2026 Q1. Of those, 6.3 million sit in what the American Immigration Council calls the net backlog — cases already past target processing time and within the agency's own control. The second number is the meaningful one for capacity planning, because it excludes cases still inside normal processing, cases delayed by the applicant, and cases waiting on visa availability.
The immigration courts are a different queue entirely: 3,195,137 cases pending as of June 2026, of which 2,310,698 are asylum applications awaiting a hearing or decision.
Throughput fell while intake did not
The part that turns a backlog into an operational problem is on the completion side. USCIS completions fell 41% year over year in FY2026 Q1. A queue that grows while throughput falls does not stabilise on its own, and nothing in the current data suggests a near-term reversal.
For a firm, that shows up as longer case lifecycles. Matters stay open for quarters longer than they used to, each one continuing to consume status checks, client updates, and re-verification of evidence that has gone stale in the meantime. Caseload rises without a single new client.
What actually absorbs the load
The work created by a backlog is mostly not legal work. It is status monitoring, receipt and notice tracking, evidence that must be refreshed because it has aged out, client communication driven by nothing but elapsed time, and re-assembly of filing packets. It is repetitive, deadline-bound, and it scales with the size of the queue rather than the difficulty of the matter.
That is the work worth delegating, and it is why the response to a backlog is an operations question before it is a hiring question. Three things tend to matter more than headcount:
- Work inside one system. The largest reported source of friction in small-firm legal operations is information scattered across disconnected tools. Support that runs in your existing case management system rather than a parallel inbox removes a problem instead of adding one.
- Make deadline tracking a process, not a person. Court-set dates do not move for staffing shortages. Tracking that depends on one individual's memory fails exactly when the queue is longest.
- Draw the delegation boundary before you delegate. Decide in writing what support personnel prepare and what only your attorneys decide, then hold the line. This is easier to do at the start than to retrofit.
The ethics work comes first, not last
Firms that outsource case support successfully tend to settle the professional-responsibility questions before the operational ones. Delegating work that touches confidential client information brings disclosure and supervision obligations with it — ABA Formal Opinion 08-451 addresses client consent where non-lawyers outside the firm receive information protected by Model Rule 1.6, and Model Rules 5.1 and 5.3 govern supervision. Several states, Florida among them, go further.
None of that is a reason not to delegate. It is a reason to have the consent language and a written supervision protocol ready before the first matter is assigned, rather than assembling them under deadline pressure later.
See what case support covers, and what stays with your attorneys →