A water treatment engineer redesigns a plant's filtration sequence so that it handles seasonal contamination better. A transit planner restructures a bus network around frequency rather than coverage. An urban planner develops a method for mapping flood exposure at the block level. Each of these professionals does work that affects the daily lives of many people. And each of them, when they sit down to describe an EB-2 National Interest Waiver endeavor, hits the same wall: the work was done for one utility, one agency, one city.
The Dhanasar framework asks about national importance. How does a project in a single metropolitan region meet that standard? The answer is not to pretend local projects are national. It is to show how the endeavor, the method, and the person behind it reach beyond the jurisdiction where the work was first done. This article explains how.
Note: This article is educational and does not give legal advice. EB1 Mentor is not a law firm. USCIS interpretation of the national interest waiver framework can change, so verify current requirements with the official USCIS Policy Manual or a qualified immigration attorney.
The Core Problem: Scale of Impact Versus Scale of Project
Infrastructure is local by nature. Pipes, rails, and roads are built in specific places for specific populations. But the problems they address are often shared across many places: aging water systems, extreme weather, congestion, housing growth, and funding constraints. The national importance argument rests on that second fact, not the first.
An officer reading a petition will ask a simple question: if this person succeeds in what they propose to do, what is the likely effect beyond the places where they work? A petition that answers 'it will help the city I work for' will usually fall short. A petition that answers 'it will give hundreds of utilities a method for addressing a problem that has been documented by credible national sources' stands on firmer ground.
Expert insight: Local excellence is evidence of capability. National importance comes from replicability, adoption, and the significance of the underlying problem. Make sure your petition separates these ideas rather than letting one stand in for the other.
Three Bridges From Local to National
There are several credible ways to connect local work to broader importance. Most strong petitions use at least two.
Bridge one: the problem is national
Many infrastructure challenges are widely documented. Government agencies, professional societies, and research institutions publish assessments of water system conditions, transportation performance, climate resilience, and housing supply. If your endeavor addresses a problem those sources identify as significant, you can cite them to establish that the problem is not parochial.
The care required here is in sourcing. Use specific publications, cite them accurately, and avoid attributing to a report a conclusion it does not state. If you are uncertain about a figure, leave it out. Statistics invented or remembered imprecisely are among the quickest ways to lose an officer's confidence.
Bridge two: the method travels
An approach developed in one setting may be usable in many. A modeling technique, a procurement framework, a data standard, a design guideline, or a public engagement process can be adopted elsewhere. The more evidence you have that others have used or adapted your approach, the stronger this bridge becomes. Evidence of adoption includes adoption by other agencies, inclusion in training or guidance materials, use by consultants across clients, and requests for your documentation.
Bridge three: the person operates at a larger scale
Some professionals work through national networks, advisory bodies, standards committees, or research collaborations that extend their influence. Participation that is documented and meaningful, rather than nominal, shows that your contribution is not confined to a single jurisdiction. As we explore in our article on how industry practitioners build an EB-2 NIW case without a research record, a deployed record can be as persuasive as a published one if it is documented well.
Defining the Endeavor So It Can Be Evaluated
The first step is writing an endeavor statement that is neither a job description nor a slogan. For infrastructure professionals, a workable structure has four parts.
| Element | Weak version | Stronger version |
|---|---|---|
| Problem | Improve water systems | Reduce the risk of treatment failure in aging surface-water plants during seasonal contamination events |
| Method | Use my engineering expertise | Apply and refine a staged filtration control approach, with monitoring and decision rules |
| Reach | Help my employer | Document the approach and make it usable by other utilities through guidance, training, and collaboration |
| Plan | Continue my career | Develop two specific guidance documents, pilot with named partners, and publish results over the next several years |
Notice that each stronger version is specific enough to be tested. An officer can ask whether the problem is real, whether the method plausibly addresses it, whether the reach is credible, and whether the plan is feasible. A weak version offers nothing to evaluate. Our guide to framing a national importance endeavor goes further into these structures, and the companion piece on the national importance argument addresses how to write it.
Three Illustrative Scenarios
These examples are hypothetical, created for teaching. They are not real cases and do not predict outcomes.
Scenario one: the stormwater modeler
Gabriela is a hydrologic engineer at a county flood control district. She built a street-level flood exposure model using publicly available elevation and rainfall data. Her first draft described the model's value to the district.
The revision reframed the work. It cited public agency material describing flood risk as a recurring concern for communities across many regions, without inventing figures. It showed that two neighboring districts and a state agency had requested her methodology, that she had published the method as an open technical report, and that a university course used it as a teaching example. The endeavor became 'making block-level flood exposure modeling accessible to public agencies that lack the resources to build their own.' The local origin was no longer an obstacle; it was where the method had been tested.
Scenario two: the transit planner
Hamid redesigned a mid-sized city's bus network using frequency-based principles, and ridership data from the agency showed improvement after implementation. The first draft treated the ridership numbers as proof of national importance.
The revised version treated them as proof of effectiveness in one setting and was careful not to extrapolate. It then showed that the agency's board report had been shared with peer agencies, that Hamid had been invited to present at a professional conference, and that a state planning body had asked him to contribute to guidance for other cities. The plan described developing a documented redesign process that smaller agencies could use. The petition acknowledged that results might vary by city and presented the process, not a guaranteed outcome, as the contribution.
Scenario three: the utility asset manager
Wen manages capital planning for a water utility and developed a risk-based method for prioritizing pipe replacement. The utility cannot share internal data. Wen proposed a plan to formalize and publish a generalized version of the method, to test it with two partner utilities, and to contribute to a professional society's working group on asset management.
Because the internal results were confidential, the petition relied on independent evidence: a letter from a partner utility describing the planned pilot, a letter from a society committee member who had reviewed the method, and public agency material identifying aging water infrastructure as a recognized challenge. It did not assert dollar savings it could not source. The weakness was acknowledged; the plan and documentation carried the argument.
Evidence That the Work Reaches Beyond Its Origin
The following table summarizes common evidence types and what each can show.
| Evidence | What it shows | Caution |
|---|---|---|
| Requests from other agencies or utilities for your method | Others see value and want to use it | Document the request, not just your recollection |
| Publication of a technical report or guidance document | The method is available and reviewable | Distinguish publication from adoption |
| Inclusion in training or course materials | Others teach it | Provide the actual materials or instructor confirmation |
| Participation in standards or advisory bodies | You influence practice more broadly | Show your actual role, not membership alone |
| Independent letters from adopters or reviewers | Testimony about reach and quality | Choose writers with direct knowledge |
| Public agency documents identifying the problem | The problem is recognized beyond one place | Quote accurately; avoid overstating |
A pattern in this table is that none of these items depends on the size of your employer. A small agency's engineer with a documented, adopted method can have a better case than a large agency's engineer with a vague record.
Turning a Local Record Into Documentation Others Can Use
A recurring weakness in infrastructure petitions is that the best material is trapped inside the employer. Design memos, internal reports, and board presentations exist, but they are not in a form an officer or an outside practitioner can follow. Part of building the case is converting a local record into documentation with a life of its own.
Write the method down in general terms
Take the approach you developed and describe it independently of the specific site: the inputs it needs, the steps it follows, the decision rules it applies, and the conditions under which it works or fails. A document written this way can be read by an outside reviewer, adopted by another agency, and cited in a petition. If the work is subject to confidentiality, seek permission to publish a generalized version, and keep sensitive site details out.
Test it somewhere else
Few things strengthen a replicability argument like a documented second site. A pilot with a neighboring agency, a joint study with a university, or a trial by a consultant working for different clients each shows that the approach is not tied to the conditions where it began. Note the results honestly, including limitations. A pilot that found the method needs adaptation in certain conditions is more credible than one that claims uniform success.
Seek review from people outside your organization
An independent technical review, whether through a professional society committee, a peer-reviewed venue, or a respected practitioner, shows that someone who owes you nothing examined the method. The resulting comments, even critical ones, are evidence that the work is taken seriously. Where reviews are confidential, ask the reviewer whether a short letter describing the review process is possible, within the limits of their obligations.
Keep a record of requests
Emails from other agencies asking for your documents, invitations to present, and requests to share data are modest on their own. Collected carefully, with dates and sender details, they form a record of reach that is hard to fabricate and easy for an officer to understand. Start collecting them now, because they are easy to lose when employees move on or inboxes are cleaned out.
Well Positioned: Beyond a Job Title
The second prong asks whether you are well positioned to advance the endeavor. Infrastructure professionals often have strong credentials: licensure, advanced degrees, years of experience. But a license shows you can practice. It does not show you are positioned to advance a particular endeavor at scale. The evidence should connect your record to the plan.
- A record of results in the relevant area, with documentation that others can verify.
- Documented adoption or interest from outside your employer.
- Relationships and commitments from partner organizations that make the plan feasible.
- Specific next steps, with timeline and deliverables.
Our article on the overlooked prongs explains how to build this part of the case, and the discussion of trajectory addresses why qualification alone is not enough.
The Employer Question
Many infrastructure professionals work for public agencies or utilities. That affects the third prong, which asks whether it would benefit the United States on balance to waive the job offer and labor certification requirement. Public-sector employment can complicate the argument in both directions. On one hand, public agencies may have limited ability to sponsor or to fit a role into a standard certification process. On the other, the officer may reasonably ask why your endeavor depends on a single employer.
The petition should show that the endeavor extends beyond any one position: that your work includes guidance, collaboration, and documentation intended for use beyond your agency, and that requiring a labor certification tied to one employer would not fit the nature of the work. The reasoning is covered in our article on the third Dhanasar prong. It is also worth reading when traditional labor certification may be the better route, because for some employer-bound roles it is.
Warning: Do not claim that your project will solve a national problem. Claim what is supportable: that the endeavor addresses a documented problem, that the method is replicable, and that you have taken concrete steps to make it available. Overreach is easy for an officer to see and costly to credibility.
The Role of Salary and Seniority
Infrastructure careers often include rising seniority, but titles and pay do not establish national importance. Our article on what high compensation really proves in an EB-2 NIW petition makes the point that compensation, by itself, is not an argument. Focus on the endeavor and the evidence of reach.
Timing and Planning
Some professionals have the method but not yet the documentation of adoption. If your reach is still limited, there may be value in a deliberate period of building it: publishing the technical report, offering a workshop, joining a standards group, or piloting with a partner. This is the territory of building an EB-2 NIW case before the endeavor fully exists. A planned build-out is different from simply waiting. It should have concrete milestones, and your petition should be filed when the evidence reflects them.
If you also have an EB-1A-level record, consider whether pursuing both routes makes sense, a question examined in our article on one record and two petitions.
A Checklist for Infrastructure Professionals
- Is the problem identified in credible, specific public sources, with accurate citations?
- Is the endeavor defined by problem, method, reach, and plan, not by job title?
- Is there documented evidence that people outside your employer have requested, used, or taught your approach?
- Do you have independent letters from adopters, reviewers, or partner organizations?
- Is your plan specific, with deliverables, partners, and timeline?
- Have you addressed why a labor certification tied to one employer does not fit the endeavor?
- Are all statistics sourced, and have you left out any you cannot verify?
- Have you cleared confidentiality for any project material you include?
Common Mistakes
- Equating local population served with national importance. Millions of residents benefiting from a utility does not by itself establish national scope.
- Using the employer's mission as the endeavor. Your endeavor should be yours, informed by your work, not the agency's charter.
- Presenting projected savings as facts. Estimates require clear sourcing and honest caveats.
- Ignoring the plan. A record of past work without a forward-looking plan leaves the prospective question unanswered.
- Waiting for perfect adoption evidence. A thoughtful plan with early indicators can be stronger than a long delay.
Frequently Asked Questions
Can a local government engineer qualify for an EB-2 NIW?
Possibly, depending on the facts and whether the person qualifies for EB-2 and meets all three Dhanasar prongs. Local employment alone does not rule it out. The endeavor must show national importance through the problem, the method's reach, or both.
Do I need peer-reviewed publications?
Not necessarily. Technical reports, guidance documents, standards contributions, and documented adoption can all play a role. Peer-reviewed publications can help but are not required in every case.
How do I show the problem is national?
Cite specific publications from credible government, professional, or research sources that describe the problem as widespread or significant. Quote accurately and avoid stretching their conclusions.
What if my employer does not allow me to share project data?
Use public records, published methods, independent letters, and employer-approved summaries. Do not include restricted material without permission, and do not fill the gap with unsupported numbers.
Is public-sector employment a problem for the third prong?
It can require careful reasoning, since the officer may ask why the endeavor depends on one employer. Show how your work extends beyond a single position and why a standard labor certification process does not fit.
How specific should the plan be?
Specific enough to be evaluated: type of project, intended deliverables, named or described partners, and approximate timeline. Avoid overpromising, and note that plans may evolve.
Does a professional engineering license help?
It supports your qualifications, but by itself it does not establish that you are well positioned to advance a particular endeavor. Pair it with evidence of results and adoption.
Can I use regional awards as evidence?
They can add context if you can show the standing of the award and what it recognized. Regional recognition is less probative of national importance than evidence of adoption beyond the region.
Should I get letters from my employer's leadership?
They can confirm your role and results. Pair them with independent letters from people at other organizations who can speak to reach and adoption.
Is the NIW always the best route for infrastructure professionals?
Not always. The right path depends on your record, employer situation, and goals. Compare options with qualified guidance and current USCIS information.
Conclusion
Infrastructure work is local in execution and national in consequence, but a petition has to prove the second claim rather than assume it. The strongest cases for professionals in water, transit, and urban systems do not exaggerate the reach of any single project. They show a documented problem, a method that others have asked for or adopted, a plan to extend it, and independent voices who can attest to its value.
If your projects are tied to particular places and you are unsure how to present their wider significance, a portfolio review can help you identify the evidence of reach you already have and the steps that would strengthen it. Every immigration case is unique, and professional guidance can help you build a stronger, more accurate portfolio. You can contact EB1 Mentor to discuss your profile, explore our EB-2 NIW services, start with the profile evaluation, or read more on the EB1 Mentor blog. EB1 Mentor is not a law firm and does not provide legal advice; for legal questions, consult a qualified immigration attorney.
References and Further Reading
- USCIS Policy Manual, Volume 6, Part F, Chapter 5: Advanced Degree or Exceptional Ability (National Interest Waiver)
- USCIS: Employment-Based Immigration, Second Preference EB-2
- 8 CFR 204.5: Petitions for employment-based immigrants
- EPA: Water Infrastructure and Resiliency Finance Center
- U.S. Department of Transportation: Federal Transit Administration
Requirements, policies, and procedures may change. Verify current requirements with official USCIS guidance or qualified legal counsel.
Every immigration case is unique. If your projects are local but your expertise matters beyond them, contact EB1 Mentor to discuss how professional guidance can help you build a stronger, more accurate portfolio. EB1 Mentor is not a law firm and does not provide legal representation.
