---
title: "Spotting schedule delays in construction projects early: critical path, float and snapshots"
excerpt: "A delay announces itself weeks ahead, in an email, a shrinking float, a predecessor that slipped. Three questions to the schedule surface it in time."
publishedAt: "2026-11-14"
updatedAt: "2026-11-15"
readTime: "6 min read"
author: "Simon Schwer"
tags:
  [
    "Construction",
    "Scheduling",
    "Schedule Delay",
    "Critical Path",
    "Project Controls",
    "AI in Construction",
    "Project Management",
    "Context-Driven Project Management",
  ]
featuredImage: "/images/blog/construction-schedule-delay-early-warning-hero.webp"
featuredImageAlt: "Illustration: a message travels from a building site with a crane to a schedule. One chain of bars is highlighted and ends at a flag; dashed outlines mark earlier dates."
featuredImagePosition: "center"
sources:
  - title: "VOB/B § 5, time limits for execution (German)"
    url: "https://lxgesetze.de/vob-b-2016/5"
    publisher: "lxgesetze.de"
  - title: "VOB/B § 6, hindrance and interruption of the works (German)"
    url: "https://lxgesetze.de/vob-b-2016/6"
    publisher: "lxgesetze.de"
  - title: "Damages for hindrance and interruption, on Federal Court of Justice ruling VII ZR 224/00 of 21 March 2002 (German)"
    url: "https://www.bauprofessor.de/schadenersatz-behinderung-unterbrechung/"
    publisher: "bauprofessor.de"
---

On Tuesday the shell contractor's foreman writes that the slab over the third story will be three weeks late. His crew is stuck on another site. The email goes to the site manager, who has two inspections that day. In the schedule, the shell still ends on the old date. Two weeks later, in the weekly coordination meeting, the window installer asks whether his slot still stands.

The information was there long before any date was missed. It just was not in the plan. So on that Tuesday nobody knows what three weeks mean for handover.

You can spot a delay early if the schedule answers three questions at any time. Which chain of activities determines the end of the project? How much float is left before that date? What has moved since the last snapshot, and why?

## What are the early signs of a schedule delay?

Each sign looks small by itself:

- A predecessor finishes later, and its successor still sits on the old date.
- The float before handover is smaller than four weeks ago, and nobody decided that.
- An approval is overdue, such as sample approvals, shop drawings or the independent structural check.
- A subcontractor has given notice of a hindrance, and nobody carried the effect into the schedule.
- An item with a long lead time has not been ordered yet: windows, the elevator, ventilation units.

None of these shows up in a bar chart by itself. They sit in emails, in the meeting minutes and in the site manager's head. Overdue approvals and open orders stay invisible to any scheduling tool as long as they are not activities in the plan. That is why they belong there.

## What does the critical path tell you, and what does it not?

The critical path is the chain of activities that determines the planned finish. If one activity on that chain slips by a day, the planned finish slips by a day. Whether handover still holds depends on the float that is left before it. Every other activity has room.

Take an apartment building with twelve units, heavily simplified. The chain runs from the shell through the roof, the first fix of building services, interior plaster and screed to flooring and painting. Between the end of painting and handover there is one week of float. In this example, windows and exterior works are not on the chain.

Now Tuesday's email arrives. The shell ends three weeks later. The roof can only start after that, the first fix only after the roof, and so on down to the painter. One week of float becomes a two-week overrun. The windows move along but stay non-critical. The exterior works do not move at all.

![Simplified example schedule: after a three-week delay in the shell, every activity on the critical path moves, the exterior works keep their dates. The forecast finish is two weeks after the project end.](/images/blog/construction-delay-critical-path-example-en.svg)

The critical path shows where speeding up wins the end date back. The first lever is the shell contractor, for instance with a second crew. After that come the activities on the chain, such as a fast-drying screed or mechanical drying. A second crew on the exterior works changes nothing about handover. With every week that passes before the decision, fewer activities are left where time can still be recovered.

The critical path only works with what is in the plan, though. A bar chart without dependencies has no critical path, it only has a last row. And a plan in which the shell still ends on the old date shows a week of float that no longer exists.

## What has moved since the last snapshot?

The critical path describes today's plan. Whether trouble is building up only shows when you compare it with last week's plan and with the contract schedule. That takes saved snapshots, namely the baseline everyone agreed on and regular ones in between.

The comparison answers questions that get lost in daily business. Which activities have drifted since the baseline, and by how many working days? Does a shift follow from a predecessor, or does it have a cause of its own? Has the float been shrinking three weeks in a row?

