Schedule risk AI that flagged a delay 5 weeks early on a $12M UAE project

Industry

Construction

Market

UAE

Client

Construction contractor in the UAE

Sponsor

Project Director

What we built

Schedule risk and procurement AI

The situation

On a construction project, most delays are visible long before they happen, just not to anyone who is looking at the right combination of information at the right moment. A long-lead item is ordered late. A submittal sits in review. A supplier's delivery date slips. Individually these look manageable. Together, on the critical path, they become weeks.

The client is a construction contractor in the UAE. The Project Director was, by their own account, a sceptic: construction AI felt like a gimmick. Their teams tracked schedules and procurement the way the industry does, through programmes, spreadsheets, meetings and experience, and discovered schedule risk when it was already expensive to fix.

What we built

A schedule risk system that watches the programme and the supply chain together and warns when they are drifting apart.

The schedule, understood. The project programme is ingested with its activities, dependencies and critical path, so the system knows which dates matter and which have float.

Procurement connected to the programme. Purchase orders, supplier lead times, submittal and approval status, and delivery dates are linked to the activities that depend on them. An item is no longer just "late"; it is late against a specific activity with a specific amount of float.

Delay risk scoring. The system continuously assesses which upcoming activities are at risk and by how much, based on the state of their inputs and on patterns from past work, and explains the driver: which item, which approval, which dependency.

Early warning that reaches decision-makers. Risks above the threshold are surfaced to the project team with the cause and the time remaining to act, while there is still room to reorder, expedite, resequence or substitute.

A project controls view. The Project Director and planners see risk across the programme in one place instead of piecing it together from separate reports.

How it went live

The system was set up on live projects using the contractor's existing programme and procurement data, with planners reviewing each flag against their own understanding of the project. That review loop tuned the thresholds so the warnings were ones the team would act on.

Results

On a $12M project, the system flagged schedule delay risk five weeks early. With that lead time, the team made a procurement adjustment that avoided three weeks of delay. The Project Director's conclusion: the system paid for itself on that single project many times over.

What made the difference

Connecting procurement to the critical path. The risk was never invisible; it was in data nobody was reading together.

Lead time, not just detection. Five weeks of warning is what turned a delay into a decision.

Warnings the team trusts. Tuning with the planners meant the flags were acted on rather than ignored.