Why Every Project Needs a Risk & Opportunity Register

What Happens When You Skip Risk Registers and Reference Class Forecasting

Here’s the deal. I talk about risk management constantly, and two specific tools do most of the real work. A genuine risk and opportunity register, and reference class forecasting. Skip either one during pre-construction, and the consequences are not vague. They show up in real, documented numbers.

Building a Maximum Virtual Product, Not a Minimum Viable One

During pre-construction, tied directly to the research behind How Big Things Get Done, the goal is a maximum virtual product, not a minimum viable one. That means a genuinely visual project plan, pulled entirely out of individual people’s heads, brought together where fresh eyes can actually analyze it properly.

The tool for that is a fresh eyes meeting, run as many times as a team can genuinely tolerate. Think of it like Pixar’s internal brain trust process, where a film gets torn apart deliberately to find every possible flaw before it ever reaches an audience. The key distinction, and it matters enormously, is that you tear apart the process, never the people. The goal is finding as many real problems with the plan as possible, while it is still cheap and early enough to fix them.

Only Three Honest Responses to a Real Risk

Once a risk gets identified, there are only three legitimate responses. Mitigate it directly. Cover it with contingency or a genuine backup plan. Or consciously absorb it. What you cannot do, under any circumstances, is wish it out of existence and hope it simply does not happen.

Work through enough of these fresh eyes sessions and plan adjustments, and most risks genuinely disappear from the list. The ones that remain, the ones you truly cannot eliminate, need to be carried in contingency and written down in a real risk and opportunity register.

Why the Register Itself Increases Profit

Here is where this becomes a genuine profit driver rather than just a defensive exercise. A real risk and opportunity register names specific targets, the specific risks that could hurt the project in days and dollars, and the specific opportunities that could genuinely help in days and dollars. Every single item gets assigned to one person, ultimately responsible for it, and gets monitored constantly, especially inside the team weekly tactical meeting.

That structure means someone is actively working to prevent each identified risk from actually happening, and actively working to capture each identified opportunity rather than letting it pass by unnoticed. Even with all of that discipline in place, you still need a contingency bucket genuinely sized to carry whatever risks remain on the list. There is no version of this where wishful thinking substitutes for a properly sized contingency.

Watch for these signs a project is relying on wishful thinking instead of a genuine risk register:

• Risks discussed informally in conversation but never actually logged, assigned an owner, or monitored on a recurring basis.
• A contingency budget set arbitrarily rather than sized against specific, named risks still on the list.
• No regular meeting cadence where the register actually gets reviewed and updated.

Why Reference Class Forecasting Protects You From Your Own Optimism

The second tool, reference class forecasting, works by aggregating real historical data by project type, duration by unit of measure, budget by unit of measure, and typical overage on both, segmented by region and program type. A data center. A wastewater treatment plant. A hospital in a specific region. Each of those carries a genuine historical track record worth checking before you commit to a number.

Here is the scenario that makes this concrete. Suppose every multifamily project your organization has built in a specific region over the past fifteen years has taken roughly sixteen months. A new, ambitious project manager and superintendent team, eager to make a name for themselves, believes they can genuinely deliver the next one in thirteen. Do you set your actual milestone at thirteen months? Do you build your proforma and financial model around that number? No. You build the real budget and schedule around sixteen months, the verified historical reference class. You can absolutely still target something faster as a stretch goal for the team to chase. You do not build your actual financial commitments around wishful thinking, no matter how talented or motivated the team pursuing that stretch goal genuinely is.

The Real Numbers Behind Skipping Both Tools

Here is what the research behind How Big Things Get Done shows happens when projects are planned without the right systems and without genuinely trained, supported people. Only fifty eight percent of projects finish on budget. Only eight percent finish both on budget and on time. And only about half a percent finish on budget, on time, and delivered the way the owner actually wanted from the start.

Those numbers are not abstract either. The average project in the United States finishes fifty eight days behind substantial completion. Across the broader global industry, projects run over budget by an average of sixty percent. Skip the risk register and skip reference class forecasting, and those are not unlikely outcomes to guard against. They are the statistically expected result.

Why Skipping Reference Class Forecasting Compounds the Damage

If you do not use a genuine historical reference class, you will undercut your milestone before the project even starts. That undercut milestone cascades into an improperly built budget, and it cascades further into general conditions and general requirements that were never properly estimated in the first place, since those costs scale directly with how long the project actually takes to build, not how long you hoped it would take.

That combination, an optimistic milestone paired with an underfunded budget, sets a project up for exactly the same downward productivity spiral and crash landing that skipping the risk register produces. These are genuinely two of the most damaging mistakes a team can make during pre-construction and planning, and they reinforce each other when both are missing at once.

Building Both Tools Into Your Own Pre-Construction Process

None of this requires exotic software or an unusual level of sophistication to implement. It requires the discipline to run genuine fresh eyes sessions, maintain a real risk and opportunity register with named owners, and check every major milestone against actual historical data before committing to it publicly.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build both of these tools directly into pre-construction, rather than relying on optimism and hoping the historical numbers simply do not apply to this particular project.

So here is the challenge. Before your next project locks in its milestone and budget, check two things honestly. Does a genuine risk and opportunity register exist, with named owners actively monitoring it? And was the milestone actually checked against real historical data for comparable projects, rather than set based on what an ambitious team believes it can achieve? If either answer is no, that is exactly where your project’s odds of finishing on budget and on time are already being quietly undermined.

Jason Schroeder said it plainly: “We cannot rely on wishful thinking to help us with any of this.” Replace it with a genuine register and real historical data, and your odds actually improve.

On we go.

FAQ

What is the actual difference between mitigating a risk and simply absorbing it?

Mitigating a risk means taking specific action to reduce the likelihood or impact of that risk before it happens, such as adjusting a sequence or securing an alternate supplier. Absorbing a risk means consciously accepting that it may occur and planning to handle its consequences through contingency, without actively working to prevent it. Both are legitimate responses, as long as the choice is deliberate rather than simply hoping the risk never materializes.

Why does reference class forecasting matter more than trusting an experienced team’s own estimate?

Because even genuinely skilled, motivated teams tend to underestimate duration and cost when they have a personal incentive to hit an ambitious target, and historical data reflects what has actually happened across many similar projects rather than what one team believes is possible this time. Building the real budget and schedule around verified historical performance protects the project financially, even while still allowing a team to pursue a faster target as a genuine stretch goal.

Why does the risk and opportunity register need a single named owner for each item rather than shared team responsibility?

Because shared responsibility often means no one individual feels genuinely accountable for actively preventing a specific risk or capturing a specific opportunity, and important items can quietly fall through the cracks. Assigning one person as ultimately responsible for each item, monitored consistently in a recurring meeting, ensures that someone is actually taking action rather than assuming someone else is handling it.

How does an undercut milestone specifically damage a project’s general conditions and general requirements budget?

Because general conditions and general requirements costs, things like site supervision, temporary facilities, and overhead, scale directly with how long a project actually takes to complete. A milestone set below what historical data would predict leads directly to underestimating those ongoing costs, since the budget assumes a shorter duration than the project is actually likely to require, creating a funding gap that surfaces later in the project when it becomes far more expensive to address.