Delay analysis methods: the records carry them, the software does not

Type what your project file actually holds. Five published methods are read against it, and on the worked file the records carry four. No method is chosen and no entitlement decided.

Live result

4 of the 5 declared methods are carried by this record.

Updates in the record3 updates

The declared tie rule names Baseline to as built comparison, and that is not advice.

Carried methods as the update count moves

Try a record

Contemporaneous updates3

This is the one dominant control. The carried list can first change at 2, and counts above 12 stop separating the methods in this audit.

Question perspective

What the project file contains

Approved baseline available

Baseline logic checked

Updates carry status dates

Sequence as built available

Delay events have dates

Logic changes are recorded

The complete record demand matrix

Baseline to as built comparison: A retrospective question with a checked baseline and a sequence as built.; Carried by these records; Nothing missing

Collapsed as built comparison: A retrospective question with a sequence as built, dated delay events and logic change records.; Carried by these records; Nothing missing

Contemporaneous event insertion: A prospective question with a checked baseline and dated delay events.; Not carried by these records; a prospective question

Periodic update comparison: A retrospective question with a checked baseline, at least 2 dated updates and a sequence as built.; Carried by these records; Nothing missing

Reconstructed as built critical path: A retrospective question with a sequence as built, dated delay events and logic change records.; Carried by these records; Nothing missing

Method	Declared demands	What is missing
Baseline to as built comparisonCarried by these records	4	Nothing missing
Collapsed as built comparisonCarried by these records	4	Nothing missing
Contemporaneous event insertionNot carried by these records	4	a prospective question
Periodic update comparisonCarried by these records	6	Nothing missing
Reconstructed as built critical pathCarried by these records	4	Nothing missing

Named by the declared rule

Baseline to as built comparison

Above 12, the count is shown as 12 or more and does not strengthen any method claim in an audit covering 2 years.

The boundary where this stopsIt reports which public practice methods the typed record set can carry, without recommending one, deciding entitlement, pricing delay, assigning cause, or reading a contract.

Contemporaneous update count

From

In steps of

It does not check the values in between.

Across the values sampled, the carried method list and the name returned by the declared tie rule stays 4 carried, Baseline to as built comparison from 2 to 24, the highest value sampled. The nearest value where it changes is 1, where it becomes 3 carried, Baseline to as built comparison.

The answer	4 carried, Baseline to as built comparison
Values sampled	0 to 24, 25 values, step 1
Holds from	2
Holds to	24, highest sampled
Nearest value that changes it	1
The answer there	3 carried, Baseline to as built comparison

What an unchanged region does and does not prove is set out in a short lesson.

Every admissible integer in this range was checked. Values outside the range remain unchecked.

Here is the maths

The formula, in words

For each method, list every declared record demand that the typed file does not meet. A method is carried only when that missing list is empty. Among carried methods, name the one with the fewest declared demands, then use alphabetical order to settle a tie.

A worked example

The file is retrospective and has a checked baseline, 3 status dated updates, a sequence as built, dated delay events and records of logic changes.
The baseline comparison, collapsed comparison, periodic update comparison and reconstructed path are carried, so the count is 4 of 5.
Four carried methods have declared demand counts of 4, 4, 6 and 4. Alphabetical order settles the 3 way tie at 4, so baseline to as built comparison is the name returned.

What this does not model

The matrix is an independently authored record demand check. It does not reproduce a sold protocol, its categories, a selection table or its wording.

A carried row says only that the typed file contains the demands declared here. It says nothing about quality, admissibility, causation or entitlement.

The name returned by the tie rule is not a method choice and not professional judgement.

What the sweep holds fixed

Only the contemporaneous update count moves from 0 through 24. The perspective and the other 6 record facts stay fixed. The first possible periodic comparison change is checked at 2 updates.

Source anchors

These public sources describe approved plans, schedule maintenance, progress records and dated impact information. They provide practice context only, and no selection taxonomy or method table is reproduced.

The record demand matrix and the tie rule belong to this page.

The whole record prints. Your browser can save it as a PDF instead of printing it.

A request to choose a method or decide entitlement is refused. A carried method is only a result of the record demands declared on this page, and the mechanically named method is not advice, a suitability finding or a contractual conclusion.

Record support audit