Give every platform the same editing tasks.
A content management system is the place staff create and maintain website content. A useful evaluation begins with routine work: change office hours, replace a document, revise a service page, add a meeting and correct a published notice. Use a representative page and an ordinary editor role rather than relying only on a vendor demonstration.
Observe the steps, permissions and help required. Can an editor preview the change on mobile? Is it clear which version is live? Can a reviewer return a draft without accidentally publishing it? Record evidence from each task, including where your team needs training.
Prepare the page types and content owners in the content audit workbook. The broader redesign process explains where platform evaluation fits in discovery and testing.
Test the service-page fields and multilingual revision workflow your editors need before comparing product claims.
Compare operating models before product names.
| Approach | What your team should test | Responsibility to clarify |
|---|---|---|
| Managed website platform | Editor tasks, available page patterns and configuration limits. | What the provider maintains, what changes cost and what can be exported. |
| Separately hosted CMS | Publishing roles, update procedures and supported extensions. | Hosting, backups, patches, plugin licensing and integration support. |
| Custom or headless setup | How editors preview content and how changes reach the public site. | Who maintains the content model, front end, deployment and connected services. |
On a small screen, scroll the table sideways to see every column.
These are operating patterns, not rankings. A managed product can reduce some maintenance work while limiting customization. A flexible stack can create more responsibility for the agency or its support partner. Test the actual proposal and configuration.
Separate a necessary requirement from a preference.
Mark a requirement as essential only when a resident task, staff process or agency obligation depends on it. For example, a department may need a separate reviewer, while a preferred editing layout is negotiable. Keep unverified capabilities marked as unverified until someone demonstrates them.
- Content structure: reusable service fields, navigation, attachments and multilingual relationships when required.
- Publishing control: roles, revisions, preview and a visible route for corrections.
- Public experience: actual templates and forms tested on mobile and with keyboard navigation.
- Operations: backups, restoration, updates, support coverage and a known escalation route.
- Portability: usable content, media, URL and metadata exports, with a clear account handoff.
An accessibility claim about a platform does not verify the pages, documents and custom interactions your project will publish. Agree on implementation testing and evidence with your reviewers.
Ask for a small proof, including an export.
Use the same sample content on shortlisted approaches. Ask an editor to make a change, a reviewer to approve it, and an administrator to revoke an editor’s access. Then export the sample and inspect whether the text, files and relationships are usable outside the platform.
Record the result as Demonstrated, Configurable, Additional work or Unverified. Include setup and training effort. This prevents a standard feature and a proposed custom extension from receiving the same assumption in a comparison.
For a service connection, follow the integration planning guide. An available API is useful only if the required operations, permissions and support are available for your account.

Compare a defined operating period and an exit.
Request separate figures for implementation, hosting, licenses, maintenance, content work, training and optional changes. Use a stated comparison period that fits your organization. Document assumptions about editor counts, traffic, storage, integrations and support hours rather than treating them as unlimited.
Ask what happens if the agency changes providers: who exports the content, which accounts remain available and what assistance costs. The ownership and maintenance guide provides the handoff questions. Use the existing cost and scope guide for the broader budget structure.

Finish with a decision record your team can review.
Keep the priority tasks, essential requirements, demonstrated evidence, unresolved gaps, operating costs and accountable decision owner in one record. If two approaches meet the task equally well, compare the effort and risk of operating them rather than adding features to manufacture a difference.
The GOV.UK technology selection guide (opens in a new tab) discusses user needs, adaptability and the surrounding technology landscape. It is UK government guidance, not a municipal procurement rule. The task-based comparison here is a practical way to organize your own evaluation.
Use the scope builder to document what remains unknown, or review Civicfield’s website design approach when you need implementation support.

