Public Records
If you manage forty districts, you have one records process, not forty
A city with one clerk has one records process. If it is weak, the weakness stays where it is: one office, one backlog, one awkward conversation when something goes wrong.
A management firm administering forty districts does not have forty records processes. It has one, applied forty times. The same intake habits, the same folder structure, the same redaction method, the same person who knows how the website gets updated. That is the whole value of the model, and it is also what changes the risk arithmetic.
What multiplies and what does not
Some of this work is genuinely per-district and cannot be standardized away: each district has its own board, its own meeting schedule, its own records, its own counsel. A request for one district's documents is answered from that district's records, by someone who knows them.
The parts that are shared are the parts worth examining:
- How a request is received and logged. If requests arrive in a shared mailbox and are tracked informally for one district, they almost certainly are for the rest.
- How documents are produced and redacted. A redaction method is learned once and repeated. If it covers rather than removes, it does so on every release across the portfolio.
- How each district's website is kept current. Special districts carry obligations about what must be published and kept up to date. Where that is one person updating many sites by hand, the question is not whether something is stale, but which one.
- How meeting materials move. Notices, agendas and minutes follow the same route for every board you serve.
- What is retained, and for how long. A retention practice is a habit before it is a policy, and habits travel.
Why the arithmetic is different
Three things change when the same process runs across a portfolio.
A single method error is not a single error. One misconfigured redaction step, one folder that was never locked down, one site template missing a required item - each is multiplied by the number of districts using it. The cost of fixing the method is roughly flat. The cost of not fixing it scales.
Requesters can work at portfolio scale too. The same request sent to every district you administer arrives as one workload, on overlapping clocks, and any inconsistency between the responses is visible side by side. Answering forty variations of the same question well is a process problem long before it is an effort problem.
Knowledge concentrates in fewer people. The efficiency of the model means one person often holds how it works for many districts. When that person is on leave, or leaves, the gap is proportional to how much they carried.
An audit you can run across the portfolio
You do not need to examine every district to find out where you stand. Because the process is shared, a sample tells you about the method, and the method is what you are actually auditing.
Pick five or six districts that differ from each other - different boards, different sizes, different people doing the day-to-day work - and for each one answer these:
- Take a records response released in the last year. Can you select and copy the text under a redaction? If yes, that is a method problem, not a district problem.
- Pick a request from six months ago. Can you reconstruct when it arrived, who handled it, what was produced and when it was closed, without asking anyone?
- Open the district's website as a resident would. Is everything that must be published there, and current?
- Take one board meeting. Can you show the notice, the agenda and the approved minutes, and say when each was posted?
- Ask who would handle a records request for this district next week if the person who normally does it were unavailable. Is the answer a name or a shrug?
If the same answer comes back for five different districts, you have learned something about the process rather than about those five. That is the useful outcome, and it is also the cheap one: fixing a shared method once fixes it everywhere it is used.
Those five questions, with what a good answer looks like and what a bad one means, are a free worksheet. Part two is built for portfolios: a sampling grid for recording results across districts, and the three questions only a portfolio has.
What standardizing actually buys
The goal is not uniformity for its own sake. It is that a new district onboards into a process that already works, that a staff change does not reset institutional knowledge, and that you can answer a board member's question about compliance with evidence rather than reassurance.
In practice that means a consistent intake route so nothing lives only in an inbox, a redaction method that has been verified rather than assumed, a predictable place where each district's records actually live, a publishing routine that does not depend on one person remembering, and enough of a trail that you could reconstruct any request without relying on memory.
None of that requires new software to begin with. Most of the first pass is configuration and habit in systems you already pay for.
We are a technology consultancy, not a law firm. This article is about process and systems, not about what any particular district is obliged to do. Those questions belong with district counsel.
If you would rather have someone else look
Our public records and Sunshine compliance assessment was built with this case in mind. For a management firm we assess the shared methodology once, then apply it per district at a fraction of the per-district rate, and the remediation plan is written to be executed in bulk rather than one district at a time.
The five questions above cost you an afternoon and no money. Start there.