Schedule analysis

This table lists unfinished activities whose exported P6 driving_path_flag is set. It reflects the schedule state saved by P6 and is not an independent network recalculation. Confirm the schedule was recalculated before export.

Start Date, Finish Date, and Total Float provide context for the exported path designation.

Highlighted in red are activities with negative total float.

This table is a total-float filter, not a critical-path calculation. Zero or negative float identifies limited or negative schedule flexibility under the saved P6 dates and constraints. Use the On LP column to distinguish activities that P6 also marked on the exported longest path.

Different activity IDs can legitimately share a description, but repeated wording can make tracking, communication, resource review, and claim analysis less precise.

Review duplicates where the wording creates ambiguity. Add a phase, location, system, or another distinguishing qualifier when the activities represent different work.

Out-of-sequence progress occurs when recorded work does not follow the current dependency order. A small amount can be normal; repeated findings may indicate changed field sequencing, incomplete progress updates, or logic that no longer reflects the work plan.

Review the cause and project context for each material finding. Revise logic or update procedures only when the supporting record shows that a change is appropriate.

This table lists nonzero relationship lag. Its timing meaning depends on the relationship type, so a negative value does not always mean that a successor starts before its predecessor finishes.

Highlighted in red are negative lag values. Display conversion uses the predecessor activity calendar. P6 scheduling behavior can instead follow the relationship-lag calendar option saved with the schedule, so use the raw relationship and P6 settings when exact date reproduction is required.

Calendars control working time, holidays, activity dates, and resource availability. Review their weekly hours, exceptions, assignments, and default status in project context.

Highlighted in green are project default and global/base default calendars, if any.
Highlighted in red are calendars not assigned to an activity. An unused calendar may be obsolete, intentionally retained, or used elsewhere in the project setup; confirm before changing it.