Risk Assessment Template

Purpose

Risk work should be specific enough to influence decisions. A risk statement should describe the event, the cause or condition, the impact, the owner, and the next treatment decision.

Copy-ready structure

# Risk Assessment

Owner:
Date:
Status:

## Purpose
Describe why this document exists and what decision or action it supports.

## Scope
Included:
Excluded:
Deferred:

## Details
- Key fact:
- Dependency:
- Risk or constraint:
- Required approval:

## Evidence
Record where the result, approval, or supporting material is stored.

## Review
Next review date:
Update trigger:

When to use

• When the work repeats often enough that memory is no longer reliable.
• When more than one person may request, perform, review, or inherit the work.
• When risk, approval, evidence, or handoff needs to be visible later.

Common failure modes

• Risk language is too vague to act on.
• Accepted risks are never reviewed.
• Mitigation tasks are not owned.

Review guidance

Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.

Related DailyWF pages