What happens on site reaches the numbers
A delay is not an administrative event — it is a cost. An unclosed snag is retention that does not release. An old drawing built to is rework. These modules tie the site to the figures, so the decision rests on both.
The questions it answers
The questions that turn into money two months later.
"How far behind are we?"
The baseline is frozen and actual progress compares against it — and the schedule performance index tells the story in one number.
"Whose delay is it?"
Each delay carries its cause, its owner and its documents — so a claim is supported, and a delay caused by the client is an extension of time rather than a penalty.
"Were those snags fixed?"
A snag with its zone and severity; the contractor claims the fix and the owner accepts it — no "it’s been done".
"Which revision was it built to?"
One current revision per drawing, and a register of every revision with its date and reason. So work built to an old copy is never untraceable.
What is inside
Six modules for managing execution.
How it connects to the rest
No module works alone. These are the links that keep the numbers consistent.
Project costing
Activities are tied to project items — so a delay shows in cost, not only in the schedule.
Certificates
The progress percentage you certify is the same one in the schedule — never two numbers.
Handover & retention
Retention release is tied to closing out handover snags.
Correspondence & claims
The delay letter and the RFI, with their dates, are the evidence behind a claim when you need one.
Try it on a live project
A project under construction: its schedule, its snags and its drawings — and watch the delay become a number.