Ian Schiller
A specialty occupation Request for Evidence (RFE) is not a request for more paper. It is a challenge to two related conclusions: that the position meets the regulatory definition of a specialty occupation, and that it satisfies at least one of the four criteria that go with that definition. Responses that work answer each challenge in the notice separately, tie it to the applicable regulatory criterion or requirement, and point to evidence that is consistent with the record already on file. Responses that fail usually restate the original support letter at greater length.
This guide covers how to decode a specialty occupation RFE, build an evidence map for it, rewrite the duty statement so it carries the legal argument, and quality-check the response before it goes back to U.S. Citizenship and Immigration Services (USCIS). It assumes you are working an active matter with a deadline.
The statutory definition at INA 214(i)(1) requires theoretical and practical application of a body of highly specialized knowledge, plus attainment of a bachelor's or higher degree in the specific specialty as a minimum for entry into the occupation. The implementing definition sits at 8 CFR 214.2(h)(4)(ii) and the criteria at 8 CFR 214.2(h)(4)(iii)(A). The two work together. A position does not meet the definition unless it also satisfies at least one criterion, so a response that argues a criterion and never addresses the definition has answered half the question. The definition also states that a position is not a specialty occupation if a general degree, without further specialization, is sufficient to qualify for it.
A position must satisfy at least one of the four criteria at 8 CFR 214.2(h)(4)(iii)(A):
One important change from the prior version of the regulation: the former "complex or unique" alternative under criterion two is gone. Specialized, complex, or unique duties now appear under criterion four.
Only one criterion has to be met, but meeting one is not the whole showing. The position must satisfy the definition and at least one criterion. Spreading a thin argument across all four is weaker than documenting one or two thoroughly. Read the notice to see which criteria the officer actually addressed, and lead with the criterion your record best supports.
DHS's Modernizing H-1B Requirements final rule took effect January 17, 2025. Four points from it are worth citing directly in a specialty occupation response:
These points are in the regulatory text, not the preamble. Cite the regulation for the governing standard, then show how the facts and evidence establish the required connection in the particular case.
USCIS Policy Alert PA-2026-05, effective August 5, 2026, revised the agency's evidentiary standards guidance and applies to benefit requests pending or filed on or after that date. Officers may deny benefit requests that lack required initial evidence or otherwise fail to establish eligibility without first issuing an RFE or a Notice of Intent to Deny. The alert also confirms that a partial response may be treated as a request for a decision on the existing record, consistent with 8 CFR 103.2(b)(11), keeps response deadlines at up to 12 weeks for RFEs and 30 days for NOIDs while allowing shorter deadlines, and eliminates the additional 14-day period previously given for notices mailed outside the United States.
Two practical consequences. First, a thin specialty occupation showing at filing is no longer reliably rescued by an RFE. Second, when you do get one, a partial response is a decision on the record, so an incomplete answer to any single challenge is a real risk. Both point the same direction: build the specialty occupation record before filing. Our pre-filing evidence and consistency audit covers that side, and the general RFE response workflow covers the mechanics that apply to any notice type.
The officer quotes your duty statement back and observes that it could describe a position at any level in any organization. This targets criteria one and four. The fix is specificity, not volume.
The petition accepts several fields and at least one has no clear connection to the duties. Under the current standard, multiple qualifying fields are permissible, and the problem is an accepted field without the required logical connection. Document that connection where the record supports it. If it does not, counsel should consider whether narrowing the stated requirement would merely clarify the position as filed or instead amount to an impermissible material change.
The officer cites the OOH entry showing that a degree is not normally required, or that employers accept varied backgrounds. The OOH is a labor market reference USCIS may consult, not the regulatory standard, and it describes occupations at a level of generality that often does not match a specific position. Where the objection rests on the OOH saying some employers accept less, the regulation's definition of "normally" at 8 CFR 214.2(h)(4)(iii)(A)(5) is directly relevant. Address the citation on the record rather than ignoring it.
This targets criterion three. The officer may point to the employer's job postings, prior hires without degrees, or an organizational structure that does not show a degreed track. This is the criterion most often lost on facts the employer already controls.
Where the beneficiary is staffed to a third party, the officer may focus on that third party's requirements for the position and evidence of the actual work to be performed. Petitioner-side documentation alone may not answer this. Before gathering that evidence, confirm that the regulatory staffing framework applies: working at a client site is not the same as being staffed into the client's organizational hierarchy.
Before drafting anything, index the notice into discrete challenges and map each one to a criterion, evidence sources, and a check against what you already filed. The mapping step is what prevents the two most common response defects: answering a challenge the officer did not make, and contradicting your own initial filing.
Most specialty occupation RFEs are, at bottom, a complaint about the duty statement. A working duty statement does five things: allocates time across duties, names the specific methods and tools used, shows where specialized knowledge is applied and why a generalist could not substitute, identifies the deliverables and who relies on them, and situates the position in a reporting structure.
Compare these two descriptions of the same illustrative position:
Weak: "Analyzes data, prepares reports, and supports business decisions using statistical methods."
Stronger: "Designs and validates mixed-effects regression models (40% of time) on claims data of roughly 2 million records to estimate the effect of formulary changes on utilization; specifies model structure, tests distributional assumptions, and documents limitations for actuarial review (25%); builds reproducible analysis pipelines in R and SQL and maintains version-controlled code and validation logs (20%); presents findings and confidence intervals to the pricing committee, which relies on them to set plan-year assumptions (15%). Reports to the Director of Actuarial Analytics."
The second version is not longer for its own sake. Every added element does legal work: it supports complexity under criterion four and makes the specialized knowledge required by the duties visible rather than asserted.
Under the "logical connection" standard, the persuasive unit is coursework, not the name on the diploma. For each field the position accepts, state which duties it prepares the candidate to perform and cite the specific courses or curriculum components that do the preparing. Where an accepted field is a general one, show the specialization: concentration, upper-division sequence, capstone, thesis, or licensure. If an accepted field cannot be connected persuasively to the duties, revisit whether that field can properly remain part of the stated educational requirement.
This is the same discipline used in evidence mapping for other categories. If you have run our EB-1A evidence mapping workflow or the O-1 evidence mapping workflow, the structure will be familiar: claim, criterion, evidence, gap, owner.
An expert opinion helps when the expert has genuine credentials in the relevant field or industry, has reviewed the actual duty statement and supporting documents, explains a methodology, and reaches a reasoned conclusion about this position rather than the occupation in general. It hurts when it is conclusory, when it recites the occupation's general profile without engaging your facts, when the expert's field does not match the duties, or when it states a degree requirement that contradicts the employer's own hiring history. Officers are not bound by expert opinions, and a weak one invites the officer to say so on the record.
Where the beneficiary is staffed to a third party, meaning contracted into a position in that third party's organizational hierarchy rather than merely providing services to it, that third party's requirements for the position are most relevant to the analysis. In practice that means an end-client letter that states the position's duties and degree requirement, a statement of work or contract showing the scope and duration, and documentation of the reporting structure. Confirm that the end-client's description of the work matches the petition, the LCA worksite, and the requested dates. A material inconsistency between third-party evidence and the petition or LCA can undermine the record and should be addressed rather than ignored.
Several decisions in this workflow are legal judgment calls that no checklist or tool should make: which criteria to lead with, whether to narrow an accepted degree field mid-case and how to explain it, whether to obtain an expert opinion, how to characterize an inconsistency in the employer's hiring history, whether the position as actually structured supports the requirement at all, and whether a withdrawal or refile is the better path. This article describes practice approaches, not legal advice for any specific matter, and adjudication varies by service center and officer.
The slow parts of a specialty occupation response are mechanical: reading the notice closely enough to catch every sub-issue, re-reading a filing you assembled weeks ago, checking whether the rewritten duties still match the LCA and support letter, and confirming that the authority you are citing is current.
Immigration teams use Visalaw AI for those steps: analyzing the notice and the filed record to produce an issue list and an evidence-gap list, checking consistency across the documents in the file, researching current immigration authority with citations that the attorney then verifies, and drafting response sections and duty language for attorney review. The practical H-1B prompts post has starting prompts for the H-1B side of this work, and the use cases page shows where the workflow fits alongside drafting and research. Attorney review of the legal theory and the final record is still the control point, and it should be.
The response that clears a specialty occupation RFE is usually not the longest one. It is the one where each challenge in the notice has a named criterion, mapped evidence, and no contradiction with the record already filed. Build the map first, and the drafting gets shorter.
See how Visalaw AI supports an H-1B case-preparation and RFE response workflow.
Working the prevention side too? Our upcoming sessions cover pre-filing evidence review and RFE response workflows in practice.
View all blogs
Subscribe below to receive tips for using AI in immigration law, product updates, and relevant news in immigration.
Memphis, TN
