Project Risk Register: Template and
Guide
Risk Identification, Scoring, and Management for AEC Projects
Purpose of the Risk Register
The Risk Register is a living document maintained throughout the project lifecycle. It provides a
structured record of all identified risks, their probability and impact, the assigned owner, and the
agreed response strategy. On ISO 19650-compliant projects, the risk register is referenced in the
BEP and reviewed at each information exchange milestone.
Risk Scoring Matrix (5x5)
Each risk is scored on two axes: Probability (1=Rare to 5=Almost Certain) and Impact (1=Negligible
to 5=Critical). The Risk Score = Probability x Impact.
Impact / Probability Rare (1) Unlikely (2) Possible (3) Likely (4) Almost Certain (5)
Critical (5) 5 10 15 20 25
Major (4) 4 8 12 16 20
Moderate (3) 3 6 9 12 15
Minor (2) 2 4 6 8 10
Negligible (1) 1 2 3 4 5
Score 15-25: Critical (Red) | 8-12: High (Orange) | 4-6: Medium (Yellow) | 1-3: Low (Green)
Risk Register Fields
Field Description
Risk ID Unique sequential reference (e.g. R-001)
Date Identified Date risk was logged
Category Design / Procurement / Programme / Cost / Regulatory / Stakeholder
Description Clear statement of the risk event
Cause Root cause or trigger condition
Effect Consequence if risk materialises
Probability (P) Score 1-5 per matrix above
Impact (I) Score 1-5 per matrix above
Risk Score PxI
Response Strategy Avoid / Transfer / Mitigate / Accept / Escalate
Response Action Specific action(s) to be taken
Owner Person responsible for the response
Due Date Target date for action completion
Residual Score Expected P x I after response
Status Open / In Progress / Closed / Escalated
Sample Risk Register Entries: Architecture/BIM
ID Risk P I Score Strategy Owner
R-001 No written brief issued by ARCH lead; modelling4begins4 without
16 direction
Mitigate: issue written RFI; document paper
BIM trail
Coord
R-002 Civil model submitted with unknown geometry errors
3 4 12 Mitigate: formal clash check before next BIM
submission
Coord
R-003 Clash detection not completed before DD issue 3 5 15 Avoid: enforce coordination gate in programme
PM
R-004 COBie data not populated by subcontractors 4 3 12 Transfer: include COBie obligation in subcontract
PM
R-005 Shared coordinate system reset by new team member
2 5 10 Mitigate: lock Project Base Point; document
BIM in
Coord
BEP