Schedule and Cost Risk Register¶
Risk register — instantiates Reference-Class Planning Calibration
A living itemized catalog of discrete schedule and cost risks, each scored and re-scored over time, aggregated into a range that shows how far the plan can slip.
Some uncertainty in a plan is not one fuzzy cloud around a number but a list of nameable things that could go wrong, each with its own likelihood and bite. Schedule and Cost Risk Register is the living catalog of exactly those: a line-item ledger of discrete schedule and cost risks — a permit that might be delayed, an integration that might fail testing, a supplier that might slip — each scored for probability and impact, re-scored as the project moves, and aggregated into a range showing how far the schedule and budget could realistically drift. Its defining move is itemization over time: uncertainty is decomposed into individual risks that are owned, tracked, and updated, and the plan's range is built up from them rather than read off a single historical distribution. It builds a bottom-up range and keeps it current; it does not, itself, set the reserve that range implies or forecast the project's headline estimate.
Example¶
A commercial construction firm is building a mid-rise office block and stands up a schedule-and-cost risk register at kickoff. Each identified risk gets a row: foundation encounters rock (prob 30%, +3 weeks / +$180k), curtain-wall supplier slips (prob 25%, +2 weeks), city inspection backlog (prob 40%, +1 week), tenant-driven design change (prob 50%, scope-dependent). Each row has an owner and a trigger date. Monthly, the register is re-scored: once the excavation is complete and no rock is found, that risk's probability drops to zero and the range tightens; when the supplier misses an early milestone, its probability climbs and the range widens. Rolling the surviving risks together — probabilities and impacts combined, often through a Monte-Carlo pass — the register reports not a single completion date but a spread: a most-likely finish, an 80th-percentile finish several weeks later, and the specific risks driving that tail.[n1] When the tenant requests a floor-plan change mid-build, it is logged in the register's scope column so its schedule effect is attributed to the change, not blamed later on execution. The register never decides the contingency; it hands the range and the tail-drivers to whoever does.
How it works¶
- Itemize risks as discrete rows. Each risk is named, given a probability and a schedule/cost impact, and assigned an owner and a trigger — uncertainty as a list, not a cloud.
- Aggregate bottom-up into a range. The individual risks are combined (a simple weighted sum or a Monte-Carlo roll-up) into a distribution of total schedule and cost outcomes, exposing the P50 and the tail.
- Re-score on a cadence. As the project advances, risks retire, emerge, and shift; the register is updated so its range always reflects current exposure rather than the kickoff snapshot.
- Log scope movement. Changes to what is being built are recorded in the register so their schedule and cost effects are attributed correctly and not mistaken for pure risk realization.
Tuning parameters¶
- Risk granularity — how finely risks are itemized. Fine-grained registers capture more exposure and give precise tail-drivers but grow unwieldy and can double-count correlated risks; coarse ones stay manageable but hide detail.
- Aggregation method — simple expected-value sum versus Monte-Carlo simulation. Simulation models correlations and produces honest tails but demands more data and can lend spurious precision to guessed inputs.[n1]
- Re-score cadence — how often the register is updated. Frequent re-scoring keeps the range live but taxes the team; infrequent updates let it drift into stale reassurance.
- Probability-impact scale — qualitative bands versus quantified distributions. Quantified inputs feed real aggregation but invite made-up numbers; qualitative bands are honest about ignorance but resist rolling up.
When it helps, and when it misleads¶
Its strength is granularity and currency: it turns a vague sense of risk into owned, trackable line items and keeps the plan's range alive as the project changes, which is exactly what a static estimate lacks. Combined with a simulation pass it produces a genuine tail rather than a single date, and its scope column protects the invariant that overruns not be quietly reclassified as scope drift.
It misleads when its bottom-up completeness is trusted too far: a register can only aggregate the risks someone thought to list, so it systematically misses the unknown-unknowns and correlated cascades that a reference class of whole comparable projects would have captured in its outcome distribution. Its quantified output can therefore look rigorous while being narrower than reality — precise about the listed risks, blind to the unlisted. The classic misuse is treating the register's P80 as the project's true uncertainty and skipping the outside view entirely. The guarding discipline is to cross-check the register's aggregated range against a reference-class distribution: if comparable finished projects routinely overran by more than the register's tail, the register is missing risks, and the class — not the list — should set the floor on uncertainty.
How it implements the components¶
uncertainty_interval_and_tail_frame— it produces a range and tail for schedule and cost by aggregating itemized risks, so the plan carries a distribution rather than a point.rolling_recalibration_trigger— its scheduled re-scoring updates the range as risks emerge and retire, keeping the uncertainty current instead of frozen at kickoff.scope_change_ledger— its scope column records changes to what is being built, attributing their schedule and cost effects correctly.
It does not convert its range into a protected reserve (contingency_buffer_policy) — that rule is the Contingency Reserve Formula, which reads a percentile off this register's distribution; the register produces the distribution, the formula sets the buffer. It also does not build its range from a class of whole comparable projects (base_rate_distribution); that is the Historical Project Outcome Database, and cross-checking against it is the register's own guard.
Related¶
- Instantiates: Reference-Class Planning Calibration — supplies the living, itemized uncertainty range the calibration and reserves rest on.
- Consumes: Historical Project Outcome Database — the class distribution used to sanity-check the register's aggregated tail.
- Sibling mechanisms: Contingency Reserve Formula · Historical Project Outcome Database · Three-Point Estimate with Base Rates · Reference-Class Forecasting Workbook · Launch or Commitment Readiness Gate · Independent Estimate Round · Forecast Backtesting Review · Premortem as Auxiliary Probe
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Schedule and Cost Risk Register operates as a persistent ledger, log, register, or case record that preserves history and traceability because it a living itemized catalog of discrete schedule and cost risks, each scored and re-scored over time, aggregated into a range that shows how far the plan can slip.
Independent corroboration: The frozen evidence defines Schedule and Cost Risk Register as 'A living itemized catalog of discrete schedule and cost risks, each scored and re-scored over time, aggregated into a range that shows how far the plan can slip', so its operative form is Record, Log & Register.
Nearest alternative: Analysis, Modeling & Optimization — Schedule and Cost Risk Register includes features of an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution, but its defining operation is a persistent ledger, log, register, or case record that preserves history and traceability.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Itemized schedule and cost risks are canonical project-management artifacts.
Related originating lineages:
- Accounting & Auditing — Accounting, auditing, and controlled-resource stewardship supplies a parallel or contributing lineage for the mechanism's defining operation: a living itemized catalog of discrete schedule and cost risks, each scored and re-scored over time, aggregated into a range that shows how far the plan can slip.
- Economics & Finance — Economics, finance, and mechanism-design practice supplies a parallel or contributing lineage for the mechanism's defining operation: a living itemized catalog of discrete schedule and cost risks, each scored and re-scored over time, aggregated into a range that shows how far the plan can slip.
- Operations Research — Probabilistic schedule and cost aggregation materially produces slip ranges.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a living itemized catalog of discrete schedule and cost risks, each scored and re-scored over time, aggregated into a range that shows how far the plan can slip.
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement starts from reviewer_a's mechanism-specific evidence: Itemized schedule and cost risks are canonical project-management artifacts. Reviewer A proposed alternates=accounting_auditing, operations_research, origin_mode=cross_disciplinary_synthesis, domain_reach=multi_domain, and encyclopedia_synthesis=true; reviewer B proposed alternates=accounting_auditing, economics_finance, systems_cybernetics, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (accounting_auditing, operations_research, economics_finance, systems_cybernetics) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and records domain_reach=multi_domain and encyclopedia_synthesis=true. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Monte-Carlo schedule and cost risk analysis repeatedly samples each itemized risk's probability and impact to build a simulated distribution of total project outcomes, from which percentiles such as the P50 and P80 completion are read — turning a list of discrete risks into an aggregate range with an explicit tail. ↩a ↩b