What Targeted Requests Actually Look Like
Last week I wrote about FOIA and Sanity — about structure, timelines, and discipline in public records work.
Tomorrow, the Board of Supervisors is scheduled to consider dissolving two advisory committees. This post focuses solely on the Finance/Audit Committee.
Originally, the Finance/Audit vote was scheduled for February 3.
Due to public interest and scheduling considerations, it was moved two weeks later to an evening session.
I used that window to do something simple:
Acquire and review as much of the committee’s working record as possible.
Not to speculate.
To document.
I have attended many of these committee meetings. I’ve raised questions, submitted reports, and tracked posting practices. With a structural decision now on the agenda, the responsible next step was to compile the relevant documentation so the discussion can rest on record rather than recollection.
Structural decisions deserve structural documentation.
This post is not about personalities. It is about process — and whether the structure matches the mission it was created to serve. If the Board concludes that the committee’s structure remains sound, this documentation still serves a purpose: it provides a baseline for improving it.
Why the Requests Clustered
Most of my recent FOIA requests revolve around the Finance/Audit Committee for a reason.
I have been attending those meetings regularly. I’ve observed:
- Posting delays for agendas and minutes.
- Situational enforcement of quorum boundaries.
- Draft policies remaining in circulation for years.
- Supervisor participation raised questions about advisory vs. Board-level boundaries.
- A supervisor preparing a presentation that was not initially posted.
- Prior references to sanitary district policy discussions I had not attended.
Each observation led to a targeted question.
Each question led to a narrow request.
Not “all communications.”
Not fishing expeditions.
Specific documents tied to:
- Specific meetings.
- Specific dates.
- Specific statements.
- Specific draft policies.
FOIA Requests Filed (Finance/Audit Related)
The following requests were filed in my individual capacity and relate directly to the Finance/Audit Committee, sanitary district policy discussions, or financial signal work leading up to the scheduled dissolution vote.
Legend: 👁️ Published; 🔐 Unpublished (at the time of this post).
For each request, I set a cost cap in advance. The cap reflects what I believe is a reasonable range for the scope requested, with modest room for adjustment so staff can proceed without repeated confirmation.
“Estimate” reflects the County’s projected cost.
“Paid” reflects the actual invoiced amount.
| Request | Topic | Type | Status | Cap | Estimate | Paid |
|---|---|---|---|---|---|---|
| 25-849👁️ | Fuel Data | Data | Done | $50 | $42.63 | $14.21 |
| 25-899🔐 | AP Transactions (GL) | Data | Done | $25 | $21.32 | $21.32 |
| 25-1012👁️ | Audit Status v2 | Doc | Done | – | – | – |
| 25-1013👁️ | Finance Director response to audit status doc | Done | $22.19 | $22.19 | ||
| 25-1025👁️ | Treasurer response to audit status doc | Done | $31.40 | $31.40 | ||
| 26-97👁️ | Meeting Audio & Draft Policies | Doc Audio | Done | $50 | – | $15.94 |
| 26-99👁️ | Emails & Text referencing myself | Done | $50 $514.61 | $8,329.06 $1,376.43 $464.61 | $464.61 -$302.44 $162.17 | |
| 26-100👁️ | SPL Ledger Audits | Data | Done | $50 $100 | $60.58 | $60.58 |
| 26-113👁️ | Doc ID Metadata | Data | Done | $100 $130 | $313.08 $110.59 | $110.59 |
| 26-115👁️ | Audit Status v1 | Doc | Done | $15 | – | – |
| 26-116👁️ | Stanmeyer Presentation | Done | $25 $45 | $35.41 | $35.41 | |
| 26-117👁️ | AP Ledger FY14 – Present | Data | Done | $150 | – | $75.47 |
| 26-118👁️ | Checks FY14 – Present | Data | Done | $75 | – | $12.20 |
| 26-119👁️ | Audit Trail January 2025 – Present | Data | Done | $75 | – | – |
| 26-120👁️ | P-Card FY21 – Present | Data | Rescind | $75 | – | – |
| 26-121👁️ | Fuel Data FY21 – Present | Data | Done | $125 | – | $5.68 |
| 26-132👁️ | Supervisor John Stanmeyer “Sanitary” Emails | Paid | $60 | $46.01 | $46.01 | |
| 26-133👁️ | Meeting Audio Jan-May 2025 | Audio | Done | $40 | – | – |
| 26-137👁️ | CivicPlus Export Instructions | Docs | Done | $25 | – | – |
| 26-140👁️ | Journal AP FY24 -Present | Data | Done | $75 | – | $23.61 |
| 26-146🔐 | Bylaws & Prior versions | Docs | Pending | $75 | ||
| 26-147🔐 | Offline Minutes / Agendas | Docs | Pending | $100 | ||
| 26-148👁️ | Formation | Docs | Invoiced | $100 | – | $35.07 |
| 26-153🔐 | Officers & Elections | Docs | Pending | $75 | ||
| 26-154🔐 | Department Purchase Orders | Data | Pending | $100 | ||
| 26-155🔐 | Audit Status Operating Account | Pending | $100 | |||
| 26 Requests | Total | $671.85 |
Each of these requests was narrow in scope and tied to:
- A specific meeting date
- A specific email chain referenced publicly
- A specific draft policy
- A specific presentation
- A specific ledger export
- A defined timeframe
They were modular by design.
Other FOIA Requests
For completeness:
I have filed additional FOIA requests this year unrelated to the Finance/Audit Committee. Those include routine document retrieval and other research threads not connected to the pending committee vote.
| Request | Topic | Status | Cap | Paid |
|---|---|---|---|---|
| 25-944👁️ | Vision Gov Solutions Contract | Done | $150 | $104.78 |
| 26-81👁️ | GFOA award | Done | $50 | $15.74 |
| 26-109👁️ | County Administrator severance negotiations, Attorney Email chain | Paid | $50 | $47.10 |
| 26-156🔐 | County Administrator, Bradley Gotshall Severance amount | Pending | $75 | |
| 4 Requests | Total | $167.62 |
They are not part of this cluster and are not connected to the memorandum referenced below.
Transparency includes acknowledging the full scope.
When Estimates and Reality Don’t Match
Request 26-113 is a good example of how process evolves.
I requested system metadata for a defined set of CivicPlus Document Center records. The initial estimate was $313, based on staff reviewing each document individually.
From a systems perspective, that estimate caught my attention. Metadata in a content management system typically exists in structured fields and can often be exported in bulk. But knowing how something should work doesn’t mean assuming how it works locally.
Instead of arguing, I did two things:
- I opened a separate request (26-137) asking whether bulk export instructions existed.
- I narrowed the scope of 26-113 to roughly one quarter of the original documents and authorized a capped amount so work could proceed.
The result:
The County ultimately provided screenshots of metadata for all of the originally requested documents — not just the narrowed subset — and the total charge was $110.
That’s less than the original $313 estimate, and $10 more than my original cap.
And it answered the underlying question.
If necessary, I could have followed up with the remaining 75% under a new request, now informed by real cost data. But I didn’t need to.
The Hard Part: Staying Calm When You Know Systems
There’s a quiet discipline required here.
When you work in technology, you know how systems are often designed:
- Metadata lives in fields.
- Fields can usually be exported.
- Bulk operations are often standard practice.
But local governments don’t always operate under ideal system assumptions. Workflows are layered over time. Permissions are constrained. Vendors control interfaces. Institutional memory fades.
The temptation is to say: “This shouldn’t cost that much.”
The disciplined response is different:
Narrow scope.
Set a cap.
Test assumptions.
Let the record speak.
That approach lowers temperature, reduces friction, and produces better information than escalation ever would.
Why Modular Requests Matter
Because I narrowed the request instead of abandoning it:
- Staff workload was reduced.
- The real cost became visible.
- The data was produced.
- The record improved.
That’s the point.
Not winning an argument.
Learning how the system actually behaves.
When the Portal Became Public
Recently, the County made FOIA requests publicly viewable through its portal.
That changed the landscape.
For the first time, I could see:
- What others were requesting
- How similar topics were framed
- Which documents had already been produced
- Which exemptions were being cited in other contexts
In several instances, I was able to download documents released to other requesters that were directly relevant to my own research. In some cases, I realized I had asked for the same material.
That visibility will reduce duplication going forward and prevent unnecessary repeat requests.
That’s how transparency is supposed to work.
Ideally, once records have been produced, they should not need to be requested repeatedly.
From Requestable to Visible
In an earlier post, FOIA and Sanity, I noted that my requests were themselves subject to FOIA — meaning anyone could request them.
Now they’re not just requestable.
They’re visible.
That’s a meaningful difference.
Anyone can browse the portal, read what I’ve asked for, see how I framed questions, and review the documents released in response — without filing anything themselves.
That level of openness changes behavior.
It reduces duplication.
It improves consistency.
It increases accountability on all sides.
And it reinforces something I’ve tried to practice from the beginning:
If you’re going to participate in transparency, you need to be comfortable living inside it.
Records vs. People
One nuance I noticed after the portal became public:
The requests and responsive documents are visible — but requester identities are not always displayed as a separate field.
Interestingly, I saw at least one request asking for the name of another requester.
That highlights something important about modern transparency systems:
There is a difference between making records public and making people public.
FOIA is about access to records of public business — not about tracking who asked.
The portal appears to strike that balance by exposing the substance of requests and responses while limiting personal identifying information.
That distinction matters.
Transparency should illuminate process and decisions — not discourage participation.
Signing My Own Requests
In my case, I often include my name in the body of the request itself as part of the signature line.
That means my authorship is visible simply because I chose to sign it.
That wasn’t strategic. It was habit.
But now that requests are publicly browsable, it means anyone reviewing them can see what I asked for and how I framed it.
That visibility doesn’t bother me.
If I’m asking questions about public process, I’m comfortable attaching my name to them.
Transparency works both ways.
What the Requests Supported
The requests supported a structural memorandum submitted to the Board ahead of the dissolution vote.
That memorandum documents:
- Bylaw conformity issues
- Posting compliance gaps
- Audit workflow conflicts
- Quorum boundary confusion
- Officer election documentation gaps
- Policy stagnation (including the Sanitary District draft remaining unresolved for approximately 2.5 years).
- Advisory output limitations.
The conclusion was structural:
If dissolution occurs, it should be treated as structural housekeeping.
Not punitive action.
The Financial Signal Work
In parallel, I built financial signal reports to evaluate spending patterns rather than reviewing isolated transactions.
These include:
- Net outflow trend comparisons
- Vendor concentration and high-value payment thresholds
- Department-level fiscal-year-to-date variance patterns
These reports are designed to prompt structured review questions, not to imply wrongdoing.
For example:
- FYTD net outflow is down compared to prior year through October
- Vendor concentration remains low (HHI 549.07), though large threshold payments merit routine contextual review
- Certain departments show significant year-over-year variance that deserve structured explanation, whether due to reclassification, timing, or true spending shifts
Signal detection is not accusation. It is the beginning of better questions.
It is oversight literacy. These tools shift review from transaction-level anecdotes to pattern-level signals.
The Sanitary District Thread
One supervisor’s attempt to present at a meeting, along with prior references to sanitary district discussions, prompted requests for documentation and a review of the draft fiscal policy.
Understanding policy stagnation required documentation.
Not recollection.
What the Spreadsheet Revealed
Alongside the document requests, I compiled a chronological spreadsheet of Finance/Audit Committee agendas, minutes, policy items, attendance notes, and posting timelines. Seeing everything side-by-side changed the perspective.
Items that felt isolated in individual meetings revealed recurring patterns when tracked over time — repeated unfinished policy discussions, audit timing conflicts with bylaw language, inconsistent posting intervals, and situational participation boundaries. None of these observations depend on interpretation; they emerge from sequence and repetition. When timelines are laid out in order, drift becomes visible without commentary.
Structural questions are easier to evaluate when the record is organized. The spreadsheet simply made the pattern visible.
On Discipline
Every request I file is itself a public record.
That means:
- It must be clear.
- It must be narrow.
- It must be defensible.
- It must withstand scrutiny.
The discipline works both ways.
Public records are not about proving someone wrong.
They are about replacing speculation with documentation.
And when structural reform is on the agenda, documentation matters.
Forward
Whatever the Board decides tomorrow, structure is the goal.
Clear bylaws.
Predictable posting practices.
Defined advisory boundaries.
Measurable output.
Transparency is strongest when it is procedural.
And procedure benefits from documentation.
