20 minutes
Set aside about 20 minutes.
How easy is it for residents to find your council’s emergency information when it matters most?
A 20-minute exercise for council communications and emergency management teams.
20 minutes
Set aside about 20 minutes.
A friend / colleague
Ideally someone who doesn’t work on your emergency pages.
Phone / Laptop
Start from your homepage, without direct links or hints from you.
Hot northerly winds have pushed a grassfire toward the edge of town. A resident wakes to the smell of smoke and picks up their phone. They want the local picture:
Where is the fire?
Which roads are closed?
Is the power out nearby?
Has council opened a relief centre?
Your council may already publish or link to all of it. How much work does the resident have to do to put the local picture together?
Before you start
Official warnings come first. This test checks how quickly your website gets people to them, and to the local information around them.
It’s a desk exercise. Use existing public information and don’t publish simulated warnings.
Top tip
A link that exists somewhere on your website is different from a link someone can find.
Set up the test
How it works
Your entries stay in this browser. Nothing is sent to Symphony3.
Why local matters
State information tells you what’s happening. Local information tells you what it means here.
A high-country council’s own weather station can read very differently from the nearest Bureau of Meteorology station. Residents need the local reading.
A central Victorian council wanted to post road closure banners straight away, rather than wait hours for an official notification.
The same council added a dedicated bird flu link for its poultry-farming community. No state page would put that first.
[Council names and sources to confirm before publishing]
Part 1 · The resident’s view
Watch your friend or colleague work on a phone or laptop. Don’t help. Note every wrong turn.
Ask: “Where would you go for emergency information about this area?” Note how long it takes to reach a useful page and whether they need site search. Then repeat from a search engine. Does it lead to a current page, an old news story or last season’s PDF?
Look for
An obvious route from the homepage, and one page council can promote before fire season.
Record
The first useful page, the time taken and anything that sent them elsewhere.
Part 1 · The resident’s view
From that starting point, ask your friend or colleague to find each of these four things.
Count the separate websites, searches and logins. Some answers rightly sit with another agency. The test is whether that handover is clear and takes them somewhere useful.
Look for
A local starting point that brings official sources and council information together.
Record
Each destination, and every point where they got stuck.
Part 2 · Behind the page
Finding information is half the test. The other half is whether people can trust it, and whether your team can keep it current at 2 am.
Pick one warning or council notice. Ask: “Who published this, when was it updated, and does it apply here?” Look for notices from last season that could pass for current ones.
Then try it without the map
Can they get the essentials as text, without map markers, colour alone or a social media login? If practical, repeat on mobile data rather than office wi-fi.
Look for
Clear sources, real update times and a clear line between live updates and preparedness advice.
Record
Anything whose source, age, location or status is unclear, or hard to use on a small screen.
Part 2 · Behind the page
Imagine council opens a relief centre at 2 am. Walk through who would do each job.
Use your real arrangements. Don’t fill a gap with “someone would probably do that”. Is there a backup if the usual publisher is asleep or on leave?
Pick one external feed on your page and ask your web team: “If this stops updating, what will residents see?”
Look for
A process the available staff can actually run, and a fallback that still points residents to official sources.
Record
The publishing steps, the owners, any single point of failure and what residents see when a feed stops.
Part 3 · Act on it
Don’t average the results into a score. One misleading notice deserves attention even if the rest of the site works well. Pick one change from each area.
Flagged for you
Anything you marked as a sticking point shows up under the matching area. Tap one to add it, then edit it.
Then repeat
Repeat that part of the test after each change, with a different friend or colleague if you can. Some fixes are a clearer heading or a corrected link. Others point to information spread across too many places. Name the problem before deciding what to build.
Your results