CIVISIGHT
The product

Filed once. Reviewed in place. Intelligence built in.

Local governments file once. Agencies review in place. Every accepted filing becomes a trusted data layer for AI-native analysis and report generation.

Two portals, one record
For the agency that receives filings
Intelligent oversight for every filing

See what is due, what is late, and what needs review in one live view.

In the agency portal
Compliance directory565 entities
Submission reviewfield by field
Reminderspolicy + run log
Extensions30 / 60 / 90 days
For the government that files
Fill the real form, not a substitute

Fill the official form online, with live totals, prior-year answers, and questions attached to the field.

In the filing portal
RLGF online form897 fields · 19 pages
Import from Excelprefill from a workbook
FormPilotprior-year values
Every form owedon its own deadline
01 · Filing
The Report of Local Government Finances rendered as an online form, showing tax revenue lines with their UCOA account codes and workbook cell references
The form itself

The whole official form, online

The Report of Local Government Finances is 897 fields across 19 pages, Parts I through XV plus attachments. CiviSight renders every one of them — carrying each line's UCOA account code and its cell reference from the state workbook, so a preparer who knows the paper form knows this one.

Why it matters Nothing is retyped into a second system later. What the county enters is what the agency receives.
A county's task list showing each form it owes, which agency receives it, and the time remaining on each deadline
Everything owed

Every form, on its own clock

Audits, millage rate reports, hotel-motel tax, SPLOST, E-Verify attestation — each one showing which agency receives it and how long is left. Deadlines are computed from the entity's own fiscal year-end, because no two local governments close their books on the same day.

Why it matters Work routes to the department that owns it, and survives the person who used to do it.
A submission returned for correction, with the agency's questions anchored to specific pages and cells of the form
Questions on the line

The question lands on the field it's about

When a reviewer questions a number, the question attaches to that number — Page 1, cell F23, Real Property Taxes — and appears there for whoever opens the form next. Replies stay on the same thread.

Why it matters One round of correction instead of three, and a written record of what was asked and answered.
02 · Review
The agency dashboard for a single form, grouping every local government by deadline with a remind action on each row
The operating picture

One form. Everyone who owes it.

See who has filed, who is late, and who has never filed. Filter by deadline, government type, or status.

Why it matters The list that used to take a week to assemble is the screen you open in the morning.
The submissions queue showing filings grouped by received, under review, accepted, and needs correction
The queue

Received, reviewed, accepted — or sent back

Filings arrive into a queue with four honest states. A reviewer opens one, works through the pages, leaves questions where they belong, and then accepts it or returns it with those questions attached.

Why it matters Review is a workflow with a record, not an inbox someone is working through.
The reminder screen stating the automatic schedule and offering targeted sends to counties still owing a filing
Automation you can audit

Deadlines, extensions, and reminders

Set reminder rules, approve 30, 60, or 90-day extensions, and keep the original statutory deadline visible on every record.

Why it matters “When do counties actually get chased?” has an answer on screen, and a log of every run.
03 · What comes out

Structured in. Usable out.

Accepted filings are immediately comparable across governments and years.

The database explorer listing filings across entities and years, with a UCOA account pulled in as a column and version history on each row
The database

Every filing, in one table

Filter by entity, year, or status. Compare accounts across the state, preserve versions, and export the view as CSV.

Why it matters A question about statewide finances stops being a data project.
A natural-language question about property tax revenue answered as a ranked chart drawn from the filing data
Ask

Ask in English. Check the SQL.

Ask in plain language and get a chart or table from live filing data. Every answer shows its assumptions and the SQL behind it.

Why it matters Analysts get answers in seconds, and can verify them rather than trust them.
A generated Financial Highlights edition for fiscal year 2024, computed from filed reports, with print and DOCX export
The statutory report

The annual report, computed from the filings

Generate the annual report from accepted filings, then scope, review, print, or export the edition to DOCX.

Why it matters The report that took a season becomes a scoping decision and a download.
Underneath all of it

Built to be the record, not a copy of it.

Every answer should hold up months later, with its source intact.

Versioned, not overwritten

A correction creates a new version of the filing. The one originally submitted stays exactly as it was filed.

Traceable to the cell

Every value keeps the page and cell it came from, and the workbook it arrived in stays downloadable.

Decisions are events

Requests, approvals, denials and review outcomes are written to an audit trail as they happen.

The detail that matters Original deadlines stay visible beside approved extensions, so the record remains clear years later.

See the workflow in practice.

Follow a statewide report from filing to analysis.

Read the case study →