The Risk-Based Test Plan Template
Template
Prioritise testing effort by risk instead of spreading it evenly and thin.
Risk
- What's most likely to break, based on recent changes?
- What's complex, unfamiliar or poorly understood?
- What has broken before?
Impact
- What happens to users if this breaks in production?
- Is this a minor annoyance or a trust-breaking failure?
- Does this touch money, data or safety?
Coverage
- What's already covered by automation?
- What genuinely needs manual, exploratory attention?
- What are we consciously choosing not to test, and why?
Owner
- Who owns testing this area?
- Is that clear to the whole team, not just QA?
- What's the plan if it's found broken close to release?
Start a conversation
Have a product or AI decision to make?
Useful first calls usually start with one unclear decision, a deadline and a team that needs a practical next move.
Tell us about it