Website Redesign Risk Register
This is a practical guide to building a risk register for a website redesign project — the living log of risks with scores, owners and responses, adapted to the realities of redesigning an existing website.
What a Risk Register is
A risk register is the living log of risks with scores, owners and responses. For the full concept and how it works in general, see Risk Register. On a website redesign project it plays the same role, tuned to this kind of work.
Why it matters for a Website Redesign project
Website Redesign projects live or die on redesigning an existing website. A well-built risk register gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how website redesign projects drift into avoidable delay and cost.
What to include
- Risk description and category
- Probability and impact
- Risk score
- Owner
- Response and trigger
Website Redesign-specific considerations
Tailor the risk register to the risks that most often derail website redesign projects:
- Scope creep
- Content migration
- SEO preservation
Example
On a real website redesign project, the risk register would be shaped by redesigning an existing website. In particular, it should explicitly account for the project’s biggest risks — scope creep, content migration, SEO preservation — rather than treating them as afterthoughts.