Most town websites have one undifferentiated news feed, so a water main break, a job posting and a reminder about leaf collection all carry the same weight. When something urgent happens, staff have nowhere to put it except the top of that same list, and residents have no way to tell that this notice is the one to read.
Illustration with invented content.
The difference a notice makes
- The notice is a PDF, so nobody can search it
- The website, the mailing list and the noticeboard say different things
- Urgent items look exactly like routine ones
- Taking a banner down needs a support ticket
- Written once, published as text a search engine can read
- The same post feeds the page, the archive and the banner
- Urgent items look urgent, and only while they are
- Up in a minute, down in a minute, by whoever is at the desk
What residents get
Writing a notice should take about as long as writing the email telling someone else to write it. The editor is plain text with the few controls a notice needs, and it works on a phone, which matters at seven in the morning when the water main has already broken.
The banner is a switch, not a redesign. It appears on every page, it looks urgent because it is, and it comes down in a minute when the situation ends. Nothing about that requires a support ticket.
A public notice carries a deadline and, sometimes, a challenge. Each one keeps its publication date and stays at the same address permanently, as text rather than as a scanned image, so it can be found and cited later.
The most common failure is not silence, it is three versions: one on the website, one on the mailing list, one taped to the door. A single post drives all of them, so the versions cannot drift apart.
What staff get
Four fields and a button. Writing the notice should take about as long as writing the email asking somebody else to write it, and on the morning a water main has already broken that difference is the whole product.
Turning on the site-wide alert is one control on the same screen, and it carries an expiry. Emergencies end at inconvenient hours, and a banner that outlives its emergency teaches residents to ignore the next one.
A hearing notice often has to be published on a particular date, not before and not after. Writing it while you have the information and letting it appear when the law requires is safer than a reminder in somebody's calendar.
During an actual emergency the person who knows is rarely at their desk. Publishing works from a phone, so the update does not wait for somebody to get back to the office.
For the moments that matter
- The emergency banner is part of the site, not a plugin, so it loads with the page and cannot be missed
- Notices carry structured publication dates, which is what search engines use to decide something is current
- Nothing about posting an urgent notice requires the person who normally does it to be available
Included in every TownFront site
This is part of the core product, not an add-on module. Every TownFront website includes it, and it is built to the same standard as the rest of the site: fast on an ordinary phone connection, navigable by keyboard, readable by a screen reader, and maintainable by your own staff.
See how this would work for your community. Request a conversation and we will walk through your current site and what changes.
Other capabilities
- Agendas & Minutes
- Events & Meeting Calendar
- Documents
- Forms & Permits
- Departments & Contacts
- Search That Works
A notice nobody can find is not a notice. It is a filing exercise with a legal deadline attached.
Why we treat notices as content rather than as attachments