Government-to-Citizen Notifications on Local Updates

Nobody likes finding out a road is closed by driving straight into it. A resident's late, annoyed, and one bad experience closer to skimming past the next alert too, even the one that matters.

Most complaints to a public works hotline aren't about the closure itself. They're about the silence before it. Nobody warned them, so they call to find out why.

This workflow warns them instead. Two messages, timed to the actual event, not a guess.

The first fires the moment a road works record gets marked "started" in the city's system. Residents near that street get the closure window and a detour before the crew even shows up.

The second fires off a matching trigger the moment the same record gets marked "ended." No fixed timer, no one remembering to send a follow-up. Just a short "you're clear" the instant it's true.

Filtered by street, too. A closure on one road doesn't page the whole city, only the residents it actually affects.

What makes this different from a scheduled broadcast:

It's event-triggered, not calendar-guessed. The alert reflects what's actually happening on the ground.

Exactly two messages, no more. Bury an urgent notice under a survey link and residents learn to skim the next one.

Wording is action-first. "Closed until 19:00, updates at tallinn.ee" beats a paragraph explaining why the crew is there.

Import it, swap in your own trigger events, and let residents hear it from you first.