“Automated” and “manual” are often presented as opposites. For public-service information, they are usually complementary. The right question is not whether people or systems should publish alerts. It is which source is best positioned to own each part of the message.
Let operational systems carry operational facts
A trusted operational system is usually the best source for structured, fast-changing facts: a route number, a stop, a predicted arrival, a service status, or a time stamp. Re-entering those details into WordPress by hand creates delay and opportunities for mismatch.
Let people carry context and judgment
A website editor is usually better positioned to explain what the public should do. A detour can require a plain-language explanation, a temporary boarding instruction, a link to a map, or a note that an event affects a particular area. Those messages depend on local judgment and may not belong in the operational system at all.
- Automate: repeated, structured, time-sensitive data from an established source.
- Publish manually: clarifications, instructions, policy explanations, and exceptions.
- Approve together: anything high-stakes that combines operational facts with public guidance.
Write the rule before the emergency
A short ownership guide prevents staff from debating the workflow while residents are waiting. It should name the system of record, the person who can add a manual notice, the approval path for sensitive updates, and the point at which an alert expires.
Good public communication is not fully automated or fully manual. It is designed so the system does what systems do well and staff retain the ability to explain, correct, and reassure.