Most construction problems are predictable. Late approvals, long-lead materials, design changes and labour shortages appear on project after project. A construction risk register captures these threats early, assigns owners and tracks responses, so the team acts before a risk becomes an issue. It is also a key part of the PMP risk management knowledge that civil engineers are tested on.
What a Risk Register Contains
A useful register is a living table, not a document written once for the tender. Typical columns are:
- Risk ID and date raised.
- Risk statement written as cause, risk and effect.
- Category, for example design, procurement, authority, site, commercial or safety.
- Probability and impact scores.
- Risk score or rating, usually probability multiplied by impact.
- Owner, a named person responsible for monitoring and responding.
- Response strategy and specific actions.
- Trigger or early warning sign.
- Residual rating after the response.
- Status and last review date.
Write Clear Risk Statements
Vague entries such as "approval delay" are hard to manage. Use a structured sentence: "Because the marble supplier needs approved shop drawings before reserving slabs, there is a risk that late consultant approval delays slab reservation, which could push lobby flooring beyond the handover date." This makes the cause, the event and the consequence clear, and suggests possible responses.
Scoring Probability and Impact
Many teams use a 1 to 5 scale for both. Define the scale in writing so different people score consistently. For example, an impact of 5 might mean a delay to the project completion date or a significant cost overrun, while 1 means a minor inconvenience absorbed within float. Plot risks on a probability-impact matrix to see which deserve attention first.
Response Strategies
The PMBOK Guide lists several strategies for threats:
- Avoid: change the plan to remove the risk, such as choosing a locally stocked stone instead of one with uncertain shipping.
- Mitigate: reduce probability or impact, such as submitting shop drawings early or ordering extra slabs from the same block.
- Transfer: shift the impact to another party, usually through contracts or insurance.
- Accept: acknowledge the risk and set aside contingency or a fallback plan.
- Escalate: pass the risk to a higher level when it is outside the project's authority.
For opportunities, the equivalent strategies are exploit, enhance, share, accept and escalate.
Example Entries for a Fit-Out Project
- Authority approval: fit-out permit takes longer than planned. Response: submit complete drawing set early, track comments daily. Owner: design manager.
- Long-lead materials: imported stone or sanitary ware arrives late. Response: early procurement, approved alternates, regular expediting. Owner: procurement lead.
- Design changes: client changes finishes after approval. Response: change control process with cost and time impact shown before approval. Owner: project manager.
- Site access: restricted working hours in an occupied building. Response: agree access plan with building management and plan night shifts. Owner: site manager.
- Interface clashes: MEP services clash with ceiling or joinery. Response: coordination drawings and clash checks before installation. Owner: MEP coordinator.
Keep the Register Alive
- Review it in every progress meeting, starting with the highest-rated risks.
- Close risks that no longer apply and record why.
- Add new risks as soon as they are identified by anyone on the team.
- Link major risks to schedule activities and cost contingency.
Tools You Can Use
A spreadsheet is enough for small projects. Larger organisations may use dedicated risk software or modules in their project controls tools. What matters more than the tool is the habit of reviewing the register regularly and acting on it.
PMP Exam Notes
Remember the difference between a risk (uncertain future event) and an issue (something already happening). Know the response strategies and that risk owners are responsible for implementing agreed responses. Questions often describe a scenario and ask which strategy is being used.
A Simple First Step
If your current project has no register, hold a thirty-minute workshop with the design, procurement and site leads. Ask each person to name the three things most likely to delay their part of the work. Write each one as a cause-risk-effect statement, score it, assign an owner and agree one action. Twenty well-written risks reviewed every week are far more useful than a long register nobody opens.
Frequently Asked Questions
What is the difference between a risk and an issue?
A risk is an uncertain event that may happen. An issue is a problem that is already happening and needs action now.
How often should a risk register be reviewed?
At least at every regular progress meeting, and immediately when a major change or new information affects the project.
Who owns the risk register?
The project manager is usually responsible for the register, while individual risks are assigned to named owners who monitor them and lead the responses.
Related Reading on ShoaibSite
Written by Shoaib Hussan, Founder of D3DDD – Dubai 3D Design & Draft.
Instagram: @mxhaib
Need drawings or 3D? Visit d3ddd.com or email info@d3ddd.com.

ConversionConversion EmoticonEmoticon