Answering a specialty occupation RFE: the record before the argument

The notice arrives, and the clock starts. You have until the response deadline printed on the form, there is no extension, and a late filing is a denial with extra steps. So the first instinct is to start drafting — open the brief bank, find the specialty occupation argument that worked last time, adapt it.

That instinct is usually backwards. The argument is rarely what fails. In a specialty occupation RFE, the officer is not asking to be persuaded that the law says what you say it says. They are asking to be shown a record that holds together — and the record is made of documents written at different times, by different people, for different purposes, none of whom were thinking about each other.

What the officer is actually asking

An H-1B RFE tends to land on one of a small number of grounds, and it is worth naming them before you start writing, because they call for different evidence:

• Specialty occupation not established. The duties read as generic, or the degree requirement isn’t tied to a specific field. This is the most common, and the rest of this post is about it.
• Beneficiary qualifications. The degree, the credential evaluation, or the experience equivalency doesn’t reach the specialty the petition claims.
• Employer-employee relationship and right to control. Third-party placement without the contracts and itinerary that show who directs the work.
• Availability of non-speculative work. No end-client work order covering the validity period requested.
• Maintenance of status. A gap in the pay stubs, I-94s, or prior approvals that the timeline can’t account for.

Read the notice closely enough to know which of these you actually have. A response that answers all five when the officer asked about one is not thorough; it is noise around the answer, and it invites a second look at four things nobody had questioned.

Specialty occupation turns on consistency

The regulation gives more than one route to establishing a specialty occupation, and you only need one of them. Which means the real decision is made early and quietly: you pick the route your evidence can carry, and then everything in the record has to point the same way.

Work from the current regulatory text rather than the version in your brief bank. The specialty occupation criteria were revised by the H-1B modernization rule that took effect in January 2025, and a template that predates it can argue a standard that has since been reworded. This post is about assembling the record, not about what the standard currently says — that part is your call, on the current text.

The failure mode is almost never a bad argument for a chosen route. It is that the record quietly argues a different one. The support letter says the role is so complex it requires a degree; the job posting the company ran three months earlier says “degree preferred.” The petition claims the employer normally requires a degree; the two most recent hires into the same title did not have one. Nobody lied. The documents were simply written by different people who were not reading each other.

The three-document problem

For most H-1B petitions the tension lives in three documents that have to agree and are drafted separately:

1. The certified LCA. Fixes the SOC code, the wage level, and the place of employment. It is the least flexible document in the file, because it is already certified.
2. The job offer letter. Written by HR, usually from a template, usually before anyone thought about the petition.
3. The employer support letter. Written by you, or with you, and the only one of the three drafted with the RFE in mind.

The classic contradiction is a wage level that says entry-level next to a duties description that says senior specialist. Both may be defensible on their own. Together they are an invitation. The same goes for an SOC code that describes a broader occupation than the duties you are characterising as specialised.

You usually cannot fix the LCA at this stage. What you can do is know about the tension before the officer points it out, and address it in the response rather than leaving it to be discovered.

A working order of assembly

The order matters, because each step constrains the next. Drafting first is what produces a beautiful brief that the exhibits quietly contradict.

1. Re-read the notice and mark the ask. One sentence, in your own words, of what the officer wants to see. If you can’t write that sentence, read it again.
2. Inventory what already exists. LCA, offer letter, prior support letter, org chart, contracts, prior approvals, the job posting. Read them as a set, not one at a time.
3. List the contradictions. Wage level against duties. SOC code against duties. Posting against claimed requirement. Prior hires against “normally requires.” This is the step people skip, and it is the one that decides the outcome.
4. Pick the route the evidence supports. Not the one you would prefer. If the industry-practice route needs comparable postings from similar organisations, you need those postings in hand before you commit to it.
5. Fill the gaps, then draft. New declarations, an expert opinion, comparable postings, a revised organisational chart. Draft last — the brief should describe a record that already exists.
6. Check every factual claim against a page. Every assertion in the response should be traceable to a specific page of a specific exhibit. If it isn’t, either find the page or drop the claim.

Before it goes out

A short pass that catches most of what comes back a second time:

• Does the duties description in the response match the one in the original petition? A materially expanded set of duties reads as a new case, not a clarification.
• Does every exhibit referenced in the brief exist in the index, and does every exhibit in the index get referenced?
• Are the dates internally consistent — employment start, LCA validity, requested validity period, and any itinerary?
• Is the response responsive to the notice as written, rather than to the RFE you have answered most often?

Why this is tedious, and what to do about it

None of the above is intellectually hard. It is hard because it is cross-referential: the contradictions live between documents, not inside any one of them, and finding them means holding five files in your head at once, late, against a fixed deadline. That is precisely the kind of work that gets compressed when the week is full — and the compression is invisible until the second RFE arrives.

It is also the part of the job that software can genuinely take on. In Attest, the LCA and the offer letter are read together and the disagreements are surfaced as a list — wage level against duties, SOC code against the specialty claimed — with each flag citing the page it came from, so checking it takes a click rather than a re-read. The evidence map is built against the criteria for the case type, so what is missing is a list rather than a memory. The drafting is assistive and the attorney approves everything before it is final; the point is not that the software writes the response, but that you start from a record you have already seen the holes in.

If you want the specifics for this case type — the full document checklist, the criteria the evidence map is built against, and the grounds USCIS comes back on — they are on the H-1B case page. If you would rather see it work than read about it, you can drop a notice in and watch what comes back.

Attest is software, not a law firm, and this post is not legal advice. It describes how to organise a file, not what to argue in one. The supervising attorney retains sole professional responsibility for the response and the filing.