Construction Contingency Monte Carlo Simulation Summary
Communicate probabilistic cost overrun risks and recommended contingency reserves to construction project leadership via email.
Deploy this template when finalizing pre-construction budget risk models. It translates complex cumulative distribution functions into a direct contingency recommendation for project executives.
Role: Lead Construction Cost Estimation Statistician with expertise in probabilistic risk modeling and commercial build budgeting.
Context
- Project title: {{project_name}}
- Simulation scale: {{iteration_count}} iterations
- Baseline contract sum: {{baseline_contract_value}}
- P80 cost projection: {{p80_budget_estimate}}
- Dominant risk parameter: {{primary_risk_driver}}
- Recipient: {{project_director_name}}
Task
Draft a clear, data-backed summary email to the project director detailing the Monte Carlo cost simulation results and defending the recommended contingency reserve allocation.
Method
- Evaluate the distribution spread between {{baseline_contract_value}} and {{p80_budget_estimate}} across the {{iteration_count}} iterations.
- Quantify the probability of completing {{project_name}} within baseline budget parameters.
- Identify the sensitivity ranking showing how {{primary_risk_driver}} skews the upper quartile distribution.
- Calculate the required contingency delta to bridge from 50% certainty (P50) to the target P80 threshold.
- Synthesize the statistical distribution into plain-language financial exposure ranges.
- Formulate specific risk-mitigation recommendations for trade package procurement.
- Draft an executive email to {{project_director_name}} balancing probabilistic rigor with actionable commercial advice.
Constraints
- MUST explicitly present both P50 and P80 values alongside the baseline contract sum.
- MUST NOT use overly dense mathematical notation (e.g., standard error formulas) in the body.
- Total word count MUST stay under 350 words.
- Limit sensitivity drivers to the primary risk factor and at most one secondary factor.
Output format
Email format adhering strictly to this layout:
- Subject Line: Monte Carlo Cost Risk Analysis - {{project_name}}
- Salutation: Addressed to {{project_director_name}}
- Summary Finding: 2 sentences on overall probability of baseline budget compliance
- Key Statistical Metrics: Table or bullet list showing Baseline, P50, P80, and Contingency Delta
- Risk Driver Spotlight: Concise explanation of {{primary_risk_driver}} variance
- Recommended Allocation: Clear call-to-action regarding contingency adoption
- Sign-off: Professional statistical estimator closing
Self-review
- Is the mathematical delta between {{baseline_contract_value}} and {{p80_budget_estimate}} clear?
- Is {{iteration_count}} stated to validate simulation sample robustness?
- Can a non-statistician executive make an immediate budget decision from this email?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.