FOIA / PUBLIC RECORDS / OPEN MEETINGS
The AI-native transparency platform for government.
Govflo runs public records requests and open meetings from intake through to release. One platform for federal FOIA, state public records law and local ordinances, configured to the statute that governs each request.
30 minutes. We load your statute and walk one of your own requests from intake through to release.
Buy on existing state price agreements
Fully managed in the cloud
Intelligence built from your own decisions
Federal, state and local
Why Govflo exists
Being late is a violation. Missing a record is worse.
The real risk in a public records request is not answering slowly. It is missing a responsive record and finding out later, in court. Govflo is built for that moment. Every document is considered, every redaction has a reason, and every action is logged. The tools agencies use today have been on the market for over a decade, and none of them were built AI-native. That is the gap Govflo was built to close.
Today
With Govflo
Today
A responsive record is missed, and surfaces later in court.
With Govflo
One sweep across every mailbox, cloud storage and body-worn camera footage.
Today
The redaction covers the text without removing it.
With Govflo
The content is removed from the file, so there is nothing left to recover.
Today
You learn a request is late after the deadline has passed.
With Govflo
Every request shows on track, at risk, overdue or met, against both clocks.
Today
What you withheld is challenged, and the reasoning is reconstructed afterwards.
With Govflo
An append-only log of every action, with the actor, the time and the IP address.
Platform
Public records, from intake to release.
Public records work is the core of Govflo today. It is where most agencies start and where the deepest tooling lives.
Every request is tagged to the law that governs it: federal FOIA, a state public records law, or a local ordinance. Govflo tracks all three separately.
Every request is tagged to the law that governs it: federal FOIA, a state public records law, or a local ordinance. Govflo tracks all three separately.
How Govflo works
Govflo proposes. Your team decides. AI-powered. Human-controlled.
Six stages from intake to release. Govflo drafts the plan, gathers the records and proposes the redactions. Your custodian signs off before anything leaves.
01
Intake
Tagged to the law that governs it.
02
Case plan
Built from your agency's precedent.
Govflo AI
03
Collection
Gathered from your mailboxes and systems.
Govflo AI
04
Redaction
Drafted, with the exemption cited.
Govflo AI
05
Sign-off
Your custodian reviews and approves.
Custodian
06
Release
The package goes out, trail assembled.
Every stage builds the compliance trail
Roles
One request, four desks.
A single request does not stay in one pair of hands. Govflo gives each desk the view it needs and nothing it does not.
Ask once, then watch it move.
Most of what a records office answers is someone asking where their request stands. The portal answers it for them.
What they get
File through the portal, with or without an account
A reference number and a tracking link on submission
Check the status of a request without contacting the office
Released records delivered as a package, with an expiry date you set
The queue, the clock and the reason in one place.
This is the desk that carries the work. Every request sits in one queue, each one measured against the statutory profile for the law that governs it.
What they get
Two clocks on every request, first response and resolution, running from the moment it arrived
A time ledger showing every period each clock has run or paused
Redaction proposals to work through, accepting what is right and rejecting what is not
Body-worn camera footage transcribed, with the relevant sections flagged
The person who did the work is not the person who signs it off.
In a dispute, who authorized a release needs an answer separate from who performed it. That is what the approver role is for.
What they get
Approve, reject, request changes or leave pending, all of it on the record
Often no permission to work a request at all, only to decide on one
Which withholdings need a second person is set per redaction rule
A document that fails verification will not release, and no setting turns that off
Set the rules once, then let them run.
The statutory profile, business hours, the approval workflows and the portal are configured once and read by every request afterwards.
What they get
The statutory profile every deadline is measured against
Working hours, holidays and the time zone behind every business-day count
Which statuses run the clock and which pause it
The agency-wide audit log, filterable by actor, action and date
Discovery
Find everything that is responsive.
Responsive records are scattered across systems no single person can search. Govflo reaches all of them.
Email sweep
Microsoft e-discovery across thousands of mailboxes.
Cloud storage
Native SharePoint and other cloud storage.
Texts and voicemail
Wherever your provider grants API access.
Paper binders
Scanned in, handled like any other document.
Media
Audio and video pulled in as records, not handled outside the request.
Redactions
Redactions you can defend.
A redaction is only as good as the reason behind it, and the reason has to survive being questioned.
Cited from precedent
Proposed from your own knowledge base, citing prior decisions.
Human sign-off
Never applied on its own; a custodian reviews and signs.
Locked once applied
Cannot be removed from the released document.
Fact vs opinion
Tag the distinction that decides what you can withhold.
Video and audio
Blur faces and mute audio in body-worn camera footage.
What backs a proposal
The Precedent Library.
When Govflo proposes a redaction, the reason comes with it. Each proposal cites the prior decisions it was drawn from, so a reviewer can see what the office has already done on the same question.
Your own decisions build the library. Every redaction your team approves and every exemption you cite adds to it. The knowledge that usually sits with one experienced officer becomes something the whole office can draw on.
A person still decides. The library shows what the office decided last time. It does not decide this one.
Your own decisions build the library. Every redaction your team approves and every exemption you cite adds to it. The knowledge that usually sits with one experienced officer becomes something the whole office can draw on.
A person still decides. The library shows what the office decided last time. It does not decide this one.
What backs a proposal
Home address, page 4
Personally identifiable information
Cited from
REQ-2026-0118
REQ-2026-0118 Same address withheld on a related request, approved 12 March
REQ-2025-0904
Complainant details withheld in full, approved 4 November
Reviewed and approved by a person before anything is applied.
Consistent
The same question answered the same way, request after request.
Explainable
A reviewer sees the reasoning without having to ask anyone.
Institutional
Never shared with another agency, never used to train a shared model.
Audit
A record that holds up in court.
When someone challenges what you withheld, the answer should already be assembled.
Reproducible searches
Every search captured as an immutable record, replayable for a judge.
Chain of custody
Hash-stamped intake and a per-access custody log.
Full activity log
Every document touched is logged, with who and why.
Version history
Across every linked request.
Open Meetings
Open meetings, handled the same way.
Agendas, notices, minutes and the posting deadline attached to each, running on the same connected and audited system as public records.
Agendas and notices
Agendas and public notices with the posting deadline attached to each.
Minutes
Minutes drafted against the agenda and the record they refer to.
Shared audit trail
The same audit trail and access controls used for public records.
What sits underneath
The statutory profile.
Every request is measured against the statutory profile for the law that governs it. Each profile starts from a jurisdiction baseline, not a blank form, and your agency edits it to fit. Govflo is not a single-state product: New Mexico was first, and others follow.
SLA policies · Statutory profile
Federal FOIA
5 U.S.C. § 552
Started from the jurisdiction baseline, then edited by your agency.
1
Governing law
Federal FOIA
2
Initial response
20
business days
3
Determination and fulfillment
Promptly after determination
4
Extensions
10
business days
5
Business hours
Mon to Fri, 09:00 to 17:00
ET
6
Paused statuses
Awaiting clarification, awaiting fees
7
Applies to
New requests only
A baseline reference for your jurisdiction, not legal advice. Your counsel verifies it before go-live.
New Mexico IPRA
NMSA 1978 § 14-2-8
Started from the jurisdiction baseline, then edited by your agency.
1
Governing law
New Mexico IPRA
2
Initial response
3
business days
3
Determination and fulfillment
15
calendar days
4
Extensions
Only if burdensome or broad
5
Business hours
Mon to Fri, 08:00 to 17:00
MST
6
Paused statuses
Awaiting requester, awaiting payment
7
Applies to
New requests only
A baseline reference for your jurisdiction, not legal advice. Your counsel verifies it before go-live.
How each one is set
1
Governing law
Tagged per request. Federal FOIA, a state public records law and a local ordinance each carry their own profile.
2
Initial response
The first clock. How long you have to get back to the requester at all.
3
Determination and fulfillment
The second clock. Each window carries its own unit, and the two do not have to match.
4
Extensions
Allowed only where your statute permits the deadline to be extended, and only on the notice it requires.
5
Business hours
Working hours, holidays and time zone. Every business-day count reads from here, so set it before anything else.
6
Paused statuses
Each status either runs the clock or pauses it. The agency default never pauses.
7
Applies to
Changing a window never touches requests already open. They keep the rules that applied when they arrived.
What it drives
The due date
The calendar date, the one the requester is told.
Time used
A stopwatch that counts only while the clock runs.
The queue
On track, at risk, overdue or met, at a glance.
Reminders
Escalation before a window closes, not after.
Defensibility and trust
Made to withstand scrutiny.
The questions that decide a records case are the ones you get asked afterwards.
Every proposal is a suggestion, never a decision.
Govflo reads every document and proposes what should be withheld before anyone opens it. Each proposal cites the prior decisions behind it, drawn from your agency's own knowledge base. The reasoning arrives with the suggestion, instead of being reconstructed months later.
It is still a suggestion. Nothing is withheld or released on the strength of a proposal alone. A reviewer accepts what is right and rejects what is not, and a rejected proposal is recorded as rejected rather than quietly dropped.
That split is deliberate. Whether an exemption applies to a particular record is a legal judgment. It stays with the person who is accountable for it. Govflo makes that judgment quicker to reach and easier to defend. The record shows what was proposed, what was decided, and who decided it.
It is still a suggestion. Nothing is withheld or released on the strength of a proposal alone. A reviewer accepts what is right and rejects what is not, and a rejected proposal is recorded as rejected rather than quietly dropped.
That split is deliberate. Whether an exemption applies to a particular record is a legal judgment. It stays with the person who is accountable for it. Govflo makes that judgment quicker to reach and easier to defend. The record shows what was proposed, what was decided, and who decided it.
Nothing releases that cannot be verified.
When a redaction session finishes, the released file is examined again for anything that should have been withheld and was not. That check does not trust the editor's record of what you applied. It reads the output.
If the file comes back clean it can move toward release. If it does not, it stops and waits for a person.
There is no setting that turns this off. Govflo is built to defer to a person rather than release material it cannot verify.
If the file comes back clean it can move toward release. If it does not, it stops and waits for a person.
There is no setting that turns this off. Govflo is built to defer to a person rather than release material it cannot verify.
Your agency's intelligence, not everyone's
Every redaction your team approves, every exemption you cite, every call you make on a close question teaches Govflo how your agency works. The institutional knowledge that usually sits with one experienced custodian becomes something your whole team can draw on.
It stays yours. It is never shared with another agency and never used to train a shared model.
It stays yours. It is never shared with another agency and never used to train a shared model.
Where your data lives
Govflo runs in the cloud, so there is no server for your team to stand up, patch or maintain. Your agency's data stays isolated to your own tenant.
No data is retained by the language model and nothing is fed back into training.
No data is retained by the language model and nothing is fed back into training.
Who can see what
Role-based access and full audit logging throughout. Viewing an unredacted original can require two authorized people together, and every access is written to an immutable log.
Talk to us
See it running on your statute.
Tell us about your agency and we will set up a working session with Govflo configured to your statute.
support@govflo.ai
A Dataflo product
New Mexico, USA
Oops! Something went wrong while submitting the form.