DOJ OIP Redirect + MuckRock Digests: Proof of Exhaustion

FOIA “exhaustion” is not a vibe. It is a record you build. If you want oversight bodies to move, you need a clean chain of requests, acknowledgments, routing decisions, determinations, and appeals. This post documents a practical method for proving exhaustion when agencies redirect, fragment, or “lose” your request. It is written for a records-first workflow, not for storytelling. 1) Start with a defensible request packet. Write one sentence that defines the records universe. Then define your time window. Then define custodians or offices. Finally define delivery format. Avoid rhetorical framing. Avoid motive. Avoid adjectives. Your goal is to force a binary outcome: either they search and produce, or they commit to “no records” in writing. 2) Log the intake receipt. Capture the portal receipt or acknowledgment email the same day. Save the raw message. Save a PDF render. Hash both. Record the control number and any PIN. This prevents later disputes about the start date and statutory clock. 3) Treat “component routing” as evidence, not as service. DOJ OIP and similar offices sometimes route requests to components. That routing is itself a record. It can show who controlled the request, when, and whether the request was narrowed without your consent. Preserve every routing notice. If you receive multiple component case numbers, tie them back to the parent request in a ledger. 4) If you get “no records,” treat it as a finding that requires validation. A “no records” response is not neutral. It is a claim about search scope and custodians. Ask for the search parameters: systems searched, custodians, date range, and keywords. Some agencies will not provide them. That refusal is also evidence. The point is to show you attempted to validate the search. 5) Use a standardized appeal template. Appeals are about process. Keep them short. Quote the agency’s decision. State why the search was inadequate or why exemptions were misapplied. Request a remand for a new search. Ask for a Vaughn index if exemptions were used. Attach the request, the receipt, and the determination. 6) Build a MuckRock digest when volume becomes unmanageable. When you have dozens of receipts and determinations, you need a digest format. A digest is a table that lists: agency, component, case number, date filed, date acknowledged, determination type, and link to the primary artifact. The digest becomes the front page for the corpus. It is how a reviewer can understand the entire campaign in minutes. 7) Prove the negative with controlled contradictions. If an agency says “no records,” but you have contemporaneous communications that imply records exist, preserve the contradiction. Do not overclaim. Just place the two statements side by side with dates and custodians. This is where adverse inference becomes a plausible remedy in later proceedings. 8) Close the loop with oversight entities. Once you have a clean ledger, you can notify oversight bodies with a concise cover letter and a binder index. They do not need the narrative. They need the map. Common failure modes. - “We did not receive your request.” Fix: preserve the first receipt and the submission metadata. - “Your request was too broad.” Fix: request a meet-and-confer and memorialize any narrowing in writing. - “No responsive records.” Fix: ask for the search description and custodians, then appeal if the description is missing or implausible. - “Transferred to another office.” Fix: treat the transfer letter as an artifact and track the new case number as a child record. - “Administrative closure.” Fix: preserve the closure notice, then resubmit with the closure language quoted and refuted. A minimal exhaustion checklist. You can usually prove exhaustion with five artifacts: 1) the request 2) the receipt or acknowledgment 3) the determination 4) the appeal 5) the final administrative action or a documented barrier preventing it In this archive, the DOJ OIP redirect pattern and related FOIA determinations are handled as discrete, hash-verifiable artifacts. The goal is not persuasion. The goal is reproducibility: any third party should be able to open the ledger, follow the receipts, and confirm the sequence. If you are running this workflow, the next action is simple: ensure every FOIA thread has (a) receipt, (b) acknowledgment, (c) determination, (d) appeal, and (e) final administrative outcome, or a documented barrier to obtaining it. That is exhaustion.