Learning Center

AACE RP 29R-03, Illustrated

AACE International’s Recommended Practice 29R-03 is best known for classifying delay analysis methods by a handful of practical questions -- not a specific technique. Here’s that decision framework, in plain language, with a mini-example on each branch.

The Framework’s Core Idea

Rather than presenting one preferred method, RP 29R-03 organizes the field around a handful of characteristics that determine which method family fits a given situation: when the analysis is performed relative to the project, what schedule data is actually available, and whether the goal is to model a hypothetical scenario or observe the real as-built record. Working through those questions in order is a practical way to arrive at a defensible method choice rather than picking one out of habit.

The Decision Path

The four questions RP 29R-03’s framework works through, in the order most analysts apply them.

Question 1

Is the analysis being done as events happen, or after project completion?

Contemporaneous (during the project) vs. retrospective (after the fact) is the first split.

Contemporaneous analyses tend toward prospective, model-based methods; retrospective analyses can use the real as-built record directly.

Question 2

Is a reliable baseline or updated schedule available to work from?

A good contemporaneous schedule update supports more defensible model-based methods; its absence pushes toward observational, as-built-driven methods instead.

Available schedule quality is often the single biggest practical constraint on which method is even feasible.

Question 3

Is the goal to model a hypothetical delay's impact, or to observe what actually drove the finish date?

Modeled/simulation approaches insert a delay event into a schedule and recalculate; observational approaches trace what the real critical path actually was, window by window or activity by activity.

This is the core distinction between something like Time Impact Analysis (modeled) and Windows Analysis (observational).

Question 4

Does the analysis need to explain a single event, or the whole project's delay history?

A single disputed event often suits a focused technique like But-For or Collapsed As-Built; a full project history usually calls for dividing the timeline into consecutive windows.

Scope of the question being asked, not just data availability, shapes which family of methods actually answers it.

Where This Leads

Walking through these four questions on a real dispute tends to land on one of the same handful of named techniques covered elsewhere in this Learning Center: Time Impact Analysis, Windows Analysis, Collapsed As-Built, or But-For Delay analysis -- the RP’s real contribution is a structured way to justify the choice, not a fifth method of its own.

Every branch of this decision tree depends on the same thing: what schedule data you actually have. Claims Digger keeps every schedule update you’ve uploaded as its own comparable snapshot, so “is a reliable contemporaneous update available” is usually a yes by the time you need to answer it. See how it works.

Frequently Asked Questions

What does 'RP 29R-03' mean?: It's AACE International's Recommended Practice number 29, revision R-03 -- 'Forensic Schedule Analysis.' AACE (originally the Association for the Advancement of Cost Engineering, now AACE International) publishes Recommended Practices covering cost engineering and project controls topics broadly, of which this is one.
How is RP 29R-03 different from the SCL Protocol?: They cover overlapping ground but organize it differently: RP 29R-03 groups methods into a formal set of Method Implementation Protocol (MIP) categories based on data source, timing, and calculation approach, while the SCL Protocol presents a more prose-based, principles-first guide. Many of the same underlying techniques (time impact analysis, windows analysis, as-planned vs. as-built) appear in both, described in each document's own terms.
Do I need to buy the full RP to use these methods?: The underlying methods themselves (time impact analysis, windows analysis, and so on) are general industry techniques, not something the RP restricts. The RP itself is a paid AACE publication if you want its specific classification framework and detailed guidance in full.

Part of the Claims Digger Learning Center. Related reading: The SCL Protocol, method by method · AACE RP 29R-03 (glossary)