NIW Recommendation Letters: What a Specific Letter Can Add—and What It Cannot Prove

A recommendation letter can help explain why a proposed U.S. endeavor matters or how an applicant is prepared to advance it. Its value comes from the writer’s first-hand knowledge, relevant expertise, and specific account of the work. A letter does not establish NIW eligibility just because the writer has an impressive title, and repeating the petition’s conclusions does not replace supporting records.

The Administrative Appeals Office’s Matter of Dhanasar decision evaluates the proposed endeavor, the applicant’s position to advance it, and whether waiving the job offer and labor certification benefits the United States on balance. A useful letter should connect to one or more of those questions and explain the basis for its statements.

Start with the evidence gap

Before asking anyone to write, identify what the rest of the record does not explain clearly. Is the technical work difficult for a general reader to understand? Does the file need context about why a problem matters to a field or group of users? Is there a real project partner who can confirm a role, resource, or next step? A letter is most useful when it answers a defined question rather than adding another broad endorsement.

Make a simple table with three columns: the point the petition needs to establish, the documents already available, and the person who can explain the remaining context. This helps avoid asking five people to write essentially the same praise.

Choose writers for what they can actually explain

A current manager, former supervisor, research collaborator, client, professional colleague, or independent expert may each know a different part of the story. The relevant question is not only how senior the writer is. It is what the writer personally observed, reviewed, funded, adopted, evaluated, or can reliably explain.

A supervisor may be best placed to describe the applicant’s responsibilities and contribution to a completed project. A client may be able to confirm how a service was used and what changed. An independent specialist may explain why a technical result is significant in the field, provided the writer can identify a sound basis for that view. These are examples of possible roles, not a required list or ranking.

If the writer has a close working, financial, or personal relationship with the applicant, describe it accurately. The relationship does not automatically make a letter unusable; hiding it can make the account harder to assess. A letter should distinguish direct observation from information the writer learned from the applicant or another source.

Ask for concrete facts, not a verdict

A strong letter usually gives a reader facts they can check: the writer’s connection to the work, the period and setting, the applicant’s specific contribution, the evidence the writer reviewed, and why that contribution matters. If the writer is describing a future project, the letter should state the actual commitment and its limits. A discussion or expression of interest should not be presented as a signed contract, funding award, or promised adoption.

Avoid asking writers to declare that the applicant “meets all three prongs,” is “essential to the United States,” or is “guaranteed to succeed.” Those are conclusions for USCIS to assess from the full record. Ask the writer to explain their own knowledge and reasoning instead.

Link each letter to the right NIW question

For the first Dhanasar element, a writer might explain a real need in the relevant field and how the proposed work could address it. General statements that the industry is important do not, by themselves, show the significance of one applicant’s specific endeavor.

For the second, a writer may describe the applicant’s relevant skills, prior results, technical role, access to resources, or progress toward the proposed work. The letter should explain how the writer knows these facts. A résumé summary adds little if it does not say what the applicant did.

For the third, a writer with direct knowledge of a project or organization may explain a concrete reason the proposed work is difficult to evaluate through a standard job-offer and labor-certification process, or why the particular plan has practical value. The letter should address the actual case circumstances, not make a generic statement that every NIW applicant should be granted a waiver.

One letter can address more than one point, but it should not stretch beyond the writer’s knowledge. It is also reasonable for a letter to be useful as context while contracts, funding records, publications, project documents, or adoption records provide separate corroboration.

Check consistency before filing

Compare every letter against the résumé, proposed endeavor statement, project plan, contracts, publications, and other exhibits. Check dates, job titles, technical terms, projected results, and the description of the applicant’s role. Resolve differences instead of silently choosing the more favorable version. If a result is still prospective, label it as a forecast and explain what it depends on.

Keep the final letter in the writer’s own voice. The applicant may provide factual information and correct errors, but should not attribute conclusions or personal observations to someone who did not make them. Do not invent a recommender, quote, client result, or commitment.

There is no substitute for assessing the whole petition against current official guidance and the applicant’s facts. Read the USCIS Policy Manual, Volume 6, Part F, Chapter 5 and Matter of Dhanasar, 26 I&N Dec. 884 (AAO 2016). Policy checked on 23 October 2026.

For general information about the U.S. EB-2 NIW service, see U.S. EB-2 National Interest Waiver.