Construction risk scoring: make the action clearer than the score
Use a risk score to prioritise a discussion, not to hide uncertainty. Describe what could happen, why it matters, what would trigger action and who owns the response. Keep immediate safety matters in the site’s established safety process.
Distinguish a risk from an issue
A risk describes an uncertain future event. An issue has already occurred and needs management. “The delivery may miss the required date” is a risk; “the required date passed without delivery” is an issue. Link the two records if the event happens, retaining the history of assumptions and actions rather than leaving an obsolete risk marked green.
Write a record that supports a decision
| Field | Question it should answer |
|---|---|
| Cause and event | What condition could lead to what event? |
| Consequence | Which milestone, cost exposure or deliverable is affected? |
| Evidence | What supports the assessment and how current is it? |
| Likelihood and impact | Which agreed definitions were applied? |
| Trigger | What observable change requires action? |
| Response and owner | Who will do what, and by when? |
| Review | When will the assessment be checked again? |
Define your scale before scoring
A simple commercial or programme register might use low, medium and high likelihood, with separately defined impact bands. Agree what each band means for the project. If you convert categories to numbers, the result is an ordering aid, not a measured probability or expected loss. Do not compare scores from teams using different definitions or allow a multiplication formula to downgrade a consequence that requires escalation.
A delivery-risk example
Illustrative scenario: a supplier has not confirmed dispatch for fixtures needed before installation. Record the latest supplier evidence, the affected activity and the date by which confirmation is required. The owner might obtain written delivery confirmation and investigate an approved alternative. The trigger could be no confirmed dispatch by the review date. Reassess the forecast after receiving evidence, rather than reducing the score because someone says they are chasing it.
Record what changed after a response
Keep the original assessment, the agreed response and the current assessment distinguishable. A proposed action has not reduced exposure merely because it appears in the register. Record completion evidence and any remaining uncertainty. Close a risk only when its exposure period ends or the team accepts a documented reason for closure.
Keep safety decisions out of a generic commercial score
This guide and its template are for programme and commercial coordination, not hazard assessment or permission to continue unsafe work. Follow the applicable site procedures and qualified safety guidance for hazards, incidents and urgent concerns. Review critical project dependencies with the planner as well as maintaining a risk register.
Common questions
- What is the difference between a risk and an issue?
- A risk is an uncertain future event, such as a delivery that may miss its date. An issue has already happened, such as the date passing without delivery. Link the two records if the risk occurs.
- What should a construction risk record include?
- Cause and event, consequence, evidence, likelihood and impact under agreed definitions, a trigger for action, the response and owner, and the next review date.
- Is a risk score a probability?
- No. Converting categories to numbers creates an ordering aid for discussion, not a measured probability or expected loss, and scores from teams using different definitions should not be compared.
Programme and commercial risk register
A blank CSV you can open in Excel or Google Sheets. Adapt the fields to your project. No signup required.
Download CSV
