How to Build a Practical NIW Endeavor Plan: Scope, Milestones, and Evidence
A useful NIW endeavor plan explains what work you intend to carry out in the United States, why that work matters, what you will personally do, and what evidence supports the next steps. A broad career goal such as “advance artificial intelligence” or “improve public health” does not answer those questions by itself. The plan should be specific enough to assess, while leaving room for a project to develop as real work does.
USCIS evaluates an NIW petition under the EB-2 category and the three-part framework in Matter of Dhanasar. A written plan can help explain the proposed endeavor and show how the applicant is positioned to advance it. It does not replace EB-2 eligibility, establish national importance on its own, or guarantee approval.
Start with the work, not the job title
Describe the actual undertaking rather than relying on an occupation, industry, or impressive title. State the problem or need you will address, the people or organizations expected to benefit, the methods or services involved, and the results you intend to produce. If the work includes several connected activities, explain how they fit together.
For example, “work as a data scientist” describes a position. A more informative description identifies the analysis or system the applicant plans to develop, the documented need it addresses, the intended users, and the applicant’s role. The facts will differ by field; the point is to let a reader understand the proposed work without guessing.
Do not make the description broader just to attach it to a nationally important field. USCIS distinguishes the importance of a field from the importance of a specific proposed endeavor. Explain the connection with evidence, such as the problem’s scale, the way the work could be used, or its potential effects beyond one employer or client. A local project may have broader implications, but its location alone does not establish them.
Turn the description into a work plan
A practical plan can be organized around a small number of stages. For each stage, identify the activity, an expected output, a realistic period, the people or resources needed, and how progress could be documented. The dates should reflect actual dependencies and should not be presented as guaranteed results.
Plan element | What to explain | Records that may help |
Scope | The problem, intended users, and work to be carried out | Project description, research outline, product or service specifications |
Applicant’s role | Decisions, technical work, leadership, or other contribution | CV, role description, prior work samples, agreements |
Next steps | Activities and outputs in a sensible order | Milestone plan, pilot outline, development schedule |
Resources | Funding, facilities, collaborators, or access required | Budget, funding records, contracts, resource commitments |
Progress | Work already completed and what it supports next | Prototypes, publications, datasets, test results, project records |
External interest | Who may use, support, evaluate, or fund the work | Customer inquiries, letters of interest, investor or partner correspondence |
These records are examples, not a mandatory checklist. Use only documents that exist and can be accurately described. A plan should distinguish completed work, work under way, and future projections. If an important step depends on a permit, funding decision, employer, or third party, say so instead of describing it as settled.
Connect the plan to the three Dhanasar questions
The first prong asks whether the specific proposed endeavor has substantial merit and national importance. Explain the need the work addresses and the likely broader implications. National importance is not established merely by saying the industry is important or that the work could help the economy. Support the explanation with reliable, relevant evidence and connect that evidence to the proposed work.
The second prong asks whether the applicant is well positioned to advance the endeavor. Link education, skills, knowledge, prior related work, progress, a detailed plan, and any relevant interest or support to the tasks ahead. Past success may be relevant, but it should not be described as proof that a future project will certainly succeed. USCIS’s guidance says a person may be well positioned without showing that success is more likely than not; unsupported claims still do not meet the burden of proof.
The third prong asks whether, on balance, it would benefit the United States to waive the job offer and labor-certification requirements. Explain the circumstances that make the waiver appropriate in the applicant’s case. A plan that shows a valuable undertaking does not automatically answer this separate question.
Make every claim traceable
Before finalizing the plan, make a simple claim-to-record table. For each important statement, record the document that supports it and note whether the document proves a past fact, a present commitment, or a future estimate. If a claim has no support, narrow it, qualify it, or leave it out.
Pay close attention to projected reach, users, job creation, savings, health effects, or economic impact. A forecast should state its assumptions and show where the numbers came from. Avoid presenting a target as an achieved result. Where a partner or prospective customer has expressed interest, quote the nature of that interest accurately; an informal conversation is not a signed commitment.
Letters from experts or interested organizations can explain context or confirm what the writer knows. They should not be asked to certify conclusions outside their knowledge. The underlying plan and documentary record still need to explain the applicant’s work and support its key claims.
Review the plan against the petition record
Use the same description of the proposed endeavor across the plan, Form I-140 materials, personal statement, CV, recommendation letters, and supporting exhibits. The wording need not be identical, but the scope, role, intended work, and stage of progress should agree. If the project changed, explain what changed and why.
A final review can ask:
Can a reader identify the proposed work, its intended users, and the applicant’s role?
Does the evidence explain why this particular work matters, rather than only why its field matters?
Do the applicant’s experience and progress relate directly to the next steps?
Are commitments, completed work, and projections clearly separated?
Can each material claim be traced to a reliable record?
Does the plan leave the three Dhanasar prongs as separate questions?
An endeavor plan is a way to make a petition’s logic and evidence easier to evaluate. It is not a fixed USCIS form or a promise of a particular decision. The facts, eligibility basis, and applicable policy should be reviewed for the individual case before filing.
For an overview of the NIW service scope, see the U.S. EB-2 NIW program page.
Comments