Keeping a municipal website current alongside the rest of your job

Keeping a municipal website current is easier when updates are part of the work that produces the information. Attach minutes when the approved file is ready, change the service page when instructions change, and set temporary notices to leave the current list when they expire.

A quarterly cleanup can catch problems, but it cannot keep a resident from following an outdated instruction between reviews. The website needs a manageable publishing process throughout the year.

Which pages deserve attention first?

Start with information that changes what a resident does: office hours, payment links, application instructions and meeting details. A wrong decorative caption is less urgent than a page sending someone to a closed counter.

Make a short list of those frequently used pages and give each an owner. The owner confirms the information; another employee can still help publish it. Avoid assigning the whole website vaguely to everyone.

Brisbane's technology assessment (opens in a new tab) recommended ongoing website maintenance and staff training. The practical lesson is to include maintenance in normal responsibilities after the redesign is finished.

How can the website reduce repeat work?

Store reusable information once. A staff directory entry can supply contact details wherever that person appears. A meeting record can connect the agenda, minutes and calendar entry. A service page can remain the main destination while a short notice announces a temporary change.

These connections reduce the number of places employees must remember to edit. Ask the provider to demonstrate them with an actual routine change. A system that needs five separate edits for one new phone number leaves five opportunities for an old number to remain.

Muniway's website service includes connected municipal tools and a staff editor. The value is in the work staff can stop repeating, so examine that during a demonstration.

What should happen to temporary information?

Set the end of a notice's current display when you publish it, if the editor supports that function. Give the notice a descriptive title and explicit dates so someone who reaches it later understands what it concerned.

Removing a notice from the homepage and destroying its record are different actions. Follow the organization's retention procedures for the underlying record. The guide to expired website notices explains how current and historical information can remain separate.

For recurring information, use one stable service page. Update its current instructions and link to older documents only where they serve a clear historical purpose.

What is a manageable review routine?

Review the highest-use pages when related services change. Add a short periodic check for items that do not have a predictable trigger, such as staff contacts and external links. Choose a frequency the office can sustain rather than creating a long checklist nobody completes.

Keep a simple correction list with the page, the issue and its owner. Separate factual corrections from design improvements so a phone number does not wait for a larger redesign discussion.

At the end of each review, open the public pages that changed. Staff should be able to explain which information is current and where the next update belongs. That is a more useful goal than keeping every page permanently new.