Preconstruction risk refers to risks that occur in the preconstruction phase, before construction, due to incomplete design, insufficient time to procure long-lead items, unresolved gaps in the project scope, and uncertainty about the construction site and existing conditions, which may affect cost, time, and/or construction safety.
Categories of preconstruction risk commonly tracked on commercial projects:
- Design development risk, where drawings aren’t sufficiently detailed to price or build reliably
- Procurement risk tied to long-lead items with uncertain delivery timing
- Scope risk, including unresolved gaps or overlaps discovered during the buyout
- Site risk from incomplete existing conditions information, particularly on renovation work
The value of formally tracking preconstruction risk, rather than just noting concerns informally as they arise, is that it creates accountability for resolving each item before it becomes a construction-phase problem. A risk logged and assigned to someone with a target resolution date tends to get addressed; a concern mentioned once in a meeting and never written down tends to get forgotten until it resurfaces as an active field issue.
Risk severity and likelihood both matter when prioritising which preconstruction risks deserve the most attention with limited time before construction starts. A low-likelihood, low-impact item can reasonably wait, while anything affecting life safety or carrying a high probability of significant cost impact needs to be resolved before the project proceeds, regardless of how much preconstruction time remains on the calendar.
A discipline worth adopting for any preconstruction risk log: assigning each item a specific owner and a target resolution date at the moment it’s logged, rather than leaving it as an open, unassigned concern. An item with a named owner and a deadline tends to actually get resolved before construction starts; an item logged generically without either tends to linger unresolved, sometimes carrying straight into construction where it becomes a live field problem instead of the preventable preconstruction issue it started out as.
Risk transfer decisions made during preconstruction, who bears the cost if a specific identified risk actually materializes, deserve explicit negotiation and documentation rather than being left to implicit assumption. A risk everyone privately assumes the other party will absorb, without that assumption ever being confirmed in writing, tends to produce exactly the kind of dispute preconstruction risk tracking was meant to help prevent in the first place. Explicit risk allocation, even for a risk that ultimately never materializes, is cheap insurance against a costly disagreement later.
