What Filing FOIA Requests Taught Me About Systems, Sanity, and Transparency

I didn’t set out to build a system.

I just wanted answers.

But somewhere between my first FOIA request and my twentieth, I realized that if I didn’t create structure for myself, I was going to lose track of what had been requested, what had been answered, what was disputed, what was tolled, and what had quietly evolved into something else entirely.

So I did what I always do when things get complicated:

I built a system.

FOIA Isn’t One Process — It’s Many Overlapping Ones

From the outside, a Freedom of Information Act (FOIA) request looks simple:
you ask for records, the government responds, and you either get them or you don’t.

In practice, FOIA quickly becomes a web of overlapping states:

• open vs. closed
• tolled vs. awaiting a cost estimate
• answered vs. actually resolved
• “no records exist” vs. “records exist but not in the form you expected”
• narrowed scope vs. reopened request

Those states don’t replace each other—they stack, and the county only shows Open or Closed status.

Without structure, it’s easy to lose context:
Which request depended on another?
Which answer contradicted an earlier response?
Which clarification actually moved things forward?

That’s when frustration sets in.

My Folder Structure Became My Case-Management System

Very early on, I realized the County’s own FOIA system alone wasn’t enough.

Every FOIA request now lives in its own folder on my drive, named with:

• the request number,
• a short human-readable description,
• and (when relevant) the estimated or final cost. (an initial estimate of ~132.31 US vs a final invoice of 12.34 US)

I add the “US” suffix because file names can’t contain dollar signs, and the “US” suffix lets me identify the number as a dollar amount programmatically. The tilde (~) represents an estimated value.

At a higher level, requests are grouped in folders by status, not topic:

• 00 Retracted for later
• 01 Pending
• 02.1 Estimated (Tolled)
• 02.2 Estimated (Narrow Scope)
• 02.3 Estimated (Proceed)
• 03 Deposited
• 04 Invoiced
• 05 Paid
• 06 Refund Pending
• 07 Disputed
• 08 Done

Inside each request folder, I keep things intentionally boring and consistent:

• every timeline update saved as a new PDF (never overwritten),
• responses and invoices as they evolve,
• a Documents/ folder for records provided,
• extracted text versions alongside the originals,
• voicemail audio related to that request,
• and notes capturing follow-up conversations.

When a request changes status, I don’t rewrite history — I add an artifact and move the folder. Weeks later, I can reconstruct exactly what happened, when it happened, and how the story changed.

This system wasn’t designed all at once. It grew over time, because it had to.

Automating the Boring Parts

Once the volume crossed a certain threshold, manual handling became unrealistic.

So I leaned into tools.

I wrote small shell scripts to:

• archive FOIA folders into timestamped ZIPs,
• extract text from PDFs,
• OCR scanned documents and images,
• handle rotated PDFs,
• extract text from images embedded in Word documents,
• and bundle outputs into searchable text collections.

Some records arrive as clean spreadsheets.
Others are scanned PDFs.
Others are sideways images inside PDFs.
Some meetings only exist as audio.

Rather than fight each case individually, I built repeatable workflows. Nothing gets discarded — only transformed.

The goal isn’t automation for its own sake. It reduces friction, so attention stays on understanding the information rather than on wrestling with formats.

Audio Counts Too

Not everything happens in writing.

Sometimes clarification happens by phone. Sometimes context appears in voicemail. Sometimes committee discussions exist only as meeting audio.

When that happens:

• I save the audio file alongside the request,
• transcribe it using external tools,
• and document the substance of the conversation back in the FOIA request itself.

That way, verbal information doesn’t disappear into memory. It becomes part of the record.

Why I Don’t Ask for Everything at Once

Another lesson I learned early on is that one giant FOIA request is almost always the worst way to proceed.

Big, all-encompassing requests tend to:

• produce massive cost estimates,
• be harder to narrow meaningfully,
• and create confusion when follow-up questions arise.

So instead, I started treating each FOIA request as a discrete, well-scoped unit of inquiry.

