The agenda-management software market was built for cities of half a million. Granicus, Legistar, NovusAGENDA, CivicPlus — the feature lists are designed around legislative analysts, parliamentary procedure consultants, and full-time clerks with assistant clerks who back them up.
If you’re running a city of 12,000, this is not your reality. Your clerk is also your HR, your records officer, and the person who unlocks the council chambers. Your “agenda team” is one person. Your IT support is a fractional contract.
So when you evaluate software, the right question isn’t “does it have feature X?” It’s “will my clerk actually use feature X, or will it sit unused while she keeps doing it the old way?”
What actually matters
After watching dozens of small-city agenda workflows, the same five things come up. Everything else is decoration.
1. Agenda assembly that survives last-minute changes
Every clerk’s nightmare: it’s 4:00 PM Friday, the city manager just emailed two new items, two existing items got pulled, the staff report on item 7 is wrong, and the agenda has to be posted by 6:00. Software that requires you to rebuild the document from scratch is software you will work around.
What you need: drag-and-drop reordering, item-level updates that don’t require regenerating the entire packet, and a one-click publish that updates the website, the PDF, and the public portal in one shot.
2. A public-facing portal you don’t have to maintain
The Brown Act and AB 2257 both require posting on a “directly accessible” web page. If your software publishes an agenda but doesn’t put it on a public page, the clerk is now also a webmaster. Watch what happens: the agenda goes up on the software side, the clerk forgets to update the city website, and the citation chain for compliance has a gap.
Modern platforms solve this with a portal at portal.yourcity.gov or yourcity.civicca.com that updates automatically. The clerk publishes once; the public sees it everywhere.
3. Public comment management
This is the feature that small cities chronically underestimate. You think you don’t need a speaker queue because you only get three speakers per meeting. Then a controversial item comes along, 40 people show up, and your clerk is hand-managing index cards while the mayor is asking who’s next.
You need: online speaker registration, a queue that displays on the dais, time tracking per speaker, and the ability to handle eComments (written comments that have to be entered into the record).
4. Minutes that don’t take three days to produce
Most small-city clerks lose a full day per meeting writing minutes. Modern platforms generate first-draft minutes from the recording — not perfect, but starting from a 70%-correct draft beats starting from a blank page.
The test: does the software actually produce something useful, or does it produce a transcript that’s harder to edit than starting fresh? Demo this with your real meeting audio. Don’t accept canned demos.
5. Compliance built into the workflow
Brown Act, SB 707, agenda-description adequacy, closed-session citations, public-comment placement — these are the things that get cities sued. A platform that flags compliance issues before publish is worth more than one that has a separate “compliance dashboard” nobody opens.
What doesn’t matter (despite what the demo says)
Most enterprise features are noise for cities under 50K:
- Custom workflow builders. You have one workflow. The clerk drafts; the city manager reviews; the mayor approves; it gets posted. Configurable workflow engines are an enterprise feature for legislative bodies that don’t exist at your scale.
- Departmental hierarchies. Your “departments” are a planning commission and a parks committee. You don’t need a 5-level org tree.
- Legislative tracking with full version history of every line edit. You aren’t a state legislature. You don’t need diff views of motion language across drafts.
- API integrations with 14 third-party systems. Your “ecosystem” is a Word doc, a PDF, and an email. Keep it that way.
The price test
If you’re paying $20K–$40K/year for software that does a smaller city’s job badly, that’s a sign the market sold you something built for someone else. Modern platforms targeting small cities run $1K–$5K/year and do the work better, because they’re designed for the workflow you actually have.
The math is rarely about the software. It’s about clerk time. A platform that saves the clerk 6 hours per meeting cycle — minutes auto-drafted, posting automated, public comment managed — is paying back several thousand dollars a month even before the licensing comparison.
What to ask in the demo
Not “does it have feature X.” Instead:
- Show me what happens when I add an item 30 minutes before publishing.
- Show me what my public website looks like the moment I publish.
- Show me a meeting that ran two hours, then show me the first-draft minutes.
- Show me what happens when my clerk types a vague description like “personnel matters.”
- Show me the bill at the end of year one.
Vendors that built for big cities will struggle with the first four. Vendors that built for cities like yours won’t.