Document Governance & Public Records in the Modern Agency

Every public works agency has a public records workflow. Almost none of them designed it. The workflow emerged organically — a request comes in, an email goes out, three departments search shared drives, a records officer assembles a packet, a redaction pass happens by hand, and the final response goes back twenty business days later, give or take. The cost of this workflow is largely invisible because it is distributed across staff who already have other jobs.

It is also, at the median agency, very high. The National Association of Government Archives and Records Administrators (NAGARA) has documented fully loaded per-request costs of $640 to $1,800 for complex requests at mid-size local governments. The Sunshine Review and various state freedom-of-information audits have separately found that median response times have lengthened over the last decade, even as the volume of requests has grown — driven primarily by the structural difficulty of locating and reconstructing records that were never structured for retrieval in the first place.

The agencies operating at the leading edge have made one architectural choice that collapses the cost: they treat document governance as a property of the operating system of record, not as a downstream compliance function. Every document is versioned at creation. Every revision carries attribution. Every reference is preserved. Retention rules live on the document class. When a request arrives, the response is a query — not a project.

The legal frame of public records compliance — every state has one, and the federal Freedom of Information Act (FOIA) sits over the federal layer — assumes that the document is the unit of accountability. The request is not "tell us what happened." The request is "produce the documents that show what happened." Agencies that retrofit a search engine over a shared drive are answering a different question than the one being asked.

A governed document record answers the actual question. The version in effect on a given date is queryable. The attribution on each revision is preserved. The reference graph — which jobs, inspections, and permits cite the document — is intact. When a journalist files a request asking for "every inspection report on the Maple Avenue overpass between 2021 and 2025, including any subsequent amendments," the response is exported in hours, not weeks, with full provenance attached.

The architectural commitment that makes this possible is that document control is not a module bolted onto the operating system — it is a property of the operating system itself. Every job, project, inspection, and approval treats its attached documents as governed records by default. The records officer is no longer a forensic investigator. They are a system operator producing a query.

A regional newspaper files a public records request with a city public works department asking for every inspection report, change order, and contractor communication associated with a $14M road resurfacing program over a four-year window. Under the legacy posture, the records officer estimates fulfillment at 22 weeks at a fully loaded cost in excess of $48,000 in staff time. The newspaper publishes a piece on the agency's slow response before the records arrive.

Under a governed posture, the same request is fulfilled in nine business days. The records officer queries the operating system for the program's project records, exports the document set with full version history and attribution, runs the standard redaction pass on the relevant fields, and delivers the response. The story the newspaper publishes is about the agency's transparency posture rather than about its delays.