Each request answers one question.

That approach has a few advantages:

• it keeps individual requests manageable,
• it makes scope-narrowing easier,
• and it allows requests to reference one another cleanly later.

If something needs clarification, I don’t derail the original request — I open a separate FOIA to answer the question first.

In one case, I had a request that was tolled while we worked through scope and cost. Rather than speculate or push forward blindly, I opened a second, narrowly tailored FOIA to answer a specific process question. Once I had that answer, I was able to return to the original request with much better precision.

That reduced staff workload and avoided unnecessary back-and-forth.

FOIA as a Threaded Conversation

Handled this way, FOIA becomes less like a single demand and more like a threaded conversation:

• Request A establishes what exists.
• Request B clarifies how it’s created or stored.
• Request C retrieves only what’s actually needed.
• Later requests can reference earlier ones explicitly.

That structure makes it easier for everyone to stay oriented — including me.

It also creates a cleaner public record. Each request stands on its own, with its own timeline, scope, and resolution, rather than one sprawling request that becomes impossible to untangle.

Personal Email Is Still a Public Record

One of the more uncomfortable but important lessons I encountered is this:

When government business is conducted on personal email accounts, those records are still subject to FOIA.

Virginia law is clear on this point. The medium doesn’t matter — the function does.

That reality has practical consequences.

When officials use personal email for public business:

• records become harder to locate,
• FOIA officers lose visibility and control,
• and requesters may not even know what exists to ask for.

This became especially relevant with citizen members of advisory boards.

In Warren County, advisory board members are not consistently issued county email accounts. That means public business often ends up on personal email systems that:

• aren’t centrally managed,
• aren’t easily searchable,
• and aren’t under the direct control of the FOIA officer.

As a result, public records can effectively disappear — not intentionally, but structurally.

That’s one of my biggest concerns.

People may not realize that when they use personal email for government work, those messages are still public records. And without institutional email accounts, preserving and producing those records becomes far more difficult than it needs to be.

This isn’t about catching anyone doing something wrong.
It’s about designing systems that make compliance easy by default.

Why This Ties Back to Everything Else

This lesson connects directly to the broader themes of this post:

• scope matters,
• structure reduces stress,
• clarity lowers cost,
• and systems shape behavior.

When requests are modular, records are centralized, and communication channels are clear, FOIA becomes less adversarial and more routine.

That’s the goal.

Learning to Work With Cost, Not Against It

One of the steepest learning curves in this process had nothing to do with documents or data.

It was cost.

Early on, I received a cost estimate for a request that came back at over $8,300. For most people, that number would be a hard stop — and honestly, I understand why. Seeing a figure like that can make FOIA feel inaccessible by design.

Instead of giving up, I treated it as a starting point.

By asking questions, narrowing scope, and iterating carefully, that same request eventually moved through several revisions:

• from $8,329,
• to $1,376,
• to $464,
• and finally to an actual cost of $162 — resulting in a refund, which I’m also tracking as part of the record.

My original cost cap on that request was $50.

I didn’t abandon that principle — I learned how to negotiate toward it responsibly.

Why Large Estimates Don’t Always Mean Large Costs

What that experience revealed is something I think many people don’t realize:

Initial FOIA estimates are often conservative to the point of being wildly disconnected from the actual work performed.

That’s not an accusation — it’s a reality of estimating staff time in complex systems. When scope is unclear, estimates tend to assume worst-case effort.

By:

• clarifying what I actually needed,
• eliminating unnecessary review steps,
• narrowing date ranges,
• and focusing on specific formats or artifacts,

the real work required dropped dramatically.

In the end, the difference between $8,300 and $162 wasn’t about staff effort — it was about precision.

Using Cost Caps as a Tool, Not a Threat

Another thing I learned is that cost caps aren’t just limits — they’re communication tools.

I started doing two things consistently:

1. Setting an initial cap that felt reasonable, with padding.
2. Once an estimate came back and I agreed to proceed, setting a second cap slightly above that estimate and asking to be notified before exceeding it.

