Nodes & Links, a UK maker of schedule analysis software, published a case study on November 20, 2026, from The Herne Group, a UK consultancy that manages defense and other regulated projects. Herne used the software to find and test ways to recover a defense project’s completion date after a client-ordered scope change pushed the forecast past a fixed deadline. The work it affects is schedule recovery: the time impact review a scheduler runs after a change, and the recovery plan that goes to the owner for approval.

What it does

On most jobs, a recovery plan starts with a scheduler copying the CPM schedule, trying out more shifts or overlapping activities, and rerunning the dates one scenario at a time. Each scenario is built and checked by hand before it goes into the owner meeting.

Nodes & Links reads the live schedule from Oracle Primavera P6, Primavera Cloud or Microsoft Project, and its homepage also lists connections to Aconex, Procore, Autodesk and Trimble. Herne’s team asked the software, in plain language, what options were left to recover the slipped completion date. The platform modeled extended working hours, fast-tracking, changes to schedule logic, earlier completion of documentation and resequencing. It showed each option’s modeled effect on the forecast finish, with the reasoning behind it.

People still decided what went into the plan. Herne’s project staff checked each option against crew availability, cost, sequencing and client requirements. The option with the largest effect was moving selected critical commissioning activities from a five-day to a seven-day week. Herne took that to the client with the supporting analysis and got approval.

Evidence so far

The evidence is a Nodes & Links blog post, a summary page for its downloadable guide, and a Construction Management article that follows the same account. Herne’s project controls director, Andy Garnett, is quoted in both the blog post and the article. The project is still in delivery.

These figures come from Nodes & Links and Herne:

Reported results on Herne's defense project
MeasureReported figure
Chance of finishing by the planned date, from a 1,000-iteration risk analysis0.2%
Cost of slippageAbout £80,000 a day
Recovery found in the first modeled scenariosUp to 39 calendar days
Improvement from measures in place by the next schedule update15 days
Movement of the P50 completion forecast within three months10 weeks earlier
Total recovery on the project8 weeks
Acceleration-related savings on the projectMore than £4 million
Source: nodeslinks.com

The guide page says the 15 days of improvement showed up in the September schedule update. Eight weeks at about £80,000 a day comes to roughly £4.5 million, close to the savings figure Herne reports for this project. The £14 million headline covers acceleration value across all of Herne’s live projects that use the software. The method behind acceleration value and the number of projects in that total are not yet public, so it is best read as Herne’s own measure.

Garnett said in the blog post that he knows of no other software that lets his team question a live schedule this way and find where recovery is possible. Construction Management reports that Aecom, Galliford Try Highways and BAM have also used the platform.

How to measure it on your projects

Track forecast finish movement per schedule update. At each update, record the forecast completion date and the number of calendar days it moved, split into days lost to new delays and days gained from recovery measures you put in place. If you run risk analysis, record the P50 date and the chance of meeting the contract date as well.

Capture the baseline before the pilot. Pull the last six updates on one job and log the same figures, plus the scheduler hours spent on each time impact analysis or recovery scenario. During the pilot, keep a log of every recovery option the software proposes, whether your team accepted it, and how many days it delivered at the next update. Herne’s account separates modeled recovery, up to 39 days, from delivered recovery, 15 days at the next update, and your log should keep those apart too. Our posts on tracking total float across updates and pricing delay from the liquidated damages rate cover how to put a dollar figure on the days.

A first step on one job: list the forecast finish date from each of the last six schedule updates in a spreadsheet, with one line on what moved it.

Availability and cost

Nodes & Links sells to owners, contractors and consultancies on capital projects, and its homepage says the platform has analyzed 23,000 projects in 23 countries. On November 17 it added a connection to Oracle Unifier, so RFIs and change orders can be read next to the Primavera schedule. The site does not list prices, and buyers start with a demo request. For other schedule tools reviewed here, see Trimble Connect Scheduling and the Oracle Primavera Cloud update.