Project Planning for Capital Projects
"Planning" and "scheduling" are not synonyms. Planning is the strategic "how will we build this?" thinking that must come before the schedule's "when" — and the schedule is only ever as good as the plan beneath it. Built on AACE 39R-06.
Planning vs. scheduling
| Planning | Scheduling | |
|---|---|---|
| Question | How will we build it? | When does each piece happen? |
| Output | Strategy, sequence, methods, resource concept | A calculated CPM with dates & float |
| Comes | First | After (expresses the plan in time) |
Why plan before you schedule
Jumping straight into the scheduling software — typing activities and dates without a deliberate plan — is one of the most common and costly mistakes in the discipline. It produces a schedule that calculates fine but doesn't reflect any real execution strategy, so the field can't follow it and it drifts immediately.
Planning first forces the hard questions early, when they're cheap to answer: What's our construction strategy — top-down, bottom-up, area-by-area? Where are the access and logistics constraints? What's the procurement and contracting approach? What resources can we realistically field? Answering these before the schedule means the schedule encodes a plan that can actually be executed.
The planning process
- Understand objectives & constraints — Scope, milestones, budget, contractual dates, site conditions, stakeholder requirements — the boundaries the plan must work within.
- Define the execution strategy — The big decisions: construction approach, phasing, contracting/procurement plan, make-vs-buy, key methods.
- Establish the sequence & logic concept — The overall order of work and major dependencies — before activity-level detail.
- Concept the resources — The crews, equipment, and key resources the strategy implies, and any limits.
- Identify risks & assumptions — What could derail the plan, and what you're assuming — feeding risk management and the schedule basis.
Planning outputs & who plans
Good planning produces tangible things — not just a schedule. A project plan/execution plan, a clear construction or execution strategy, a phasing and logistics concept, a procurement plan, and the documented assumptions and risks that flow into the schedule basis. On capital projects these are deliberate deliverables, reviewed and agreed before detailed scheduling begins.
Ten things to remember
- Planning ≠ scheduling — planning is "how we'll build it," scheduling is "when."
- Planning comes first — the schedule is the time model of the plan.
- No CPM precision saves an unsound plan — fix the strategy, not the dates.
- Scheduling-without-planning produces a critical path that makes no construction sense.
- Plan the execution strategy — approach, phasing, procurement, key methods.
- Establish the sequence concept before activity-level logic.
- Concept the resources and surface risks/assumptions early.
- Planning outputs are real deliverables — execution plan, phasing, procurement, assumptions.
- Planning is a team sport — superintendent, procurement, engineering, owner all feed it.
- The plan feeds the schedule basis — strategy and assumptions documented together.
Glossary
- Execution plan
- The documented project plan that scheduling then implements.
- Execution strategy
- The overall approach to building the project.
- Phasing
- How the project is divided into stages or areas over time.
- Procurement plan
- How materials, equipment and subcontracts will be sourced and timed.
- Project planning
- Deciding how a project will be executed — strategy, sequence, methods, resources.
- Resource concept
- The crews/equipment the strategy implies, and their limits.
- Scheduling
- Expressing the plan in time as a calculated CPM with dates and float.
- Sequence concept
- The high-level order of work before detailed logic.