The Request for Evidence asked what the petition never answered

An applied professional petitioning on her own record, after years of working in the United States in an employer-sponsored status. Her field, her employer and her country are not on this page, and not one of them is what this case turned on. No national award, no startup, no long publication list.

Her strongest work was a multi-year project whose technical design she had led, built for a group of public agencies that could not have built it themselves. It was not an invention. It was a practical system assembled out of established methods and the agencies' own operating data, and it let them find failures in what they run, decide which repairs came first, and plan for what they could see coming. The agencies used it, relied on it, and cited it when they applied for public funding.

She filed it herself, and her reasons were reasonable ones. An NIW can be self-petitioned, she reads technical documents and government instructions for a living, and she used a template service that gave her forms and no legal advice. She also worried that a lawyer would make her work sound exaggerated, or would not understand what she actually does. That second worry deserves a straight answer rather than a sales one, so here is mine: it is a fair thing to worry about.

What she filed was not thin. Degrees and transcripts, a credential evaluation for the foreign degree, a resume, employment verification letters, technical reports, conference presentations, a trade-publication article, a cost-savings spreadsheet, a supervisor letter, colleague letters, screenshots of the agencies' own public pages, and a twelve-page personal statement. Volume was never the problem.

The proposed endeavor was. In the petition it came through as an intention to keep working in her field and to help communities with a problem everyone agrees is serious. Every word of it was true. None of it told an officer what she would actually do, for whom, by what method, or why it amounted to more than a job. The petition had headings for all three prongs, and all three said the same thing in different clothes: the field is important, she is credentialed in the field, the country benefits from her working in it.

Nine months after she filed, the Request for Evidence arrived. It challenged all three prongs and her threshold EB-2 eligibility, and it asked what she specifically planned to do going forward, where, what her role on the earlier project had actually been, and why she believed labor certification was impractical. Her instinct was to send more background articles and a few more colleague letters. That instinct is the trap. The officer was not asking whether the problem matters. The officer was asking whether her particular endeavor is nationally important, and whether she specifically is positioned to carry it out, and the filing had never answered those as two separate questions.

I asked one question. In practical terms, what do you expect to be doing for the next three to five years? Her answer was far better than her petition. She wants to help small and midsize public agencies use their own data and predictive modeling to cut losses, sequence repairs, and plan for what is coming, and eventually to build a standardized assessment and training program for the agencies that cannot afford to hire this work out.

She had already started. Her employer had approved her participation in a new public-agency initiative. One agency had agreed to serve as a pilot partner. She had drafted a technical roadmap. She had opened a data-sharing conversation with a university research center. She had been invited onto a working group in her area of practice.

None of it appeared in the petition. She did not leave the pilot commitment out because she was hiding it. She left it out because she did not think of it as immigration evidence. To her it was just work.

Her role on the earlier project was the same story. She had described it as teamwork, because that was professionally accurate and because people who do technical work in teams do not go around claiming sole credit. In the consultation it came out that she had designed the data architecture, written the forecasting methodology, trained the staff who ran it, and coordinated technical feedback across the participating agencies. A materially different picture, and true the entire time.

The largest single change in the whole response was one sentence. As filed, the proposed endeavor read: an intention to continue working in her field in the United States, helping communities address a problem everyone agrees is serious.

Rewritten, it read: to develop, implement, and disseminate data-driven detection, forecasting, and resilience tools for small and midsize U.S. public agencies, beginning with one agency already committed to a pilot and expanding through public-agency partnerships, technical training, and implementation methods other agencies can replicate.

The second version names the subject matter, the problem, the intended users, the starting point, the method, and the path to broader use. It also does not claim she will single-handedly solve a national problem. It is ambitious and it is checkable, and checkable is what an officer can work with.

Threshold EB-2 first, separately, before touching the waiver at all. The intended occupation, the degrees, the credential evaluation for the foreign degree, and evidence about what the occupation itself requires, plus why this is technical work rather than advocacy in technical clothing. Since the January 2025 guidance, a response that leaves this step to be inferred is leaving the first question on the officer's list unanswered.

Prong one, and the concession goes first. That the underlying problem is important in general does not make her endeavor nationally important, and saying so up front costs nothing and buys credibility. Then the real argument. Small and midsize agencies do not have the resources to build systems like this, and declarations from agency officials said so directly. The earlier project showed that the approach works and that independent public bodies relied on it. A technical plan showed how the tools adapt elsewhere. A specific starting point, with implications that run past it.

Prong two, organized around readiness rather than resume. Letters from the agencies describing what she actually did, not what a pleasure she is to work with. The pilot partner's letter, for present-tense commitment. The roadmap, to show work rather than aspiration. And a plain statement of what she does not have. Pretending otherwise costs credibility, and an officer notices when a record only argues in one direction.

Prong three is not that she is highly qualified, and it is not that the country needs people like her. The argument is structural. Methods developed for use across many agencies, partnerships with public bodies and researchers, tools adapted to systems that are not alike. A single sponsored position does not capture any of that, and the benefit being weighed is not her employment. It is the effect on the systems those agencies are responsible for. One argument I did not make: that labor certification is slow, or a nuisance. That reads badly and it is not the test. Prong three is the one where it helps most to know exactly what you are asking the government to skip, and I have spent years inside labor certification on the employer side.

The response went in as one argument rather than as more paper. USCIS approved the I-140 in the EB-2 national interest waiver classification.

The petition was approved. What that proves is narrow: that on this record, with these facts, a rebuilt response answered the questions the officer had asked. It says nothing about what a different record will do. An NIW carries discretion, so nobody can put a number on anyone's odds, and I would not try. What a properly built record does is give an officer a coherent way to evaluate the case, and that is the whole job.

That is where this record ends. If you are holding a Request for Evidence right now, the one thing worth taking from this is to read it as a list of questions rather than as a decision already made, and not to answer volume with volume. Pages added at the end do not reach what was asked unless somebody first works out what was asked.