How engineering work maps onto the three Dhanasar prongs
USCIS evaluates every NIW petition against three prongs set out in Matter of Dhanasar: (1) the proposed endeavor has substantial merit and national importance, (2) the petitioner is well positioned to advance it, and (3) on balance it would benefit the United States to waive the job offer and labor certification requirement. The proposed endeavor statement is the anchor document for all three — write it to name a field of activity, not a single employer's deliverable.
Phrasing the endeavor
Weak: "Improving the seismic retrofit program at [Employer]." Better: "Advancing design standards for seismic retrofit of pre-1980s reinforced concrete buildings." The second version survives a job change and maps directly onto a field where merit and importance can be shown independently of any one employer.
Worked examples by prong
- Substantial merit and national importance: An electrical engineer developing a grid-stability control algorithm can point to DOE grid-modernization priorities and the algorithm's applicability across multiple utilities, not just one deployment.
- Well positioned to advance it: A mechanical engineer with a manufacturing process that reduces fuel consumption documents prior results (test data, pilot-line output), relevant patents, and a track record of implementing similar process changes.
- Balance favors waiver: A civil engineer contributing to an ASCE retrofit standard shows that requiring a single sponsoring employer and labor certification would not serve the standard's nationwide adoption, since the work's value lies in dissemination across the field, not employment at one firm.
Each prong draws on the same underlying evidence base — technical documentation, recognition, and independent impact — organized differently depending on which prong it supports.
Evidence that documents technical contribution
Gather original source documents, not summaries. An officer reviewing the file wants to trace each claim in the personal statement back to a primary record.
Core document types
- Patents and patent applications — download the full PDF from USPTO Patent Public Search (or the relevant foreign office), including the first page showing inventorship, the claims, and any citing-patent list.
- Peer-reviewed papers — collect the published PDF, not just the abstract, plus the journal or conference's indexing record (Scopus, Web of Science, or the publisher's own page) showing acceptance date and peer-review status.
- Standards and codes contributed to — working-group ballots, draft redlines, meeting minutes, or committee rosters from bodies such as ASME, IEEE, ASCE, ACI, or NFPA that name the petitioner as a contributor or voting member.
- Internal engineering reports and test data — design calculations, test logs, failure analyses, or validation reports, with employer permission to disclose if marked proprietary.
- Software and firmware repositories — exported commit logs (GitHub, GitLab, or internal version control) showing authorship, commit frequency, and code review approvals tied to the petitioner's account.
- PE licensure records — the license certificate and, where available, the state board's public verification page.
Requesting a confirming letter
When a document alone does not show scope of contribution, request a short letter from the standards committee chair or employer. Ask it to state: the petitioner's exact role, the dates of involvement, which sections or claims are attributable to them, and how that contribution differs from routine participation. Request it on letterhead, signed, with the writer's title and contact information.
Recommendation letters: who to ask and what to ask them to address
Choose letter writers who can speak to specific technical facts, not general praise. For engineering petitions, five categories of writer cover most of the ground:
- PE-licensed supervisors or managers who directed or reviewed the petitioner's work
- Academic collaborators or co-authors who can describe the technical substance of joint research or publications
- Standards-body chairs or working-group leads who can confirm the scope and nature of a contribution to a code or standard
- Clients or downstream engineering teams who adopted a design, process, or software component
- Independent experts in the same subfield who have reviewed the work but have no employment or co-authorship relationship with the petitioner
What each letter needs to state
Every letter should give enough factual detail that an officer unfamiliar with the subfield can follow it without outside help. Ask each writer to include:
- Their own professional background — title, employer, licensure (PE number and state, if applicable), years in the field, and how they are positioned to judge the work described.
- How they know the petitioner — direct supervision, co-authorship, review of a submitted standard, deployment of a delivered design, or similar.
- The specific technical contribution they observed — a named project, patent, paper, or standard section, described in enough detail to identify it independently.
- Measurable outcomes where available — percentage reduction in failure rate, kWh or fuel savings, cost reduction, extended service life, or safety-incident reduction, with the basis for the figure (test report, field data, audit).
Avoid letters that restate the petitioner's resume without adding the writer's own firsthand observations.
Logistics
Draft a fact sheet for each writer listing the projects and dates relevant to their knowledge, so letters remain accurate and consistent without being identical in wording.
Building a citation and impact index for your work
A single spreadsheet that tracks every publication, patent, and code contribution, along with who cited or adopted it, gives an officer a compact way to see the scope of the work without reading every exhibit.
Set up the spreadsheet
Create one row per publication or patent, with these columns:
| Title | Venue | Date | Citation Count | Source | Date Pulled | Adoption Evidence | Description |
|---|
- Citation Count / Source: record the number alongside where it came from — Google Scholar, Web of Science, Scopus, or USPTO Patent Public Search for patent citations. Counts differ across databases; do not merge them into one figure.
- Date Pulled: the day you captured the count. Citation counts change, so every pull needs a timestamp.
- Adoption Evidence: name the specific company, project, product, or codebase that used the work — not a general claim of influence.
- Description: one or two sentences on what the item covers, written so a non-specialist can follow it.
Pulling and documenting counts
For each source, take a dated screenshot or export (CSV where available) the day you record the number, and save it alongside the spreadsheet as supporting backup. For patents, USPTO Patent Public Search shows forward citations — record the citing patent numbers, not just a count. Re-pull counts shortly before filing so the figures are current at submission, not months stale.
File naming
Use a consistent convention: LASTNAME_citation-index_YYYY-MM.xlsx, updating the date suffix each time you refresh the data. Keep prior versions rather than overwriting them, so you can show the trend if asked.
Letters, metrics and media showing field-level recognition
Beyond your own publications and patents, gather material produced by others that shows the subfield you work in — not just your individual project — carries recognized weight.
Government and agency sources
Search for roadmaps, strategic plans, and technical reports from agencies relevant to your discipline: DOE technology roadmaps and multi-year program plans, DOT and FHWA research priorities and technical advisories, NIST standards and measurement research, and comparable state-level infrastructure plans. Look for passages that name your subfield, method, or class of technology, even without naming you. Save the PDF, note the publishing agency, publication date, and page number of the relevant passage.
Industry adoption and media
Collect press releases, trade publications, or conference proceedings announcing adoption of a method, code provision, or technology in your subfield. Screenshot or archive the page (use a tool such as archive.org's Wayback Machine) with a visible date.
Awards and invited talks
List competition results, best-paper awards, and invited or keynote talks at professional conferences (ASME, IEEE, ASCE, ACI, NFPA, or equivalent). Keep the program listing or award announcement as the source document.
Building the reference table
Compile everything into one table:
| Source | Date | Relevance note |
|---|---|---|
| DOE Grid Modernization Multi-Year Program Plan | 2023 | Identifies distributed control algorithms as a research priority |
| FHWA Bridge Preservation Guide | 2022 | References retrofit standard class petitioner contributed to |
Keep the table in sync with the citation index described above, using the same file-naming convention, and cite the original document in every letter that references it.
Assembling Form I-140 and the supporting exhibit package
Organize the filing in the order an officer will read it, not the order you produced it.
Package order
- Cover letter summarizing the classification requested and listing enclosures.
- One-page exhibit index (a table: Exhibit letter, description, page count).
- Form I-140 — confirm you have the current edition and instructions on uscis.gov before filing.
- Personal statement / proposed endeavor description.
- Evidence exhibits, lettered A, B, C… in the order referenced in the statement.
- Recommendation letters, each as its own exhibit or grouped under one exhibit with sub-tabs.
- The citation and impact index, as a standalone exhibit.
Exhibit numbering
Assign one letter per distinct evidence category — patents, publications, standards contributions, employer letters, recommendation letters, citation index, media/recognition items — and keep that letter consistent across the cover letter, the statement's footnotes, and the exhibit index. Within an exhibit holding multiple documents, use numbered sub-items (Exhibit C-1, C-2) rather than renumbering the whole set.
File naming
Use a flat, consistent scheme for every PDF, matching the exhibit letter to the filename so nothing gets misfiled during scanning or upload:
Illustrative template, not a real source: LASTNAME_ExhibitC-2_PatentCitationReport_2026-03.pdf
Apply the same pattern to the statement (LASTNAME_PersonalStatement_2026-03.pdf) and the citation index (LASTNAME_citation-index_2026-03.xlsx converted to PDF for the exhibit set). Keep a local copy of the full package, named consistently, separate from what you submit, so you can reference exhibit letters if USCIS issues a request for evidence.
Confirm current filing mechanics — mailing address, online filing availability, and page limits if any — on uscis.gov before assembling the final set.
Costs, premium processing and timeline checks before filing
Budget the cost categories separately
Before filing, confirm each of the following on the USCIS Fee Calculator or the current Fee Schedule at uscis.gov, since figures change:
- Form I-140 filing fee — paid when the petition is filed.
- Asylum Program Fee — a separate, required payment that applies to Form I-140 filings. It is paid as its own transaction, using the same payment type as the I-140 fee (check or money order, or Form G-1450 if paying by card). Do not combine the two into a single check or a single G-1450 authorization.
- Premium processing fee (optional) — filed on Form I-907 if you choose expedited adjudication. Confirm the current fee amount and the current processing timeframe, stated in business days, on uscis.gov before relying on it for planning.
Check the Visa Bulletin before you file or plan next steps
Find the current Visa Bulletin on the Department of State's website and locate your country of chargeability under EB-2, in both the Final Action Dates chart and the Dates for Filing chart — the two charts can carry different cutoff dates and different filing implications.
- Identify the cutoff date listed for your category and country.
- Compare it to your priority date (the date your I-140 is filed, or an earlier priority date if one carries over).
- Your priority date is current only if it is earlier than the cutoff date, or if the chart shows "C". A priority date equal to the cutoff date is not current.
- Recheck monthly — cutoff dates can advance, hold, or retrogress to an earlier date or to "U" from one month to the next.
You may also like
EB-2 NIW for South Korean Engineers and Researchers
Build a document set that translates South Korean credentials, employers, and publication records into evidence a USCIS officer can verify and evaluate.
Read →EB-2 NIW for Vietnamese Engineers and Tech Professionals
Assemble a complete, well-documented EB-2 NIW petition using Vietnamese academic, employment, and credentialing records translated and organized to USCIS standards.
Read →How to Build an Exhibit Index for Your EB-2 NIW Petition
Learn how to build a numbered exhibit index for your EB-2 NIW petition, from labeling conventions to cross-referencing the petition letter, so your filing is easy for a USCIS officer to navigate.
Read →