Resources / Records, Audits & Public Accountability / Public records requests

What do you actually have to produce when a public records request asks for your internal approval records?

The short answer

A public records request for approval records usually asks for more than the final decision. It asks for the sequence: who reviewed a document, in what order, and when each step happened. When that sequence exists as a byproduct of how the approval was routed in the first place, answering the request means pulling an existing record rather than reconstructing one from memory and old emails. Without it, someone spends hours rebuilding a timeline that should have already existed. The record has to exist before anyone asks for it, not get assembled once they do.

On this page

Why the existing system does not cover it How districts handle it now Where it goes wrong

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

Why the existing system does not cover it

Most approval systems store the outcome, an approved requisition or a signed form, without preserving the process that produced it. A records request that asks how something moved, not just what was decided, is asking for information that often was never captured as a retrievable record at all. It lived in email threads, verbal check-ins, or whoever happened to remember how that particular approval went.

Even a request that's simple in principle, every instance of one form from a given period, runs into the same problem from a different angle. The forms aren't in one place. They're scattered across shared drives, individual staff email accounts, and whatever the district was using before, which means finding all of them is its own task before anyone even gets to reading them.

How districts handle it now

When a request like this lands, staff typically start from scratch: searching email for the relevant thread, checking with whoever handled the approval if they're still there, and piecing together a timeline by hand. What should be a quick pull turns into hours of reconstruction, because the sequence was never captured as its own record in the first place.

A simple request has its own version of the same problem: someone has to know which staff member, which folder, which year, and go collect the files one at a time.

Where it goes wrong

These requests aren't isolated anymore. Districts report seeing them more often, and not always from someone local, alongside the routine ones from parents, staff, or local reporters. A district that can turn one around in minutes instead of hours isn't just saving staff time. It's answering, quickly and completely, exactly when someone is looking closely.

What doing it well actually requires

Producing a defensible answer means the sequence already exists: who reviewed a document, in what order, and when each step happened, captured automatically as the approval moves rather than reconstructed afterward. A district should be able to open one submission and see exactly where it stands, and pull the full history behind it on demand.

Not every request needs that depth, though. Sometimes the request is simply for the records themselves, every instance of a specific form from a given period, and the answer is just as direct: filter to what's being asked for and download it, without needing to reconstruct anything.

Common questions

Questions we hear from every district office.

Does this apply to requests from parents and staff, or only outside requesters?

It applies the same way regardless of who's asking. The record exists whether the requester is a parent, a staff member, a local reporter, or someone with no connection to the district at all.

Can a request be answered with a partial pull, or does it always mean exporting everything?

A request can be answered at whatever scope it asks for, one submission's history, every instance of one form from a specific period, or a broader export across multiple form types. Nothing forces an all-or-nothing pull.

What about records from before Flow Forms was in place?

Those records live wherever they always did, paper files, email, or whatever system was in use at the time. Flow Forms captures what moves through it going forward. It doesn't reconstruct history from before a district started using it.

Is this the same record a district would produce if a signature or approval were challenged rather than publicly requested?

Yes. The underlying record, who reviewed something, in what order, and when, doesn't change based on why someone is asking for it. A public records request and an internal dispute draw on the same history.

Does answering a request always mean pulling the full approval history, or can you just hand over the documents themselves?

Most requests are the second kind. When someone wants the documents themselves rather than the process behind them, the answer is a straightforward filter and download, no history to pull or explain.

How Flow Forms handles it

Flow Forms captures the sequence automatically as an approval moves: who reviewed it, in what order, and when. That record is available at whatever scope a request calls for, a single submission's full history, or a batch export of every instance of a form from a given period. One district was expecting a records request to take hours of staff time. It took fifteen minutes.

See how it would work for your district →