No Fault or Technical Reasons Under INA §245(c)(2)

The statutory exception in INA §245(c)(2)

INA §245(c)(2) bars specified applicants who failed to maintain continuously lawful status since entry, but expressly excludes a failure occurring “through no fault” of the applicant or “for technical reasons.”

The implementing regulation at 8 C.F.R. §245.1(d)(2) defines what those terms mean for adjustment purposes.

The exception is expressly limited by regulation

8 C.F.R. §245.1(d)(2) states that the no-fault or technical-reasons phrase “shall be limited to” the listed categories.

Inaction of a designated individual or organization

The first regulatory category requires more than merely proving that another person made a mistake.

The regulation requires:

1. An individual or organization designated by immigration regulation to act for the applicant;
2. Inaction by that designated person or organization;
3. A circumstance over which the applicant had no control; and
4. Acknowledgment of the inaction by that person or organization.

Designated school officials and exchange program sponsors

The regulation itself provides examples involving:

• A designated school official under the F-1 regulations; and
• An exchange program sponsor under the J-1 regulations.

A qualifying case may arise where the designated official fails to provide required notification or fails to forward a request necessary to continue immigration status.

Attorney or representative error

Attorney error does not automatically satisfy 8 C.F.R. §245.1(d)(2)(i).

The first question is whether the person or organization was actually designated by immigration regulation to act for the applicant in the relevant status-maintenance process.

The analysis can become highly fact-specific where:

• An employer's counsel handled an H-1B extension;
• A dependent believed the principal's filing also protected the dependent;
• A representative failed to submit a separately required application;
• An authorized school official failed to complete a required action; or
• USCIS records contain an agency-generated status error.

Technical violation caused by USCIS inaction

8 C.F.R. §245.1(d)(2)(ii) recognizes a technical violation resulting from agency inaction.

The regulation gives as an example an applicant who:

1. Properly files a request;
2. Files it timely;
3. Seeks to maintain immigration status; and
4. Remains awaiting USCIS action on that request.

The importance of a timely status-maintenance filing

The USCIS-inaction example in the regulation specifically contemplates a properly filed and timely request to maintain status.

A late application presents a different issue and should not automatically be characterized as technical delay simply because USCIS ultimately adjudicated it.

Questions include:

• When did the previous status expire?
• When was the extension or change-of-status filing received?
• Was the request facially proper?
• Did a regulation permit late filing?
• Did USCIS retroactively recognize the requested period?
• Was the application ultimately granted or denied?
• What status did the approval notice actually confer?

What if USCIS later denies the extension or change of status?

A pending request and an approved request do not necessarily produce the same immigration consequences.

A later denial may reveal that the applicant never obtained the requested continuation of lawful status.

The precise effect depends on:

• The underlying classification;
• The filing date;
• The status expiration date;
• The reason for denial;
• Whether any period received regulatory protection;
• Whether the no-fault/technical exception independently applies; and
• Whether INA §245(k) or another adjustment exemption is available.

Physical inability to request an extension

8 C.F.R. §245.1(d)(2)(iii) recognizes a technical violation caused by the applicant's physical inability to request an extension of nonimmigrant stay.

The regulation gives hospitalization when the authorized stay expires as an example.

The explanation must be supported by a letter from:

• The hospital; or
• The attending physician.

Does a pending asylum application qualify as a technical reason?

A pending asylum application does not automatically create lawful nonimmigrant status.

Likewise, merely filing Form I-589 does not automatically establish that a subsequent nonimmigrant status violation occurred through no fault or for technical reasons under 8 C.F.R. §245.1(d)(2).

Does a pending Form I-485 qualify as a technical reason?

Not merely because it was filed.

A pending adjustment application generally does not recreate or extend the nonimmigrant status that existed before filing.

An applicant can therefore be:

• Lawfully admitted historically;
• Out of nonimmigrant status;
• In a period of authorized stay because Form I-485 is pending; and
• Still subject to a statutory status bar unless an exemption applies.

See Admission vs. Lawful Status.

Evidence for a no-fault or technical-reasons claim

The evidence should be matched to the exact regulatory subsection.

Potential evidence includes:

• Prior Forms I-94;
• Forms I-797;
• Extension or change-of-status applications;
• USCIS receipt notices;
• Proof of filing and delivery;
• USCIS processing history;
• Letters from designated school officials;
• Letters from exchange program sponsors;
• Acknowledgment of qualifying inaction;
• Hospital records;
• Physician letters;
• Employer records;
• Immigration correspondence;
• Applicant declaration; and
• A precise chronological status chart.

Responding to an RFE or NOID

When USCIS alleges failure to maintain status, the response should identify:

1. The exact alleged period of unlawful status;
2. The immigration classification during that period;
3. The statutory adjustment bar USCIS invokes;
4. The particular subsection of 8 C.F.R. §245.1(d)(2) relied upon;
5. Evidence proving each regulatory element;
6. Any immediate-relative or special-category exemption;
7. Any INA §245(k) argument;
8. Any INA §245(i) grandfathering; and
9. Why USCIS's chronology or legal conclusion is incorrect, if applicable.

See I-485 RFEs, NOIDs & Denials.

Other provisions may be stronger than the technical exception

Before relying on 8 C.F.R. §245.1(d)(2), determine whether a broader statutory exemption already resolves the problem.

Technical violations and adjustment discretion

If the applicant establishes that the statutory status bar does not apply because the failure falls within the regulatory exception, statutory eligibility and discretion remain separate issues.

Relevant discretionary evidence can include:

• The cause of the status problem;
• The applicant's diligence;
• Prompt efforts to correct the issue;
• Reliance on official procedures;
• Family circumstances;
• Length of residence;
• Employment history;
• Compliance after the problem was discovered; and
• Other favorable and adverse circumstances.

Frequently asked questions