Why RFEs happen in NIW cases, and why you can predict most of them
A Request for Evidence is issued when the record, as filed, does not establish an element of the case by a preponderance of the evidence. The officer reviewing the I-140 is not asking whether the petitioner is impressive in the abstract; they are checking whether each required element is supported by evidence in the file, and issuing an RFE wherever a gap exists between what the petition claims and what the exhibits actually show.
In NIW cases, those gaps cluster predictably around the three prongs set out in Matter of Dhanasar: substantial merit and national importance of the proposed endeavor, the petitioner's being well positioned to advance it, and the balance of factors favoring a waiver of the job offer and labor certification requirement. Officers evaluate each prong independently, so a petition can be strong on one and weak on another — and an RFE will typically name the specific prong, or the specific sub-element of a prong, where the evidence falls short.
Why this is predictable, not random
Because the three prongs are fixed and publicly described in USCIS policy guidance, most of the gaps that trigger an RFE already exist in the petition before it is filed — in a proposed endeavor statement that is too vague, in letters that assert conclusions without supporting exhibits, or in evidence that documents expertise without tying it to the specific endeavor. A structured review of the petition against these three prongs before filing can surface these gaps while they are still fixable. This does not prevent an RFE; it is a way of finding, before submission, the same weaknesses an officer would find after it.
Using this checklist
The sections below walk through that review prong by prong and document by document.
Build the proposed endeavor statement review
Every NIW petition depends on a one- to two-paragraph statement of the proposed endeavor. Before anything else, isolate that statement from the petition letter and review it on its own.
Check items
- Specificity. The statement should name an activity, not a discipline. "Working in renewable energy" is a field. "Developing grid-scale battery storage systems to reduce curtailment losses at utility-scale solar installations in the southwestern United States" is an endeavor.
- Who, what, scope. Confirm the sentence identifies what will be done, in what industry or technical domain, and over what geographic or sectoral reach — a region, a national market, an industry segment.
- Word-for-word alignment. Pull the same sentence (or close paraphrase) from the personal statement, each reference letter, and the exhibit index. If recommenders describe the endeavor differently from the petitioner's own statement, flag the discrepancy.
Worked example
- Vague: "The petitioner intends to continue research in artificial intelligence."
- Specific: "The petitioner intends to develop machine-learning models for early detection of diabetic retinopathy from retinal imaging, for deployment in rural primary-care clinics across the United States."
The second version gives an officer something concrete to measure evidence against — a method, an application, and a population. The first invites a comparison to the entire field, not the petitioner's actual work.
Record the finalized endeavor sentence in one place and copy it verbatim everywhere else it appears in the petition.
Audit the evidence for each Dhanasar prong separately
Go through the evidence exhibit by exhibit and sort each item under the prong it supports. Treat the three prongs as separate audits — evidence that is strong for one prong does not substitute for a gap in another.
Prong one: substantial merit and national importance
- Confirm at least some evidence addresses impact beyond the petitioner's current employer — industry-wide adoption, downstream users, policy influence, or a broader research community, not just internal recognition.
- Confirm impact claims are tied to specific metrics: citation counts, grant or contract amounts, publication venues and reach, licensing or commercialization figures, or documented implemented outcomes.
- Flag any sentence that asserts importance without a citable number or named outcome attached to it.
Prong two: well-positioned to advance the endeavor
- Confirm degrees and credentials are explicitly linked in the narrative to the endeavor, not just listed.
- Confirm employment history, citation record, and letters each state how they connect to carrying out this specific endeavor, not to the field generally.
- Confirm any track record of prior similar work is described with outcomes, not just job titles.
Prong three: benefit of waiving the job offer
- Confirm the petition discusses why the labor certification process is impractical for this kind of work — not merely that it would be inconvenient or slower.
Recording the audit
Use a simple table:
| Prong | Checklist item | Status |
|---|---|---|
| National importance | Impact beyond single employer | Documented / Partially Documented / Missing |
| Well-positioned | Credentials linked to endeavor | Documented / Partially Documented / Missing |
| Waiver benefit | Labor certification impracticality discussed | Documented / Partially Documented / Missing |
Any row marked Missing or Partially Documented identifies where to add or strengthen evidence before filing.
Cross-check reference letters against the record
Reference letters are read against each other and against the personal statement, not in isolation. Run each letter through the following checks before it goes into the packet.
Step 1: Confirm relationship and basis of knowledge
Each letter should state, early and explicitly, who the recommender is, how they know the petitioner's work (supervisor, collaborator, independent expert who reviewed the record, etc.), and how long that relationship has existed. A letter that praises the work without saying how the writer came to know it leaves that basis unestablished.
Step 2: Match specific claims to exhibits
For every number, date, or outcome a letter cites — citation counts, grant amounts, patient outcomes, adoption by a named organization — locate the exhibit that documents it. Build a quick table: Letter author, Claim, Supporting exhibit #. Any claim with no corresponding exhibit needs either a supporting document added or the sentence revised.
Step 3: Compare letters against one another
Read all letters side by side. Flag repeated phrasing, identical sentence structures, or paragraphs that could have been drafted from the same template. Letters that read as interchangeable, even from recommenders with different relationships to the petitioner, draw scrutiny.
Step 4: Compare letters against the personal statement
Check that factual claims — dates of employment, project names, figures — are stated consistently across letters and the personal statement. A discrepancy in a date or a number between a letter and the statement is the kind of inconsistency an officer is positioned to notice on a side-by-side read.
Resolve every flagged item before the letters are finalized.
Build the exhibit index and label scheme
Every factual claim in the petition narrative should point to a specific, numbered exhibit — not to a vague bundle of attachments. If the cover letter states "the petitioner's method has been cited over 200 times (Exhibit 7)," Exhibit 7 should be a citation report, and no other document in the packet should also claim that number.
Build the index table
Create a single table, in the order exhibits are cited in the narrative, with these columns:
| Exhibit # | Description | Source | Date | Relevance to prong |
|---|---|---|---|---|
| 7 | Google Scholar citation report | Google Scholar export | [date pulled] | National importance |
| 12 | Letter from Dr. X, former supervisor | Recommender | [date signed] | Well-positioned |
Keep the Relevance to prong column honest — if an exhibit does not clearly support a prong, that is worth noticing before filing, not after.
Name the files to match
Use a consistent, zero-padded naming scheme so files sort in citation order: Exhibit_07_CitationReport.pdf, Exhibit_12_RecommenderLetter_Smith.pdf. Avoid generic names like scan1.pdf or final_v3.pdf — an officer and, later, you, should be able to tell what a file is without opening it.
Keep it as a living document
The index is not paperwork for its own sake. If an actual Request for Evidence arrives, this table is what you will reopen first: it shows at a glance which prong each exhibit supports and where the gaps are, letting you add or replace exhibits without reconstructing the whole evidentiary record from scratch.
Run a document currency and consistency pass
Small inconsistencies across a petition packet draw attention out of proportion to their importance, because they are the easiest thing for an officer to check and the first sign the file was assembled hastily. Run this pass after the narrative and exhibits are otherwise finished.
CV and resume
- Confirm the CV attached as an exhibit is the current version, not an earlier draft used to write the personal statement.
- Confirm it is dated, and that the date postdates any recent publications, patents, or positions cited in the narrative.
- Confirm every achievement cited in the personal statement or reference letters also appears on the CV, and vice versa.
Names, degrees, and spellings
- Confirm your name is spelled identically on diplomas, transcripts, the personal statement, the CV, and Form I-140.
- Confirm degree titles and institution names match across all of these documents; translated and original versions sometimes differ.
- Where a name has changed (marriage, transliteration variant), confirm supporting documentation of the name change is included.
Translations
- Confirm every foreign-language document has an attached English translation.
- Confirm each translation carries a certification of accuracy and the translator's signature, as USCIS requires for any document not in English.
Priority date basis
- Confirm the petition package will make clear, once filed, that the priority date is the date USCIS receives the properly filed petition — this becomes fixed only upon receipt, not upon mailing.
Before finalizing, check the current Form I-140 edition date, filing fees, and evidentiary expectations on uscis.gov, since these change periodically.
This article describes document-preparation practice only. It is not legal advice.
Final pre-filing self-RFE simulation
Before assembling the final packet, read the completed cover letter and petition narrative one more time — this time as an adversary trying to find gaps, not as the author.
Step 1: List every factual claim
Go paragraph by paragraph through the cover letter and mark each sentence that asserts a fact: a number, a date, an outcome, a credential, a relationship. For each one, write down the exhibit number that supports it. If no exhibit number comes to mind immediately, that claim is a candidate gap.
Step 2: Draft a hypothetical RFE paragraph
For each unsupported or weakly supported claim, write one sentence in the voice of an officer questioning it — for example, "The record does not establish the basis for the recommender's familiarity with the petitioner's specific contributions." This is an internal drafting exercise, not a document to submit or quote from an actual case; it exists only to surface structural gaps.
Step 3: Resolve each hypothetical question
For every question generated in Step 2, either locate or add the supporting exhibit, revise the claim to match what the evidence actually shows, or remove the claim if it cannot be supported. Update the exhibit index accordingly.
Step 4: Repeat once
After revisions, run the same pass again on the updated cover letter. A second pass typically surfaces fewer items; if it surfaces new ones, the narrative likely shifted during edits and needs another consistency check against the exhibit index.
This exercise is a structural review method for checking that claims and evidence align before filing. It does not predict whether USCIS will issue a Request for Evidence or how any particular petition will be adjudicated.
You may also like
Turning a CV into EB-2 NIW Petition Evidence: A Document Inventory Worksheet
Learn how to break down every claim on your CV, match it to a document category for your EB-2 NIW petition, spot gaps, and cross-check it against your recommendation letters.
Read →EB-2 NIW Costs: What to Budget For and Where to Check Each Fee
Lists every cost category an EB-2 NIW petitioner is likely to meet, how to find the current amount on uscis.gov, and how to assemble a simple budget worksheet before filing.
Read →How to Respond to an RFE on Your EB-2 NIW Petition
Learn how to read a NIW RFE notice, build a compliant response packet, and submit it before the deadline without missing a required element.
Read →