Schedule quality
A schedule can look fine and be structurally unsound.
Open ends. Hard constraints propping the dates up. Negative float nobody has looked at since the last revision. None of it shows on a bar chart. All of it decides whether the finish date means anything.
All 26 checks, on every recalculation.
Every finding is clickable — it selects the activities or links it is complaining about. Numbers shown are the house profile's; switch to the published DCMA bands, or set your own per project.
The DCMA 14-point assessment — all fourteen, covered
- Every activity has at least one predecessor and one successor
- No negative lag anywhere
- No more than 5 % of links carry positive lag
- At least 85 % of links are Finish-to-Start
- No Start-to-Finish links
- No hard constraints outside the set you allow
- Total float no greater than 44 days
- No negative total float
- Activity duration at most two fiscal months
- No dates on the wrong side of the data date
- Activities of a day or more carry resources or budget
- At most 5 % of activities due by the data date have missed it
- A delay injected into a driving critical activity moves the project finish
- Critical Path Length Index at or above 0.95
- Baseline Execution Index at or above 0.95
Eleven more, from what actually goes wrong on site
- At most 15 predecessors on any one activity
- Activity duration at least one working day
- Critical activities under 40 % of the schedule
- Near-critical activities (float ≤ 20 d) at most 20 %
- FF lag within the successor's duration, capped at 22 days
- Every SS link paired with an FF link to the same successor
- No resource loaded beyond max units for five days or more
- Work is planned inside its permitted windows — outages, possessions, road closures
- Externally-driven dates have been re-confirmed since their review date
- A weather buffer milestone exists where work is weather-sensitive
- Reported actual cost reconciles with budget × percent complete
Findings are clickable. Break the schedule and watch.
A small invented network, graded live. Nothing here is a real programme — it is arithmetic on seven activities, run in your browser.
Click a button below to break the schedule, then click a red finding to see which activity it means.
—
One of the 26 is not a reading. It is an experiment.
Proving the finish date is genuinely driven by the network takes three steps: inject a delay into a driving critical activity, reschedule, and check the finish actually moved. LumaPlan runs that test. When the finish does not move, the result names the first activity downstream that absorbed the delay, and why. That is the row to open.
The bands are a setting, not our opinion.
Tighter than the standard
85 % Finish-to-Start, a warning on any unresourced work, and every hard constraint reported rather than a 5 % allowance.
The published bands
Switch the profile and the numbers move to the standard as written — 90 % Finish-to-Start, no unresourced allowance.
What the contract says
Override any threshold per project, and save the result as a profile. A rule with no data to judge reports "not assessed" — never a quiet pass.
It runs before the submittal, not after it lands.
The health engine reads the same in-memory schedule the scheduler just produced, so the check happens while the file is still yours to fix. Fixing an open end is a click, not next month's report.
It works on schedules that are not yours, too. Drop a .mpp or .xer you were sent into Review a schedule file and LumaPlan grades it on the spot — no project to set up, nothing saved, and a PDF report at the end.
Quality over revisions
Capture a dated snapshot each revision and the drift shows up as a line, not as a surprise at handover. Change the bands and the line breaks in two — a tightened threshold is never plotted as if the schedule got worse.
Driving-path replay
When the finish moved, replay shows which chain took over, and on which update. The difference between "we are late" and "this is why".
Monte Carlo on top
Once the logic is sound, simulate it. A criticality index earned on a schedule with broken logic is a confident answer to the wrong question.
Find it before the submittal does.
26 checks, on every recalculation, inside the scheduler that produced the dates. Early access is opening to teams running live work.
Bring a programme to grade. A .mpp or .xer — yours or one you were sent — goes straight in, and the full report comes back the same minute.