WorkflowCapital Projects & Commissioning

Construction Claims Management

Construction claims management that tests each delay event against the path as it really ran, traces each dollar to a record, and keeps legal points with counsel.

See the demo Book a demo

Follow one delay event through counsel to a signature ↓

The problem

A contractor’s final claim, and six weeks to answer it

The contractor’s final claim lands with two dozen delay events and a mountain of letters, minutes, schedule updates, daily reports and timesheets behind it. People who lived through the worst months have moved to other jobs, and the response clock is already running.

A drawing that ran weeks late may have moved the finish by far less, because the critical path had already left it. Nobody sees that unless the path is drawn window by window. Notice dates get counted from the wrong letter, and the other side’s best argument turns up after the position is signed.

Built forContract claims leadsDelay analystsCommercial managersLegal counselInternal auditors

The Problem Today

A final claim mixes days that moved the finish with days that did not, across records nobody can read in time.

3,107: hours to skim the claim’s records at a minute each our estimate

Assembled from five systems today

Letters
Schedules
Daily logs
Cost files

Notice clocks miscountedOne date in the minutes can move a whole clock
Their best reply comes lateIt arrives after the position is signed

The Solution

Windows, then the pathThe job cut at schedule updates, with the critical path as it really ran
Each event testedClaimed days set against the days that moved the finish
The other side repliesThe strongest reply from the same record, before anyone signs
Each dollar to a recordTimesheets, invoices and hire traced; the rest named as unproven

Built-in controls

Agents draw no legal conclusions
Whoever decides an event cannot check it
Legal hold; privileged notes stay out

What You Get

Your team signs a position it can defend, knowing its weak points before the other side raises them.

A cited responseEach line carries its source, or it cannot go out
Exposure in plain numbersWhat it nets to if the strong replies land
Clocks counted both waysEach notice clock shown from each start date argued

One event, 15 days left

Construction claims management on a 41-day event that moved the finish 12

A marine terminal expansion finished 147 days late, and the contractor’s final claim asks 112 days and $148.6M on 23 delay events. This is the day the owner’s side settles the largest one, with 15 days left on the response clock.

demoTerminal, companies, people, dates and dollars in this walk are sample data, made up for it.

0115 days left
112 days claimed, and a draft position of 52 before anyone signs
Contract claims lead
The ribbon draws the job in 14 windows, cut at the schedule updates, with the critical path as it really ran across the jetty, tanks, compressors, pipe rack and piping. Each delay event sits where it happened. The agents’ draft reads 52 days and $13.1M, not signed. Her next step is the compressor vendor data event, which counsel has to read first.
02The event
Drawings 41 days late, and only the first 12 moved the finish
Contract claims lead
The event file lines up what the record shows, each entry cited: the owner had to furnish certified compressor foundation drawings by a set date, and they arrived 41 days late. The compressor path held the finish for 12 of those days. Then inspection failed welds on rack modules, and the rack took the path. The draft is 12 days with money, $3,990,000.
03The decision
She cannot decide yet, because counsel has not read the notice point
Contract claims lead
The notice looks late: day 31 of 28 counted from the drawings’ due date, but day 28 counted from the minutes where the contractor said it would assess the effect. No agent calls a claim time barred. When the claims lead tries to agree 12 days, the screen stops her: the legal point is with counsel, and deciding now would settle it before he has read it.
04Counsel
Counsel reads the notice point, and his reading stays privileged
Legal counsel
Counsel sees the two counts and the owner’s own conduct: it acknowledged the notice and reserved rights without calling it late within the 14 days the clause allows. His choices are to keep the days and reserve rights, rely on a time bar, or ask back. He keeps the days. His reading is marked privileged and stays out of exports and the response.
05The decision
12 days with money, decided after counsel, with a reason
Contract claims lead
With both legal points read, the claims lead agrees the proposal: 12 days and $3,990,000, with the records and the windows as her reason. She cannot be the one who checks it. The event goes to the commercial manager, and the trail shows counsel read first.
06The check
The commercial manager must open three sources before she can sign
Commercial manager
The check panel lists what she must open herself: the two schedule updates that show the path leaving the compressors, and the notice letter. She opens each record herself, after the decision. Only when all three are opened does check and sign become live. An open by anyone else does not count for her.
07After
The event is signed, and the ribbon still reads draft
Commercial manager
Back on the ribbon, under her own name, the event shows signed. The position stays a draft, 52 days and $13.1M before damages, until each event is decided and checked and the position itself is proposed and signed. The response clock still reads 15 days.

Where the $148.6M claimed goes in the draft position

Each claimed dollar falls into one of three places.

No record behind it	$54,414,000
Traced, but not tied to an owner delay	$81,048,000
In the position, line by line	$13,138,000
Claimed	$148,600,000

