Skip to content
← Resources

Incidents

How to create a practical website incident process

When something goes wrong, the first hour is easier if decisions were made in advance.

Define the basics

Who reports an incident, who is contacted, who can make decisions, and where credentials and backups are documented.

Triage, contain, communicate

Confirm the problem, limit further damage, tell the people affected what is happening, then work on recovery.

Review afterwards

Record the cause and what would prevent a repeat. Small improvements after each incident build resilience over time.

General guidance only. Every site is different; a health review applies these principles to yours.

Next step

Start with a clear view of your website.

A health review shows the site’s current condition, what needs attention first, and what can wait. The scope is confirmed before any work begins.

Request a website health review