Schedule review

10 Project Scheduling Challenges and Practical P6 Checks

Wiznic World Editorial Team · Archive date: · Updated:
10 Project Scheduling Challenges and Practical P6 Checks

Primavera P6 can reveal scheduling problems, but it cannot resolve missing scope, unsupported assumptions or unavailable resources by itself. Use the following checks during baseline preparation and each progress update. Resolve findings with the responsible project team before treating the resulting dates as reliable.

1. Missing scope

Compare the WBS and activity register with drawings, BOQ, deliverables and handover requirements. Missing work may leave the finish date unrealistically early even when the network calculates without an error.

2. Incomplete activity logic

Review activities without appropriate predecessors or successors, unexplained lags and links that do not reflect the delivery sequence. Record justified exceptions, including genuine project start and finish milestones.

3. Unrealistic durations

Trace important durations to quantities, productivity, crew size and working calendars. Obtain the execution team’s input. A duration chosen only to achieve a target finish is an assumption that needs testing.

4. Resource overload

Compare demand profiles with confirmed labour and equipment capacity. Resource levelling can move work and affect completion; review the levelling settings, priorities and resulting dates before accepting the result.

5. Misleading constraints

Check mandatory and date constraints against contract requirements. A constraint can show a required date, but it cannot make a late delivery or unavailable crew disappear.

6. Inconsistent progress updates

Agree a data date, verify actual dates and review remaining durations. Investigate out-of-sequence progress and understand how the selected scheduling options affect remaining work.

7. Unexplained milestone movement

Compare the current forecast with the agreed baseline and previous update. Trace movement to the activities and assumptions that changed; do not overwrite the baseline simply to remove a variance.

8. Poor procurement interfaces

Include the approvals, manufacturing, delivery and release milestones that control site work. Assign responsibility for confirming lead times and identify provisional information.

9. Conflicting reporting measures

Define physical progress, schedule progress, quantities and earned value separately. Reconcile report totals and state which scope, budget and weighting rules each measure uses.

10. Uncontrolled schedule revisions

Retain dated issue files, the schedule basis and a change log. Distinguish an approved baseline revision from a regular progress update, and record who accepted material changes.

Use findings to agree an action plan

For each issue, record the affected milestone, evidence, proposed correction, owner and decision date. Some findings require schedule edits; others require a commercial, procurement or site decision. Keep both visible in the review record.

See our schedule review service for support with this process.

Reference: Oracle Primavera P6 Professional User Guide. Check the guide for your installed version; available features and settings differ between products and editions.

Apply this to your project

Need to develop your scheduling skills or review a live project requirement? Share your scope and the planning problem you want to solve.

Primavera P6 training · Scheduling services · Ask Wiznic World

Have a question or a correction? Contact the editorial team and include this article's title.

image