A detailed review of a submitted baseline is more than a formality; it is a critical process that ensures the schedule’s accuracy, feasibility, and alignment with contractual and project requirements, through detailed analysis. Potential issues such as unrealistic durations, illogical relationships, or missing scope elements can be identified and resolved before they impact the project’s progress.

This article explores the importance of reviewing a baseline schedule, highlighting how a review process enhances transparency, mitigates risks, and lays a solid foundation for effective project monitoring and control.

Guidelines by Agencies to Review Baseline Schedules

Several organizations and entities set guidelines and best practices for reviewing baseline schedules, including those created in Primavera P6.

The following organizations provide recognized standards and frameworks applicable to baseline schedule reviews.

A. Association for the Advancement of Cost Engineering (AACE)

The Association for the Advancement of Cost Engineering (AACE) provides several recommended practices for reviewing submitted schedules, ensuring the baseline is accurate, realistic, and aligned with project goals and contractual requirements. Below is an outline of how to review a schedule based on AACE guidelines:

1. Contractual Compliance

• Verify that the schedule meets all contractual requirements, including format, structure, and deliverables.

• Check the milestones, key dates, and constraints specified in the contract.

2. Scope Coverage

• Ensure the schedule includes all activities required to complete the scope of work.

• Look for missing work packages or deliverables that could affect project execution.

3. Logic and Sequencing

• Review the logical relationships between activities (predecessors and successors).

• Detect missing dependencies, redundant links, or illogical sequences.

• Confirm that the critical path is accurate and reasonable.

4. Activity Durations

• Assess the durations of activities for realism and consistency with historical data or industry standards.

• Avoid excessively long or short durations that could distort schedule tracking.

5. Critical Path and Float Analysis

• Analyze the critical path to ensure it reflects the project’s true priorities.

• Check for unusual float values (e.g., high float or negative float) that could indicate schedule issues.

6. Resource and Cost Loading

• Evaluate the allocation of resources (labor, equipment, materials) to ensure they align with project constraints and availability.

• Check the integration of cost loading with the schedule if required by the contract.

7. Constraints and Milestones

• Review the use of constraints (e.g., “Must Start On,” “Must Finish On“) to ensure they are justified and do not artificially manipulate the schedule.

• Verify that milestone dates align with contractual requirements and logical progressions.

8. Progress Measurement and Reporting

• Assess how progress will be measured against the baseline during execution.

• Ensure the schedule includes appropriate activity codes, work breakdown structure (WBS), and progress tracking mechanisms.

9. Schedule Risk Analysis

• Conduct a qualitative or quantitative risk analysis to identify potential risks to the baseline.

• Evaluate the inclusion of contingency buffers for high-risk activities.

10. Deliverables and Reporting

• Ensure the schedule includes provisions for regular updates and reporting.

• Validate that the schedule format is compatible with project reporting systems (e.g., Primavera P6).

B. Defence Contract Management Agency (DCMA)

The Defense Contract Management Agency (DCMA) provides a methodology for reviewing submitted schedules, often referred to as the DCMA 14-Point Assessment. This approach ensures that schedules, including those developed in Primavera P6, meet critical standards of quality, realism, and compliance. Here’s how to review a submitted schedule based on the DCMA guidelines:

1. Logic Check

• Evaluate the logical relationships between activities to ensure they are well-defined.

• Look for missing predecessors or successors, as activities without proper logic can disrupt the critical path.

2. Leads and Lags

• Review the use of leads (negative lags) and lags in the schedule.

• Excessive or unjustified leads and lags can distort the schedule’s realism.

3. Critical Path Test

• Identify the critical path and confirm that it accurately reflects the longest sequence of dependent activities.

• Validate the finish date against contractual requirements.

4. High-Float Test

• Assess activities with excessively high float (e.g., over 44 days).

• High float values may indicate missing logic or poorly defined activities.

5. Negative Float

• Check for activities with negative float, which may indicate scheduling conflicts or unrealistic constraints.

6. Constraints

• Minimize the use of hard constraints (e.g., “Must Finish On“) that can restrict schedule flexibility.

• Ensure constraints are justified and documented.

7. Baseline Execution Index (BEI)

• Measure the ratio of completed tasks to the total number of baseline tasks.

• A BEI less than 1.0 indicates a schedule falling behind the plan.

8. Missed Tasks

• Identify tasks that were planned but not completed by the data date.

• Analyze their impact on the critical path and overall schedule.

9. Critical Path Length Index (CPLI)

• Calculate the CPLI to assess the realism of the schedule’s ability to meet the finish date.

• A CPLI below 1.0 suggests the schedule is not achievable.

10. Number of Critical Activities

• Review the proportion of critical activities in the schedule.

• An unusually high or low percentage may indicate unrealistic durations or missing logic.

11. Reasonable Durations

• Check for activities with overly long durations (e.g., greater than 44 days).

• Break down long activities into smaller, manageable tasks for better tracking.

12. Invalid Dates

• Ensure there are no invalid dates, such as planned start or finish dates in the past.

• Validate that all activities are updated to reflect the status.

13. Resources

• Verify that resources are appropriately allocated, particularly for critical path activities.

• Ensure resource leveling does not distort the schedule.

14. Schedule Density

• Evaluate the density of the schedule, ensuring there is an appropriate level of detail to manage the project effectively.

• Avoid excessive division or lack of detail that may hinder tracking.

Best Practices to Review a Baseline Schedule Efficiently

• Baseline Review Checklist: Use a checklist to ensure all critical elements of the schedule are reviewed systematically. You can customize this list based on your project and use the major points that DCMA and AACE covered that will suit your project.

• Collaborative Review: Engage all stakeholders (owner, contractor, consultants) during the review process to align expectations.

• Documentation: Document all findings and recommendations from the review for future reference and dispute resolution.

Note

If you are one of our students registered in the Construction Project Planning Intermediate Level with P6 course, you will find a free checklist to help you review a submitted baseline. This checklist was created based on experiences and following the DCMA and AACE guidelines.

Conclusion

the baseline outlines the planned sequence of activities, milestones, and timelines that guide all stakeholders toward achieving project objectives. However, the effectiveness of a baseline schedule depends not only on its preparation but also on the accuracy with which it is reviewed. By following worldwide guidelines and the project’s unique requirements. Project stakeholders can ensure that the submitted schedule is realistic, and compliant with project requirements, ultimately contributing to successful project delivery.

---

Download the Resources of this Article