Get the time extensions you're owed
Every entitled delay day you lose is a day of LDs you didn't have to pay. DelayFlow makes sure the notices land, the evidence sticks, and the time you're owed gets approved.
Built for GC project teams
Don't let delays turn into liquidated damages.
Projects slip — and when they do, the time extensions you're owed and the LDs you're trying to avoid both come down to one thing: whether the notice process held up. DelayFlow keeps it tight and the entitlement case airtight, so delays don't turn into damages.
Built by PSP-certified claims professionals — so your PMs don't need to be.
Delay Event
Owner access restriction
Notice due tomorrow
14 days
impacted
$7,800/day
general conditions
$109,200
at stake
LD risk:
Active
Next step
Send written notice before the contract window closes.
"Make the case" checklist
Delay event logged
Notice requirement found
Photos and daily reports attached
Schedule activities selected
Draft time request started
Timeline
Build Time RequestMay 3
Access blocked
May 4
Field note added
May 5
Photos uploaded
May 6
Notice draft ready
May 7
Time request started
85% of construction projects run late
14 days is the typical notice window
$8,500 average daily LD + GC exposure
One missed notice can cost more than a year of DelayFlow
Recover the extended general conditions sitting in your record
Extended GCs are real money — and most PMs never recover them because the record doesn't connect the dots between delay events, schedule impact, and daily cost. DelayFlow does that work as the project runs.
Keep LDs off the table entirely
Liquidated damages get assessed when the record can't defend the delay. DelayFlow builds the record from day one, so by the time anyone reaches for an LD clause, the entitlement case is already standing.
Exposure calculator
One missed notice costs more than a year of DelayFlow.
Enter your project duration, daily LD rate, and daily extended general conditions. DelayFlow shows you the dollar exposure tied to time you're already entitled to — time the notice process either preserves or forfeits.
Start free workspacePotential exposure protected
$229,500
This model assumes DelayFlow helps your team preserve 5% of project duration as compensable time. On most projects, the actual recoverable time is significantly higher — 5% is the conservative case.
Protected days
27
Daily exposure
$8,500
Project days
540
The conservative model above typically shows six-figure exposure on a single project. The cost-benefit math doesn't require a finance team.
AI notice workflow
Complicated notice processes, made simple enough to actually run
Every construction contract buries the notice process in dense language most PMs read once and never look at again. DelayFlow reads it on every delay event and turns it into a workflow your team can actually follow — without becoming claims experts.
Reads your contract
DelayFlow pulls the notice provisions out of your actual contract: deadlines, required recipients, content requirements, response windows. Not a generic template. Your contract, your terms, your clauses.
Builds the workflow for every delay
Each delay event gets its own tracked notice process. Your PM sees what's due, to whom, by when, and exactly what evidence the contract requires. No legal interpretation required.
Drafts the notice letter
When a delay is logged, DelayFlow produces a contract-aware notice letter referencing the right clause in language your PM can review and send the same day. The drafting work that used to mean digging through the contract and starting from a blank page is mostly done before your PM opens it.
Built by people who've defended these claims
DelayFlow was built by PSP-certified claims professionals with published work in forensic scheduling. The product knows what a defensible record looks like because the people who built it have built one — many times, under scrutiny.
Notice compliance
Contract-required. PM-friendly.
Contract rights are protected by process — but only if the process is simple enough to run on a busy job. DelayFlow ties every delay to its required notice, owner response, evidence, and schedule impact in one record, in one view, on one screen your PMs will actually open.
01
One view of every delay
Active events, notice deadlines, entitlement status, and LD exposure on a single screen. No more guessing which project is quietly going sideways.
02
Notice deadlines that don't slip
Every required notice and response date, tracked by project, event, and contract. PMs see what's coming before it's late.
03
One record your team works from
PMs, project controls, and leadership look at the same delay record. No reconciling spreadsheets the week before closeout.
04
The facts behind every day you're owed
Photos, correspondence, RFIs, and schedule impact connected to each event — so the entitlement case is ready when the owner pushes back.
LD prevention
LDs are won and lost in the first 14 days
By the time liquidated damages are on the table, the record is either defensible or it isn't. DelayFlow keeps notice status, entitlement, and next action visible from the first delay event — not the day the owner sends a letter. The work happens while the facts are fresh and the team still remembers what happened.
85%
of construction projects run late
5%
of project duration is what DelayFlow's ROI model conservatively assumes you can preserve as compensable time
$315k
sample event impact preserved in the record
Delay action list
17 active items
8 overdue
DF-001
Notice deadline missed
3 days overdue
DF-002
Missing evidence
2 days overdue
DF-007
Draft notice required
Due today
DF-011
Evidence review required
Due May 19
Next action
Send contract notice for steel delivery delay.
Event impact
DF-001
Notice deadline missed
Cost impact
$315,000
Time impact
7 days
Evidence files
14
Steel delivery delay reported
Field team records first delay event and owner-facing summary.
Schedule impact added
Critical path impact is tied to the same event record.
Notice package ready
PM has the evidence and notice language in one place.
Action list
The shortlist of what's late, what's owed, and what to send today
DelayFlow surfaces only the delays that need attention: notices due, evidence missing, schedule review required, leadership visibility needed. Your PMs stop wondering what's slipping. Leadership stops being surprised at closeout. Nobody has to maintain a parallel spreadsheet to keep track.
AI notice drafting
Contract-aware notice letters drafted from the delay facts and the contract's notice requirements. Review, edit, send — same day.
Notice deadline tracking
Every required notice and response date visible before rights are waived. The system reminds your PMs before the clock runs out.
Exposure reporting
The events, days, dollars, and missing proof behind each project's risk — in language leadership can act on without translation.
Delay record
One event. One record. Everything the entitlement case needs.
A defensible delay claim is built from documentation that was captured when it happened — not reconstructed at closeout from memory and a Dropbox folder. DelayFlow makes the capture part of the workflow, not a separate task someone has to remember to do.
Record the delay
Capture the issue while the facts are fresh and the people involved still remember the details. Field-friendly and mobile-ready. Logging an event is fast enough that PMs will actually do it in the moment, not at the end of the week.
Track the notice requirement
What notice is required, who owns sending it, when rights expire, pulled directly from the contract clause that governs the event.
Attach the proof
Photos, emails, RFIs, schedule fragments, and field notes tied to the event, not scattered across drives, inboxes, and someone's phone.
Preserve entitlement and recover GCs
Scattered facts become a record that supports time extensions, recovers extended general conditions, and shuts down liquidated damages before they get traction.
Questions
Questions worth asking
What does DelayFlow do?+
DelayFlow turns your contract's notice requirements into a tracked workflow. When a delay happens, your PM knows what to send, who to send it to, by when, and with what evidence — and gets a draft letter to review. The result is a defensible record for time extensions, recoverable extended GCs, and a clean defense against LDs.
Will my PMs actually use it?+
That's the right question. DelayFlow is built around a single workflow: log the delay, follow the prompts, send the notice. The interface is built around how a PM already thinks about a delay: what happened, what's due, what proof we have — not around claims theory or scheduling software conventions. Most PMs are productive on day one.
How does AI fit in?+
DelayFlow reads the notice provisions in your actual contract, builds the required workflow for each delay event, tracks every step, and drafts a contract-aware notice letter for your PM to review and send. The PM is always in the loop. Nothing leaves your workspace without human review.
Who created DelayFlow?+
DelayFlow was built by PSP-certified claims professionals with published work in forensic scheduling and delay claims. The product reflects what a defensible record actually looks like because the people who built it have built one many times.
Who is DelayFlow for?+
General contractors running projects with serious notice requirements and real LD exposure. Public work, private commercial, healthcare, industrial, higher-ed — anywhere the contract has a notice clause and the owner has the leverage to enforce it. Specifically the PMs and project controls teams responsible for protecting time extensions, recovering extended general conditions, and keeping liquidated damages off the table.
How does this fit with our existing PM tools?+
DelayFlow runs alongside Procore, P6, and whatever else your team already uses. It owns the delay-specific workflow — event, notice, evidence, entitlement, exposure — and doesn't try to replace anything else.
Is the AI going to do something stupid on its own?+
No. DelayFlow drafts; your PM reviews and sends. Every notice letter is human-approved before it leaves your workspace. The AI's job is to make sure nothing falls through the cracks, not to act on its own.
How secure is our project data?+
Project data lives behind authenticated workspace access, scoped to your team. We don't train models on your contracts. Security questionnaires and SOC 2 documentation available on request.
What does it cost?+
Pricing is per active project per month, with volume discounts for portfolios of 10 or more active projects. 6-month minimum per project. Run the exposure calculator above — for almost any project, one preserved notice covers more than a year of the platform.
Pricing
Priced per project. Built to pay for itself on the first one.
One preserved notice on one project typically covers more than a year of DelayFlow. Run the exposure calculator above if you want the math.
Project
For GCs running a focused project portfolio.
$799
per project,
per month
per month
Includes:
AI notice workflow on every project
Contract-aware notice letter drafting
Notice deadline tracking and action list
Delay event records with evidence library
Exposure reporting for leadership
Unlimited contracts uploaded per project
Up to 10 users per workspace
6-month minimum per project. Add projects any time.
Start free workspacePortfolio
For GCs managing 10 or more active projects.
Recommended
$495
per project,
per month
per month
Everything in Project, plus:
Volume pricing across all active projects
Portfolio-level exposure dashboard
Cross-project notice and entitlement reporting
Priority onboarding and support
Unlimited users per workspace
6-month minimum per project. Add projects any time.
Talk to usNot sure which tier fits? Most GCs running 3 to 8 active projects start on Project. Teams with a steady book of 10+ concurrent projects save meaningfully on Portfolio. You can move between tiers as your active project count changes.
Be ready when delays happen.
Track every notice. Preserve every day you're owed. Recover the GCs sitting in your record. Keep LDs off the table — by building the case as the project runs, not reconstructing it under pressure later.
Start free workspace