CWICR Cost Risk Contingency Calculator

A contingency line usually gets set as one flat percentage applied across the whole bid — 10% on everything — which means a division with almost no real risk carries the same cushion as one sitting on unknown subsurface conditions or a 20-week equipment lead time, and the number that actually needed the padding never gets called out.

The skill takes a CWICR-coded estimate plus a risk register — per division, a probability of overrun, an estimated impact percentage, and a short description of the risk driver — and calculates a risk-weighted contingency dollar amount for each division individually, not a blanket rate. It rolls those up into a total recommended contingency and a blended percentage, then flags any division where the calculated contingency is disproportionately large relative to its own base cost, worth a second look before the bid goes out.

It doesn't identify risks or assign probability and impact numbers itself — that has to come from the user's own risk register, built from a risk workshop, a geotech report, a buyout review, or a schedule risk assessment — and it doesn't run a Monte Carlo simulation or produce a P50/P80 confidence-level output. This is single-point probability × impact math done correctly and consistently across every division, not a full quantitative risk analysis.

Bloqbase's own risk matrix skill for the Spanish market (Matriz de Riesgos de Obra) is a general probability-times-impact prioritization tool with no cost coding or dollar output, built for a different job: ranking and assigning mitigation owners. This skill is CWICR-specific and produces a contingency figure that rolls into an estimate. If you manage projects across markets and CWICR is part of how your US jobs get bid, this skill slots into that workflow directly — download it free with your email, or write to us if you want to see it working with your actual project's risk register.

How to put it to work on a real project

The idea isn't to download another file and forget it in a folder. Use it with a specific case: a pending certificate, a coordination meeting, a cost overrun or a handover to the developer. Fill in the resource with real data from your project, validate the result with your own technical judgment, and keep it as an internal reference to repeat the process next time.