EB-2 NIW for STEM Fields: Why USCIS Policy Gives Extra Weight

What the USCIS Policy Manual actually says about STEM

The USCIS Policy Manual, Volume 6, Part F covers the National Interest Waiver classification, including the three-prong framework from Matter of Dhanasar. Within that chapter, USCIS discusses how an officer may weigh certain fields — including those identified on the Department of Homeland Security STEM Designated Degree Program list — when evaluating the first Dhanasar prong, substantial merit and national importance. The chapter also references critical and emerging technology fields tied to federal strategy documents.

Do not rely on a summary of this text, including this one, as the basis for drafting a petition. Policy Manual content is revised by USCIS from time to time, and a chapter number, a cross-reference, or the specific wording used to describe STEM fields can change between updates. Before drafting the national importance section of a petition letter, open the current version of Volume 6, Part F directly on uscis.gov and read the relevant chapter in full. Note the date the page states it was last updated, and record that date alongside any other source material being compiled for the petition.

What this guidance does and does not establish

The Policy Manual text describes a consideration an officer may take into account when evaluating evidence submitted under the national importance prong. It does not create a separate eligibility category for STEM fields, and it does not exempt a petition from the general Dhanasar framework. Nothing in that chapter, and nothing in this article, should be read as establishing that any particular degree, field, or line of research satisfies any Dhanasar prong for any individual petitioner.

The remainder of this article explains how to identify whether a given field falls within the categories the Policy Manual discusses, and how to document and organize evidence connected to those categories. It does not characterize what that evidence does for any specific case, and it does not predict how an officer will weigh it.

Confirm your field counts as STEM for this purpose

Before drafting any argument about STEM, establish, with documentation, whether the applicant's degree and field actually fall under a recognized STEM classification. Two separate frameworks are relevant, and they are not interchangeable.

Step 1: Identify the CIP code on the degree

Every degree conferred by a U.S. institution (and most foreign degrees evaluated by a credential evaluation service) maps to a six-digit Classification of Instructional Programs (CIP) code. Check the transcript, diploma, or degree audit for this code; if it is not printed there, contact the registrar's office or the evaluation service that produced the applicant's credential report and ask them to confirm the CIP code assigned.

Step 2: Check the CIP code against the DHS STEM Designated Degree Program list

The current list is maintained by ICE on the Study in the States website. Search the list for the exact CIP code identified in Step 1. Do not rely on the program's title or department name — matching is done by code, not by name, and similarly named programs sometimes fall on different sides of the list.

Step 3: Save evidence of the lookup

Save a PDF or screenshot of the list page showing the matching CIP code, and record the date accessed. Policy text and designated-degree lists are both subject to revision, so a dated copy establishes what the list said at the time of filing.

Step 4: Check for a separate critical and emerging technology connection

Independent of degree classification, the NIW policy discussion references critical and emerging technology fields drawn from national strategy documents. If the applicant's work relates to one of these named technology areas, note that separately — it does not depend on the CIP code match.

Step 5: Record the outcome

For each applicant, write down plainly: CIP code, whether it appears on the STEM Designated Degree Program list (yes/no, with date checked), and whether the work independently relates to a named critical or emerging technology area. This record becomes the basis for the evidence file built in the next step.

Build the STEM-specific evidence file

Once the applicable CIP code and any critical/emerging technology category are confirmed, assemble a dedicated set of documents that ties the applicant's credentials and work directly to that classification.

Documents to collect

1. Degree transcripts and diplomas — official transcripts showing the degree title and, where printed, the CIP code or program name used by the registrar. If the CIP code is not printed on the transcript, keep the registrar's program description or catalog page that supports the classification used.
2. Doctoral dissertation abstract (if applicable) — the abstract page, with the degree-granting department named, showing the technical subject matter.
3. Federal funding award documents — grant award notices or summaries from agencies such as NSF, NIH, or DOE, with the grant number, award title, and funding period visible.
4. Published critical and emerging technology lists — the specific page or excerpt of any agency or national strategy list naming the technology area, saved with its access date.
5. Agency or national strategy publications — reports, strategy documents, or agency statements that discuss the specific technology area, even where they do not use the word

Map STEM evidence to the Dhanasar prongs in your petition letter

