The Record Nobody Found: How Responsive Documents Get Missed
Agencies miss responsive records because nobody searchedwhere the record was. A document sits in a departmental folder outside thesystems anyone thought to check, and it surfaces later by another route. Thisis the failure that turns an administrative process into litigation, and it isa coverage problem rather than a diligence one.
That distinction carries more weight than it first appears.A diligence problem is solved by asking people to try harder. A coverageproblem is not, because the staff running the search are already searchingeverything they know about. The gap sits between what they know about and whatthe agency actually holds.
A record is responsive when it falls inside the scope ofwhat was asked for. Not when it is convenient, not when it is well organized,and not when it happens to live in the system the records office uses.Responsiveness is decided by the request, and a request has no obligation torespect how an agency is structured internally.
Take a request for correspondence about a contract award.The correspondence exists in the procurement officer's mailbox. It also existsin a shared drive belonging to the department that wanted the contract, in achat thread between two managers who compared bidders, and possibly in a textmessage sent from a parking lot. All four are responsive. Only the first issomewhere anyone would think to look first.
Departmental drives nobody inventoried
Most agencies have a document library that is officiallywhere records go, and a much larger set of folders where the work actuallyhappens. Departments build their own structures, name them after projectsrather than record types, and keep them long after the project ends. Nothingabout that is misconduct. It is what people do when they need somewhere to puta file today.
Chat and personal devices
Discussion that used to happen in email now happens in chat,and some proportion of it happens on personal phones. Many jurisdictions holdthat a record about public business is disclosable regardless of the deviceholding it, which leaves an agency owing material it does not control andcannot search directly. That is covered in more depth in text messages,personal devices, and chat platforms.
Systems nobody calls a records system
Case management, permitting, licensing, complaint intake, HRplatforms, and the ticket queue that IT runs all hold records. None of them arethought of as records systems, so none of them appear on the list of places tosearch. The request does not care what the vendor called the product.
Material that is not searchable text
Scanned binders, photographs of a whiteboard, PDFs producedby a scanner with no text layer, and video. A keyword search returns nothingfrom any of these.
This is the failuremode worth sitting with. A search that cannot read a document reports exactlythe same result as a search across a document that does not exist. Both comeback empty, and nothing in the empty result distinguishes them.
The reason missed records are so persistent is that nothingsignals the miss at the time. A caseworker searches the three systems they haveaccess to, finds eleven documents, reviews them, and closes the request in goodfaith. The file looks complete. It reads as complete to a supervisor. It willread as complete for months.
The miss surfaces through a different route entirely. Asecond requester asks a narrower question and gets a document the firstrequester should have received. A former employee mentions an email in adeposition. A department produces something in litigation that never appearedin the response. By then the question has stopped being whether the search wasthorough and has become why the agency said it had produced everything.
Agencies rarely reach that point through carelessness. Theyreach it because coverage was never written down, so nobody could see what itexcluded.
The standard is not perfection. Under federal FOIA and moststate analogues, an agency must conduct a search reasonably calculated touncover responsive records. Missing a document does not by itself mean thesearch was inadequate. What matters is whether the method was reasonable givenwhat the agency knew about where records live.
That is a more forgiving standard than most records officersassume, and it has a sharp edge. Reasonableness is judged on the method, so theagency has to be able to describe the method. Which systems were searched,which custodians were covered, which terms were run, and which date rangesapplied. An agency that found ten documents and can describe its search is in afar stronger position than one that found forty and cannot. Proving an adequatesearch covers what that description needs to contain.
Coverage is one of the few parts of this work that can besettled before a request ever arrives.
Write the inventory once. List every system thatholds anything, including the ones nobody calls a records system, and name acustodian for each. The list will be longer than expected and that is the pointof making it.
Search by custodian, not by system. Start from whowas involved and work outward to what they use. Starting from systems means youonly ever search the systems you already remembered.
Make unsearchable material visible. Scanned andimage-based documents need optical character recognition before a keywordsearch means anything. Where that is not possible, the material needs to be listedand reviewed by hand rather than passed over silently.
Record what you excluded and why. A systemdeliberately left out of scope is a defensible decision. A system nobodyremembered is not. The only difference between them, eight months later, is whethersomebody wrote it down.
Coverage is the specific thing Govflo is meant to make visible. Everydocument the search reaches is recorded with the source it came from and whatwas decided about it, including the ones set aside as non-responsive orexcluded under an existing confidentiality label. The four outcomes are keptdistinct, because a document nobody produced and a document deliberately leftout look identical in a file that only lists what was released.
Coverage stops being something a caseworker holds in theirhead and becomes part of the record.
None of that decides responsiveness for you, and it shouldnot. Whether a document falls inside the scope of a request is a judgment thatbelongs to the agency. What changes is that the judgment gets made against thematerial that actually exists, rather than the subset somebody happened toremember.
Frequently asked questions
Usually the question is not whether a specific document was missed but whether the search was reasonable. An agency that can describe a methodical search across the systems it knew about is generally on solid ground. The exposure grows when the agency cannot describe its search at all, or when the missed material sat somewhere an obvious inquiry would have reached.
No, and doing so would be unworkable. Scope should follow the request. The point of an inventory is not to search everything every time, it is to make the decision about what to leave out a conscious one that gets recorded, rather than an accident of who was available that week.
Produce it, and say plainly that it was located after the original response. Most statutes contemplate supplemental production, and a late release handled openly is a far smaller problem than one discovered by the requester. Record how it was found, because that usually points at the coverage gap that will otherwise produce the next one.
See it running on your statute
Govflo runs public records requests and open meetings from intake through to release, configured to the law that governs each request. Tell us about your agency and we will set up a working session.
The inventory of every system holding records, with a custodian named for each, is the highest-value hour a records office can spend.
