Preconstruction — Risk & Contracts

Risk Register

The living log of every identified project risk, its owner, its score, and its response.

Quick Answer

A risk register is a structured log of every risk identified on a project. Each entry records the risk, its likelihood and impact, an assigned owner, and a planned response. It's a living document, updated as risks arise, change, or close, and it drives how much contingency a project carries and where.

The Full Picture

A risk register exists to turn risk from a gut feeling into a managed list. Without one, risks live in scattered emails and individual heads, and the same surprise hits multiple projects. The register forces every identified risk to be written down, scored, owned, and tracked to closure — so nothing that was foreseen gets quietly forgotten.

Each entry captures a description, a category, a likelihood and an impact rating, a combined severity score, an owner, and a response. Many teams visualize the severity ratings on a risk matrix — a likelihood-by-impact grid — so the highest-severity risks are obvious at a glance and get attention first. The register also notes trigger conditions and target closure dates.

In practice the register is reviewed on a cadence — at design milestones and in regular precon meetings. Risks get added as the design reveals them, re-scored as conditions change, and closed when they're retired or realized. A stale register that's built once and never revisited is worse than none, because it creates false confidence that risk is being managed.

For a GC, the register is also the audit trail behind contingency. When an owner asks why the budget carries a given contingency, the register shows the specific risks it covers and how they were scored. That traceability is what separates a defensible contingency from an arbitrary percentage.

Real Examples

→Milestone re-scoring: At design development the team reopens the register, drops a permitting risk that cleared, and raises the impact score on a utility-relocation risk that grew as the civil design firmed up.
→Risk matrix triage: Plotting entries on a likelihood-by-impact grid, the team focuses the next month on the three risks sitting in the high-high corner rather than spreading effort evenly.
→Contingency justification: When the owner questions the contingency line, the precon manager walks the register entry by entry to show exactly which risks the number covers.

Common Misconceptions

People assume: A risk register is a one-time document you build at kickoff.

Actually: It's only useful if it's living. Risks emerge and change as the design develops, so a register built once and shelved gives false comfort. The value is in the regular re-scoring and closing, not the initial list.

People assume: The register should list every conceivable risk.

Actually: A register bloated with trivial or duplicate risks buries the ones that matter. Good registers are curated — scored, prioritized, and pruned — so attention lands on the high-severity items instead of a wall of noise.

Does MeltPlan Solve This?

Not directly

A risk register is a governance and tracking tool — a scored, owned, continuously updated log of project risks. Maintaining it is a program-management activity, not a drawing-review or takeoff task, so it falls outside MeltPlan's product scope. Teams typically keep a register in a spreadsheet or a dedicated risk-management tool.

Frequently Asked Questions

What goes in a construction risk register?

Each entry includes a risk description, category, likelihood and impact ratings, a combined severity score, an assigned owner, a planned response, trigger conditions, and a status. Together those fields let a team prioritize and track every identified risk to closure.

What is the difference between a risk register and a risk matrix?

A risk register is the full log of risks with all their detail. A risk matrix is a likelihood-by-impact grid that visualizes the register's severity scores, making the highest-priority risks easy to spot. The matrix is a view of the register, not a replacement.

How often should a risk register be updated?

At every design milestone and on a regular meeting cadence during preconstruction. Risks are added as they emerge, re-scored as conditions change, and closed when retired or realized. A register that isn't revisited quickly loses its value.

Who owns the risk register?

Typically the preconstruction manager or a designated risk lead owns the register itself, while individual entries have their own owners responsible for executing each response. The register owner runs the review cadence and keeps it current.

Related Terms

Preconstruction Risk ManagementFinding and assigning a project's risks before ground breaks, while they're still cheap to manage.Risk Allocation (Construction)Deciding, in the contract, which party carries each of a project's risks.Liquidated DamagesA pre-agreed dollar amount per day of late completion, set in the contract.Force MajeureA clause excusing a party from delay caused by events beyond its reasonable control.PreconstructionEverything a contractor does to plan, price, and de-risk a project before ground breaks.GMP ContractA contract that reimburses cost plus a fee but caps the total at a guaranteed maximum.

More Preconstruction — Risk & Contracts Terms

Sources

  1. Associated General Contractors of America (AGC) — Risk management resources
  2. IRMI — Construction Industry risk and insurance resources
MELTPLAN