Chennai HQ · serving India, UAE, Saudi Arabia and Omaninfo@projectassure.inCall us 24/7 +91 94895 88922
Project Assure
Schedule Quality

Primavera P6 schedule review checklist: data quality checks and how to QA an update

Review a P6 schedule in a fixed order, from data date to sign-off, and test it against the DCMA thresholds before you accept an update.

In short

A Primavera P6 schedule review checks setup (data date, calendars, baseline), then logic, constraints, float and the critical path, then resources, durations and progress, and ends with a sign-off table where every item passes or is explained. The DCMA 14-point thresholds give the pass marks: open ends, lags, hard constraints, high float and long durations each under 5%, no leads or negative float, at least 90% Finish-to-Start, and CPLI and BEI of 0.95 or above. Run it at every update and before any baseline change.

A Primavera P6 schedule review checklist works through the file in a fixed order: setup (data date, calendars, baseline), logic, constraints, float and the critical path, then resources and durations, and finally a sign-off table where every item must pass or be explained. Run it on every update before you accept it, not only on the baseline submission.

This guide combines that checklist with the quality-check thresholds from the DCMA 14-point assessment and a repeatable QA workflow, so the same review can be used for a baseline, a monthly update or a revised programme.

Why does schedule quality matter before you accept an update?

Accepting a contractor's schedule update without a quality check is like signing off structural calculations without reading them. A poor-quality schedule can mask delay, misrepresent progress and lead to disputes later. A sound QA process confirms the schedule is logically connected, reflects the work actually being done, and is fit for performance measurement and, if it comes to it, forensic delay analysis.

Quality matters contractually too. An accepted update becomes part of the project record. A schedule with broken logic or hard constraints is weak evidence for an extension of time (EOT) claim, and an update accepted without comment is hard to challenge later.

What should you check before the review starts?

Data date

Confirm the data date is the status date for the reporting period and is the same across every project in the submission. If it is wrong, every remaining duration, float value and performance metric is calculated from the wrong point. Check also that no actual dates fall after the data date and no forecast dates fall before it: these are the DCMA invalid dates check, and the target is zero.

Calendars

  • Right calendar for the work: each activity should use the calendar that matches how the work is done (5-day, 6-day, 7-day or shift).
  • Exceptions: holidays, shutdowns and non-working periods are entered and match the contract.
  • Assignment: every activity has a deliberate calendar. Activities left on the project default calendar by accident are a common source of wrong dates and float.

Baseline

Confirm a baseline exists, that it is the approved version, and that it is assigned as the project baseline used for performance measurement. Check that baseline dates have not been overwritten by a later update. Where several baselines are held, make sure the one used for variance and BEI is the contractually approved one.

Metadata and structure

Check the project start date, the planned or must-finish date, the WBS structure and the activity count against the previous update. A sudden jump or drop in activities is worth asking about before you look at anything else.

What logic checks should a P6 schedule pass?

Open ends (missing predecessors or successors)

Every activity except the project start and finish milestones should have at least one predecessor and one successor. Open ends break the logic chain, so float and the critical path can no longer be trusted. The DCMA logic check sets the threshold at less than 5% of incomplete activities missing a predecessor or successor. Open ends are the most common issue found in reviews, and each one should be justified or fixed.

Leads and lags

Leads (negative lags) are often used to fake overlapping work and hide the real sequence. DCMA sets the target for leads at zero. Positive lags should be used sparingly, for genuine waiting periods such as concrete curing, and DCMA limits them to less than 5% of relationships. Each lag should be documented with its reason.

Relationship types

Finish-to-Start (FS) should be the norm: DCMA expects at least 90% of relationships to be FS. Start-to-Start (SS) and Finish-to-Finish (FF) are legitimate for overlapping work but produce unrealistic logic when used without care. Start-to-Finish (SF) should be very rare. Review every non-FS relationship and confirm it reflects the real sequence.

How do you review constraints, float and the critical path?

Constraints

Constraints override logic and can hide problems. Hard constraints are the main concern. In P6 these are Mandatory Start and Mandatory Finish (which break logic outright), and Start On, Finish On, Start On or Before and Finish On or Before, which stop dates moving freely and can create negative float. Soft constraints such as Start On or After are less harmful but should still have a reason.

  • Mandatory constraints should be extremely rare and justified in writing.
  • Finish On or Before constraints on contractual milestones are acceptable when they match the contract.
  • DCMA limits hard constraints to less than 5% of incomplete activities.

For more detail on each type, see Primavera P6 constraints explained.

Float

  • Negative float: DCMA targets zero. Negative float means the calculated early finish is later than a constraint or required date, so the programme cannot meet that date as planned. Check whether it is real slippage or the product of an illogical constraint.
  • High float: activities with more than 44 working days of total float should be less than 5% of incomplete activities. High float usually means a missing successor rather than genuine flexibility.
  • Distribution: a large share of activities at zero or negative float suggests an unrealistic plan, while a large share with very high float suggests weak logic.
  • Free float: large free float on an activity that should be driving its successor often points to a missing or wrong relationship.

Critical path

The critical path should run continuously from the data date to project completion with no gaps or breaks in logic. Set P6 to define critical activities as the Longest Path (rather than total float of zero or less) so the path is not distorted by constraints or calendars. Walk the path segment by segment and confirm each activity really drives the end date. The DCMA critical path test adds a delay to a critical activity and checks that the finish date moves by the same amount. The Critical Path Length Index (CPLI) should be 0.95 or above.

