Planning basis

Before Primavera P6 opens.

The questions that deserve answers before the first activity gets a date.

2 MIN READ
FIELD NOTES / ILLUSTRATIVEScope?Method?Access?A planning basis

Scope before structure

The work breakdown should follow the project’s scope and delivery strategy. Identify the packages, areas and interfaces before deciding how activities will be grouped. A schedule that looks organized can still omit important work if its structure starts from a generic template.

A method before durations

Discuss how the work will be built. Work-area releases, access restrictions and procurement priorities often determine the sequence. Durations should follow quantities, crew assumptions and the construction method rather than a desired finish date alone.

The quality of the schedule starts with the quality of the questions.

Assumptions that can be reviewed

Write down the basis for calendars, resource availability, approvals and handovers. Separate confirmed commitments from planning assumptions. This makes it easier to review the baseline and understand later changes.

A practical starting checklist

Before baseline development, confirm the schedule requirements and submission format. Gather the scope documents, key milestones and proposed construction methods. Identify long-lead packages and unanswered interface questions. The result is a planning basis the project team can challenge and improve.

TRY THIS ON YOUR NEXT REVIEW
  • Define scope boundaries before activity detail.
  • Review access and the construction method.
  • Record assumptions that need confirmation.

This article is general planning commentary. Project requirements and engagement methods are defined for each assignment.

Keep exploring

Where to next? Follow the loop.

Let’s put a better plan behind your next project.

Start a conversation