What is a risk register in construction?
A risk register is a living list of the things that could hurt a project's cost, schedule, safety, or quality, with a rating for each, a named owner, and a plan to reduce or handle it. It starts in preconstruction and should be reviewed at least every two weeks. An issue log, by contrast, tracks problems that already happened.
A risk register is where a project team writes down what might go wrong before it does. Each entry describes the risk, scores how likely it is and how much it would hurt, names one person to own it, and records what the team will do about it. It starts during preconstruction and stays open until closeout. Good registers are short, specific, and reviewed every couple of weeks. Bad ones are a 200-line spreadsheet nobody opens after kickoff.
The register is not insurance and it is not a contingency budget. It is the reasoning behind both: it tells you which risks to price, which to transfer, and which to manage on site.
What goes in a risk register
- Risk description: cause and effect in one line. "Switchgear lead time slips past energization date, delaying startup" beats "electrical delays."
- Likelihood and impact: often a 1 to 5 scale each, multiplied for a score. Keep the scale simple enough that two people score the same risk the same way.
- Cost and time exposure: a rough dollar and day estimate where you can.
- Owner: one name, not a company.
- Response: avoid, reduce, transfer (to a sub, a supplier, or an insurer), or accept.
- Trigger and status: what early sign tells you the risk is happening, and whether it is open, closed, or realized.
A worked example
A GC wins a $5.2 million school gym renovation that must be done before classes start in August. In precon the team logs 14 risks. Three float to the top:
| Risk | L x I | Response | Owner |
|---|---|---|---|
| Hidden asbestos in floor mastic once old wood is pulled | 3 x 5 = 15 | Ask owner for a hazmat survey before bid; carry an allowance; line up an abatement sub | PM |
| Rooftop unit lead time pushes past July | 4 x 4 = 16 | Release RTU submittal in week 1; track as a long-lead item; ask about temporary cooling | Project engineer |
| Wood floor install needs conditioned space and acclimation | 3 x 3 = 9 | Sequence HVAC startup ahead of flooring in the schedule | Superintendent |
In week 6 the RTU supplier warns of a slip. Because the risk had a trigger and an owner, the PM already had a temporary cooling quote in hand and took it to the owner the same day.
Common mistakes
- Listing generic risks (weather, labor shortage) that apply to every job and never get a real response.
- Assigning ownership to "GC" or "team." If everyone owns it, no one does.
- Building the register at kickoff and never touching it again.
- Not tying high-score risks to money. If a risk is likely and expensive, it should be reflected in contingency, an allowance, an exclusion, or a contract clause.
- Ignoring opportunities. Some teams track upside items too, such as a value engineering idea that could save weeks.
Related terms
Related ideas include differing site conditions, long-lead items, and the early warning notice some contracts require. Smart Business Automator can flag risk signals from daily logs and project data, such as a slipping delivery or repeated weather notes, so they land on the register sooner; see construction workflow automation.
Frequently asked questions
Who owns the risk register on a construction project?
Usually the general contractor's project manager maintains it, but each risk gets its own owner, often a superintendent, project engineer, or subcontractor.
How often should a risk register be updated?
Review it at least every two weeks during construction, and any time something big changes, such as a new change order, a supplier warning, or a schedule revision.
What is the difference between a risk register and an issue log?
A risk register tracks things that might happen. An issue log tracks things that already have. When a risk happens, it moves to the issue log or becomes a change, claim, or schedule update.
Do small contractors need a risk register?
A simple one, yes. Even a list of five risks with owners, written during estimate handoff, catches problems a crew lead would otherwise find too late.
