Civicade

Implementation

A Municipal Software Implementation Checklist for Small and Mid-Sized Cities

A phase-by-phase implementation checklist for small and mid-sized municipalities adopting new administrative software, from planning through go-live and review.

· 8 min read · Civicade

Most software implementations in small and mid-sized municipalities succeed or struggle for reasons that have little to do with the software itself: unclear ownership, decisions left too late, and staff who were never really brought along. This checklist breaks an implementation into practical phases, with the decisions, people, and pitfalls to plan for at each stage. It uses a public records request system as the running example, but most of it applies to any administrative software.

Before you start: set up for success

Name an owner

Every implementation needs one person who is accountable for moving it forward — often the clerk or records officer for a records system. This person does not do all the work, but they track decisions, chase open items, and make sure nothing stalls.

Define the team

In a smaller city, the same few people may wear several hats. Identify who will fill each role, even if one person covers several:

Role Responsibility during implementation
Project owner Schedule, decisions, coordination
Primary users Configure workflows, test, train others
Department representatives Confirm how their department will participate
Municipal counsel Review deadline rules, exemption reasons, templates, AI and data terms
IT (in-house or contracted) Security review, accounts, access, integrations
Executive sponsor Removes obstacles, supports adoption, approves scope changes

Agree on goals

Write three to five observable outcomes you want from the implementation. For example: "every request has an owner and a recorded due date," or "department assignments are tracked rather than emailed." Goals help you decide what to configure first and how to judge whether the project worked.

  • Project owner named
  • Team roles assigned, including counsel and IT
  • Three to five goals agreed and written down
  • Executive sponsor confirmed

Phase 1: Discovery and planning

The aim of this phase is to understand your current process well enough to configure the new system around it.

Map the current process

Walk through several recent requests — simple, moderate, and complex — from arrival to closure. Note who touches each request, which tools they use, and where delays occur. The Records Request Process Mapping Worksheet is designed for this.

Inventory what you will need

Gather the information the new system will need:

  • List of departments and a contact in each
  • List of staff who will use the system and their roles
  • Current request categories (or a proposed list)
  • Current deadline practices, written down
  • Current exemption reasons used, with counsel's citations
  • Current message wording for acknowledgments, clarifications, fee notices, and releases
  • This year's holiday and closure calendar
  • A list of open requests that will need to move to the new system

Decide scope for launch

Decide what will be live on day one and what can wait. A common, lower-risk approach is to launch with core intake, tracking, deadlines, department tasks, redaction, and review, then add optional features such as integrations or AI later, after the team is comfortable.

Plan the schedule around real constraints

Account for council meetings, budget season, elections, and staff vacations. Counsel review and IT security review often take longer than configuration, so start them early.

  • Current process mapped
  • Inventory complete
  • Launch scope agreed, with a list of deferred items
  • Schedule accounts for known busy periods

Some decisions require your counsel. Requirements vary by state and locality; refer to your state's official guidance and rely on your municipal counsel, not a vendor, for legal determinations.

Deadline rules

Document, with counsel, how your response deadlines work: business or calendar days, the length of the period, when the clock starts, how after-hours and closed-day receipts are handled, whether the clock may pause and when, and whether extensions are permitted. If different categories have different rules, document each.

Exemption reasons

Replace any generic or example exemption reasons in the system with the reasons and citations your counsel approves.

Templates

Have counsel review the wording of acknowledgments, clarification requests, fee notices, denial or partial-release language, and release messages.

Review policy

Decide which requests require legal review — all of them, or only certain categories — and whether release requires approval by someone other than the person who prepared the records.

AI and data sharing

If the system includes optional AI features, decide whether to enable them at launch. If any feature would send record content to an external provider, have counsel and IT review the provider's terms before approval. Many municipalities defer this decision until after go-live.

  • Deadline rules documented and reviewed by counsel
  • Exemption reasons and citations approved
  • Templates reviewed
  • Legal review and release approval policy decided
  • AI decision made (enable, defer, or decline), with reasons recorded

Phase 3: Security and access

Security review

Give your IT staff time to review the vendor's security documentation. Ask the vendor to distinguish what is implemented from what is planned, and be clear about your own requirements for a pilot versus full production.

Accounts and roles

