Resources / Records, Audits & Public Accountability / Audit landscape

What actually gets audited in a school district or public agency?

The short answer

A school district or public agency can face several different kinds of scrutiny in the same year: an annual financial audit, a state or federal program review tied to a specific funding source, a public records request, or an internal question about a specific decision. Each one is usually owned by a different person in the office, so nobody typically has the whole landscape in view at once. The risk shows up when two of them land close together, or when the person who owned one of them leaves and nobody else knows what it required. Doing it well means recognizing that every one of these, regardless of category, is asking the same underlying question: who did this, when, and what happened.

On this page

Why no one person usually sees the whole landscape The four kinds of scrutiny that actually show up What all of them are actually asking for

What doing it well actually requires Common questions How Flow Forms handles it

Why no one person usually sees the whole landscape

In most offices, each kind of scrutiny has its own owner. The business manager handles the annual financial audit. A program coordinator handles a state or federal program review. Whoever answers the phone that day handles a public records request. Because each one is rare enough on its own, nobody ends up mapping them side by side, and each person tends to assume their version is what "an audit" actually means.

The four kinds of scrutiny that actually show up

Four kinds of scrutiny actually show up, and they behave differently. The annual financial audit is the one everyone already expects: a full review of the district or agency's finances, on a set schedule, with plenty of notice. A state or federal program review is different. It's tied to a specific funding source, like special education or a career and technical education grant, and it runs on the funding agency's cycle, not the office's own calendar. A public records request can arrive with no warning at all, from anyone, about anything the office has on file. An internal question, someone asking who approved a specific decision, sometimes surfaces months after the decision was made, and often without warning either.

What all of them are actually asking for

Despite looking different on the surface, every one of these is asking some version of the same question: who did this, when, and what happened as a result. A financial audit wants proof a purchase was approved by the right person before it happened. A program review wants proof a required step, a signature, a notification, a deadline, actually happened on time. A records request wants the actual decision trail, not just the final outcome. An internal question wants to know who's accountable. The specific paperwork differs from one to the next. The underlying ask does not.

What doing it well actually requires

Because the underlying ask is the same across all four, readiness for one is largely readiness for the rest.

The record exists before any of them ask

Every step routed through Flow Forms is captured automatically, by default, as a byproduct of the approval itself moving through the system. Nobody has to remember to start tracking once a specific audit or request is announced, because the record was already being built before anyone asked.

It names who, not just what

The record carries the person who took the action and the exact time, to the minute, that they took it. That's true whether the eventual question comes from a financial auditor, a program reviewer, a records custodian, or someone inside the office.

It can be pulled for whichever one shows up

Whichever kind of scrutiny actually arrives, the same history can be exported as a batch file. The office doesn't need one process for a financial audit and a different one for a records request. It needs the record to already exist, and a way to hand it over.

Common questions

Questions we hear from every office juggling more than one of these at once.

Does a public records request count as an audit?

Not formally, but it asks for the same kind of proof an audit would: a specific decision, and evidence of who made it and when. Treating it with that same seriousness, rather than as a one-off inconvenience, is usually the difference between answering it in an afternoon and spending a week digging.

Who in the office is actually responsible for being ready for all of these?

In most offices, nobody, because each one is typically owned by whoever happens to handle that particular funding source or that particular request. That's less a staffing problem than a records problem: readiness depends less on one person owning it and more on whether the underlying documentation already exists before anyone asks.

Does each kind of scrutiny need its own separate process to prepare for?

Not if the underlying record already exists the same way for every approval, regardless of which kind of scrutiny eventually asks for it. The preparation converges on one consistent record, not four different ones.

How Flow Forms handles it

Every approval routed through Flow Forms carries the same record regardless of which kind of scrutiny eventually asks for it: who took the action, when, and what happened. That record already exists before a financial audit, a program review, a records request, or an internal question ever arrives, and it can be pulled the same way no matter which one shows up.

See how it would work for your office →