The "Backlog" Exposed: Manufactured Minutes and a Year of Missing Records
- nicholasjbroughan
- May 1
- 3 min read
Transparency isn’t just about what the government says, it’s about when they say it. For the last three weeks, I have been engaged in a FOIA (Freedom of Information Act) process to secure the draft minutes for our Board of Supervisors meetings from January through April 2026.
What I discovered is a systemic failure of accountability that every resident of the Western District, and all of Caroline County, needs to see.
The 21-Day Wait for a "Draft"
I filed my request for these minutes on April 16th. These are standard documents that should be ready within days of a meeting. Instead, the County invoked a legal extension, making me wait 21 days for records that are essentially the "receipts" of how they are spending your tax dollars.
When I finally received the files, the digital evidence (metadata) revealed why they made me wait.
Documents "Born" Under Pressure
While the meetings took place in January, February, and March, the digital fingerprints on these files show they didn't exist until I asked for them.
The January 13th Meeting: The draft minutes for this meeting were not created until April 29, 2026—over 100 days after the meeting occurred.
The May 1st Creation Dates: Multiple files show creation dates ranging from April 28th to May 1st, the exact window the County was preparing its response to my request.
This means for over three months, there was no official draft record of the Board’s January actions. Our government was operating in the dark, and they only turned the lights on because a resident forced the issue.
AI-Generated History
Perhaps most concerning is the County’s admission in their final response: "Given the current backlog, the County is utilizing AI (Artificial Intelligence) to assist with the preparation of the minutes."
We are now in a situation where:
A machine is writing our history months after the facts occurred.
Accuracy is at risk. AI is known to "hallucinate" details. If a staff member wasn't recording these minutes in real-time (and the author is missing from the attendance records of several drafts), who is ensuring the machine got the votes and the motions right?
The "Backlog" Excuse. If the County has AI tools to make things "timely," why did it take a FOIA request and 21 days to see them?
Accountability is Not a "Plug-In"
Meeting minutes are legal documents. They record tax hikes, budget shifts, and infrastructure failures. They should be written by humans, in real-time, and made available to the public immediately. Using AI to clear a "backlog" that shouldn't exist is not transparency, it’s narrative management.
On May 12th, the Board is scheduled to officially adopt these minutes. I am calling on the Board to explain how they can swear to the accuracy of machine-generated drafts for meetings that happened four months ago.
The Missing Year: A Pattern of Silence
While the County scrambles to use AI to manufacture minutes for 2026, a much larger gap remains in the public record.
Upon auditing the County’s official website, it appears that meeting minutes from April 2025 until January 2026 are also missing. This means nearly a full year of Board decisions, including votes on major land-use permits, budgetary shifts, and infrastructure projects, is effectively invisible to the average resident.
A website with a "Minutes" section that hasn't been updated in a year isn't a technical error; it’s a failure of governance. When we are told to "trust the process," we should at least be allowed to see what that process was. If the County can’t keep its own website updated with the basic records of its meetings, how can we trust them to manage the complex future of our County?
Audit the Record Yourself
I believe you shouldn't have to file a FOIA request and wait 21 days to see what your government is doing. I am making the records I fought for available to everyone right now.
Download the complete Jan-April 2026 Draft Minutes below and see for yourself what has been happening behind the "backlog."
Comments