Building an Evidence Inventory: From Achievements to Verifiable Claims

• ○Write the proposed claim before naming the supporting document.
• ○Record who created each item, when it was created, and why it existed.
• ○Separate possession of a file from proof of the fact asserted.
• ○Mark missing context, translation, authentication, and date problems.
• ○Assign one owner and one next action to every unresolved gap.

Start with propositions, not folders#

A conventional document drive answers where a file is stored. An evidence inventory answers a harder set of questions: what fact is being asserted, why that fact matters, what record supports it, what the record does not establish, and what a second reviewer would need to verify the conclusion. That difference prevents a familiar failure in achievement-based filings: hundreds of pages accumulate, yet no one can explain which proposition each page proves. Begin with a neutral statement such as “the beneficiary completed peer review for Journal X on three documented occasions,” not the conclusion “the beneficiary is an internationally recognized judge.” The first statement can be tested; the second requires additional analysis.

Create the inventory before drafting advocacy. Interview notes, a résumé, and a personal chronology are discovery tools, not self-proving evidence. Extract one factual unit at a time: event, actor, date, role, selection rule, audience, measurable outcome, or independent response. Give every unit a stable claim code. When one document supports several facts, link it to each relevant claim rather than copying it into unrelated folders. When several documents support one fact, preserve the relationship among them so the corroboration is visible.

Build the chronology before the argument#

A chronology reveals sequence, duration, and causation problems that subject folders conceal. Record when the underlying work began, when recognition occurred, when a metric was measured, when a source was published, and when a copy was captured. For awards, the selection date may differ from the ceremony and announcement dates. For judging, an invitation may precede completed review by months. For contributions, adoption may occur long after publication. If dates conflict, preserve both records and investigate; do not silently choose the more favorable one.

1. Discovery

   Collect résumé entries, calendars, repositories, contracts, correspondence, public pages, and prior filing records as leads.

2. Claim extraction

   Convert each lead into one or more testable factual propositions with stable IDs.

3. Source capture

   Acquire complete records, record provenance, preserve URLs and dates, and identify translations or missing pages.

4. Gap review

   Test whether the source proves the actor, event, role, scope, date, and significance actually asserted.

5. Controlled use

   Map verified claims to the relevant framework and cite the same source consistently throughout the record.

Distinguish existence, participation, and significance#

Many achievements require three separate proof layers. First, show that the institution, event, publication, product, award, or activity exists. Second, show the person’s actual role or participation. Third, establish the context that makes that role probative for the relevant question. An event website may prove an event existed but not that the person attended. A program may list the person but not explain selection. An employer letter may describe a role but not independently establish the organization’s standing. Recording the layers separately exposes exactly where corroboration is needed.

The inventory should also distinguish identity from attribution. Names change, initials collide, organizations merge, titles differ across records, and team outputs may not specify individual contribution. Record the identity bridge rather than assuming it. For a publication, retain the bibliographic record and author list. For a patent, connect inventorship to the official record while separately documenting commercial or field impact. For a company result, identify the team, time period, baseline, methodology, and source of the number before attributing the outcome to one person.

Use gap codes that lead to action#

A useful gap taxonomy is operational. “Missing evidence” is too vague. Use codes such as missing primary record, incomplete date, unidentified author, inaccessible URL, untranslated text, unexplained comparison group, unsupported attribution, duplicate evidence, source created for filing, conflicting measurement, or unclear criterion fit. Each code should trigger a concrete action: obtain the official rule, request the complete record, capture an archived version, commission a compliant translation, calculate a transparent benchmark, or revise the claim to match what can actually be shown.

Prioritize gaps by consequence and replaceability. A missing award certificate may be replaceable through an official registry; an undocumented selection process may require direct rules from the granting body. A broken media URL may be recoverable from an archive, while a screenshot without publication identity may remain weak. Do not chase every possible document equally. Focus first on facts essential to eligibility, then on corroboration that materially improves reliability, and finally on context that helps the record be understood.

Connect the inventory to the right framework only after verification#

Once facts are verified, mapping becomes more disciplined. An invitation to judge may inform an evidentiary criterion, while completion records prove actual participation and repeat invitations may add context. A high-revenue project may support a leading-role narrative only if the person’s responsibility and the organization’s distinguished standing are separately established. NIW evidence may concern the proposed endeavor, national importance, or positioning rather than extraordinary-ability criteria. Review the distinct frameworks in the EB-1A overview, O-1A overview, and Dhanasar framework guide before assigning a document to a legal question.

Keep the inventory auditable as the record changes#

Use version control principles even in an ordinary spreadsheet. Lock stable claim IDs, maintain a change log, identify the reviewer, and record why a status changed. Do not replace an original source with an edited PDF. Store working extracts separately, preserve the complete record, and document redactions. When new evidence arrives, update its provenance and mappings rather than attaching it to the end of a folder without review. A frozen export at major drafting milestones helps detect later inconsistency.

The inventory should remain narrower than the final narrative. It is a verification layer, not a place to write persuasive conclusions. Its value is that different writers can cite the same facts, dates, names, and source versions across forms, letters, exhibits, and summaries. When a proposition changes, the inventory makes downstream references discoverable. This reduces contradiction, prevents obsolete links from surviving in the filing, and makes final quality review possible without rereading every page from the beginning.

A periodic inventory review should test negative space as carefully as collected material. Ask which expected ordinary-course records do not exist, which systems retain only short histories, which institutions control replacement documents, and which claims depend on a single person’s memory. Record unsuccessful collection attempts and retention limits. Absence should not be disguised with a conclusory letter; it should lead to a narrower assertion, an alternative source with an explained basis, or a candid limitation. This makes the collection plan realistic and prevents late drafting from converting an unavailable record into an unsupported fact. Revisit high-risk gaps before each drafting milestone and document the decision to collect, qualify, defer, or remove the associated claim. Keep that decision visible to later reviewers.