That approach:

• protects both sides,
• prevents surprise invoices,
• and forces clarity about where time is actually being spent.

It also makes it much easier to have constructive conversations about narrowing the scope before money is spent.

Narrowing Requests Without Losing Signal

Over time, I also got better at what I was asking for.

Instead of just requesting “records,” I learned to be explicit about including:

• draft documents, when relevant,
• supporting materials used in meetings,
• audio recordings, when discussions mattered more than final text.

Those details matter — because final documents rarely capture the full context.

In one case, I requested audio recordings and received a ZIP file that was nearly 9 GB in size. The files were high-quality stereo WAV recordings — excellent for archival purposes, but far more than was necessary for review.

By converting those files to MP3, I was able to reduce the total size to around 210 MB, with individual files in the 20–40 MB range.

That was more usable for me — and it also highlighted something else:
there was now a 9 GB archive sitting on a FOIA server, doing nothing, simply because no one had stopped to ask what format was actually needed.

That’s another recurring theme in this work:
often the burden isn’t the data itself — it’s how it’s packaged.

Why This Matters for Normal People

I share this part of the process because many people never make it past the first large estimate.

They see a number with four digits — or five — and assume:

“FOIA isn’t for people like me.”

What I learned is that estimates are negotiable in good faith, scope can almost always be refined, and persistence — when paired with clarity and respect — can lead to outcomes that are far more reasonable than they first appear.

That doesn’t mean everyone should push every request.

It means people should know they have options.

A lesson I didn’t expect

FOIA isn’t just about asking the right questions. It’s about learning how systems estimate effort — and how much clarity can reduce that effort for everyone involved.

The Phone Call That Wasn’t What It Seemed

There was one moment in this process that genuinely made my stomach drop.

My phone rang.
Caller ID said: “Warren County Attorney.”

If you’ve ever filed a FOIA request, you know that split-second panic:
Did I overstep?
Did something escalate?
Did I misunderstand something?

I didn’t answer immediately.

When I checked the voicemail, the tension evaporated almost instantly. It wasn’t the county attorney at all — it was the FOIA officer, calling to follow up after getting additional information from Finance.

The caller ID was just misleading.

Nothing dramatic had happened. No confrontation. No escalation. Just normal process — obscured by a confusing phone label.

That moment stuck with me because it perfectly captured what FOIA feels like from the outside: opaque, intimidating, and easy to misinterpret without context.

And it reinforced why I rely so heavily on written follow-ups, documentation, and structure. Without those anchors, it’s easy to let uncertainty fill the gaps.

Am I Being Too Aggressive?

There’s a question I’ve asked myself more than once:

Am I overwhelming the very people I’m trying to help?

FOIA can feel aggressive from the inside, even when that’s not the intent. Requests arrive asynchronously. Staff juggle audits, meetings, daily responsibilities, and legacy systems. And it’s not always clear on their side how individual requests relate to one another.

There was one moment that really stuck with me.

In response to an earlier request, I explicitly offered to wait until after the first of the year before making a second request for an increased scope. I did more than that — waited until February — and then submitted the request. Shortly afterward, I got a call saying they thought we were going to “confirm before proceeding.”

Looking back, I can see how that happened. Her email stated the following:

I would like to hold off right now with the promise that we can pick this back up after the first of the year.

My intent was: I’ll wait until after the new year.
Their interpretation was: We’ll reconnect before anything moves forward.

No one was wrong. But it was a reminder that process assumptions live in people’s heads unless they’re written down clearly.

That moment reinforced something important for me: part of doing this responsibly isn’t just what I ask for — it’s how clearly I signal intent.

This Isn’t About More Data — It’s About Less Work

Here’s the part that often gets missed.

The end goal of this work is not more FOIA.

In the long term, finance staff should not be fielding repeated requests for raw data from the public or oversight committees. Oversight bodies shouldn’t review thousands of transactions unless something genuinely stands out.

That’s why I’ve spent time building example reports and dashboards from FOIA-provided data.

