Who keeps a municipal website updated after launch?

Municipal website maintenance needs clear ownership after launch. Staff usually maintain the accuracy of public information, while the provider handles the technical work included in its service. Confirm the boundary for hosting, software updates, connected tools and support so neither side assumes the other is handling it.

A new design can make the website easier to use. Keeping it useful requires continuing work as information, software and staff responsibilities change.

Which updates belong to municipal staff?

The organization supplies and approves its public information. Staff know when office hours change, a meeting document is ready or a service instruction needs correction. They need an editor and training that let them publish those changes appropriately.

Give each important section an owner and backup. The current-content guide explains how to tie updates to the work that produces them.

A provider can assist with content, but it cannot independently know every operational change. Make the handoff explicit when the service arrangement includes posting information on the office's behalf.

Which technical work should be assigned?

Identify responsibility for the website software, hosting and recovery arrangements. Include the tools residents use through the website, even when a separate company operates them.

Brisbane's technology assessment (opens in a new tab) recommended ongoing website maintenance responsibilities. Any platform needs an appropriate maintenance arrangement; the office should know what its provider maintains and what remains outside that scope.

Ask how changes are tested before they affect public services and how staff report a problem afterward. An update can be technically installed while a form or integration still needs checking.

What should the maintenance record show?

Keep a practical record of responsibilities and completed work. Staff should know whom to contact, which services are covered and how to obtain evidence of recovery testing or a resolved problem.

The website backup checklist covers evidence that recovery works. Avoid treating a backup setting as the whole maintenance plan.

How do you keep the arrangement useful over time?

Review responsibilities when a new tool is added or the provider changes. A payment connection or online form can introduce another service owner. Make sure the office knows who handles failures at that boundary.

Include staff transitions. New editors need training and authorized access; departing employees should be handled through the organization's access process. Support contacts should remain available to the people covering essential work.

Muniway's website service includes hosting, backups and software updates alongside the staff editor. Discuss those responsibilities in the context of the tools the community actually uses.

A maintained website has an owner for each recurring job and a clear route when something fails. Establish that arrangement while the website works well, then keep it current as the service changes.