How do you check resources, durations and progress?

Resource and cost loading

Where the schedule is resource-loaded, check that resources are assigned to the activities that need them, resource calendars are consistent with activity calendars, and no resource is over-allocated beyond its availability. The resource usage profile shows peaks quickly. Where costs are loaded, check the total agrees with the budget and the cost distribution over time is logical. DCMA's resources check looks for incomplete activities with duration but no resources or cost, where the contract requires loading.

Duration reasonableness

Very short durations (one day across a whole area of work) can mean detail is missing. Very long durations hide progress problems. DCMA limits incomplete activities with a duration over 44 working days to less than 5%. Compare durations with historical data or norms for the work, and check that milestones have zero duration.

Units, percent complete and actual dates

Confirm physical percent complete is consistent with actual units and remaining duration, because inconsistent values distort earned value. Check that actual start and actual finish dates are recorded correctly and that activities have not progressed out of sequence without the logic being corrected. Two DCMA checks look at delivery against the baseline: missed tasks should be less than 5% of tasks due to finish by the data date, and the Baseline Execution Index (BEI) should be 0.95 or above.

How do the DCMA, GAO and NASA frameworks compare?

Several government frameworks set out standard schedule quality checks. They share one point: a schedule must be a reliable decision-making tool, not a compliance document.

FrameworkKey focusTypical measures
DCMA 14-point assessmentSchedule health: logic, relationships, constraints, float, durations and executionOpen ends, leads, lags, FS ratio, hard constraints, high and negative float, high duration, invalid dates, resources, missed tasks, critical path test, CPLI, BEI
GAO Schedule Assessment GuideBest practices for a comprehensive, well-constructed, credible and controlled scheduleCapturing all activities, sequencing, resources, realistic durations, critical path, float, schedule risk analysis, updating with actuals, baseline control
NASA schedule management guidanceCredibility, traceability and handling of riskLogic ties, schedule margin, integration with earned value, schedule risk analysis

For each DCMA metric and how to read the results, see DCMA 14-point assessment explained.

What is a repeatable QA workflow for a P6 schedule update?

  1. Import and review metadata: project start, data date, calendars, WBS and activity count against the last update.
  2. Run the metric checks: produce the DCMA 14-point results from a schedule-checking tool or P6 reports and filters, so the same thresholds are applied every time.
  3. Analyse logic and constraints: open ends, leads, lags, non-FS relationships and hard constraints.
  4. Review float and the critical path: negative and high float, and a continuous longest path.
  5. Check durations and calendars: flag outliers and calendar mismatches.
  6. Validate resource and cost loading where the contract requires it.
  7. Document findings: a QA report listing each issue, its severity and the correction required.
  8. Iterate with the contractor: discuss the findings and require corrections before the update is accepted.

Run the workflow at every update (usually monthly) and always before a baseline is set or revised. Regular checks catch problems while they are still cheap to fix.

What goes on the sign-off checklist?

Before approving the schedule, every item below should pass or carry a documented, accepted explanation.

ItemWhat passes
Data dateMatches the end of the reporting period; no actuals after it and no forecasts before it
BaselineApproved version assigned as the project baseline, dates not overwritten
CalendarsDefined, with correct exceptions, and deliberately assigned to every activity
Open endsLess than 5% of incomplete activities, each justified
Leads and lagsNo leads; lags under 5% of relationships and documented
Relationship typesAt least 90% Finish-to-Start; non-FS relationships justified
ConstraintsHard constraints under 5% of incomplete activities, each documented and approved
FloatNo negative float, or explained; high float (over 44 working days) under 5%
Critical pathContinuous, logical longest path from data date to completion; CPLI 0.95 or above
ResourcesLoaded where required and not over-allocated
DurationsReasonable; activities over 44 working days under 5%; milestones at zero duration
ProgressPercent complete consistent with units and remaining duration; actual dates correct; BEI 0.95 or above

If any item fails, record the issue and require corrective action before sign-off. A checklist like this is the core of an independent review, and Project Assure applies it as part of its project planning and schedule review work on live programmes.

FAQ

Common questions

What is the most important check in a P6 schedule review?
The data date and the baseline assignment come first. If the data date is wrong or the wrong baseline is assigned, every float value, variance and performance metric in the review is meaningless.
How many open ends are acceptable in a schedule?
The DCMA 14-point assessment sets the threshold at less than 5% of incomplete activities missing a predecessor or successor. Only the project start and finish milestones should have a genuine open end, and every other one should be justified or fixed.
Should I use leads in a P6 schedule?
Generally no. The DCMA target for leads (negative lags) is zero, because they hide the real sequence of work and make the schedule less reliable; overlapping work is better shown with Start-to-Start relationships or by splitting activities.
What does negative total float indicate?
Negative total float means the calculated early finish of an activity is later than a constraint or required date, so the programme cannot meet that date as planned. It needs either recovery, a revised plan, or removal of an illogical constraint that is causing it.
How often should I perform a schedule quality check?
Check every schedule update, which is usually monthly, and always before a baseline is set or revised. Regular checks catch problems while they are still cheap to correct.
Chennai city skyline at dusk under a vivid pink and violet sky

Bring this discipline onto your programme.

Every insight comes from live mandates. A principal replies within one working day.