Examples of artifacts I’ve produced include:

Not to audit staff — but to demonstrate what good oversight artifacts look like.

Oversight committees don’t need raw ledgers.
They need signals:

• monthly and quarterly trends,
• year-over-year comparisons,
• clear variance explanations,
• consistent formatting,
• and predictable reporting.

If those signals are present, everyone wins:

• less stress on staff,
• fewer surprises for committees,
• more confidence for the public.

Raw data is for auditors.
Reports are for governance.

Why Timing and Process Suddenly Mattered Even More

There was another procedural detail that reinforced the urgency of this work.

The Finance/Audit Committee was originally scheduled for February 3, 2026, to consider dissolution, but that meeting fell on the Board’s first-of-the-month session — a meeting traditionally reserved for non-controversial items and held midday, when public attendance is typically lower.

During that meeting, two supervisors raised concerns about how to handle Finance/Audit Committee matters in that setting. As a result, the item was removed from the agenda and rescheduled for February 17.

That decision made sense procedurally, but it also underscored something important:
oversight structures don’t just depend on what is discussed — they depend on when, where, and how discussions happen.

For me, it reinforced the need to preserve:

• the committee’s prior work,
• its operating rhythm,
• and the context in which oversight decisions were being considered.

Once agenda items move, meetings shift, or committees are restructured, it becomes very easy for prior efforts to fade from view — not because anyone intended that outcome, but because process itself can quietly reshape what remains visible.

That realization further clarified why this work needed to happen before decisions were finalized, not afterward.

FOIA as a Bridge, Not a Hammer

I don’t see FOIA as a permanent operating mode.

I see it as a bridge — a way to move from “we don’t quite know how to show this yet” to “here’s a clean, repeatable way to communicate financial health.”

That’s why I’ve tried to:

• offer scope-narrowing up front,
• accept reasonable delays,
• document verbal conversations in writing,
• and invite guidance from directors rather than guessing at constraints.

None of this makes the process effortless. But it makes it constructive.

And it helps me sleep at night knowing I’m pushing systems forward, not just pushing people.

What This Means for the New Financial System

It’s worth noting that the County has already approved an RFP to replace its legacy AS/400 financial system with an Enterprise Resource Planning (ERP) Financial Software Systems Environment—a decision I publicly supported at the Board of Supervisors meeting on January 20, 2026 (Timestamp 00:06:58).

Where I offered criticism wasn’t about whether to modernize, but how modernization was being defined.

One thing that stood out to me when reviewing the RFP was that nearly every feature was classified as “critical.” That’s understandable — everyone wants a system that does everything. But when everything is critical, it becomes harder to distinguish what actually improves day-to-day governance from what simply checks a box.

My FOIA experience helped clarify that distinction.

What repeatedly created friction wasn’t the absence of advanced features — it was the lack of basic transparency affordances:

• clear, reusable data exports,
• consistent identifiers across modules,
• traceable correction paths,
• and reports designed for oversight rather than transaction processing.

Those are the features that reduce FOIA volume, lower staff burden, and improve public confidence — yet they’re often treated as secondary to operational requirements.

FOIA didn’t just reveal data. It revealed where the system itself adds unnecessary friction.

That’s why I believe transparency and public-records considerations shouldn’t be treated as add-ons in a new system, but as core design requirements. Not because of FOIA compliance alone, but because systems that make oversight easier tend to make daily operations calmer as well.

In that sense, FOIA became an unexpected form of user testing — showing where the old system strained, and where the new one has the opportunity to do better.

There Are No Villains Here

One thing I want to be very clear about:
this work hasn’t revealed villains, conspiracies, or secret plots.

FOIA isn’t a detective novel. It doesn’t uncover shadowy cabals or hidden agendas. What it shows you — over and over again — are people following processes.

Sometimes those processes are inefficient.
Sometimes they’re outdated.
Sometimes they rely too heavily on institutional memory.
Sometimes they assume tools or staffing levels that no longer exist.

But they’re still just processes.

