Know sooner. Act faster.Download Excel workbook · September 2026 / v1.0 · No account required
Before you start
Use throughout planning and delivery to review uncertain events and their responses. Agree the project's likelihood and impact definitions before assigning ratings.
- Project objectives and current delivery assumptions
- Agreed likelihood and impact definitions
- Risk workshop or project review records
- Accountable owners and response commitments
How to use it
Write a specific risk
Describe the condition, possible event and consequence. Separate an uncertain future event from an issue that has already occurred.
Agree a response
Use the project's qualitative rating definitions. Record a response, trigger and owner; this register deliberately avoids a universal numerical scoring formula.
Review on a fixed date
Set the reporting date and next review dates. Days overdue highlights open reviews; it does not quantify probability or expected delay.
Fields included
- ID
- Condition / event / consequence
- Owner
- Likelihood
- Impact
- Response / trigger
- Review due
- Status
- Days overdue
- Evidence / notes
A long-lead delivery uncertainty
Illustrative example: if factory testing fails, switchgear delivery may miss the installation window. The procurement lead owns the response and confirms the next factory test date. The register tracks the review commitment; a schedule risk model is needed to quantify the potential completion effect.
Before issue
- Risk wording identifies a cause and consequence.
- Ratings use agreed project definitions.
- A response and review owner are recorded.
- Closed risks retain a reason and evidence reference.
Practice references
- GAO Schedule Assessment Guide, GAO-16-89G
- Kairos project-controls practice
Original Kairos working templates informed by common project-controls practice. Adapt them to your contract, project procedure and approval authority. They are not official standards-body forms or a certification of compliance.
Editorial standards