What AACE 70R-12's 2026 Revision Changes About Schedule Contingency

On August 18, 2026, AACE International published the revised Recommended Practice (RP) 70R-12, "Principles of Schedule Contingency – As Applied in Engineering, Procurement, and Construction". Spearheaded by primary contributor Natasha Dahl, the update provides a modernised framework for implementing schedule contingency and managing schedule risk during the execution phase of capital construction projects. The revision addresses a fundamental flaw in how most programmes handle time risk: treating it as an abstract concept rather than a quantifiable, consumable resource.

The chronic failure of schedule risk management

The requirement for a revised approach to schedule contingency is evident in the persistent failure of capital projects to meet their baseline commitments. Highlighting the chronic need for better schedule risk management, a recent study by Independent Project Analysis examined 91 pipeline projects and found that two-thirds missed mechanical completion. The same study noted that 80 percent of projects finished later than their earliest Front-End Loading (FEL 1) schedule, and 15 percent took about twice as long as their initial early-stage estimates.

These failures are rarely the result of a single, catastrophic event. Instead, they stem from systemic flaws in how schedule risk is quantified and managed. Historically, project teams have attempted to account for uncertainty by padding the durations of individual activities. A task that should take ten days is scheduled for fifteen, with the extra five days acting as an informal, invisible buffer against things going wrong.

This approach obscures the true baseline execution duration and makes it impossible to track whether risk is actually materialising. When a padded activity finishes in twelve days, the project appears to be ahead of schedule, even though it took two days longer than the unpadded baseline. The 2026 revision of AACE 70R-12 dismantles this practice, establishing a formal distinction between the time required to execute the work and the time held in reserve to manage risk.

The shift from hidden padding to explicit buffers

The core directive of the revised RP 70R-12 is that schedule contingency must be modelled as a distinct, explicitly defined buffer of time. Rather than burying contingency within individual activity durations, project teams must separate the baseline execution durations from the risk buffers. This contingency is a quantified allocation of time that the project team draws down from as risks occur.

The guidance outlines specific procedures for achieving this separation. It requires integrating risk register events directly into the schedule logic. When a risk is identified, the response—what the team will actually do if the risk materialises—must be linked to specific schedule impacts. This forces a direct relationship between the risk register and the schedule, moving away from arbitrary duration padding based on intuition.

By modelling contingency as an explicit buffer, project teams can monitor its consumption over time. The RP mandates the establishment of a formal schedule control plan. This plan must define the rules for earning progress against the contingency and forecasting remaining durations. As the project progresses, the team must continuously monitor and re-evaluate the contingency buffer, ensuring it remains sufficient to cover the remaining quantified risks.

Float, contingency, and management reserve

A critical component of the 2026 update, and the surrounding industry commentary, is the strict delineation between different types of schedule allowance. The most common error in schedule risk management is conflating float with contingency. The revised practice reinforces that schedule float is merely a mathematical byproduct of network logic. It is the amount of time an activity can be delayed without delaying the project end date. Contingency, conversely, is a quantified, managed buffer specifically allocated for identified risks. They are not interchangeable. Relying on float to absorb risk events is a failure of risk management, as float belongs to the project network, not to specific risk responses.

Furthermore, the practice maintains a strict boundary between schedule contingency and schedule management reserve. Schedule contingency covers quantified risks that have been modelled and are expected to be expended during execution. The project manager typically has the authority to draw down from this contingency as those specific risks materialise.

Schedule management reserve, however, covers unquantifiable risks or major scope changes. It is held outside the performance measurement baseline. Accessing the management reserve generally requires a formal baseline change and authorisation from senior management or the client. Blurring the lines between these two reserves leads to a loss of control over the project baseline and obscures the true cost of scope creep versus poor execution.

The visibility of schedule slippage is another area where the practice demands rigour. Industry experts warn against the common habit of clearing negative float or slack by simply dragging bars or changing constraints during schedule updates. Negative float is not an error to be corrected; it is a diagnostic warning of a missed commitment. Artificially clearing negative float only hides the underlying risk rather than managing the contingency required to fix it. The schedule must reflect reality, even when that reality shows a breach of the baseline.

What this means for your programme

For practitioners running Quantitative Schedule Risk Analysis (QSRA), the 2026 revision of AACE 70R-12 provides a defensible, standardised framework for managing schedule risk. It aligns the management of time risk with the established practices for managing cost risk in Quantitative Cost Risk Analysis (QCRA).

In a mature QCRA model, cost contingency is never hidden by inflating the unit rates of individual materials. It is held as a distinct line item that is drawn down as risks occur. The revised AACE practice demands the exact same discipline for schedule risk. QSRA models must now show risk quantification as a distinct buffer of time, separate from the baseline execution durations.

This requires a fundamental shift in how programmes conduct schedule risk analysis. A risk register is not a risk analysis. A list of things that might go wrong, each with a number someone typed in, is insufficient. Programmes must explicitly define the rules for earning progress against their schedule contingency. They must force a direct link between their planned risk responses and the logical impacts on the schedule.

When running a quantified risk analysis on a real programme, this means the QSRA output is no longer just a probabilistic completion date. It is a defined contingency buffer that must be actively managed, monitored, and re-evaluated through a formal schedule control plan. If a risk does not materialise, the associated contingency is not simply absorbed by inefficient execution; it is retired, bringing the forecast completion date forward.

Implementing the 2026 guidelines

While the 2026 revision provides a robust framework, AACE explicitly notes that RP 70R-12 is intended to provide guidelines rather than strict, inflexible standards. The practice is designed to be used as a companion to other AACE practices, particularly those concerning forecasting and change management.

Implementation must be tailored to the specific contracting environment of the programme. A lump-sum engineering, procurement, and construction (EPC) contract will require a different approach to contingency management and reporting than a reimbursable alliance contract. The ownership of the contingency buffer, the rules for its drawdown, and the reporting requirements must be clearly defined in the contract and the schedule control plan.

To implement these guidelines, programmes must stop treating the schedule and the risk register as disparate documents. The risk register events must be integrated into the schedule logic, and the impacted activities must be updated as risks are mitigated or materialise. By adopting the principles of the August 2026 revision, programmes can move away from arbitrary padding and mathematical illusions, bringing the same level of certainty to project time as they demand for project cost.