What changed since the last update? Net slip, activities that moved, new critical items, float changes since your last submission.
Click or drop file
Baseline (.XER) — Optional
Unlocks full DCMA checks
Enables CPLI and BEI calculations in the Schedule Health check — required for a complete 14-point DCMA assessment.
Click or drop file
🔒 Nothing leaves your browser
Analysis coverage
Existing FloatCheck outputs
01
Project Overview
FloatCheck Engine
What is this programme? Activities, calendars, duration and data date, read straight from the file.
02
Is This Schedule On Time?
FloatCheck Engine
Forward and backward pass over the network, with the critical and near-critical path called out.
03
What Changed Since Last Update?
FloatCheck Engine
Activity-by-activity comparison against the previous update: dates, logic, durations, float.
04
Is This Schedule Healthy?
DCMA 14-Point Check
All fourteen checks scored pass, warning or fail, with the offending activities listed.
05
What's Happening in the Next 3 Weeks?
Lookahead
A three-week window generated from the data date, ready to take to a site walk.
06
What Needs to Be Ordered?
LeadTime Engine
Procurement dates worked back from installation, so long-lead items surface before they bite.
07
How Complete Is This Project?
Progress Engine
Progress measured against duration and remaining work, not a percentage someone typed in.
08
Where Can We Recover Time?
Crashing Workbench
Test duration cuts on critical activities and watch the completion date move before you commit.
🔒
Stays in your browser
No server, no upload, no data leaves your machine. Confidential programmes stay confidential.
⚡
Deterministic maths
Every number comes from real CPM code. Nothing estimated, nothing AI-generated.
📋
Primavera P6 XER
Supports standard P6 exports from any version, straight out of the box.
Plan / Analyse / Current schedule
Critical Path Gantt
Critical (total float ≤ 0) and near-critical (≤ 10 working days) activities, sorted by early start - from the same CPM run as the rest of this page, not a separate calculation.
Project Overview
Everything below comes straight from the uploaded schedule's own PROJECT row and this page's CPM run — nothing here is estimated.
Is This Schedule On Time?
Critical Path Timeline
Recomputed via CPM from current schedule logic and durations. Red bars are critical (zero float).
Watch These Next
Near-critical activities (1–10 working days of float) from this update alone — the ones most likely to become critical if anything slips.
Activity
WBS
Float
Early Finish
What Changed Since Last Update?
Prior Finish
—
Current Finish
—
Net Slip
—
Newly Critical
—
Project Finish — Dimension Check
Activity Variance Register
CriticalNear-criticalStable / healthy
Activity
Prior Finish
Curr. Finish
Variance
Prior TF
Curr. TF
Flag
Float Watchlist
Sorted by how fast float is disappearing between updates, not by where it sits today — an activity that dropped from 20 days float to 8 is a bigger near-term worry right now than one that's simply sat at 8 days both updates, even though a current-float-only view treats them the same.
Activity
WBS
Prior TF
Curr. TF
Δ Float
Trend
Is This Schedule Healthy?
The DCMA 14-point schedule quality audit, run against the current update, with a plain-English line under each check. Four checks require data this XER export doesn't carry (constraints, resources, baseline performance indices) and are marked accordingly — that's an honest gap, not a bug.
#
Check
Result
Threshold
Status
What's Happening in the Next 3 Weeks?
Activities starting or already active within the window from the current data date, ordered by start date and grouped by WBS (the closest thing to "who owns it" this file carries — no resource/assignee field is parsed).
Start
Activity
Duration
Finish
Float
Predecessor Status
What Needs to Be Ordered?
Activities auto-matched against a keyword library of long-lead materials, with an order-by date computed from that activity's own early start minus its typical lead time. Overdue items (order-by date already passed) are pinned to the top. Need to check one manually? Use the Procurement Lead Time Calculator.
Activity
Material
Lead Time
Early Start
Order By
Days Remaining
Float
How Complete Is This Project?
Physical % Complete (weighted)
Duration % Complete
—
Units % Complete
—
Cost % Complete
—
Progress Distribution
Quality Flags
Active, 0% Progress
—
100% But Not Marked Complete
—
Progress, No Actual Start
—
Duration % vs Physical % Divergence
Activity
Status
Physical %
Duration %
Divergence
Where Can We Recover Time?
Computed fresh from the current schedule's logic and durations. Max-crash-days and cost/day below are pre-filled with placeholder estimates (duration-based, not from any file field — this XER format carries no per-activity cost data) so the workbench is usable immediately; replace them with real numbers for an accurate result.
Activity
WBS
Duration
Float (CPM)
Max Crash (days)
Cost / Day Crashed ($)
Time – Cost Trade-off
Crash Sequence
Step
Activity Crashed
Cost this Step
Cumulative Cost
Resulting Finish
Recovered
Greedy least-cost heuristic: crashes the cheapest currently-critical activity one day at a time and re-derives the critical path each step. Correct for a single dominant critical path; where parallel near-critical paths exist, a full LP-based multi-path optimisation may find a lower-cost combination — treat this as a strong first-pass estimate, not a contractual figure.
Compare Two Scenarios
Uses the same cost/max-crash assumptions entered above, run against two different targets — and, optionally, a cost multiplier for Scenario B (e.g. 1.5× to model overtime/expedite rates), so you're not stuck seeing only one result at a time.