Every shift needs its reason, written down on the day it happens. That matters at the latest when money is in dispute. VOB/B, the standard contract terms used for most German construction work, assigns duties according to the cause. In the example the cause lies with the shell contractor. If his workforce is plainly insufficient to meet the deadlines, he has to remedy that without delay when the client demands it (§ 5 (3) VOB/B). The follow-on trades that cannot start because of the shell in turn give written notice of their hindrance without delay (§ 6 (1) VOB/B).

A party that later claims damages for a hindrance will, according to the German Federal Court of Justice, as a rule have to present it specifically and tied to the actual construction sequence (ruling of 21 March 2002, VII ZR 224/00). Weekly snapshots with recorded reasons give you that account. The same snapshots let you check such an account when it comes from the other side. Memory and an inbox full of emails rarely manage either a year later.

Other jurisdictions have their own notice and record-keeping rules, and the practical point is the same. None of this is legal advice. It is meant to explain why keeping the record pays.

## A routine for every week

The three questions are not tied to a particular tool. Any scheduling program that knows dependencies can answer them, MS Project or Asta Powerproject for example. What it takes is four things every week, ideally before the coordination meeting:

1. Save the plan before you change anything.
2. Enter everything about dates that came in since last week: emails, minutes, phone notes.
3. Look at the critical path and the float. Has the float shrunk?
4. Compare the plan with last week's snapshot and note the reason for every shift.

The second step takes most of the time. It is where the routine breaks down in a busy week, and it is where an AI can help.

## What can AI take over here?

Two chores above all stay undone in the office because they take time and belong to no one: getting news into the plan, and explaining what changed.

For the first, an AI project agent reads the foreman's email, recognizes that it concerns a date and proposes the change: shell ends three weeks later, new risk for handover. The site manager confirms the proposal, corrects it or discards it. Without confirmation nothing changes in the plan.

For the second, the AI pulls up the emails, minutes and decisions that belong to each shift between two snapshots and turns them into a draft report for the client.

The calculation in between needs no language model. Which successors have to move and how much float remains is worked out by scheduling logic, as in any scheduling program.

What stays with the site and project managers is the decision whether to accelerate, who pays for it and how to tell the subcontractor. The legal assessment does not belong in the hands of an AI either.

One caveat comes from our own measurements. In our benchmark ProjectBench, 14 AI models each built a plan for a single-family house and then received the same message: shell start three weeks later, EUR 25,000 less financing. In two plans not a single task date moved afterwards, and in only five did the change reach tasks, milestones, project end date and decision log together. Several replies in the chat reported adjustments that the stored plan did not contain. The details are in [Which AI model plans a project best?](/blog/projectbench-one-change-half-the-plan).

So do not rely on the reply in the chat. Whether a change has arrived shows in the comparison with the last snapshot.

## What does this look like in TensorPM?

TensorPM is an AI project agent for the office side of construction: site managers, project managers and project controllers. Defects, the site diary and photos stay in tools such as PlanRadar, Capmo or Procore. TensorPM sits above them and keeps the state of the project together: dates, decisions, risks and budget.

For the three questions and the routine the app offers this:

- In the Gantt view, `Critical path` highlights the chain that determines the planned finish. Hover over a bar and you see its float in working days. If the chain ends after the project end, the Gantt shows the overrun, in the tooltip for example “Forecast: 10 working days past the project end”.
- Under `Snapshots` you save the schedule, set one snapshot as the baseline and compare today's plan with any earlier one. If the plan has changed, TensorPM saves a weekly snapshot by itself the first time you open the project in a calendar week.
- The comparison shows the reason for each shift where it is known, for example from the chat or from a linked decision. Where it is missing, you record it with `+ Document reason`, and it stays in the project as a decision.
- TensorPM does not move successors by itself. If a date contradicts its dependency, the forecast shows it, and the context menu offers `Align with dependencies`. Before you apply it, you see which tasks move by how many working days and what that does to the planned finish.
- Emails from a connected mailbox and documents you add pass through a review step. The agent proposes what changes in the project, and you approve.
- Starting from a comparison, the agent can look for causes in the project context, assess the effect on milestones and the project end, and suggest steering measures.

A few limits are worth knowing. The calculation counts working days from Monday to Friday and knows no public holidays. Dependencies carry no lag, so you plan waiting times such as screed drying as an activity of their own. Snapshots so far live only on the device where they were saved. And the critical path is as good as the dependencies kept in the plan.

## Back to Tuesday's email

Work this way and Tuesday's email is in the plan before the next coordination meeting at the latest. The two-week overrun is then a number you can discuss with the shell contractor and the client, and the window installer hears his new date from you before he has to ask.

If you want to try this on a project of your own, you can [try TensorPM for free](/getting-started). The app builds the first schedule from a project description or from documents you already have.
