Reviewed September 7, 2026. Features depend on your enabled modules, permissions, and configured integrations.
Districts
District records carry a name, type, code, and ZIP information for district reporting. The office’s structured jurisdiction is configured separately and determines voter matching and voter-based audience scope.
Review both with the administrator during setup. Selecting or editing a district reporting record does not redefine the office’s jurisdiction or restrict all casework intake to its ZIP list.
Scoped to your turf
District intelligence is bounded by the office's structured jurisdiction: a municipality, a county, a legislative district, or a congressional district, set once at setup. It profiles the area you serve from census and demographic data for that ground, and every count, heatmap, and snapshot on this tab is drawn to that boundary and no wider.
The underlying data reaches far past your border; the tab does not. Even when the source covers the whole state, District only ever surfaces the turf the office actually serves, so the numbers you brief the official with are the ones you are accountable for.
Casework heatmap
Casework volume by ZIP or by category, as horizontal meter rows over a last-N-days window. It shows where the district is hurting before the town hall does, and whether last month's pothole surge was a blip or a trend.
Read it weekly, by category first. A Benefits spike is a policy signal worth a letter to the agency; an Infrastructure spike clustered in one ZIP is a public-works call and a paragraph in the newsletter.
Demographics
A scope summary with total voters, then bucket tables by party and by ZIP with counts and percentages: enough context to brief the official in the car, not a data-science project.
The numbers come from the voter file's district slice and refresh with it; annotations from the campaign side never ride along.
Annual reports
One click generates the year's report as a PDF (cases handled and closed, response times against SLA, events held, meetings taken), with a payload summary on screen before you commit. Prior years stay listed with their generated dates, and each is cached as a point-in-time snapshot of the district, there to reopen, re-send, and quote from, not rebuilt from scratch every time someone asks.
Generate in January, publish in the February newsletter, and keep the PDF in the record. A line like “We closed 154 cases this year” then has the report behind it whenever the office cites it.