Most cities that run CivicPlus products did not set out to buy a suite. They bought a website, later added an agenda module, and perhaps picked up a resident request tool or a code publishing service along the way. Years later, the vendor relationship touches several departments, several budgets and several renewal dates. That is not a problem in itself. One relationship can simplify support, billing and training. But when a renewal notice arrives, a key staff member leaves, or the clerk's office has a rough run of meeting cycles, the question of what else is out there gets complicated quickly.
This guide is for clerks, managers, IT staff and council support staff at cities that use one or more CivicPlus products and want a clear view of their options for agenda and meeting management. Staying with your current system may turn out to be the right answer, and you should go into the review open to that. The goal here is to help you decide on criteria that matter to a public body, understand the tradeoffs between a bundled suite and separate tools, protect your website and your public record during any change, and ask contract questions before you need the answers.
A caution that applies throughout: product names, editions and ownership in this market change through acquisitions and rebranding. Treat anything here about a specific company as a starting point to confirm in a demo and in writing.
Start with an inventory of what you actually run
Before you look at alternatives, write down exactly what you have. Many cities discover during this step that nobody holds the full picture. The website contract sits with communications or IT, the agenda contract sits with the clerk, and a third product was purchased by a department that has since reorganized.
For each CivicPlus product, or any related product from another vendor, record the following:
| Item to record | Why it matters | Who usually knows |
|---|---|---|
| Product and edition name | Names change; you need the exact one in your contract | Contract file, vendor account manager |
| Contract start, end and renewal terms | Notice periods and auto-renewal clauses drive your timeline | Purchasing, city attorney |
| Whether it is part of a bundle | Removing one product may change terms on others | Purchasing, finance |
| What data it holds | Agendas, minutes, video, votes, attachments, subscriber lists | Clerk, IT |
| What links to it | Website pages, ordinances, emails, social posts, other systems | Communications, IT |
| Who uses it and how often | Department submitters, council, public | Clerk, department heads |
| Known pain points | Documented problems are your starting requirements | Clerk's office, staff surveys |
Be concrete about pain points. "The system is clunky" will not help you compare vendors. "Department staff submit items by email because the intake form does not fit how they work, so the clerk retypes them" will. So will "we cannot find which meeting a prior council direction came from without reading old minutes page by page." Each specific problem becomes a question you can put to every vendor, including the one you already have.
What CivicPlus is publicly known for
CivicPlus is a US government technology company widely known for municipal and county website platforms. Over time, partly through acquisitions, its portfolio has grown to include agenda and meeting management, resident request and engagement tools, recreation management, mass notification, code publishing and other products. Its agenda and meeting line has been marketed under the CivicClerk name in recent years, but confirm the current product name and edition for your city, since naming in this market shifts.
That breadth is the main reason this review is different from switching a single standalone product. A city on CivicPlus may be weighing an agenda change while its website, its public notification list and its online code all sit with the same vendor. Each of those connections is worth understanding before you move anything.
Questions to ask CivicPlus first
Your current vendor deserves a fair chance to answer the same questions as anyone else. Ask in writing:
- Is the product, edition and hosting arrangement in the renewal the same as what you run today?
- Are any of your products being retired, merged or moved to a new platform, and on what timeline?
- If you change one product, how do the terms, discounts or support levels on your other products change?
- What does the vendor propose for each documented pain point, and will it commit to that in writing?
- What would a transition look like if you replaced one product but kept the others?
None of this is adversarial. Any vendor that has grown through acquisitions may run several overlapping products, and asking where yours fits is ordinary due diligence. A clear, written answer also gives your council something solid if they later ask why you stayed or why you moved.
Bundled suites versus best-of-breed tools
The central structural choice in this review is whether to keep most of your civic technology with one vendor or to assemble separate tools that each do one job well. Neither approach is right for every city.
A bundled suite is a set of products from one vendor, often sold together and supported through one account. Several large vendors in local government offer suites that cover websites, agendas, video, notifications and more.
A best-of-breed approach picks the strongest available tool for each function, such as one product for the website, another for meeting management, another for records, and connects them where needed.
Many cities end up with a hybrid: one vendor for the website and public-facing pieces, and a specialist for the work behind the agenda.
How the two approaches compare
| Consideration | Bundled suite | Best-of-breed |
|---|---|---|
| Contracts and billing | Fewer contracts, one account manager | More contracts to track and renew |
| Support | One number to call, though different products may have different support teams | Clear ownership per tool, but problems between tools need coordination |
| Integration | Often built in, but confirm how deep it goes | Depends on each vendor's export, embed and connection options |
| Fit for each function | Some modules may be stronger than others | You can choose the best fit for each job |
| Switching later | Changing one piece can affect bundle terms | Easier to replace one tool without touching others |
| Staff training | One login and style may help adoption | More systems to learn, unless they share sign-on |
| Vendor dependence | Higher concentration with one company | Spread across several companies |
Questions that cut through the comparison
- Is the suite actually one platform? Products acquired from different companies may share a brand but run on separate systems with separate logins and databases. Ask how the agenda product shares data with the website product today, not on a roadmap.
- Which function matters most to your city? If agenda preparation is where your staff loses the most time, the strength of that module matters more than how neatly it fits the bundle.
- What is your capacity to manage vendors? A small clerk's office with no dedicated IT support may reasonably value one relationship over a slightly better tool. A larger city with IT staff may be comfortable connecting several.
- What happens to the bundle if you leave one part? Get the answer in writing before you start talking to other vendors seriously.
The honest answer for many cities is that the suite is fine for some functions and a poor fit for others. That is an argument for a hybrid, not necessarily for a full switch.
The website question: integration without breaking the public record
For a CivicPlus city, the website is often the hardest part of any agenda change, because residents, reporters and other agencies reach your agendas and minutes through it. Whatever you decide about meeting software, the public path to your records has to keep working.
Where public meeting materials live today
Map this before you change anything:
- Does your website host agendas and minutes directly, link to a separate agenda portal, or embed one?
- Where does meeting video live, and how is it connected to agenda items?
- Do residents subscribe to agenda notices, and which system holds that subscriber list?
- What URLs do your ordinances, resolutions, staff reports, press releases and outside websites use to point to past agendas and minutes?
The last item is the one cities most often underestimate. Old links live in places you do not control: county websites, newspaper archives, regional planning documents, and your own adopted resolutions. If a switch breaks those links, people will reasonably conclude your records are gone, even if they are safely stored somewhere new.
If you keep the website and change the agenda system
- Ask your website vendor what it supports for linking to or embedding a third-party agenda portal.
- Ask the new agenda vendor exactly how it publishes public materials: its own public portal, an embeddable page, a data feed, or posted files.
- Decide where historical agendas and minutes will live after the switch, and whether old URLs can be redirected.
- Test site search. Residents who search your website for a topic should still find relevant meeting materials.
- Confirm who updates the agenda page each meeting cycle and how many steps it takes.
If you change the website and keep the agenda system
The same questions apply in reverse. Confirm that your agenda system can publish into the new website's structure, and that video and subscriber notices still connect.
Accessibility and notice requirements
Public meeting materials posted online have to meet accessibility requirements, and federal requirements for state and local government websites have been updated in recent years. Ask every vendor how its published agendas, packets and minutes meet current accessibility standards, including attachments that departments upload as PDFs. Ask your city attorney to confirm what applies to you and by when.
Posting requirements for public meeting notices also vary by state. Some states require posting at a physical location, some allow or require posting online, and timing rules differ. Your software has to support your state's rules, not a generic version. Confirm the requirements with your city attorney or your state clerk association, then check each vendor against them.
Contract, renewal and exit questions
The best time to negotiate your exit is before you sign. The second best time is now, while you are still under contract and have options.
Before your renewal date
- Notice period: Many government software contracts renew automatically unless you give notice by a set date. Find that date and put it on the calendar of at least two people.
- Term length: Longer terms may come with better pricing but less flexibility. Weigh that against how confident you are in the product's direction.
- Escalation terms: Read how renewal pricing is calculated and whether there is a cap.
- Bundle dependencies: Confirm whether discounts or terms on one product depend on keeping another.
- Procurement path: Whether you can renew, use a cooperative purchasing contract, or must go out for proposals depends on state law, local policy and contract size. Confirm with your purchasing officer and city attorney early, so your evaluation fits the process you will actually use.
Data ownership and export
Your agendas, minutes, votes and attachments are public records. The contract should say clearly that the city owns them. Beyond ownership, ask:
- What formats does the export use, and can another system read them without custom work?
- Does the export include metadata such as meeting body, meeting date, item number, item title, attachments, votes and the link between video and agenda items?
- How long does an export take, and is there a fee?
- Can you run a test export now, while you are still a customer?
- Will the vendor keep a read-only public archive available for a period after the contract ends?
- How will the vendor certify deletion of city data once the transition is complete?
A test export is one of the most useful steps in the whole review. It shows you, in concrete terms, what moving would involve, and it costs nothing to ask for.
Records retention does not change with the vendor
Your records retention schedule applies no matter which system holds the records. Before you migrate, confirm with your records manager which meeting records are permanent, which have set retention periods, and whether any are subject to legal holds or open public records requests. Nothing should be deleted from the old system until the migrated copy is verified and the retention requirements are satisfied.
Exit checklist
- Notice deadline identified and calendared
- Bundle dependencies confirmed in writing
- Procurement path confirmed with purchasing and the city attorney
- Data ownership language reviewed
- Test export requested and reviewed
- Metadata included in export confirmed
- Read-only archive period agreed
- URL redirect plan in place for historical links
- Subscriber list export confirmed
- Retention and legal hold review completed
- Deletion certification process agreed
Evaluation criteria for a public body
Feature lists from vendors tend to look alike. A shorter list of criteria grounded in how a city actually works will separate options more clearly. Use the table below as a starting point and adjust it to your inventory and pain points.
| Criterion | What to ask | Good evidence |
|---|---|---|
| Item intake and routing | How do departments submit items, and how are reviews and approvals tracked? | A live walkthrough using one of your real item types |
| Packet preparation | How are staff reports and attachments assembled, and what catches missing pieces? | Demonstration of a packet with a missing attachment or approval |
| Public publishing | How do agendas, packets and minutes reach the public, and in what formats? | Published sample pages you can test for accessibility and search |
| Meeting day | How are votes, motions, attendance and minutes recorded? | A mock meeting run by your clerk, not the vendor |
| Archive and search | Can staff and residents find past items, votes and directions by topic? | A search for a real past issue in your migrated sample data |
| Security and data separation | How is your city's data separated from other customers, and what is logged? | Written answers and any security documentation the vendor provides |
| Integration | How does it connect to your website, video, records system and sign-on? | A test of the actual connection you would use |
| Implementation and support | Who does the migration, training and ongoing support, and how fast? | Named implementation plan and reference calls |
| Exit and portability | What leaves with you if you go? | A test export and written contract language |
Weighting the criteria
Not every criterion deserves equal weight. A city with a small clerk's office and a heavy load of commissions may care most about intake and packet preparation. A city with frequent public records requests about past council actions may care most about archive and search. Decide the weights before demos begin, and write them down. That keeps the evaluation from drifting toward whichever vendor gave the most polished presentation.
Security questions that belong in every evaluation
Meeting software holds closed session materials, draft documents and personal information about residents who comment or apply for boards. Ask each vendor:
- How is our data separated from other customers' data?
- Which actions are logged, and can we see the logs?
- How are user accounts managed when staff or council members leave?
- Where is data hosted, and how is it backed up?
- How will the vendor notify us of a security incident?
Bring your IT lead into these conversations. Federal guidance from organizations such as CISA can help your team frame its questions about vendor security practices.
If a vendor offers AI features
Many vendors now include drafting, summarizing or search features that use AI. Ask how outputs are checked, whether they cite the source documents they draw from, whether staff review is required before anything is published, and whether city data is used to train models that serve other customers. Anything that becomes part of the public record should be reviewed by staff before it goes out, regardless of the tool that drafted it.
Where the alternatives fit
Once you have your criteria, the options tend to fall into a few broad groups. The vendors named here are examples drawn from well-established public knowledge, not a complete list or a ranking. Confirm current products and capabilities with each one directly.
Other full suites
Granicus is the best-known other vendor offering a broad local government suite, including website and meeting management products. If you value a single relationship but want to compare it with another, this is the closest like-for-like comparison. The same bundle questions apply: how connected the products are today, and what happens if you later change one piece.
Meeting management specialists
Several vendors focus mainly on agenda and meeting management for public bodies. eScribe is one example that serves municipalities. BoardDocs, now part of Diligent, is widely used by school boards and also by some cities and other public bodies. Specialists can be a good fit for a hybrid approach where you keep your current website and replace only the agenda system.
Records platforms with agenda workflows
Some cities manage agenda routing and approvals inside their enterprise content or records management system. Laserfiche is a well-known example of a records platform that many local governments use for document workflows. This path can make sense if your records system is already central to how departments work, though you will want to confirm how public publishing and meeting-day functions are handled.
Preparation and institutional memory tools
A newer group of tools focuses less on publishing the agenda and more on the work that goes into it. Govera is one option in this group. It drafts staff reports, resolutions and agenda items grounded in the city's own records, with citations to the source document, page and meeting. It also searches the full archive for institutional memory, tracks commitments made in minutes, prepares council briefings for each agenda item, runs packet completeness checks, and flags possible budget concerns and possible conflicts as suggestions for staff to consider. Staff review every output, each city's data is isolated in its own database schema, and every action is audit logged. Ask how a tool like this would fit with whichever system publishes your agenda and hosts your meeting video, and whether you would run it alongside your current tools or as part of a larger change.
Staying put
Your current vendor remains a legitimate option. If CivicPlus answers your written questions well, addresses your documented pain points, and offers contract terms you are comfortable with, renewing is a sound decision. A switch has real costs in staff time, training and risk to the public record, and the system your residents already know has value.
Running a fair evaluation
A structured process protects both the decision and the people who make it. It also gives every vendor, including your current one, an equal chance.
Build a small evaluation team
Include the clerk or deputy clerk who runs meetings, a department staff member who regularly submits items, someone from IT, your records manager, and someone from communications who manages the website. If your council is willing, ask one council member to sit in on demos of the council-facing features. Different users notice different problems.
Script the demos
Do not let vendors run their standard presentation. Send every vendor the same script in advance, built from your inventory and pain points. For example:
- Submit a staff report from a department, route it through two approvals, and add it to a regular meeting agenda.
- Show what happens when a required attachment is missing.
- Publish the agenda and packet, then show the public page as a resident would see it.
- Run a short mock meeting with a motion, a vote and a continued item.
- Search for a past council action on a topic your city has dealt with more than once.
- Show how the agenda connects to your website and to meeting video.
- Export a meeting's records and show what the export contains.
Use your own sample data wherever the vendor allows. A demo built on a tidy sample city tells you little about how the product handles your item types, your committee structure and your history.
Check references carefully
Ask each vendor for references from cities of similar size, governance structure and state. Ask references about implementation, migration of historical records, support response, and anything they wish they had known before signing. Ask whether they kept a website or other products from a different vendor, and how that connection has worked.
Get the answers in writing
Verbal assurances about roadmaps, integrations and support do not bind anyone. Ask each vendor to confirm key answers in writing, and attach the most important ones to the contract where your city attorney agrees it is appropriate.
Document the decision
Keep a short record of your criteria, weights, scores, demo notes and reference call summaries. If a council member, auditor or resident later asks how the city chose its meeting software, you will have a clear answer. That record may itself be a public record, so write it accordingly.
Next steps
You do not need to finish the whole review at once. A practical sequence for the next few weeks:
- Find the notice deadline on every CivicPlus contract and calendar it.
- Complete the product inventory table with help from purchasing, IT and communications.
- Write down 3 to 5 specific pain points from the clerk's office and departments.
- Send your written questions to CivicPlus and request a test export.
- Confirm your procurement path with purchasing and your city attorney.
- Map every place your website and outside sites link to agendas and minutes.
- Draft your weighted evaluation criteria and a demo script.
- Shortlist 2 to 4 options across the groups above, including staying put.
If agenda preparation, institutional memory and packet completeness are the areas where your staff loses the most time, include a preparation tool such as Govera in your shortlist and run it through the same demo script as everyone else.
