See the schedule quality result and the evidence behind it

Network integrity

Logic and relationships

1. Logic Is remaining work fully tied into the network? ≤ 5%

   What it checksRemaining discrete activities that lack a predecessor or successor, excluding level-of-effort and WBS summary rows. External ties count as connections, while valid start- and finish-milestone boundaries are respected.

   Why it mattersOpen ends interrupt network flow. They can create unreliable float and prevent the effect of a delay from propagating through the schedule.

   What to review nextConfirm that each open end is intentional. Connect legitimate work to the driving and driven sequence while preserving valid start- and finish-milestone boundaries.

2. Leads Is planned overlap hidden inside a negative lag? ≤ 0%

   What it checksThe share of internal activity relationships whose lag value is below zero.

   Why it mattersA lead hides planned overlap inside a logic tie. Explicit activities and relationships usually make that sequence easier to understand, status, and defend.

   What to review nextWhere overlap is real, consider modeling its parts as visible activities and ties so progress, ownership, and the effect of change can be reviewed directly.

3. Lags How much waiting time is hidden inside logic ties? ≤ 5%

   What it checksThe share of internal activity relationships whose lag value is above zero.

   Why it mattersSome waiting periods are legitimate, but lag time cannot be statused like an activity. Heavy use can conceal work, approvals, curing, or other reviewable waiting periods.

   What to review nextIdentify what each lag represents. When a material wait has an owner or can vary, such as curing, review, or approval time, consider a named activity that can be statused.

4. Relationship Types Is the network dominated by straightforward finish-to-start logic? ≥ 90%

   What it checksThe percentage of internal relationships that are finish-to-start; the findings identify start-to-start, finish-to-finish, and start-to-finish ties.

   Why it mattersNon-finish-to-start logic can be valid, but extensive use increases network complexity and can make the controlling sequence harder to trace.

   What to review nextReview non-finish-to-start ties for necessity, particularly where combinations obscure the controlling sequence. Decompose work only when doing so improves schedule fidelity.

Schedule controls

Constraints, float, and duration

5. Hard Constraints Are fixed dates overriding dates calculated by network logic? ≤ 5%

   What it checksThe P6 Check Schedule percentage for remaining detail activities with Mandatory Start, Mandatory Finish, Start On, or Finish On. Start constraints on activities that already started are inventoried but excluded. Directional constraints and As Late As Possible are disclosed separately and do not enter the score.

   Why it mattersMandatory and exact-date constraints can override dates calculated by network logic and distort float. Directional constraints are less restrictive but can still shape dates and deserve review.

   What to review nextVerify the contractual or control basis for every scored constraint. Review the informational tiers for unnecessary date restrictions, but do not treat every directional constraint as a failed check.

6. High Float Do unusually large float values reveal weak logic? ≤ 5%

   What it checksRemaining non-level-of-effort, non-summary activities whose total float exceeds 44 working days using the activity calendar. Milestones remain in scope.

   Why it mattersHigh float can be intentional, but it can also point to missing downstream logic or an activity that is weakly connected to completion. The cause matters more than the number alone.

   What to review nextTrace high-float activities to downstream milestones and completion. Add missing logic where warranted and document legitimate flexibility rather than treating every high value as an error.

7. Negative Float Can the current network still meet its required dates? ≤ 0%

   What it checksThe share of remaining activities whose total float is less than zero.

   Why it mattersNegative float signals that the current network dates do not support a constraint or required finish. The affected path needs schedule and project-context review.

   What to review nextIdentify the constraint or required finish driving the negative float, review the affected path, and record the recovery or mitigation response.

8. High Duration Are long activities hiding measurable handoffs or risk? ≤ 5%

   What it checksRemaining tasks with original duration above 44 working days, excluding milestones, level-of-effort activities, and WBS summary rows.

   Why it mattersLarge work packages reduce progress visibility and can hide intermediate handoffs, resource changes, and risks that deserve their own activities.

   What to review nextDecide whether each long activity is a legitimate continuous or procurement span. Break it into measurable steps when that improves status visibility and control.

Schedule data

Dates and resources

9. Invalid Dates Does schedule status agree with the data date? ≤ 0%

   What it checksActual starts or finishes after the data date, plus unstarted forecast starts or unfinished forecast finishes before the data date.

   Why it mattersThese date conflicts indicate that status or recalculation needs attention and can distort the schedule’s representation of completed and remaining work.

   What to review nextCorrect erroneous actuals, update stale forecasts, and recalculate in the scheduling system before relying on downstream schedule metrics.

10. Resources Do required detail activities have assignment coverage? ≤ 0%

    What it checksPositive-duration remaining tasks without a resource or role assignment, excluding milestones, level-of-effort activities, and WBS summary rows. This point runs only when resource loading is required.

    Why it mattersMissing assignments leave gaps in resource coverage. Passing this check confirms assignment presence; it does not prove that staffing levels are feasible.

    What to review nextConfirm that resource loading is contractually required, then address missing resource or role assignments. Review quantities and feasibility separately; this point checks presence only.

Resource loading is evaluated only when it is identified as a contractual requirement.

Performance

Baseline and critical path

11. Missed Tasks Did baseline work due by the data date finish as planned? ≤ 5%

    What it checksBaseline discrete activities planned to finish by the current data date that are missing from the update, have no current finish, or finish later than their baseline date. The automatic baseline is not scored against itself.

    Why it mattersThe result identifies baseline commitments that were not achieved on their planned dates. It locates performance variance but does not determine its cause or responsibility.

    What to review nextGroup missed commitments by path, WBS, and cause, then connect the variance to a documented recovery or change-control response. The metric alone does not establish responsibility.

12. Critical Path Test Does a controlled critical-path delay move project completion equally? Not evaluated

    What it checksA true test introduces a controlled delay and recalculates the network to verify that project completion responds as expected.

    Why it mattersThis tests whether the identified critical path actually drives completion. A static saved schedule cannot perform the required recalculation, so Schedule Tracker reports this point as not evaluated.

    What to review nextRun the controlled-delay test in a scheduling engine, compare the recalculated completion movement, and restore the test change before saving the production schedule.

13. Critical Path Length Index Does remaining path length fit inside the time available? ≥ 0.950

    What it checksCPLI uses a single terminal finish milestone, selected automatically when unambiguous or supplied as an override, and compares average calendar working days to its total float in the same unit.

    Why it mattersAn index below the threshold indicates that the remaining path and available float do not support the forecast finish without recovery or other corrective action.

    What to review nextValidate the chosen completion milestone and calendar basis before interpreting the index. Calendar exceptions are not modeled in this version. If the index is low, examine the driving path, constraints, and credible recovery options.

14. Baseline Execution Index Is execution keeping pace with baseline commitments due to date? ≥ 0.950

    What it checksBEI compares completed baseline discrete activities with baseline discrete activities planned complete by the current data date. It is not scored when the selected schedule is the automatic baseline.

    Why it mattersA low value points to execution behind the baseline plan. The pattern across successive updates is generally more informative than one isolated result.

    What to review nextRead the index as a trend across updates, then inspect baseline-due activities not completed by the status date. Confirm baseline identity and investigate any missing baseline finish dates before drawing performance conclusions.