Get your team started in minutes
Sign up with your work email for seamless collaboration.
The 5 Phases of Project Management
Initiation, planning, execution, monitoring and closure — what actually happens in each phase, who owns it, and where projects most often go wrong.
Every project moves through the same five stages, whether or not anyone names them. Naming them helps, because each phase has a different job — and most project failures trace back to skipping one, usually initiation or closure.
This is the standard five-phase model used in most project management practice. Below is what happens in each phase, who is involved, and the failure mode to watch for. If you are about to plan one, the step-by-step project plan walkthrough covers phase two in more depth.
The five phases
- Initiation — decide whether the project should exist at all.
- Planning — turn the goal into scope, sequence, owners and dates.
- Execution — do the work, and keep status visible while you do.
- Monitoring & controlling — compare reality to the plan and correct.
- Closure — ship, hand over and capture what you learned.
Phase 1 — Initiation
Initiation answers one question: should this project happen? You define the problem, sketch the value, identify stakeholders, and get an explicit decision to proceed. The output is usually a project charter — a short document stating the objective, the rough scope, and who is accountable.
The temptation is to skip straight to planning because the project feels obviously worthwhile. That is precisely when initiation matters most, because “obviously worthwhile” often means nobody has written down what success is.
Watch for: starting work before anyone has agreed, in writing, what the project is for.
Phase 2 — Planning
Planning turns an agreed objective into something executable: scope, work breakdown, sequence, dependencies, estimates, owners, dates and a risk list. This is the longest phase on paper and the one most often rushed.
A good plan is specific enough that each person knows their next task and loose enough to survive a surprise. Plan the near term in detail and later phases roughly — detail you invent now about month four will be wrong.
Watch for: a plan so detailed nobody updates it, or so vague nobody can act on it.
Phase 3 — Execution
Execution is the work: building the thing, coordinating people, and keeping everyone pointed the same way. The project manager's job shifts from designing the plan to removing what blocks it.
Status should be visible without a meeting. When progress lives only in people's heads and weekly calls, problems surface a week late — which is usually a week too late to absorb cheaply.
Watch for: status that only exists in meetings, so blockers surface late.
Phase 4 — Monitoring and controlling
This phase runs in parallel with execution rather than after it. You compare actual progress against the plan, look at scope, schedule and budget, and correct where they diverge.
The point is not to defend the original plan but to notice early when it has stopped being true. A dependency slipping by three days is a small conversation now and a missed launch later.
Watch for: tracking that reports what happened without changing what happens next.
Phase 5 — Closure
Closure means delivering the work, handing it to whoever owns it next, releasing the team, closing contracts, and running a retrospective while memory is fresh.
Closure is the most skipped phase, because the work already feels done. Skipping it costs you the same mistake twice — the retrospective is where the next project's estimates get better.
Watch for: teams rolling straight onto the next project without capturing what they learned.
FAQs
What are the five phases of project management?
Are there really five phases, or four, or six?
Do the phases apply to agile projects?
Which phase takes the longest?
What is the most commonly skipped phase?
