Primavera P6 Schedule Review Checklist (Printable Steps)
Introduction
Reviewing a Primavera P6 schedule submission can be daunting. A structured checklist ensures you catch common issues that lead to unreliable baselines or misleading updates. This article provides a concrete, printable checklist covering pre‑review setup, logic checks, constraints, float, resources, and sign‑off. Use it to standardise your reviews and improve schedule quality.
1. Pre‑Review Setup
1.1 Data Date
Verify the data date is correct and consistent across all projects. The data date should be the most recent status date and must match the reporting period end. An incorrect data date invalidates all performance metrics.
1.2 Calendars
Check that all calendars are properly defined and assigned. Look for:
- Global vs. project calendars: Ensure the correct calendar is used for each activity (e.g., 5‑day, 7‑day, or shift calendars).
- Calendar exceptions: Holidays and non‑working days should be accurately reflected.
- Consistency: All activities should have a calendar assigned; missing calendars default to the project default, which may be wrong.
1.3 Baseline
Confirm that a baseline exists and is properly assigned. The baseline should be the approved schedule version. Check that the baseline dates are not inadvertently overwritten. If using multiple baselines, ensure the primary baseline is the one used for performance measurement.
2. Logic Checks
2.1 Open Ends (Missing Predecessors or Successors)
Activities with no predecessors or no successors create dangling logic. The DCMA 14‑point check flags these as open ends. Every activity (except the first and last) should have at least one predecessor and one successor. Review the open ends list and justify or correct them.
2.2 Leads and Lags
Leads (negative lags) and positive lags can distort the critical path. Leads are often used incorrectly to represent overlapping work. Check that all leads are justified and documented. Lags should be used sparingly and only for genuine waiting periods (e.g., concrete curing).
2.3 Relationship Types
The default relationship should be Finish‑to‑Start (FS). Start‑to‑Start (SS) and Finish‑to‑Finish (FF) relationships can create unrealistic logic if not carefully applied. Review all non‑FS relationships and ensure they are necessary and correctly reflect the actual work sequence.
3. Constraints, Float and Critical Path
3.1 Constraints
Constraints override logic and can hide schedule issues. Check for:
- Mandatory constraints (e.g., Must Finish By) – these should be extremely rare.
- Start On or Finish On constraints – often used to anchor the start or end but can create negative float.
- Late constraints (e.g., Finish No Later Than) – may indicate a contractual milestone.
All constraints should be documented and approved. The DCMA check limits constraints to 5% of total activities.
3.2 Float
Total float values indicate schedule flexibility. Negative float means the project is behind schedule. Review:
- Total float distribution: A large number of activities with zero or negative float suggests an unrealistic plan.
- Free float: Free float should be positive or zero; negative free float indicates logic errors.
- Float path: Identify the longest path and verify it makes sense.
3.3 Critical Path
The critical path (longest path) drives the project duration. Check that the critical path is continuous and logical. Break the path into segments and confirm each activity is truly driving the end date. Use the DCMA longest path check to ensure the critical path is correctly calculated (often requires setting the critical path definition to “Longest Path” in P6).
4. Resources and Durations
4.1 Resource Loading
Check that resources are assigned to activities and that resource calendars are consistent. Look for overallocation – resources assigned to more work than available in a given period. Use the resource usage profile to spot peaks. Unrealistic resource loading can lead to schedule slippage.
4.2 Duration Reasonableness
Review activity durations for reasonableness. Very short durations (e.g., 1 day) may indicate a missing level of detail. Very long durations (e.g., > 30 days) may hide progress issues. Compare durations against historical data or industry benchmarks.
4.3 Units and Percent Complete
Verify that physical percent complete is consistent with actual units and remaining duration. Inconsistent values can distort earned value metrics. For updates, ensure that actual start and actual finish dates are correctly recorded.
5. Sign‑Off Checklist
Before approving the schedule, run through this final checklist:
| Item | Pass/Fail |
|---|---|
| Data date matches reporting period | |
| Baseline assigned and correct | |
| Calendars defined and assigned to all activities | |
| Open ends < 5% of total activities (or justified) | |
| Leads and lags justified | |
| Non‑FS relationships justified | |
| Constraints < 5% of total activities (or justified) | |
| No negative float (or explained) | |
| Critical path is logical and continuous | |
| Resources not overallocated | |
| Durations reasonable | |
| Percent complete consistent |
If any item fails, document the issue and require corrective action before sign‑off.
Automating the Checks
Manually performing these checks can be time‑consuming. Tools like Project Assure (a free, browser‑based P6 XER analyser) can run DCMA 14‑point, GAO, and NASA checks instantly. It parses your XER file locally – nothing is uploaded – and provides a detailed report. This can save hours and ensure consistency across reviews.
Conclusion
A structured P6 schedule review checklist helps you catch errors early and maintain schedule integrity. Use the steps above to build your own checklist or print this page for your next review. Combine manual checks with automated analysis for a robust quality assurance process.
Run these checks free, in your browser
Free, browser-based Primavera P6 XER schedule analyser — DCMA 14-point, GAO & NASA checks, EVM/S-curve, and forensic baseline-vs-update comparison. Nothing is uploaded; your XER is parsed locally in the browser. 3 free analyses, no card required.
Analyse your XER →Frequently asked questions
What is the most important check in a P6 schedule review?
The data date and baseline assignment are foundational. Without a correct data date and baseline, all performance metrics and progress comparisons are meaningless. Always verify these first.
How many open ends are acceptable in a schedule?
The DCMA 14‑point check recommends that open ends (activities without predecessors or successors) should be less than 5% of total activities. Any open ends should be justified, such as the first/last activity or contractual milestones.
Should I use leads in my schedule?
Leads (negative lags) should be used sparingly and only when justified by the work sequence. They can hide logic and make the schedule less reliable. Many review guidelines recommend avoiding leads altogether.
What does negative total float indicate?
Negative total float means the project is behind schedule; the planned completion date is earlier than the calculated early finish. It indicates that the schedule needs compression or the plan needs revision.
How can I automate DCMA checks?
You can use free browser‑based tools like Project Assure that parse your XER file locally and run DCMA 14‑point, GAO, and NASA checks. No upload is required, ensuring data security.