I-765 Processing Time — By Office (2026)

Processing time by office

Click a column to sort. Offices flagged with the visa-bulletin / preference-category caveat show context rather than a bare number.

What a delay on I-765 actually means

Reviewed by Aaron Elinoff, Managing Partner, Novo Legal Group — CO Bar #46468, WA Bar #58949

What USCIS's published range actually means

The number USCIS publishes for I-765 is not a promise, an average, or a target. It is a lookback. USCIS reports the time it recently took to complete the large majority of adjudicated cases (as of USCIS's most recent methodology, roughly 80%) at that service center over a trailing window (see USCIS's own methodology explainer at https://egov.uscis.gov/processing-times/more-info). Read carefully, that means the remainder took longer — sometimes materially longer, and an individual case can sit inside or outside that range for reasons that have nothing to do with the "typical" applicant. When you see a range like "X to Y months" on the applicable row, treat it as USCIS's description of recent history for that adjudication unit, not a schedule the case is on. For I-765 in particular, the published range depends heavily on which eligibility category the applicant filed under — a fact that is often the first thing to check when one applicant's I-765 appears to be moving faster than another's.

The service-request date is a separate signal — and the one that matters

Alongside the range, USCIS publishes a service-request date for each form and office. This is the date that determines whether a still-pending case is considered outside USCIS's normal processing time. It is a distinct concept from the range, and confusing the two is one of the most common mistakes we see on I-765 files.

Two states people often mix up:

• Past the typical range, but filed after the service-request date. The case is past the top of the published range, but was filed too recently to submit a case inquiry. An applicant in this posture is not yet eligible to submit a case inquiry. Watchful posture is typical — monitoring the online case status, responding promptly to any RFE, and talking to counsel if the delay is starting to affect a job, travel, or a downstream benefit. This is generally not the moment to escalate; it is the moment to prepare.
• Filed on or before the service-request date and still pending — "inquiry-eligible." This is the state USCIS itself treats as outside normal processing time. A case inquiry (a service request) can be submitted through the USCIS online account, and if that goes nowhere, other tools open up. This is where the conversation with a lawyer earns its keep.

The order matters: the inquiry-eligibility check runs off the service-request date first, independently of where a case sits in the range. A case filed well before the service-request date and still pending is inquiry-eligible even when nothing about the file appears unusual.

What actually drives I-765 timing — and why it's not just the range

The I-765 (Application for Employment Authorization) is a derivative benefit tied to an underlying status or application. That structure — not the published range alone — is what actually drives how long an EAD takes to issue in practice. Understanding it is the difference between reading the hub table usefully and being misled by it.

(a) Eligibility category codes drive different timelines. Every I-765 is filed under a specific eligibility category — a code the applicant enters on Form I-765 that identifies the legal basis for the work authorization request. Examples include (c)(8) for applicants with a pending asylum application, (c)(9) for applicants with a pending I-485 adjustment application, (c)(33) for DACA recipients, (c)(3)(B) for F-1 students on standard post-completion OPT (with (c)(3)(C) for the 24-month STEM OPT extension), (a)(12) for TPS beneficiaries, (c)(26) for H-4 dependent spouses of certain H-1B nonimmigrants, and (a)(18) for L-2 dependent spouses of L-1 nonimmigrants. Each category is adjudicated on the review path tied to the underlying status, and USCIS publishes processing-time data by category — which means one applicant's I-765 and another's can show meaningfully different ranges on the same day at the same service center simply because the categories don't share a review path. When using USCIS's processing-times checker, the category selector is not cosmetic: selecting the wrong category returns a number that does not map to the case. Confirming the category on the receipt notice (and matching it to the checker's dropdown) is where any I-765 timing diagnosis typically starts.

(b) I-765 is derivative of an underlying application or status. The real EAD-timing question is often two questions layered on top of each other: is the underlying case moving? and is USCIS's I-765 track for this category current? Both need to be functioning for the EAD to actually issue. An asylum applicant on a (c)(8) EAD renewal, for example, is affected both by the asylum office's or immigration court's posture on the underlying application and by whichever service center is adjudicating the I-765. A DACA renewal on (c)(33) is affected both by DACA-program posture at the policy level and by I-765 service-center throughput. Diagnosing a stuck I-765 without also looking at where the underlying application sits is a common source of mis-scoped analysis; the two often move together, and sometimes only one is actually the blocker.

(c) An unexpired EAD is a List A document, and the physical card is what matters. Work authorization attaches upon USCIS approval of Form I-765, but under federal I-9 rules an employee proves that authorization to an employer by presenting an unexpired Form I-766 Employment Authorization Document (the physical EAD card). Without the physical card in hand, an employee typically cannot complete I-9 verification for a new job, even after approval issues. Under federal I-9 rules, an unexpired I-766 EAD serves as List A for both identity and employment authorization purposes, standing on its own without needing an accompanying List B or List C document. That structure has a practical consequence: the applicant needs the card in hand — not just an approval notice — to start or continue work. Card production and mailing happens after approval, and delays or mail issues at that stage can add real days to the effective "usable EAD" timeline in ways the published processing-times range does not capture.

(d) Automatic extension for eligible renewals — the 540-day rule. For certain renewal categories enumerated at 8 CFR § 274a.13(d), work authorization is automatically extended for up to 540 days past the expiration date on the current EAD when a timely I-765 renewal is filed under the same category. (The 540-day figure reflects the 2024 permanent rule; earlier versions of the auto-extension provided shorter windows.) This carve-out is often a significant lever for a stuck EAD renewal client in a qualifying category, because the applicant can typically continue working — and satisfy I-9 reverification by presenting the expired EAD together with the still-pending I-765 receipt notice showing the qualifying category — while USCIS finishes adjudicating the renewal. Two important caveats: not every category qualifies for the automatic extension (the regulation enumerates which do), and the extension attaches only to a timely-filed renewal in the same category. Applicants outside the qualifying categories, or who filed after their EAD expired, do not get the automatic extension, and the timing question in those cases becomes much sharper.

(e) Concurrent filing with I-485. Adjustment-of-status applicants may file Form I-765 under category (c)(9) concurrently with — or after — Form I-485 to obtain interim work authorization while the I-485 is pending. That interim EAD lets the applicant work legally during the wait, but it does not accelerate the I-485 itself, and the I-765 and I-485 typically adjudicate on their own tracks (the EAD often issues before the underlying green-card decision). Once the I-485 is approved and the applicant becomes a lawful permanent resident, the (c)(9) EAD is no longer functionally needed — LPR status confers work authorization incident to status, and the green card itself is the document that satisfies I-9 verification. This is the pattern to expect on the concurrent-filing path: the EAD is a bridge, and the bridge stops being useful once the underlying I-485 approval closes the gap.

When mandamus is worth discussing — and when it isn't

Mandamus is a federal-court action under 28 U.S.C. § 1361 that asks a judge to compel USCIS to make a decision on a case that has been unreasonably delayed. Two things are worth being blunt about. First, it is not a shortcut for a case that is a few months late. Courts look for unreasonable delay — cases genuinely stuck well past the outer edge of normal processing, usually after a case inquiry has already failed to move the file. Second, mandamus forces a decision; it does not order an approval. In the right case it is a meaningful tool, and this firm has litigated it. In the wrong case it burns money and goodwill.

For I-765 specifically, there are two important derivative-benefit caveats. First, mandamus rarely fits when the delay is really on the underlying application (asylum, adjustment, DACA), not on the I-765 itself. The EAD is derivative; if USCIS is genuinely delayed in adjudicating the asylum case or the I-485, the mandamus analysis usually belongs to that filing, not to the derivative I-765 that is waiting behind it. Courts have been broadly sympathetic to the government's category-driven timing framing on derivative benefits — the argument that the I-765 track is running as expected given the underlying case's posture is often the government's first move, and it often lands. Second, the 540-day automatic-extension rule at 8 CFR § 274a.13(d) sometimes moots the practical urgency of an I-765 renewal delay before mandamus becomes worthwhile — if the applicant can continue working under the auto-extension while USCIS finishes the renewal, the "irreparable harm" pressure that drives an unreasonable-delay case is reduced. Where mandamus does tend to fit on the I-765 side is a clean (c)(9) EAD delay: the underlying I-485 is moving at expected pace, but the concurrently filed I-765 has stalled well past USCIS's published range for that category at that service center, and a case inquiry has already gone unanswered. That is a diagnostic conversation, not a mail-order remedy.

Why this practice can speak to it

Novo Legal Group is a bilingual, Colorado-and-Washington immigration practice. Aaron Elinoff is admitted in both states (CO Bar #46468, admitted 2013; WA Bar #58949, admitted 2022), and the firm actively practices at both the Denver and Kent field offices — the two anchors of the firm's employment-authorization work — with additional Washington coverage in the Seattle, Tri-Cities, Yakima, and Spokane areas, and additional Colorado metros beyond Denver. I-765 work spans the full category spread the firm sees in daily practice — asylum-based (c)(8) renewals, concurrent (c)(9) filings paired with I-485 adjustments, DACA (c)(33) renewals, F-1 OPT and STEM OPT, TPS, and H-4/L-2 spousal EADs — which is why the firm's read of a stuck EAD file usually starts with the category code and the underlying-application posture, not with the published range in isolation.

FAQ — I-765 processing time