Many strong projects never become a public paper, patent, or press release. A security system, a clinical workflow, an internal platform, or a customer deployment may be confidential for good reasons. That does not make the work disappear. It does mean a résumé line is not enough.
For EB1A preparation, do not begin by trying to disclose more. Begin by separating three questions: what you personally did, whether the work was actually used, and why the result mattered. An immigration lawyer can advise whether the resulting record supports a particular claim. Your job is to assemble truthful, permitted source material so that assessment is possible.
Why “my work is confidential” is not the end of the analysis
USCIS evaluates evidence in the context of the claimed criterion and then looks at the whole record. It does not publish a rule saying that only public work can matter. But a private assertion can be difficult for a reader to test. The answer is not a dramatic letter filled with undisclosed metrics. It is a record that gives a reviewer enough reliable context to understand the contribution without exposing protected details. See the agency’s extraordinary-ability guidance in the USCIS Policy Manual and the regulation at 8 CFR 204.5(h).
Build one evidence row for each claim
| Question | Useful permitted evidence | What it cannot establish alone |
|---|---|---|
| What did you do? | Role description, contemporaneous project record, permitted manager letter, authorship or ownership record. | That you alone caused every team outcome. |
| Was it used? | Deployment record, release note, customer-facing description, dated internal adoption confirmation, or a permitted implementation letter. | Field-wide influence from one internal rollout. |
| Why did it matter? | Defined before-and-after measure, independent customer or partner context, external recognition, or a well-sourced business impact explanation. | Significance from a large number without its method, baseline, or source. |
| What remains confidential? | A precise boundary: what cannot be shared, why, and what permitted substitute supports the point. | A license to leave every material fact unverified. |
Each row should have a source, date, author, and limitation. If a leader says a system “saved millions,” ask what period, which business unit, which baseline, and whether they can truthfully put that explanation in writing. Narrow, verifiable facts beat expansive conclusions.
Use a claim ladder, not a single all-purpose letter
A supervisor can often explain responsibility. A release owner can explain implementation. A customer, partner, or independent user may be better placed to explain why the outcome mattered outside the immediate team. Those witnesses have different knowledge. Do not label someone independent simply because they changed jobs, and do not ask a signer to repeat facts they cannot verify.
- Start with attribution. Identify the specific decision, design, method, or leadership work that was yours.
- Then show use. Record where the work was deployed, adopted, or relied upon, with dates and a permissible source.
- Then explain significance. Tie the result to a meaningful operational, technical, or market consequence using a method a reader can understand.
- State the boundary. Explain the protected material without pretending the boundary does not exist.
A safe first-hour worksheet
Make a private inventory before you ask anyone for a letter. For each project, write: your exact role; the project’s objective; a non-sensitive description; the strongest permitted proof; the best person to verify it; the remaining gap; and the legal or company-approval question. Keep the original records in the authorized location. Do not send personal immigration documents or employer-confidential files to ChatEB1.
Then test the claim with a skeptical question: could a reader distinguish your work from the team’s work, and could they understand the result without being asked to trust a vague superlative? If not, the next task is evidence collection or claim narrowing, not stronger adjectives.
Common mistakes
- Using a company logo as proof of personal distinction. A famous employer can provide context, but it does not identify your contribution.
- Equating confidentiality with independent impact. A confidential project can be important, but importance still needs support.
- Asking a recommender to certify legal conclusions. Ask for facts they know; counsel can address the legal framework.
- Sharing material you are not authorized to share. A strong evidence plan should reduce this risk, not create it.
- Counting documents instead of propositions. Ten copies of the same internal summary do not answer ten different questions.
Turn the record into a cleaner attorney handoff
A useful handoff is short enough to read and specific enough to challenge. List the claim, the evidence, the source limitation, and the question you need answered. For example: “I led X; a dated release record and manager letter support that role; an internal deployment metric is available with approval; does this support a contribution or critical-role theory, and what independent proof would change the analysis?”
That structure helps you get better legal advice and reduces the temptation to fill gaps with marketing language. It also makes it easier to decide whether the right next step is to seek permission for one document, find a public substitute, narrow the claim, or stop pursuing a weak theory.
Where ChatEB1 fits
If your facts are real but scattered, the free approach above is enough to begin. If you want a repeatable private worksheet for ranking claims, separating weak proof from missing proof, and preparing questions for counsel, review the Profile Builder Pro contents and fit. It is a $99 educational evidence-organization product, not legal representation, legal advice, or a promise about eligibility or approval.
For current status, deadlines, travel, employer permissions, or filing strategy, speak with qualified immigration counsel. Use this evidence map to make that conversation more concrete.