A risk register gives the project team one place to track uncertainties that could affect scope, cost, schedule, quality, safety, or the client’s intended outcome. It is useful when each entry leads to a decision, an action, or a clear reason to monitor the issue. A long list with no owners or follow-up dates quickly becomes stale.
For each risk, write the cause and possible effect in plain language. For example: “Utility records may not show all services near the proposed connection, which could require design changes after field verification.” Record when it was raised, who owns the next action, the current response, status, assumptions, and any decision needed. Set a review date or project milestone for checking whether the risk has changed.
Common entries include incomplete survey information, uncertain subsurface conditions, utility conflicts, delayed client decisions, agency review, site access, procurement lead times, staffing gaps, and coordination with other consultants. State what information would reduce uncertainty. If a geotechnical report is pending, identify who will request it and when the design team needs it. Avoid presenting a probability, cost, or schedule impact as precise unless the team has a defensible basis.
Distinguish a risk from an issue. A risk may occur; an issue has already happened and needs active resolution. If an unknown utility is found in the field, move it to the issue process while retaining any remaining related uncertainty as a risk. This distinction helps owners see both emerging exposure and current problems.
Review the register at agreed project checkpoints and when a new instruction, field condition, or agency comment changes the picture. Ask task leads what could prevent their next milestone, who is handling each response, and what needs owner escalation. Material concerns may also call for the firm’s safety, insurance, contractual notice, or quality process.
It supports communication but does not replace engineering analysis or safety planning.
Licensed PE judgment and local codes govern.