demoSample data, from the working solution.

What the position nets to, and what happens if their replies land

Delay damages are $306,000 a day and stay on the days that remain the contractor’s.

Case	Days	Owner pays	Net
This position	52	$13,138,000	$15,932,000 to the owner
Strong replies land	57	$15,718,400	$11,821,600 to the owner
Strong and fair replies land	86	$19,310,400	$644,400 to the contractor
After a time bar	40	$9,148,000	$23,594,000 to the owner

demoSample data, from the working solution. The other side’s replies are written from the same record before anyone signs, and counsel reads them first.

Around the claim

Concurrent delay, notice clocks and the cited response

Six more screens the claims team, the delay analyst and counsel work from.

Windows analysis for one window: rack modules took the critical path, 31 days lost, compressors 10 days behind on float — **Window 9, where the count stops**The rack took the path and lost 31 days; the compressors sat 10 days of float behind, so the rule reads one path. Taken after the signature.

Concurrent delay view: two windows where two paths held the finish together, and one window that is not two causes — **Two paths at once**One rule for every window: two paths hold the finish together only if the second is within 3 days of float. Two windows meet it.

Notice clocks for all 23 events: days counted from the event date, the late or missing notices, and whether the owner objected in time — **Notice clocks, both ways**Each event’s clock from the event date. The compressor event adds the count from the minutes and whether the owner objected in time. No agent calls anything barred.

Cost trace for a construction claim: claimed, traced and position by head of claim, with lost productivity lines and their records — **Each dollar traced**Seven heads of claim, from claimed to traced to the position, lost productivity summed by event, and the lines with no record ready for a request.

Response to the claim drafted line by line from decisions, each with its cited records, privileged notes left out — **The response, cited**Drafted line by line from decisions, each line carrying its source. Counsel’s readings and the other side’s replies stay out of the file.

Audit trail for a claim: agent runs, counsel’s privileged reading, the claims lead’s decision and the commercial manager’s check — **Audit trail**Each read, decision, check and signature by person or agent, with counsel’s reading logged as privileged and kept out of the evidence export.

demoSample data, from the working solution.

Who decides a delay event, who checks it, and who reads the law

Contract claims lead

Sees: The event file, the windows and the replies
Signs: Decides each event and proposes the position

Planning and delay analyst

Sees: The schedule update closing each window
Signs: Agrees the critical path, window by window

Legal counsel

Sees: Legal points, the other side’s replies and the hold
Signs: Reads first, asks back, keeps privilege

Commercial manager

Sees: The sources she must open herself
Signs: Checks each event and signs the position

Internal auditor

Sees: Every step and the evidence export
Signs: Reads only

Behind the ribbon

Eight agents read the record and argue both sides, and none states the law

Each one hands to a named person.

Record reader

Reads, dates and files each record.

Never changes a record

Window builder

Cuts windows and finds the path, days lost and driver.

Never rewrites a schedule update

Event builder

Builds the chronology and effect, each statement cited.

Never decides days

Notice clock

Counts each clause clock and shows other start dates.

Never calls a claim barred

Cost tracer

Ties cost lines to records and finds rate gaps.

Never prices without a source

Other side reader

Writes the strongest reply from the same record.

Never gives legal advice

Response drafter

Drafts the response from decisions, line by line.

Never states a legal conclusion
Never quotes privileged notes

Hold and privilege guard

Keeps the hold and filters exports.

Never lifts a hold

What owners’ claims teams ask about construction claims management

What is construction claims management?

Construction claims management is how a party assesses and answers delay and cost claims on a project. Here, for the owner, agents draw the critical path window by window, test each delay event against it, count notice clocks and trace each claimed dollar to a record. People decide each event, counsel reads the legal points, and the commercial manager checks each one.

How does it handle an extension of time claim?

Each event’s claimed days are set against the days it moved the finish, using the schedule update that closes each window. Days on another path stay the contractor’s, and time-only days are kept apart from days with money.

Is this forensic schedule analysis?

It uses a windows approach on the contractor’s own schedule updates, without rewriting them. A practitioner should still review the windows; the screen shows how sure each path finding is.

How is concurrent delay treated?

With one rule in every window: two paths hold the finish together only if the second is within a set number of days of float. Windows that meet it go to counsel.

How does this construction claim software keep privilege?

Counsel’s readings and the other side’s replies are marked privileged and stay out of the response and the evidence export. A legal hold lifts only with counsel and the commercial manager together, and never while the claim is open.

Does it work for contractors building a claim?

No. It answers claims for the owner’s team: the claims lead, the delay analyst, the commercial manager and counsel. It does not build a contractor’s claim.

Capital Projects & Commissioning