7 Common EB-2 NIW Application Mistakes to Avoid

1. Weak or Generic Statement of the Proposed Endeavor

The single most common defect in a self-prepared NIW petition is a proposed endeavor described as a field of work rather than a specific undertaking. Every other part of the petition — the Dhanasar analysis, the letters, the exhibits — depends on this statement being precise enough to evaluate. If it reads like a job description or a broad research area, an officer has nothing concrete to test against the three prongs.

What goes wrong

Petitioners often describe their endeavor at the level of a discipline: "advancing renewable energy research," "improving cancer treatment," "developing better AI systems." These statements describe a career, not a plan. They give no sense of what the petitioner will actually do, how, or with what measurable result.

Before and after

Weak: "My proposed endeavor is advancing renewable energy research to help the United States transition to clean energy."

Specific: "My proposed endeavor is the development of a low-cost perovskite-silicon tandem solar cell architecture, using a novel encapsulation method to extend outdoor operational lifespan beyond 20 years, with the goal of reducing utility-scale solar module degradation rates below 0.3% per year within five years."

The second version names the technology, the method, and a measurable target outcome. It can be cross-referenced against evidence of feasibility, prior work, and industry data — the second version gives the officer something to evaluate.

How to fix it

Write the endeavor statement last, after drafting the rest of the petition, and reduce it to one or two sentences naming: (1) the specific technology, process, or intervention; (2) the method or approach; (3) the concrete, ideally quantifiable, outcome sought. If the statement could apply to any qualified person in the field rather than to this petitioner's specific project, revise it further.

2. Mismatched Evidence and Dunstan/Matter of Dhanasar Prongs

A common structural error is assembling a pile of strong evidence — degrees, publications, patents, media coverage — without ever showing which of the three Matter of Dhanasar prongs each item supports. Officers evaluate the record prong by prong, not as an undifferentiated mass of credentials. If your petition doesn't do this sorting for them, they have to do it themselves, and thin spots become obvious rather than buried.

Build an evidence map before you write the brief

Create a working table, one row per exhibit, before drafting the personal statement. This becomes both a drafting tool and something you can adapt into an appendix.

Check for imbalance

Once the table is complete, count rows per prong. A frequent failure mode is stacking ten items under Prong 1 — degrees, awards, citations — while Prong 3 has nothing beyond a boilerplate paragraph, or Prong 2 relies solely on the petitioner's own claims with no corroborating letters. Each prong needs its own distinct evidentiary base; a surplus in one area does not offset a gap in another. Revise the exhibit list until each prong has at least several independent, specific items before finalizing the petition.

3. Letters of Recommendation That Repeat the Resume

A recommendation letter that simply lists degrees, job titles, and publication counts already appearing in the CV adds nothing to the record. Officers read these letters as filler, and when several letters from different recommenders share the same structure, transitional phrases, or even identical sentences, it signals that the petitioner (or a drafter) wrote them rather than the recommenders themselves. This does not automatically defeat a petition, but it invites closer scrutiny of every other document in the package.

What Each Letter Should Contain

1. The relationship. State how the recommender knows the petitioner — as a supervisor, collaborator, journal editor, conference co-panelist, or independent expert who reviewed the petitioner's work. Include how long and in what capacity.
2. Specific projects. Name particular projects, papers, datasets, or deployments the recommender directly observed or evaluated — not a general reference to "the petitioner's research."
3. Independent assessment. Explain, in the recommender's own words, what changed or improved because of the petitioner's work, and why that matters in the recommender's professional judgment.

Signs an Officer Notices

• Identical paragraph structure or phrasing across letters from unrelated recommenders.
• Letters that restate CV bullet points without added detail.
• No explanation of how the recommender came to know the petitioner's work.
• Superlatives ($\text{"world-leading," "exceptional"}$) unsupported by specific examples.

Draft each letter individually with the recommender's input, and vary structure, vocabulary, and examples so each reads as an independent professional opinion.

4. Missing or Inconsistent Documentation of National Importance

A common gap in the national importance argument is asserting that a problem matters without documenting its scale. Statements like "data privacy is a growing concern" or "the US faces a shortage of skilled engineers" carry no weight unless tied to a specific, citable source. Petitions that rely on the petitioner's own framing of importance, rather than external evidence, tend to draw questions about whether the claimed benefit is broad enough to matter beyond the petitioner's immediate field.

Steps to build this section

1. Identify authoritative sources. Use federal agency reports (e.g., Department of Energy, NIH, BLS, CDC), peer-reviewed journal articles, and data from recognized industry associations. Avoid blogs, press releases, or advocacy sites as primary support.
2. Cite precisely. Give the publishing body, report title, year, and a specific figure or finding — not a general reference to "studies show." Include the source as a labeled exhibit, not just a footnote.
3. Tie each citation to the endeavor's stated goal. After citing a statistic or finding, add a sentence connecting it directly to what the proposed endeavor addresses. For example: a Department of Energy report estimating grid storage losses should connect explicitly to the specific storage technology the endeavor develops, not to renewable energy generally.
4. Check for consistency. Make sure the scale of the problem described matches the scope of the endeavor. Citing national shortage statistics while describing a narrow, localized project invites scrutiny over the mismatch between the evidence and the claim it supports.

