With the rapid growth of digital scheduling tools, data
analytics, and artificial intelligence, it is easy to assume that
delay analysis has become a purely technical exercise. Programmes
are more detailed than ever, software outputs look increasingly
precise, and analyses can be produced at the click of a button.
But anyone who has spent time on real projects or in front of a
tribunal knows this is not how delay analysis works.
Despite all the advances in tools and technology, the
fundamentals have not changed. Delay analysis is not a mechanical
or automated process. It is, and always has been, a balance of
science, art, and common sense.
This article is not about promoting one methodology over
another. It is simply a reminder that credibility in delay analysis
does not come from methodology alone. Tribunals want to understand
what was planned, what actually happened, why it happened, and
whether the conclusions make sense when viewed against the reality
of