Agency access, scoped
Role-based access and tenant isolation are foundational requirements.
Replace scattered emails and spreadsheets with one workspace for public records requests, department assignments, deadlines, and responses.
Public records request
Permits, inspection reports, and related correspondence.
The problem · 02
A shared inbox. Three departments. Another spreadsheet. Keeping a request moving shouldn’t mean reconstructing its story every morning.
The foundation · 03
Records work carries real responsibility. Clear access boundaries and accountable decisions are part of how we’re building the product.
Illustrative activity, never real requester data.
Clear boundaries
Residents get their request’s progress. Staff get an authorized workspace for the work behind it.
Role-based access and tenant isolation are foundational requirements.
Source records, working copies, and release versions have distinct purposes.
Human review and deliberate release decisions stay central to the workflow.
The workflow · 04
The planned end-to-end workflow keeps the request, records, decisions, and people connected.
A clear place for residents to ask for the records they need.
A case owner and a clear next step for each department.
Records, redactions, and decisions with their context intact.
The approved versions, for the intended audience.
A traceable history of the work and the response.
A better start for residents
Residents don’t need to learn your organization chart. They need a simple way to ask and a clear way to follow along.
No account required to submit a request.
A few things to know
FetchCivic is being designed for U.S. municipalities, counties, school districts, and public agencies—especially clerks and records officers coordinating requests across departments. The initial focus is teams handling roughly 100 to 5,000 requests a year.
FetchCivic is in development. The examples on this page illustrate the intended experience using sample data; they are not a live product. We’re starting conversations with agencies to understand their workflows and discuss potential pilots.
We’d start by understanding your current process, departments, request volume, and review needs. Together, we’d identify a manageable set of scenarios to test. Scope, timing, configuration, and any migration would be agreed before a pilot begins.
Agency-specific deadlines, fees, exemptions, and retention rules are part of the planned product. Microsoft 365 and Google Workspace are integration priorities. Availability and support for your agency’s requirements will need to be confirmed as the product develops.
The planned foundations include role-based access, tenant isolation, encryption, protected audit history, and controlled download links. These are design requirements, not claims of implemented or independently verified controls. FetchCivic does not currently hold security certifications.
The next step · 05
Tell us where requests get stuck. Help shape a workspace that fits your agency.
Prepare for a pilot conversation