Every national importance claim should be traceable to a numbered exhibit, not asserted from memory or general knowledge.

5. Overlooking the 'Well Positioned' Evidence Requirement

A common assembly error is treating a strong CV as self-evident proof of being well positioned to advance the endeavor. Degrees, publication counts, and past employers describe a career; they do not by themselves describe a plan. Petitions built this way tend to submit the same credentials evidence twice — once for merit and importance, once again as if it also proved capacity to execute — while leaving the actual forward-looking case thin.

What This Prong Actually Requires

USCIS guidance under Matter of Dhanasar lists specific categories of evidence relevant to this prong. Treat each as a distinct exhibit category, not a byproduct of the CV.

• Track record: prior projects, products, funded work, or ventures similar in nature to the proposed endeavor.
• Model or plan: a written description of how the endeavor will be carried out — methods, milestones, resources needed.
• Progress to date: pilot data, prototypes, preliminary results, signed agreements, or funding already secured.
• Letters addressing feasibility: recommenders who speak specifically to whether the plan is workable, not just whether the petitioner is talented.
• Knowledge of the field: evidence of awareness of the competitive and regulatory landscape relevant to executing the endeavor.

Checklist Before Filing

• At least one exhibit documents a comparable prior undertaking
• A standalone document or section lays out the plan, not just the goal
• Progress evidence exists and is dated
• At least one letter explicitly addresses feasibility, not just merit
• Evidence shows awareness of the field's current state, competitors, or barriers

If any box is empty, that category is missing evidence, not just under-described.

Credentials remain relevant, but only as one input among several, not a substitute for the rest.

6. Disorganized Exhibit List and Poor Cross-Referencing

A petition can contain strong evidence and still generate a Request for Evidence simply because the officer cannot locate the document being referenced. When the personal statement says "see letter from Dr. Smith addressing feasibility" and the exhibits are a stack of unlabeled PDFs merged into one 400-page file, the reviewer either has to hunt for it or notes it as missing.

Build a numbered exhibit list

Create a single index page listing every exhibit in the order it appears in the package. Use a consistent naming convention for both the index and the files themselves:

• Exhibit 1 – Curriculum Vitae
• Exhibit 2 – Letter of Recommendation – Dr. Jane Smith
• Exhibit 3 – Publication – Journal of Applied Physics, 2022
• Exhibit 4 – Citation Report – Google Scholar, [date pulled]
• Exhibit 5 – Press Coverage – [Outlet Name], [date]

Name the actual PDF files the same way (e.g., "Exhibit 3 - Publication - Journal of Applied Physics 2022.pdf") so the physical file matches the index line exactly, whether filed electronically or on paper.

Cross-reference by number, not by description

In the personal statement and cover letter, cite exhibits by number every time a claim depends on supporting evidence: "As shown in Exhibit 4, the petitioner's work has been cited 340 times independently of self-citation." Avoid vague references like "see attached letters" or "as demonstrated by supporting documentation" — these force the officer to search rather than verify.

Final check

Before assembling the final package, read through the personal statement and confirm every exhibit number mentioned actually exists in the index and the file set, and that no exhibit sits in the package unreferenced.

7. Submitting Without a Final Consistency Check

A petition assembled over weeks or months often accumulates small contradictions: a job title listed as "Senior Scientist" on the CV and "Research Scientist II" in a recommendation letter, a publication count that grew between drafting the personal statement and finalizing the exhibits, a citation count pulled from Google Scholar on one date and not updated before filing. Individually these look trivial. To an officer scanning for reliability, they read as carelessness at best and misrepresentation at worst — and they invite an RFE asking the petitioner to reconcile the discrepancy.

Final Review Procedure

1. Build a master fact sheet. List every factual claim that appears more than once — employment dates, titles, degree dates, publication and citation counts, grant amounts, patent numbers — and note where each appears (CV, letters, personal statement, Form I-140).
2. Cross-check each entry. Flag any variance, however minor, and correct it at the source document, not just in the summary.
3. Verify form fields against evidence. Every entry on Form I-140 should be traceable to a supporting exhibit.
4. Confirm the exhibit list is complete. Every exhibit number cited in the personal statement or cover letter must correspond to an actual, correctly labeled document in the package.
5. Read every letter aloud. This catches repeated phrasing, awkward boilerplate, and factual mismatches that silent reading misses.
6. Check uscis.gov for current form editions and fees before printing and assembling the final package, since both change periodically.

Complete this review after all drafting is finished, not during it.