The information was always public. Now it's actually usable.
Most residents don't know how to file, what they're entitled to, or how long it takes. It's all published.
The RTK process is opaque
Most residents don't know how to file a right-to-know request, what information they're entitled to, what exemptions apply, or how long the municipality has to respond. This creates unnecessary barriers to public information that's supposed to be accessible.
Staff fields procedural questions before requests are even filed
A significant share of RTK-related staff time goes to explaining the process rather than processing actual requests. How do I file? What can I request? How long will it take? These have published answers that most residents simply can't find.
Requesters give up before completing
When the process feels complicated or unclear, residents abandon their requests. Information that should be public stays effectively inaccessible. Clear process guidance keeps requests moving and access real.
From RTK policy to plain-language guidance.
GovToKnow lives on your existing website. Residents get process guidance without calling your office. Staff handles actual requests, not procedural questions.
We load your published RTK policy and procedures
Right-to-know policies, response timelines, exemption categories, fee schedules, appeal procedures: we import every public-facing document that governs your RTK process.
Residents ask in plain language
No policy document to navigate. No statute to decode. A resident types a question on your city's website and gets clear guidance in seconds.
Every answer cites its source
Responses link directly to the policy section or procedure they came from. Residents can verify. Staff can trust. Nothing is interpreted beyond what's published.
Not a records portal. A records guide.
This is what your Open Records Officer and solicitor will ask about. Here's the direct answer.
Document layer only
GovToKnow reads from your published RTK policy and procedures only. No connection to your records management system or case files.
US-based infrastructure
All data lives on AWS servers in the United States. Nothing leaves domestic borders.
No AI training on your data
Your documents and resident queries are never used to train AI models. Not ours, not anyone else's.
Give your Open Records Officer their time back.
Open Records Officers spend a meaningful portion of their week fielding questions about the RTK process itself: how to file, what can be requested, how long it takes, how to appeal. These answers are in your published policy.
When GovToKnow handles those procedural questions from your published RTK policy, it absorbs the pre-request inquiries, freeing your Open Records Officer to focus on actually processing requests, applying exemptions, and handling appeals that require professional judgment.