This guide explains how to organize a large collection of records requests, receipts, responses, and appeals so another reader can locate a specific document.

The article proposes one row per artifact, with an identifier, agency, control number, filing and receipt dates, response type, location, and hash reference.

The guide recommends identifiers that survive sorting and re-export. A row's position in a spreadsheet should not be its only identity.

If an email mentions an unavailable attachment, the guide says to retain the reference and describe the gap. A reference must not be presented as the missing document itself.

Chronological, agency, and issue views can organize the same underlying records. Changing the view should not change what an artifact contains.

The guide favors additive updates with a new volume, index, and change note. This keeps older citations connected to the version originally reviewed.

A preserved hash helps detect whether a file matches a recorded copy. It does not independently establish the document's truth, authorship, or legal effect.

Open the guide. Use the identifier and location to read the actual request, receipt, or decision. The index helps navigation; the underlying record supports the claim.

The method is useful when another person can locate the document without accepting the compiler's interpretation. A filing is not a finding.