Buying strategic planning software in local government

The procurement route matters more than the feature comparison, because it determines how long the purchase takes. Settle it before writing requirements.

Step 1: establish the route

Check your own purchasing policy for the thresholds; they vary widely by jurisdiction and state. In broad terms:

• Below the small-purchase threshold — often a single quote or a documented price. Fastest route, and annual subscriptions for a planning tool frequently fall here.
• Middle band — typically three written quotes or informal solicitation.
• Above the formal threshold — RFP with evaluation criteria and a scoring committee.
• Cooperative or piggyback contract — an existing awarded contract you can ride on, which skips solicitation entirely where your policy allows it.

Ask your purchasing officer which applies before you scope. A requirement set written for an RFP when a quote would do adds a quarter for no benefit.

Step 2: write requirements around the failure modes, not features

Requirements copied from a vendor's feature list select for that vendor. Write them around what makes plans fail:

• Single ownership. Every goal, initiative and action must carry exactly one accountable owner, visible without opening a document.
• Measure definitions stored with the measure. Formula, exclusions, unit, source, owner, update frequency, baseline and target — held in the system, not in a separate data dictionary.
• Measure history retained. Multi-year trend per measure, with a record of any definition change and re-baselining.
• Department self-service. Department staff update their own items without a central administrator transcribing.
• Public-facing reporting. A resident-readable view or export that renders from the same data staff maintain, so the published version cannot silently diverge.
• Role-based access. View-only for elected officials and the public, edit rights scoped by department.
• Export and exit. Full export of plan, measures and history in a documented format, on request, at no additional charge.
• Audit trail. Who changed what, when — relevant wherever the plan or its measures may be subject to public records requests.

Step 3: security, hosting and records questions

Ask each vendor, in writing:

1. Where is data hosted, and can hosting be kept in the United States?
2. Is access encrypted in transit and at rest?
3. Is single sign-on supported against the city's identity provider, and can multi-factor authentication be enforced?
4. What is the incident notification commitment and its timeframe?
5. Is a data processing agreement available, and does it survive termination for the export period?
6. What third parties process data, and are they disclosed?
7. What are the service availability commitments and where are they published?
8. On termination, how long is data retained and how is it destroyed?

Route these to IT early. Security review, not price, is the most common cause of delay in this category.

Note also that plan content, measures and decision records held in the system may be subject to your state's public records law. Confirm export capability is sufficient to respond to a request without vendor assistance.

Step 4: evaluation criteria that predict adoption

If you run a formal solicitation, weight for adoption rather than feature count:

Ease of use carries real weight here for a reason: the department director who has to update a measure monthly is the person who determines whether the system is still in use in year two.

Step 5: pilot with your own plan

Before award, require each finalist to load one of your actual priorities — three or four goals with real measures and real owners — and demonstrate a quarterly review against it. Demonstrations on vendor sample data show the tool at its best and tell you nothing about your own measure definitions, which is where the friction always is.

Costing over three years

Ask for: annual subscription, any implementation or setup fee, cost of additional users or departments, cost of the public-facing view, training, and the annual uplift cap. A per-user price that looks favourable for the leadership team can multiply once every department updates its own items — which is the model you want.

What to leave out of the requirements

• Named integrations you do not currently use.
• AI features, unless you can state the decision they support.
• Unlimited custom dashboards. Cities that ask for these usually end up maintaining four and using one.

Related reading: strategic planning for city governments and how to build a balanced scorecard, the framework most commonly used for published municipal performance reporting.