After-hours website work is rarely about a complicated design change. It is about getting a clear, approved message in front of the public quickly: a boil-water advisory, a road closure, a weather-related facility change, or an election update. The hard part is not publishing one paragraph. It is knowing who has authority, where the message goes, and how the team confirms it is correct.
Make the first ten minutes predictable
A short runbook should name an on-call contact, the communication channel used for approval, the WordPress account or publishing path, and the pages or alert formats available. It should be understandable by a trained backup person, not only the person who built the site.
- Receive: record the source and exact wording of the requested update.
- Confirm: identify who is approving the message and whether an official source must be linked.
- Publish: use the prepared alert format and central updates page.
- Verify: check the live mobile view, the link destination, and the time stamp.
- Close: remove or resolve the notice when the responsible department confirms the issue is over.
Set reasonable service expectations
A runbook should not promise an impossible response time. It should define what counts as an emergency, how staff reach the right person, and what the fallback is if the primary contact is unavailable. For routine edits, normal business-hour handling may be appropriate. For a safety or major service interruption, the workflow should be different and documented.
The test is practical: could a new communications director, IT contact, or agency partner publish the right message at 9:00 p.m. without improvising? If not, the process needs another pass before the next real-world event.