The Baseline Schedule - Audit

A well-validated baseline schedule not only ensures smooth execution but also lays the foundation for effective monitoring, control, and successful project delivery. Below is a comprehensive checklist that project managers can use to validate their baseline schedules.

1. Check the Use of Contractual Start and Finish Dates

Ensure that the project’s start and finish dates align with the contractual obligations. These dates form the boundaries for all scheduling activities and milestones, reflecting the agreed project duration.

2. Verify the Work Breakdown Structure (WBS) Hierarchy

The WBS should be reviewed to ensure its structure accurately reflects the project’s scope:

• Level 1: The highest level should summarize the main project milestones.
• Level 2: Should detail the scope of work required to achieve these milestones.
• Level 3: Should provide a breakdown of deliverables.
• Level 4: Should outline tasks or work packages needed to complete these deliverables.
• Level 5: Should include fully resourced tasks for execution.

These levels form a clear and detailed roadmap from the overall project to individual tasks.

3. Confirm the WBS Covers the Full Scope of Work

Check that the WBS adequately reflects and covers the entire scope of work. Missing scope can lead to significant delays and increased costs.

4. Analyze the Critical Path

Ensure that the critical path (the sequence of tasks that directly impacts the project finish date) makes logical sense. A flawed critical path can cause improper prioritization of activities and delays.

5. Evaluate the Number of Critical Activities

The number of activities on the critical path should typically range between 5% and 15% of the total activities. A higher percentage may indicate too much criticality and an aggressive schedule, which increases project risks.

6. Check for Negative Float

There should be no negative float (i.e., delays that exceed the available buffer time). Negative float indicates an unrealistic or infeasible schedule.

7. Ensure No Actual Dates Are Entered in the Baseline Schedule

The baseline schedule should not include actual start or finish dates, as it represents the project plan prior to execution.

8. Verify Schedule Coverage of Drawings

Ensure that the baseline schedule accounts for all required drawings, including:

• Composed drawings
• Shop drawings
• As-built drawings

Incomplete documentation can disrupt the project's flow and delay approvals or subsequent activities.

9. Include Engineering Activities

The baseline schedule must include all necessary engineering activities, ensuring the project’s technical scope is fully planned out.

10. Account for Long-Lead Procurement Items

Verify that all important procurement items with long lead times are included and properly scheduled. Neglecting these items can lead to significant project delays.

11. Incorporate Testing and Commissioning Activities

The baseline should reflect all testing and commissioning activities that need to be completed before the project is handed over.

12. Check for Open-Ended Activities

Ensure that no open-ended activities exist, except for the project start and finish milestones. Each activity should be properly linked to predecessors and successors.

13. Avoid Dangling Activities

Ensure there are no “dangling” activities—tasks that are not properly tied to others. These activities may create confusion and disrupt logical workflow.

14. Review the Project Calendar

The project calendar should reflect weekends, national holidays, and any other non-working days. An inaccurate calendar could lead to scheduling issues.

15. Ensure Fixed Durations and Units

Review all activity durations, ensuring they are based on fixed durations and resource availability. Avoiding dynamic or variable durations ensures stability and control over the project timeline.

16. Confirm Percentage Types Are Defined

Ensure that all percentage complete types (for progress measurement) are properly set for the project’s tracking and reporting system.

17. Limit Activity Durations

Verify that the maximum allowable durations of activities do not exceed two monitoring periods (e.g., two update cycles). This keeps activities manageable and easier to track.

18. Check Relationships Between Activities

Ensure that no activities have incorrect, missing, or redundant relationships. Clear and correct activity relationships are critical for accurate scheduling and project flow.

19. Validate Correct Use of SS and FF Relationships

Start-to-Start (SS) and Finish-to-Finish (FF) relationships should be used correctly within the project schedule. Incorrect use can distort the logic of the sequence of activities.

20. Ensure No Unallowed Relationship Types

The project should avoid using any relationship types other than Start-to-Start (SS) and Finish-to-Finish (FF) unless contractually allowed. Unapproved relationships can cause project timeline distortions.

21. Total Float Should Not Exceed 44 Days

Ensure that total float (the amount of time that tasks can be delayed without affecting the project completion date) does not exceed 44 days, as per DCMA . Excessive float may indicate a loose schedule, lacking sufficient control.

22. Avoid Non-Contractual Constraints

Non-contractual constraints, such as imposed dates or artificial deadlines, should not be used. These constraints can distort the schedule’s flexibility and create unnecessary pressure.

23. Assess Resource Estimates

Ensure that resource estimates are realistic and reasonable. An unrealistic allocation of resources can lead to bottlenecks, delays, and budget overruns.

For Planning and Delay Claims Services contact Pragmatic Project Consilium