Why Monthly Schedule Reviews Are Harder Than They Look
A contractor's monthly P6 schedule update looks straightforward on the surface: a revised XER file, a Gantt bar chart export, and a cover memo claiming everything is on track. But for an owner or OPM without a P6-trained eye, the submitted package is nearly impossible to evaluate with confidence.
The five indicators below are not visible in a Gantt chart. They live in the logic, the float distribution, the constraint record, and the data date — and they only appear when you open the XER in Primavera P6 and run the analysis properly.
Red Flag 1: Total Float Erosion Without a Corresponding Change Event
Total float on near-critical activities is a leading indicator of schedule pressure. When total float on key milestone chains drops significantly between updates — and there is no documented change order, RFI, or weather event to explain it — the contractor's program is absorbing unacknowledged delays.
What to watch: Compare total float values on the five to ten most critical activity chains between the current and prior period. A drop of more than 10 days on a major milestone without a corresponding change directive is a signal that demands a written explanation from the contractor before the next period closes.
Can the contractor identify the specific event or series of events that caused the float reduction? If not, the reduction likely reflects real-time performance slippage being absorbed silently into the schedule.
Red Flag 2: Critical Path Migration Across Multiple Updates
In a healthy P6 schedule, the critical path is relatively stable from month to month. Activities become critical as predecessors slip, and that migration should be explainable by documented events. When the critical path jumps between entirely different work scopes across consecutive updates — say, from mechanical rough-in to exterior glazing to electrical gear installation — without a clear narrative, the schedule logic is likely being manipulated to avoid showing a true critical path.
What to watch: Compare the critical path activities (total float = 0 or negative) between updates. If the critical path chain changes by more than 30% in activities between periods, request a written critical path narrative from the contractor explaining the change.
Red Flag 3: Constraint Additions After Baseline Approval
Hard constraints — "Start No Earlier Than," "Finish No Later Than," "Must Start On" — are powerful tools for matching the schedule to contractual milestone requirements. They are also a primary manipulation technique. When contractors add hard constraints to activities after the baseline is approved and accepted, those constraints can artificially protect float, suppress negative float, and prevent the schedule from honestly reporting delay.
What to watch: Compare the constraint log between the current and prior update. Any new hard constraints added to activities that were previously logic-driven should trigger a review. The contractor should be required to justify each addition with a contractual or physical basis before the next update is accepted.
In Primavera P6, you can filter for constrained activities using Activity Columns > Primary Constraint. Compare the count and type of constraints between update periods to catch additions.
Red Flag 4: Activity Percent Complete Misalignment
Activity percent complete is self-reported by the contractor in most monthly update processes. Without independent verification, it is one of the easiest schedule metrics to inflate. The indicator to watch is the relationship between activity percent complete and the physical work visible in site photos, progress reports, and inspection logs.
What to watch: Pull the five to ten highest-value activities approaching completion in the current period. Cross-reference their reported percent complete against the most recent progress photos, contractor pay applications, and inspection records. A structural concrete activity reported at 85% complete while the pay application shows 60% billed is a discrepancy that warrants an inquiry.
Red Flag 5: Open Ends and Dangling Activities
A properly built CPM schedule has virtually no dangling activities — every activity (except the first and last) should have at least one predecessor and one successor relationship. Open ends create "float sinks" — places in the network where total float accumulates artificially because the activity has no successor to consume it. This inflates the apparent health of the schedule and allows activities on the true critical path to appear non-critical.
What to watch: Run the DCMA open-end check in P6. Any schedule with more than 5% of activities showing open ends should be returned to the contractor for correction before acceptance. This is a baseline quality requirement — it should also be monitored monthly because contractors occasionally delete logic relationships to manage float after baseline approval.
What to Do When You Spot These Red Flags
Identifying a red flag in the monthly update does not automatically mean the contractor is acting in bad faith. Schedules reflect real-world complexity, and some variation is expected. The issue is the absence of explanation — red flags become problems when the contractor cannot or will not provide a clear, documented rationale for the schedule condition you've identified.
When you see any of the five indicators above, the appropriate owner response is a formal Contractor's Recovery Schedule Request — a written document requiring the contractor to explain the schedule condition, identify the cause, and provide a written recovery plan by a specified date. This response is procedurally important: it creates a contemporaneous record of the owner's active schedule oversight, which protects your position if the project later heads toward a delay claim.
If your OPM team would benefit from a dedicated P6 specialist reviewing monthly contractor updates, consider retaining an independent schedule reviewer. A monthly narrative retainer delivers a written analysis — including these red flag checks — within three business days of each update receipt, so your team stays focused on program leadership while the schedule detail gets the technical scrutiny it deserves.