Defining the Proposed Endeavor With Specificity and Credible Scope

Use an endeavor canvas before writing narrative#

The endeavor statement is the load-bearing description in an NIW filing. Substantial merit and national importance are assessed with respect to the endeavor; positioning concerns the ability to advance it; and the waiver balance depends on its nature and expected benefit. If the statement changes from section to section, the prongs may appear to address different projects. Create one controlled endeavor definition and a glossary for its central terms before collecting support letters or drafting prong arguments.

Do not confuse occupation, career, and endeavor#

Confirm that the occupation and degree or exceptional ability align by reviewing Who Qualifies for the Underlying EB-2 Classification?. The endeavor cannot repair an unrelated or unsupported underlying classification.

A job description can contribute facts but usually describes duties within one position, while an endeavor may extend across employers, projects, research, entrepreneurship, consulting, or collaborations. Conversely, describing a lifetime mission can be too broad to evaluate. The correct level includes enough operational detail to test merit, reach, positioning, and waiver rationale while allowing reasonable implementation changes. State what is stable—the problem, method, output, or beneficiary group—and what can vary, such as employer, client, partner, or location.

Build the causal pathway from activity to benefit#

1. Inputs

   Identify expertise, data, funding, facilities, relationships, permissions, or other necessary resources.

2. Activities

   Describe the actual research, development, delivery, analysis, commercialization, education, or implementation work.

3. Outputs

   Name concrete products, studies, services, standards, tools, programs, or deliverables.

4. Adoption or use

   Explain who may use the outputs and what evidence supports that pathway.

5. Outcomes

   Describe the credible technical, economic, health, educational, cultural, business, or other benefit.

6. Broader implications

   Explain how effects could extend beyond a single employer, client, or local transaction.

Every arrow in the causal pathway needs a source or a stated assumption. Expertise may support the ability to perform activities but does not prove that users will adopt outputs. A letter of interest may support demand but not completed deployment. A pilot can show feasibility but not national scale. Label completed, in-progress, committed, and projected facts separately. This prevents a plausible vision from being written as an accomplished nationwide result.

Calibrate scope to the evidence#

Scope has at least four dimensions: subject matter, activities, geography, and time. An endeavor can be nationally important without operating in every state, but the claimed broader implications should be supported. A local pilot may be part of a broader endeavor when the evidence explains replication, dissemination, standards influence, supply-chain effects, research contribution, or another credible pathway. Do not add “national” to a local service merely to satisfy the prong. Instead, identify the actual scale mechanism and its constraints.

• ○The endeavor can be summarized without using only a job title or industry name.
• ○Activities use specific verbs and identify expected outputs.
• ○Users, beneficiaries, or adopters are defined.
• ○The causal pathway distinguishes evidence from assumptions.
• ○Geographic and stakeholder scope match the supporting record.
• ○Completed progress is separated from future milestones.
• ○The execution setting is credible and internally consistent.
• ○The statement is the same across forms, plan, letters, and prong analyses.

Compare three versions before choosing the final scope#

Draft a narrow version limited to committed near-term work, a central version reflecting the best-supported program, and a broad version capturing longer-term possibilities. Test each against available evidence. The narrow version may understate broader implications; the broad version may depend on speculative partners, funding, or adoption. The central version should maximize explanatory accuracy rather than ambition. Preserve the rejected versions and the reason for choosing the final one so later updates do not silently expand the filing theory.

Once the endeavor is stable, test the first half of prong one through Dhanasar Prong One: Establishing the Endeavor’s Substantial Merit and then assess the separate national-importance inquiry.

Control changes between planning and filing#

Version the endeavor statement and maintain a change log. Record changes in employer, venture, research topic, product, customer group, methodology, geography, funding, or milestones and assess whether the central endeavor remains the same. Reconcile older business plans, grant applications, public profiles, patents, publications, contracts, and letters. Differences can reflect legitimate evolution, but unexplained incompatibility can weaken the credibility of the plan and the connection between past achievements and future work.

The final endeavor packet should contain the one-paragraph definition, canvas, causal pathway, milestone plan, stakeholder map, execution structure, evidence register, assumptions, risks, and version history. A reviewer should be able to evaluate the endeavor without reconstructing it from the résumé. That packet then becomes the shared factual source for the substantial-merit, national-importance, well-positioned, and balancing analyses, while each prong retains its own conclusion.

Model the endeavor through concrete stakeholder journeys#

Select two or three representative users, institutions, customers, communities, or field actors and describe how each encounters the endeavor. Identify the starting condition, activity received, output used, behavior or decision changed, expected outcome, and evidence source. The journeys should not be fictional success stories; they are test cases for the operating logic. Where a stakeholder is prospective, label the assumptions and use comparable evidence or specific interest records to show why the pathway is credible.

A stakeholder map also reveals conflicts. A product may benefit users while imposing integration costs on institutions; research may have broad value but depend on restricted data; a workforce program may serve participants but require employer adoption; a consulting model may help individual clients without producing broader dissemination. Address these tradeoffs and identify how the endeavor manages them. This strengthens both the merit mechanism and the later national-importance analysis.

Translate the endeavor into a minimum viable evidence plan. For each activity, name one primary record that would verify completion and one measure that would show progress: protocol, prototype, publication, executed agreement, curriculum, deployment log, user result, validation report, standards submission, or another output. Set a realistic date or sequence and assign responsibility. The plan should allow a future reviewer to compare intention with actual development instead of relying on a static business narrative.

Perform a boundary test against adjacent work. List activities that are inside the endeavor, related but not central, and outside. This is especially important for multidisciplinary professionals, founders with several ventures, and consultants serving different industries. The filing need not describe every future task, but it should not claim national importance for one activity while using unrelated achievements to establish positioning. The boundary table keeps evidence selection faithful to the stated endeavor.

Test the final definition with three readers: a field expert, an operational partner, and a reviewer unfamiliar with the occupation. The expert should recognize the technical or professional substance; the partner should understand activities, resources, and outputs; the unfamiliar reviewer should be able to distinguish the endeavor from the industry and from the person's résumé. Record questions from each review and revise ambiguous terms. If different readers imagine materially different projects, the statement is not yet controlled enough for consistent prong analysis.

Keep a terminology register for acronyms, product names, research methods, market segments, and beneficiary groups. Define each term once and use it consistently. Explain technical language in plain English without changing its meaning. This is particularly important when letters from experts use narrower language than a business plan or when public materials use marketing terms. A controlled vocabulary helps the reviewer follow the same endeavor across disciplines and prevents accidental expansion through synonyms.