STEM evidence that sits in the petition as unattached background does little for an officer who has to decide which prong of the three-prong Dhanasar framework it supports. Every exhibit referenced in the personal statement or a support letter should be tied, by exhibit number, to one of the three prongs: substantial merit and national importance, well positioned to advance the endeavor, or benefit of waiving the job offer requirement.

Structure the personal statement by prong, not by chronology

Draft the statement in sections headed by each prong rather than as a career narrative. Under each heading, cite exhibits directly: "See Exhibit 14 (CIP code 14.0903, Electrical and Electronics Engineering, matched against the DHS STEM Designated Degree Program list)." Avoid describing a credential or a technology area and leaving the reader to infer which prong it supports.

Instruct support-letter writers to do the same

Give each recommender the exhibit index and ask them to reference specific exhibit numbers rather than paraphrasing the applicant's STEM background in their own words. A letter that names a CIP code, a grant number, or a named critical-technology list entry is easier to cross-check than one that says only "this is an important STEM field."

Worked example (illustrative template, not a real document)

Illustrative template, not a real source: "Dr. [Name]'s doctoral work (CIP code 14.1001, Electrical and Communications Engineering, Exhibit 3) addresses semiconductor fabrication processes identified in [name of agency critical and emerging technology list], Exhibit 9, under the category of advanced manufacturing. This work was supported by [federal agency] award number [award number], Exhibit 11. These three exhibits are offered in support of the substantial merit and national importance prong."

Use this pattern — degree classification, named list entry, funding document — for every STEM-related claim, and repeat the same exhibit numbers consistently between the personal statement, the support letters, and the evidence index described below.

Common mistakes that trigger RFEs on the STEM claim

Generic STEM assertions

A petition letter that calls the applicant's work "a STEM field" without naming the CIP code, the specific DHS list entry, or the critical and emerging technology category it falls under gives an officer nothing to verify. The fix is always the same: name the code, name the list, name the date accessed.

Field importance asserted without a named technology or funding source

Statements like "this area is important to national competitiveness" carry no weight unless tied to a specific, named technology area appearing in a published list or strategy document, or to a specific grant number from a named funding agency. An officer checking this claim looks for a citation they can independently confirm, not a general proposition about the value of science.

Boilerplate repeated across support letters

When several independent support letters contain the same STEM paragraph, word for word or near enough, it reads as drafted by the petitioner rather than written by the recommender. Each letter should draw on the evidence index but frame the STEM connection in the recommender's own language, tied to their own knowledge of the applicant's work.

Stale evidence

DHS updates the STEM Designated Degree Program list periodically, and critical and emerging technology lists are revised as agencies update them. Evidence collected months before filing can reference a superseded version. Before filing, recheck every STEM-related citation against the current list and update the access date in the evidence index.

What an officer checks

In practice this comes down to three things: specificity (a named code or list entry, not a category label), currency (the cited list or document is the version in effect, with a dated access record), and consistency (the evidence index, the petition letter, and the support letters all cite the same sources the same way). A mismatch among these three is a common RFE trigger.

Assemble the final STEM evidence index for filing

Once the evidence file and the petition letter are both drafted, produce a single consolidated index that collects only the STEM-related exhibits into one navigable table. This is a finding aid for the officer reviewing the petition, not a replacement for the full exhibit list that accompanies Form I-140.

Draft the table

Keep it to one or two pages. Pull the relevant rows directly from the running evidence spreadaheet you have maintained, in exhibit order, and format them for printing or PDF insertion.

Sample layout:

Place it correctly

Insert this index immediately after the main table of contents and before the first STEM exhibit itself, so a reviewer encounters it before the underlying documents. In a paper binder, use a labeled divider; in a PDF, add a bookmark titled something like "STEM Evidence Index."

Cross-check before filing

1. Confirm every exhibit number in the STEM index matches the number used in the full table of contents filed with Form I-140 — renumbering during drafting is a common source of mismatches.
2. Confirm every exhibit listed in the index is physically present in the filing.
3. Confirm the "Prong Supported" column matches the prong each exhibit is cited under in the petition letter itself.
4. Save the final version using your established file naming convention and retain a copy for your own records before submission.