For people new to FOIA, it can be tempting to read delays, redactions, or large cost estimates as evidence of something being hidden. In my experience, that interpretation is almost always wrong.

What you’re usually seeing is:

• manual workflows,
• conservative estimates,
• siloed systems,
• and staff doing their best inside real constraints.

What FOIA Actually Reveals

What FOIA does reveal — consistently — is how information moves.

You start to see:

• which offices act as communication hubs,
• where decisions slow down,
• which systems generate the most friction,
• and where clarity breaks down between departments.

That’s not about blame. It’s about structure.

And once you see structure, you can start asking better questions:

• Where could this be simpler?
• What would reduce repeated work?
• How could information be shared more cleanly the first time?

Those are governance questions, not accusations.

FOIA Is (and Should Be) Boring

At its best, FOIA is very, very boring.

It’s spreadsheets.
It’s timelines.
It’s invoices.
It’s status changes.
It’s clarifications.
It’s waiting.

The only real excitement I get out of it is when I finally have enough data to build something useful — a report, a chart, a system that helps make sense of things.

That’s the kind of excitement you want in public records work:
quiet, incremental, and cumulative.

If FOIA feels dramatic, something has already gone wrong.

Curiosity Without Suspicion

I approach this work with curiosity, not suspicion.

The goal isn’t to catch someone.
It’s to understand how things actually work, and how they might work better.

That mindset has shaped everything I’ve described in this post:
how I scope requests,
how I talk to staff,
how I document interactions,
and how I share what I learn.

FOIA doesn’t require cynicism to be effective.
It requires patience.

And a willingness to accept that most of the time, the story is not about people — it’s about systems doing exactly what they were designed to do, long after the world around them changed.

Transparency Applies to Me Too

There’s one more thing worth saying explicitly.

My FOIA requests are themselves public records.

Anyone can request them.
Anyone can read what I asked for.
Anyone can see how I framed questions, how I responded to estimates, how I followed up, and how I interacted with staff.

That reality imposes a discipline of its own.

Because when your own requests are FOIA-able, you don’t get to posture, speculate, or make accusations lightly. You have to assume that how you ask matters just as much as what you ask.

If I’m impatient, dismissive, or unfair, that tone becomes part of the public record.
If I make assumptions or jump to conclusions, those words can be read later without context.
If I treat staff poorly, anyone else can see it.

That knowledge forces you to be on your best behavior — not performatively, but ethically.

Why That Constraint Is a Feature, Not a Bug

In practice, this means:

• I avoid accusatory language.
• I document facts instead of motives.
• I ask clarifying questions instead of drawing conclusions.
• I treat every interaction as something that could be read by someone who wasn’t there.

That’s not because I expect everyone to agree with me. It’s because FOIA isn’t a private negotiation — it’s a public process.

Once you internalize that, it changes how you operate.

You stop trying to “win.”
You focus on creating a record that’s fair, readable, and defensible on its own.

Transparency Enforces Civics

This is one of the quieter virtues of open-records laws: they don’t just expose institutions — they expose process.

FOIA doesn’t reward outrage.
It rewards clarity.

It doesn’t reward clever accusations.
It rewards careful questions.

And it doesn’t protect anyone — requester or staff — from scrutiny. It simply makes the interaction visible.

That mutual visibility is why I’ve tried to approach this work with restraint, patience, and respect, even when the process has been frustrating.

If I’m going to ask for transparency, I need to be willing to live inside it too.

Why I’m Sharing This

I’m sharing this because transparency isn’t just about whether records are technically available.

It’s about whether the public can use them — to understand patterns, ask better questions, and reduce speculation.

The folders, the scripts, the reports — they’re not the point.
They’re scaffolding.

The point is clearer communication, calmer oversight, and fewer surprises.

And yes — without this system, I’d be completely lost too.

Closing Thought

FOIA works best when it’s treated not as a one-off demand, but as part of an ongoing conversation between the public, the data, and the systems that produce it.

Everything else is just structure to keep that conversation honest.