Direct answer
A useful EB1A evidence checklist usually has seven layers: identity and timeline basics, criterion-by-criterion exhibit groups, independent third-party proof, quantified impact, recommendation letters that match the record, an exhibit index, and one final-merits explanation tying the strongest evidence together. If one of those layers is missing, the file usually starts feeling thinner than the resume suggests.
Who this applies to
People building or cleaning an EB1A self-petition, especially when the profile sounds strong but the packet still feels messy or repetitive.
What matters most
Criterion fit, independent proof, quantified impact, clean exhibit labels, and fewer low-signal attachments.
Common mistake
Making a document collection before deciding which claims each document is supposed to support.
Next step
Turn the checklist into an exhibit map so every file has one clear job in the petition.
The seven layers of a strong checklist
- Identity and timeline basics. Passport bio page, CV, role history, immigration-status context if relevant, and a clean chronology.
- Criterion-specific evidence groups. Build separate exhibit clusters for each EB1A criterion you are actually using.
- Independent corroboration. Third-party sources usually matter more than self-description.
- Quantified impact. Numbers, benchmarks, reach, adoption, outcomes, and selectivity signals usually make the story more credible.
- Recommendation letters that match the record. Letters should reinforce documented facts, not introduce heroic claims no exhibit can support.
- Exhibit index and labels. The officer should be able to find the right document fast.
- Final-merits synthesis. A packet still needs one layer that explains why the total record is stronger than a stack of unrelated wins.
Checklist by evidence job
| Evidence job | What usually belongs here | What weakens it |
|---|---|---|
| Criterion proof | Awards, judging invites, media, memberships, salary data, authorship, contribution documentation, critical-role proof. | Loose screenshots, internal praise, or documents that do not clearly map to a criterion. |
| Independent validation | Third-party articles, neutral benchmarks, public records, invitation emails, external awards pages. | Self-written summaries with no outside support. |
| Impact proof | Revenue influence, adoption, growth, cost savings, reach, citations, user numbers, or business-critical responsibility. | Claims of importance with no scale, comparison point, or consequence. |
| Officer readability | Exhibit list, labels, short explanations, clean ordering. | A large folder of files with no map. |
What to collect first
- The strongest independent proof for the top three or four criteria you can really defend.
- Any document that proves selectivity, scale, or external recognition.
- Quantified outcome proof attached to your named role.
- Only the recommendation letters that reinforce documents already in the record.
What usually does not help as much as people think
- Generic praise letters without specific supporting exhibits.
- Employer-branded slides that describe the project but not your unusual role or impact.
- Large screenshot packs where the officer has to infer meaning.
- Weak criteria included just to reach a bigger count.
Bottom line
An EB1A evidence checklist should reduce ambiguity, not increase it. If the checklist makes the packet bigger without making the logic cleaner, it is still the wrong checklist. Strong files are organized around proof value and officer readability, not around attachment volume.
How many criteria should the checklist cover?
Only the criteria you can defend cleanly. Three plausible buckets are not automatically enough if the evidence inside them is thin or repetitive.
Should recommendation letters come first or last?
Usually after the factual exhibits are mapped. Good letters amplify documented proof; they should not be the foundation of the claim.
What should I read next?
Read EB1A criteria explained if you are still choosing which criteria are actually real, or EB1A final merits explained if the packet already looks full but still feels risky.