Assign each user a role that gives them what they need and no more. Department contributors typically need access only to their own assignments. Limit who can see requester personal information and unredacted originals.

Authentication

Require strong passwords and ask every user to enable two-step verification. If your organization requires single sign-on, confirm whether the vendor supports it now or only plans to.

  • Security documentation reviewed by IT
  • Roles assigned on a least-privilege basis
  • Two-step verification enabled for all staff
  • Access to sensitive information restricted

Phase 4: Configuration

With decisions made, configuration is usually the most straightforward part.

  • Municipality profile, contact details, and public portal text entered
  • Departments and contacts added
  • Users invited and roles assigned
  • Business calendar, hours, holidays, and closures entered
  • Deadline rules configured, previewed against sample dates, and marked as reviewed by counsel
  • Request categories configured, with default departments where useful
  • Exemption reasons entered
  • Templates entered
  • Legal review and release policies configured
  • Optional features (integrations, AI) left off unless deliberately approved

Test deadline calculations

Before go-live, test several sample scenarios with your counsel's input: a request received on a weekday morning, one received after hours on a Friday, one spanning a holiday, one with a pause, and one with an extension. Confirm the system's result matches what counsel expects.

Phase 5: Data migration

Decide what history to bring across. For most municipalities, open requests matter most; closed requests can often remain in the old system or be archived.

  • Open requests exported from the current tool or spreadsheet
  • Data cleaned (consistent dates, categories, requester details)
  • Original received dates preserved so deadlines remain correct
  • A dry-run import checked before the final import
  • Imported requests spot-checked against the source
  • Decision recorded about closed historical requests

Phase 6: Training

Training should be short, role-specific, and hands-on.

Audience Focus
Records staff Full workflow: intake, deadlines, tasks, redaction, review, release
Department contributors Seeing assignments, uploading records, saying "no responsive records"
Legal reviewers Reviewing release packages, approving or requesting changes
Managers Dashboards and reports

Provide a one-page quick reference for each role. Department contributors in particular benefit from a short, clear guide they can keep at hand.

  • Role-specific sessions scheduled
  • Quick references prepared
  • Practice requests set up in a test environment or clearly labeled

Phase 7: Acceptance testing and go-live

Run an end-to-end test

Submit a test request through the public portal and take it all the way through: routing, department assignment, document upload, redaction, legal review, release, and requester download. Confirm the audit trail records each step.

Pilot before full launch

Consider a limited pilot: for example, new requests in one or two categories for a few weeks, while other requests continue in the old process. Agree on what success looks like before the pilot starts.

Switch over

  • End-to-end test passed
  • Pilot complete and reviewed
  • Public portal link published on the municipal website
  • Shared inbox auto-reply and printed materials updated
  • Old channels monitored for stragglers during transition

Phase 8: After go-live

The first few months determine whether the new system becomes part of daily work.

  • Weekly check-ins for the first month, then monthly
  • A simple way for staff to report problems and suggestions
  • Monthly review of overdue requests and department turnaround
  • Annual tasks scheduled: update holiday calendar, review templates and rules with counsel, review user access
  • Deferred features revisited once the team is comfortable

Common pitfalls

Configuring before deciding. Configuration goes quickly once decisions are made; it stalls when the system is used to make legal or policy decisions on the fly.

Treating vendor defaults as approved. Example rules, exemption lists, and templates are starting points. Have counsel review them.

Training everyone the same way. Department contributors do not need a full workflow course.

Launching everything at once. A narrower launch that works builds more confidence than a broad launch with rough edges.

No plan for annual maintenance. Calendars, templates, and access lists drift if nobody owns them.

How Civicade supports implementation

Civicade works alongside municipal staff through configuration, testing, and launch, and CivicRecords includes setup tools for many of the steps above: municipality profile and portal text, departments and roles, business calendars, versioned deadline rules with a preview tool and a "validated by counsel" marker, exemption reasons, templates, legal review policy, and a spreadsheet import process for open requests that preserves original received dates. AI features are off by default. We are currently preparing pilot programs. You can read more about our approach on the implementation page, and if you are still comparing options, see What to Consider When Evaluating Public Records Request Management Software.

This article is general information, not legal advice. Public records requirements vary by state and locality. Confirm your obligations with your municipal counsel and official state guidance.

All insights