Skip to main content
National Public-Interest Evidence Archive
Menu

Archive Article: Muckrock Binder Index Records

Archive article preserving source-linked FOIA and public records. This archive does not establish motive, guilt, intent, or selective enforcement.

By David Medeiros

Video explainer: Binder index method: Find the document behind the claim

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

Press Play to load the video. Once loaded, you can move to any point. The original MP4 link remains available below.

A filing is not a finding. Read the original source before drawing conclusions.

Download video · English captions (VTT) · Transcript text

Read the complete transcript

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.

A large binder is useless without an index. If you are compiling hundreds or thousands of pages of FOIA correspondence, you need a stable way to reference any page, any artifact, and any agency decision in seconds. This post describes a binder index method designed for oversight review.

What the binder is.
The binder is a single, ordered corpus that contains receipts, acknowledgments, determinations, appeals, and related communications. It is designed to be immutable once published. Updates are additive: a new volume, a new index, and a new manifest.

What the index is.
The index is not a narrative. It is a table. Each row is a record. The minimum fields are:

  • Artifact ID (unique)
  • Agency and component
  • Case or control number
  • Date filed
  • Date received or acknowledged
  • Determination type (produced, partial, denied, no records, routed)
  • Related statute or policy hook
  • Storage location (folder path or URL)
  • Hash reference (SHA-256)

How to structure Artifact IDs.
Use stable IDs that encode category and date. Example: FOIA-2024-12-23-DOJ-OIP-0001. Do not use sequential numbers alone. The ID should survive re-sorting and re-export.

How to handle “referenced-only” items.
Sometimes you have an email that references an attachment you do not have, or a portal message that points to a document you cannot retrieve. Do not delete the record. Mark it as REFERENCED-ONLY and describe the gap. That gap is itself a forensic finding. It also prevents later claims that you fabricated the absence.

How to map to your public site.
Your public site can be curated. Your index must not be. If the public site shows 73 events, your index can still show 500 artifacts. The index is where reviewers go to verify. The site is where readers go to orient.

How to make the index reviewable.
Provide three views:

  1. Chronological view
  2. Agency view
  3. Issue view (FOIA, ADA/504, retaliation, billing, access, spoliation)

Each view is the same records, just grouped differently. This is the difference between a pile of PDFs and an investigation-ready archive.

A practical publication pattern.

  • Publish the binder PDF (or volume PDFs).
  • Publish the index CSV.
  • Publish a manifest that lists every file and its hash.
  • Publish a short “what changed” note for each new volume.

Quality controls that matter.

  • Uniqueness. Artifact IDs must be unique across the archive.
  • Stability. Do not reuse IDs after corrections. Create a new ID and link back.
  • Completeness. Every determination should have a corresponding request and receipt.
  • Traceability. Every index row should point to an artifact a reviewer can open.
  • Integrity. Every artifact should have a hash in a manifest that is also preserved.

Finally, publish a manifest.
A manifest is a list of files and their hashes. It is the integrity proof that the binder has not been altered. Publish the manifest alongside the binder. If you update the binder, publish a new manifest. Never rewrite old manifests.

If you adopt this method, oversight reviewers can verify your work without trusting your interpretation. They can pull a case number, locate the artifact, confirm the hash, and assess the agency action directly.

Dataset provenance

Administrative Burden Livewire Index

This canonical article is represented by 1 preserved source row in the complete 272-record Administrative Burden dataset. The links below open every non-empty field under its original CSV heading.

Browse the complete dataset →

Cite this archive article

This citation identifies this article—not an original filing, an agency finding or a court decision. For a factual claim, also identify and check the particular source linked in the article.

Select the text and copy it using your device’s copy command. Replace the access-date placeholder with the date you actually read the page. The publication date is the article’s recorded date, not a new verification or revision date.