Public Sector Software Adoption in Local Government: How Cities Build the Scoring Habit

Every city that buys strategy software buys it for the same reason: the spreadsheet stopped telling the truth. The plan lived in four places, the quarterly report took three weeks to assemble, and nobody could answer "are we on track?" without a meeting first.

Then the platform goes in. Configuration finishes. Training happens. And somewhere in month five, the thing quietly stops being used. The license renews, the logo stays on the org chart, and nobody files a report saying so.

That silence is the interesting part. A failed implementation announces itself. A failed adoption does not. It looks exactly like a working one from the outside, which is why most cities discover it at renewal, eighteen months after the moment it could have been fixed.

We can see that moment, because we host the plans. What follows is what post-purchase adoption looks like when you measure it with behavior instead of a survey, across 161 local governments running 6,627 active plans on the ClearPoint platform, as of 21 August 2026.

What "software adoption" means once a local government has already bought

Adoption, in the post-purchase sense, is the share of the work the software was bought to carry that it is actually carrying. Licenses issued is a procurement fact. Logins are an attendance record. Adoption is narrower and harder: the plan lives in the system, the numbers get refreshed on a cadence, the goals carry a current status, and the report a council member reads is generated rather than assembled.

Generic SaaS benchmarks put healthy adoption at roughly 60–70% of licensed users active within the first three to six months. That figure travels widely, and it measures the wrong thing for a city. A public works director who logs in monthly to update six measures is fully adopted. A department head who opens the dashboard weekly and updates nothing is not. Presence and maintenance are different behaviors, and only one of them keeps a strategic plan alive.

What adoption actually measures: scoring

Inside a strategic plan, two things can carry a live performance status: measures (the KPIs) and objectives (the goals the KPIs are supposed to serve). Scoring is the act that turns a plan into a report. It is what makes a goal green, yellow, or red on the day someone asks.

Across 161 local governments as of 21 August 2026, ClearPoint shows which measures and objectives carry an active performance status and which haven't been scored yet. The layer closest to the council, the goals a city actually campaigned on, is the one to score first.

How we define it: "actively scored" means the element carries a live evaluation rule that assigns it a performance status. It is a measure of whether the scoring habit was ever installed, not of whether a human has ever touched the record. We report it in aggregate only, and we never publish a named customer's rate — an actively maintained city that tracks without status rules reads as zero, and a handful of them do.

The owner who hasn't updated yet

Assigning an owner is the single most repeated instruction in strategic planning. It is also the instruction most likely to be completed on paper and abandoned in practice.

Across local government users who hold at least one assigned element, ClearPoint shows which owners haven't recorded an update yet, so teams can follow up before the review.

What makes this an adoption metric rather than an accountability complaint: a phantom owner is visible on day 30. You do not need a year of decay to detect one — you need a report that lists every owner with zero updates since assignment, which takes about a minute to run.

We have written about the mechanics of this at length in why department heads resist strategy execution software, and about how it compounds through a first year in why most local government software implementations fail in Year 1.

The variable that predicts adoption better than training does

Here is where the platform data disagrees with the corpus most sharply.

We grouped 156 local governments by how many measures they hang on each objective — a proxy for how heavy the plan is — and looked at the median share of measures actually scored in each band:

A city running fewer than three measures per goal scores 58.3% of them. A city running twelve or more scores 8.6%. That is close to a sevenfold spread, produced entirely by how much a city asked itself to maintain.

We also tested whether automation rescues a heavy plan — whether cities with update workflows and scheduled reminders configured show better adoption. Once we controlled for plan size, the effect disappeared and the direction flipped between size bands on small samples. We are not publishing a number for it, because there is not an honest one to publish. Scope did the work that tooling was credited with.

Four adoption metrics worth putting on your own dashboard

The instrument a city needs is small. Four numbers, pulled monthly, each one a behavior rather than an opinion:

None of these requires a survey, a consultant, or a satisfaction score. All four are visible from inside the platform a city already pays for. That is what makes the measurement gap a habit problem rather than a data problem.

The 90-day checkpoint

The corpus is unanimous that adoption should be planned for, and silent on when to check. Ninety days after go-live is early enough that the configuration is still fresh in everyone's memory and late enough that the first real update cycle has happened.

Three questions, answered with numbers rather than impressions:

• Did every goal get scored at least once? If a goal has never carried a status, the habit was never installed for it, and the first cycle is where that is cheapest to correct.
• Which owners have never updated? Reassign or retire the element. An owner who has not acted in 90 days will not act in 900.
• Is the plan too heavy to maintain at this cadence? If updating took more than a few days of staff time, cut the measure list before the next cycle rather than after the third.

Cities that get through those three questions honestly tend to keep the scoring habit. The ones that skip it end up describing, eighteen months later, a tool that never quite took — which is the abandonment story we mapped in the seven reasons mid-size cities abandon strategic planning software.

The short version

Local governments do not lose software to a bad product or an untrained staff. They lose it to a scoring habit that was never installed and never measured, on a plan built heavier than the staff who inherited it could carry. Both of those conditions are visible in the first ninety days, and both are cheaper to fix there than anywhere downstream.

The cities that score most of their goals are not better resourced. They are running fewer things, more often, with names attached that mean something.

If you would rather see the four metrics running against your own plan, book a 30-minute walkthrough and we will build the adoption view with your data in it. You can also browse how the rest of this fits together in the strategic planning guide, or see what the platform looks like for a city in strategic planning software for local government.

Download the Status Rule Playbook — the scoring rules behind this article

See how ClearPoint runs your government's strategic plan — book a demo

Methodology and sources

Platform figures are drawn from aggregated, anonymized ClearPoint platform data as of 21 August 2026, covering 161 local government organizations (cities, counties, towns, villages, boroughs, townships and metropolitan authorities) running 6,627 active plans, 124,755 measures and 23,806 objectives. "Actively scored" means an element carries a live evaluation rule assigning it a performance status; it is reported in aggregate only and is not a per-customer usage claim. Sub-analyses restrict to organizations with at least 3 objectives and 20 measures (n=156) to avoid small-plan distortion.

The one external dataset cited here is ICMA, Strategic Plan Implementation: Off The Shelf And Into Action (June 2026, n=59 US municipalities and counties, self-reported survey). The corpus review referenced above covers the six highest-ranking guides on public sector software adoption as of 21 August 2026; we counted which subtopics each one covered and did not reproduce the third-party failure-rate figures they quote, because those figures largely trace back to other blog posts rather than to primary research. Further background on plan-level benchmarks is in strategic planning: what over 20,000 plans taught us and local government KPIs.