Skip to content
BIMpedia
Chapter 4 · Lesson 2 of 6Topic: Managing the work

Risk management

Risk management finds what could go wrong, decides what to do about it, and makes someone own each risk. Information has its own risks (late models, wrong data, systems that don't talk), and ISO 19650 expects them on the register.

3 min read3 quiz questions
Skip to the quiz
  • Watch out
  • What it costs
  • Experienced readers
  • Remember
  • In BIMpedia
Mayainformation manager
Even if you do this every day, watch for this: A risk without an owner and an action is just a worry. 'Late MEP model' on a register helps nobody; 'MEP model for stage 4 later than 1 May (likely: subcontractor not yet appointed). Owner: PM. Action: appoint by 1 April or agree an interim design model' is a risk someone can manage.

Risk management is the habit of asking "what could go wrong, and what will we do about it?" before it does. Every project keeps a risk register. Information has its own risks, and a coordinator who brings them to the register early is worth a lot.

Basics
StepWhat it means
DescribeCause → event → effect ("If X, then Y, leading to Z")
ScoreLikelihood × impact (often 1–5 each)
OwnOne named person
RespondAvoid, reduce, transfer or accept
ReviewAt every project meeting

Information risks worth registering

RiskTypical response
A key model or subcontractor lateAppoint earlier; interim design model
Data required at handover not plannedWrite it into requirements now; check at milestones
Teams' software can't exchange wellTest exchange at mobilisation; agree formats
Key BIM person leavesSecond person trained; documented procedures
Sensitive information shared too widelySecurity assessment; access rules

ISO 19650 asks the delivery team to assess information delivery risks as part of its tender response, and to keep them on the project's risk register.

Story · The risk that became an issue
How it goes wrong

Everyone knows the façade subcontractor will be appointed late, but nobody writes it down. Stage 4 coordination runs without façade brackets; the clashes appear in fabrication, and the slab edges have to be re-detailed.

How it goes right

The coordinator adds the risk to the register: cause (late appointment), effect (no bracket coordination), owner (PM), action (the façade engineer models bracket zones by stage 3). The zones are coordinated, and fabrication fits.

Mayainformation manager
Your turn. Give it about 15 min and work it out on your own before you open the model answer: that is where it sticks.
Exercise: Write three information risks 15 min

For a new office building, write three information risks in cause–event–effect form, with a score (likelihood and impact, 1–5), an owner and a response.

Key takeaways

  • A risk is an uncertain event that would affect the project's objectives; an issue is a risk that has happened.
  • Each risk is described, scored (likelihood × impact), owned, and given a response: avoid, reduce, transfer or accept.
  • Information risks belong on the register: late or missing deliverables, poor data, interoperability, skills, security.
  • ISO 19650 asks the delivery team to assess information delivery risks in its tender response and keep them up to date.

Your notes

Check yourself

3 questions · 2 right to complete
  1. 1. What is the difference between a risk and an issue?
  2. 2. Which is the best-written risk?
  3. 3. Buying insurance against a risk is an example of which response?
0 of 3 answered