Skip to main content
Schedule Intelligence

Every delay, with its cause
and its impact.

Storia reads your schedule and the record around it, so every slip arrives with its cause attached and its damage already mapped.

Send us a P6 fileSee the trace
  • Primavera P6
  • MS Project
  • XER
  • Asta
  • Project documents indexed
  • Version aware

Delay analysis

The screen a scheduler opens on Monday.

Delay analysis · North Slab / L7 envelopeSchedule v3 · weeks 14 to 22

BaselineCurrentCritical slip

ACT 104Curtain wall installRFI 247 · anchorage
+11d
ACT 112MEP rough-inDIR 18 · stop work
+9d
ACT 128Drywall level 7CR 09 · added reinf.
+8d

Downstream impact

+11 critical-path days

pushed onto substantial completion, from a single unanswered clarification.

  • ACT 104 · Curtain wall+11d
  • ACT 128 · Drywall L7+8d
  • ACT 134 · Ceiling grid+6d

3 activities affected · 1 driving event

The gap

The schedule lives in one tool. The cause lives in three.

68%Reported

of major construction projects miss their contract completion date.

KPMG · Global Construction Survey

14¢Recovered

of delay-claim dollars are backed by documentation tying event to impact.

AACE recovery benchmarks

How it works

Two moves. One story per delay.

02 / 02 · Explain

Every slip, traced from cause to consequence.

We compare the schedule against its prior versions, mark the activities that moved, and read the linked documents to explain why. The output is one line: this event, this activity, these consequences.

  • Version-to-version comparison on every upload
  • Moved activities attributed to a driving event
  • Downstream effects mapped, not just the first slip
Cause & effect · ACT 104Traced
1
Caused byRFI 247 · Apr 09Curtain wall anchorage clarification, unanswered 18 days.
2
Which movedCurtain wall install+11dStart pushed to May 06 on the v3 replan.
3
Which brokeDrywall L7, ceiling gridTwo successors off the critical path and onto it.

Window delay0d

Finish date unchanged this update.

Float erosion−11d

Buffer lost on the critical path.

Three clicks

One delay, end to end.

Curtain wall slipped 11 days. The cause is sitting next to it.

Click the slip. The linked RFI surfaces in the same view, with downstream impact already mapped.

Cause identified in 2 seconds · not two afternoons

Impact map · RFI 2473 affected
SourceRFI 247 · curtain wall anchorageApr 09

Direct

ACT 104Curtain wall install+11d

Downstream

ACT 128Drywall level 7+8d
ACT 134Ceiling grid+6d

One document layer. Three products.

See how the four products share one record

Why we win

Schedule analysis, with the paper trail attached.

Document aware

A slip without a cause is a guess.

The slip and the document that caused it sit next to each other. Which RFI raised the issue. Which directive paused the work. Which change request reshaped the scope.

  • Cause field populated from the record, not typed by hand
  • Every attribution opens the source page it came from
  • Unattributed movement is flagged rather than smoothed over

A specialist scheduling tool

ACT 104 · Curtain wall+11d

Cause

no cause recorded

Storia

ACT 104 · Curtain wall+11d

Cause

RFI 247Anchorage clarification, open 18 days
DIR 18Stop work, south face
Version aware

Baselines drift. We keep score.

Every revision is a fact. We mark the activities that moved between versions and attribute each move to the event that drove it. The history is queryable, not lost.

  • Every uploaded revision retained and comparable
  • Movement between versions attributed to driving events
  • Nothing rebaselined behind the scheduler’s back
Version history · substantial completion4 revisions
Baseline
Jun 02 · as-tendered
n/a
v2
Jun 02 · Mar 14 update
0d
v3
Jun 13 · Apr 30 update
+11d
Current
Jun 14 · May 06 replan
+12d

Drift attributed to RFI 247 DIR 18

Who buys it

Different buyers, same missing layer.

01

Owners & PMO consultants

One version of the truth across the portfolio. Every slip explained by a document they can cite.

TruthExplanationPortfolio

“My GC tells me the schedule's fine. I need a second opinion that's read the same RFIs.”Program director · public infrastructure

02

General contractors

Defend the schedule against scope creep. Accelerate the claim when the slip wasn't theirs.

DefendAccelerateRecover

“We're losing claims on documentation, not on merit. Storia closes that gap.”Commercial manager · general contractor

03

Schedulers

Live in the file. Validate the depth before anyone above them adopts the tool.

TechnicalIn the fileValidators

“I'll use it if it respects my logic and doesn't rebaseline behind my back.”Lead planner · tier-one contractor

Inside the product

Three views.

Delay analysis

Click any activity to see the slip, the prior versions, and the events that explain the move.

Open the view

Schedule

The active schedule with every prior baseline beside it. Filter by trade, area, or version.

Open the view

Impact map

Pick one event. See every activity it touched: direct, downstream, parked.

Open the view

Reads your files

Your schedule, your PMIS, unchanged.

SchedulesPrimavera P6
SchedulesMS Project
ExportXER & XML
SchedulesAsta
PMISProcore
PMISOracle Aconex

On your own data

Send us one P6 or MPP file.

No deck. No discovery call. Bring a schedule, share the documents you already have, and we walk through the slips Storia finds in thirty minutes.

Book a demo Ask a question
  • Your file
  • NDA friendly
  • 30 minutes
Drop a schedule file

P6 · MPP · XER · Asta supported

Schedule Intelligence Platform for Construction · Storia