Resources
Delay analysis, explained without the jargon
Short reference notes we use with clients — method selection, the vocabulary that shows up in every determination, and the questions we get asked most.
Choosing a delay analysis method
As-planned vs as-built
Compares the original intent with what actually happened. Simple to present, weakest on causation — best as a supporting view.
Impacted as-planned
Inserts delay fragments into the baseline. Prospective and quick, but ignores contemporaneous progress.
Time impact analysis
Models each event against the update in force when it occurred. Widely accepted for prospective entitlement.
Windows / contemporaneous
Splits the job into periods and tests critical-path movement in each. Usually the most defensible retrospective method.
Collapsed as-built
Removes delay events from the as-built to infer a but-for completion date. Data hungry and sensitive to assumptions.
Scheduling glossary
- Total float
- Days an activity can slip without delaying project completion.
- Free float
- Days an activity can slip without delaying any successor.
- Critical path
- The longest logic chain driving the completion date; usually zero or lowest float.
- Data date
- The as-of date of a schedule update — everything left of it is actual, right of it is forecast.
- Concurrency
- Two or more delays affecting completion in the same period, with different responsibility.
- DCMA 14-point
- A standard health check covering logic, leads, lags, float, durations, invalid dates and CPLI/BEI.
Frequently asked questions
Do I need a credit card for the trial?
No. The 14-day trial unlocks every module with no card. Exports carry a trial watermark until you subscribe.
What happens when the trial ends?
Your projects stay safe and readable. Analysis and export features lock until you pick a plan.
Can I change plans later?
Yes. Upgrades and downgrades take effect immediately and are prorated by the payment provider. Cancelling keeps access until the end of the paid period.
Which files can I import?
Primavera P6 XER and XML, plus CSV and JSON. Your source file is never altered.
Who owns the data?
You do. Data is isolated per organisation, encrypted in transit and at rest, and can be exported at any time.
Is TideLine suitable for expert evidence?
It is built for it: reproducible runs from the original export, an audit trail of changes, and exhibits formatted for adjudication, arbitration and court.