Skip to main content

Privacy

A note about cookies

Essential cookies keep this site running. Optional analytics help us understand what's working, only enabled if you accept.

Schedule Intelligence

Every delay, with its cause and its impact.

Storia reads your schedule and the record around it, so every slip arrives with the document that caused it and the activities it pushed. Then it writes the delay report.

  • Primavera P6 and MS Project
  • Every update compared
  • Nothing written into your file
Delay analysis · lab wingSample project
  1. A2120Lab wing structure
  2. A2140IFC, lab wing+73 d
  3. A2165Level 3 HVAC coordination+9 d
  4. A2172Lab ventilation package+6 d
Caused byChange orderCR-014 · Level 3 lab layout changewaiting 108 d

BaselineUpdate 22 AprCritical slip

3 causes traced · in your delay report

How it ties in

From the slipped activity back to its cause.

The schedule on one side, the record behind the slip on the other. Storia holds the moved activity against the documents that caused it, and writes the delay report.

Delay report

The delay report sets every slip against the baseline, names the event behind it and counts the days each party added.

  1. 01

    Slips since the last update, with their causes

  2. 02

    Critical path days, by party

  3. 03

    Linked documents for every line

See a full sample report →
02 / 02 · Explain

Every slip, traced from cause to consequence.

Storia compares the schedule with its earlier versions, marks what moved and reads the linked documents to say why. One line per slip: this event, this activity, these consequences.

  • Compared with every earlier version
  • Moves attributed to a driving event
  • Unexplained movement flagged, not smoothed over
Cause and effect · A2140Traced
  1. 1
    Change orderCaused by CR-014Owner decision waiting since 18 Jul
  2. 2
    ScheduleWhich moved IFC, lab wingFinish pushed on the 22 Apr update
    +58 d
  3. 3
    DrawingWhich held the HVAC layoutDWG-M-204 review waits on the decision
    +9 d

Float lost on the critical path: 73 d

Version aware

Baselines drift. Storia keeps score.

Every revision is kept and compared, and each move is attributed to the event that drove it. Nothing is re-baselined behind the scheduler's back.

RevisionData dateLab wing IFCDriven by
Baseline06 Jan 20260 dAs tendered
Update 0324 Mar 20260 dNo movement
Update 0422 Apr 2026+15 dDWG-M-204 review
Now, read from the record02 Nov 2026+73 dCR-014, DWG-M-204, SPEC-M-031
Who it is for

Different buyers, the same missing layer.

  1. 01

    Owners and PMO consultants

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

  2. 02

    General contractors

    Defend the schedule against scope creep, and move quickly when the slip was not theirs.

  3. 03

    Schedulers

    It respects your logic and stays out of your file. Validate the depth before anyone above you adopts it.

Schedule Intelligence

Send us a schedule. We will send back the causes.

Bring a P6 or MS Project file and the project it belongs to. In twenty minutes we walk you through every slip and what drove it.

Schedule Intelligence Platform for Construction · Storia