Menu
Categories Document Collaboration Online Whiteboard Project Management Task Management Team Communication Video Conferencing Compare Guides Blog Get Listed List your tool Contact
Search

How to Create a Project Plan in 8 Steps (2026 Guide) | The Collaborative Organization

By The Collaborative Organization Team · November 19, 2026 · Last verified November 19, 2026 · 16 min read

Navy cover with the title How to Create a Project Plan in 8 Steps and a checklist icon

A project plan is a formal, approved document that guides both project execution and project control, and you build it in eight steps: define the scope, break down the work, sequence and schedule it, assign resources, set the budget, plan risks, plan communication, then get sign-off and save the baseline.

Each step adds one section to the document, so the plan grows in order and nothing is missed.

Key takeaways

  • A project plan is a formal, approved document that guides execution and control, in the PMBOK Guide definition.
  • The eight steps are scope, work breakdown, schedule, resources, budget, risks, communication and sign-off.
  • A 3-week project needs about a 2-page plan, while a 6-month cross-team effort needs a 15 to 20 page plan, with the same structure.
  • The work breakdown structure follows the 100% rule: it covers all of the work in scope and nothing extra.
  • Approval turns the draft into the baseline, and the plan changes after that only through a recorded change request.
  • A plan that is never updated becomes fiction within two weeks, so review it weekly and log every approved change.

What a project plan is

A project plan is a formal, approved document used to guide both project execution and project control. That is the PMBOK Guide definition, and it names the two jobs of the document: it tells the team what to do, and it gives the sponsor something to measure progress against. Without the second job, the plan is a wish list, not a plan.

The plan is not a task list. A task list says what to do today, while a plan says what the project will deliver, who will do the work, when it will happen, what it will cost and how changes are handled.

It also records the decisions the team made while planning, so a new person can read it and understand why the work is shaped the way it is.

The plan is built during the planning phase, after the charter is approved. Our guide on project charter vs project plan explains the split.

The charter authorizes the work and states the goal, while the plan says how the work gets done in detail. Start the plan only when the charter is signed, or you may plan work the sponsor never approved.

What you need before you start

Before the first step, you need the approved charter, the sponsor’s contact and a list of the people who must be involved. The charter gives you the goal, the high-level scope and the budget limit. The sponsor is the person who will approve the plan at the end. The stakeholder list tells you who to ask for requirements and who must sign off on the result.

You also need a place to build the plan where the team will actually read it. A shared tool beats a document that lives on one person’s laptop, because the plan must be open to the whole team from the day it is approved. Pick the tool now, before the first section is written.

Set aside real time for the work. A small project needs a few hours spread over a week, with short calls to confirm the scope and the dates. A large project needs days of planning with the team in the room. A plan written in one rushed afternoon will not survive the first week of the work.

The 8 steps at a glance

The eight steps move from the scope to the sign-off, and each one adds one section to the plan. The table below is the map for the rest of this guide, and the filled-in example at the end shows the same eight steps on one real project.

Eight steps to create a project plan from scope to sign-off
The eight steps, each adding one section to the plan document.
Step What you write Time it takes
1. Define the scope Scope statement Half a day
2. Break down the work Work breakdown structure Half a day
3. Sequence and schedule Schedule, milestones, critical path One day
4. Assign resources Resource plan with named owners Half a day
5. Set the budget Cost baseline Half a day
6. Plan risks Risk register with responses Half a day
7. Plan communication Communication plan A few hours
8. Get sign-off Approved plan and baseline Half a day

The times are for a small to medium project, and they grow with the size of the work. A large project may take a week per step, but the order stays the same. Do not skip a step to save time, because the missing section is the one that causes the delay later.

Step 1: Define the scope

Step 1 writes a scope statement that says what the project will deliver, what it will not deliver and what success looks like. Start from the charter goal and list the deliverables in plain words, then list the exclusions: the work people might assume is included but is not. Add the assumptions you are making and the limits you must respect, such as a fixed launch date or a set budget.

Write the goal as a measurable outcome, not a vague hope. “Launch a new checkout flow that cuts cart abandonment” is a goal, while “improve the website” is not, because no one can tell when it is done. The scope statement should let any reader say whether a new request is inside or outside the project.

Confirm the statement with the sponsor before moving on. A scope that the sponsor has not read is not agreed, and the first disagreement about it will arrive during the work, when it costs the most to fix.

Outcome of step 1

A one-page scope statement with deliverables, exclusions, assumptions and limits, signed by the sponsor. If two stakeholders describe the result differently after reading it, rewrite it until they describe the same thing.

Step 2: Break down the work

Step 2 builds a work breakdown structure, which is a deliverable-oriented breakdown of the total scope into smaller, manageable pieces. Take each deliverable from the scope statement and split it into parts, then split those parts again, until you reach work packages: chunks of work with one owner that you can estimate and assign.

The WBS is organized around deliverables, not activities. A deliverable is a tangible, verifiable outcome the project produces, such as a tested checkout page, while an activity is the work done to produce it, such as writing the code. The WBS shows the what, not the how, and the schedule in the next step adds the when.

The 100% rule governs the whole structure: the WBS includes 100% of the work in scope, and the children of any element roll up to exactly that element. Nothing is left out, and no extra work sneaks in. PMI published its WBS practice standard in 2001, and the same rule still holds in its August 2026 guide to the structure.

Outcome of step 2

A WBS tree with every deliverable broken into work packages, each with one owner. If a piece of work has no place in the tree, it is either out of scope or the tree is missing a branch.

Step 3: Sequence and schedule the work

Step 3 turns the work packages into a dated schedule with dependencies, durations and milestones. List each package, estimate how long it takes, then put the packages in order: which ones must finish before the next can start, and which ones can run at the same time. The chain of tasks that sets the earliest finish date is the critical path, and any slip on that path moves the end date.

Set milestones at the points that matter to the sponsor: design approved, first version built, testing done, launch. A milestone is a date with a result attached, not a task, and it is the point where the sponsor can see real progress.

A Gantt chart is the standard format for the detailed schedule, while a milestone timeline is the standard format for telling executives what is happening.

Our guide on project roadmap vs project plan explains the difference: the roadmap shows the direction and the big dates, while the plan holds the detail behind them. The schedule in this step is the detail.

Outcome of step 3

A dated schedule with dependencies, a critical path and named milestones. If a task has no date or no dependency, it is not scheduled yet, and it will be the task that slips.

Step 4: Assign resources

Step 4 matches every work package to a person, a tool or a material, and checks that no one is booked twice. Go through the schedule task by task and name the owner, the hours needed and the date the work happens. Check each person’s other commitments, because a plan that gives one person two full-time jobs in the same week is fiction.

This is also the step to confirm outside help: suppliers, contractors and approvals from other teams. Book them now, with dates, so a missing approval does not stall the work later. A supplier told in week one can plan around you, while a supplier told in week five may have no capacity left.

For tasks with unclear effort, use the estimating guide in our article on how to estimate story points. A rough estimate with a named range beats a precise-looking number that no one believes.

Outcome of step 4

A resource plan with a named owner for every task and confirmed dates for outside help. If the same person owns three tasks on the same day, rebalance before the work starts.

Step 5: Set the budget

Step 5 costs each work package and adds the totals into a budget baseline the sponsor approves. Estimate the cost of people, tools, materials and outside help for each package, then add the packages into a total. Keep a small reserve for risks that are likely but not certain, and say how big that reserve is, so the sponsor knows it is there.

The baseline is the snapshot you measure against later, so save it before the work starts. Do not move the baseline without a recorded change, or the team will have no honest way to say whether it is over budget. A budget that moves quietly is not a budget.

Check the numbers with the people who will spend them. A budget written by one person without asking the team is a guess, and the team will ignore it the first time a real cost appears.

Outcome of step 5

A cost baseline with a total, a reserve and a named owner for the budget. If the total is higher than the charter limit, the sponsor must choose: raise the budget, cut the scope or move the date.

Step 6: Plan risks

Step 6 lists what could go wrong, rates each risk by impact and likelihood, and writes a response for the ones that matter. Brainstorm with the team, not alone, because the people doing the work know the risks best. For each risk, write one line: what could happen, how likely it is, how bad it would be and what you will do if it happens.

Use a simple impact and likelihood grid to sort the list. A risk that is both likely and damaging needs a response now, such as extra time, a backup supplier or a simpler design.

A risk that is unlikely and small needs only a note, so the team knows it exists. The register should fit on one page, or no one will read it.

Review the register every week during the work. Risks change as the project moves, and a risk that was small in planning can grow into the biggest threat in week six.

Outcome of step 6

A one-page risk register with a named owner and a response for each serious risk. If a risk has no owner, it has no response, and it will be the problem that surprises the team.

Step 7: Plan communication

Step 7 writes a communication plan that says who needs what information, how often and in what form. Make a table with the stakeholder names, what each one needs to know, how often they need it and the format, such as a short email, a dashboard or a meeting. The sponsor needs a weekly status with dates and budget, while the team needs daily task updates and a place to ask questions.

Keep the plan short and keep the meetings few. A weekly status report and a short weekly check-in cover most projects, and anything more is usually a sign that the plan is not trusted. If stakeholders ask for more meetings, the fix is usually a better status report, not more meetings.

Name one person to own the status report and set its day. A report with no owner arrives late or not at all, and the sponsor learns the news from a hallway chat instead.

Outcome of step 7

A communication table with a named owner for the status report and a fixed day for it. If a stakeholder first hears bad news from someone else, the plan failed, not the stakeholder.

Step 8: Get sign-off and save the baseline

Step 8 gets the sponsor’s approval, saves the approved scope, schedule and budget as the baseline, and shares the plan with the team. Walk the sponsor through the plan section by section, and fix what they challenge before asking for the signature. A signature on a plan the sponsor has not read is worth nothing when the first problem arrives.

Once approved, save the baseline and share the plan where the team works. The baseline is the snapshot that later progress is measured against, and it changes only through a recorded change request: request, review, approve, log. The log records the decision, so the team does not argue it again.

Outcome of step 8

An approved plan, a saved baseline and a team that has read it. If the sponsor will not sign, the project is not ready, and the right move is to fix the plan, not to start the work anyway.

Worked example: a project plan for a training course

A plan for a 6-week training course shows all eight steps on one page each. Imagine a team of three people building an online course for 50 new sales staff, with a budget of $8,000 and a launch date fixed by the hiring round. The result is one course: six lessons, a quiz and a certificate.

Step 1 sets the scope: six lessons and a quiz are in, while a live workshop is out, because the sponsor wants it next year. Step 2 breaks the course into work packages: one per lesson, plus the quiz, the certificate and the launch.

Step 3 schedules the work: two lessons per week, a milestone each fortnight and a launch in week six, with the quiz on the critical path.

Step 4 assigns the work: one writer owns four lessons, one designer owns the quiz and the certificate, and the manager owns the launch. Step 5 sets the budget: $5,000 for the writers, $2,000 for the designer and $1,000 held as reserve.

Step 6 logs the risks: the designer is on leave in week four, so a backup is booked now.

Step 7 sets the communication: a weekly status email to the sponsor each Friday and a short check-in with the team each Monday.

Step 8 gets the sign-off: the sponsor approves the plan, the baseline is saved, and the team starts the work on Monday. The course launches on the fixed date, and the final report says the reserve was never used.

Plan template: the sections in one table

The table below is the skeleton of the plan document, and you can copy it as the contents page for your own plan. Each row is one section, with the question it answers and the page it belongs on.

Template table for a project plan with eight sections and what each one answers
The plan template: eight sections, each answering one question.
Section Question it answers Where it comes from
Scope statement What will we deliver, and what is out? Step 1
Work breakdown structure What are the pieces, and who owns each? Step 2
Schedule and milestones When does each piece happen? Step 3
Resource plan Who does the work, and when? Step 4
Budget baseline What does it cost, and what is the reserve? Step 5
Risk register What could go wrong, and what will we do? Step 6
Communication plan Who needs what, how often, in what form? Step 7
Change control How does the plan change after approval? Step 8

Fill in each row before the work starts, and keep the document where the team can open it. A plan that lives on one person’s laptop is not a plan, it is a private note.

How to measure whether the plan worked

Measure the plan by three numbers: scope delivered, variance from the baseline and lessons recorded. Scope delivered is the share of the written deliverables the sponsor accepted. Variance is the gap between the planned dates and costs and the real ones, and small gaps mean the plan was honest. Lessons recorded is the simplest check: a closed project with no lessons page taught the next project nothing.

Add one softer check: ask the team whether the plan helped or got in the way. A plan that produces good numbers but is ignored by the team will not survive the next project, so the answer matters as much as the numbers. If the team says the plan was fiction, fix the planning steps before the next project starts.

Tools that hold the plan

A project tool holds the plan in one place, so the WBS, the schedule and the change log stay together. The tool carries the dates, the owners and the status, which means the manager updates one place instead of three documents. Our shortlist on the project management software page compares the options.

Tool Best for Free plan Starting price (as of November 2026) Notable limit
Asana Teams that want the plan, tasks and timeline together Free for 2 people $10.99 per user per month (Starter), billed annually Free plan covers 2 people
ClickUp Teams that want the WBS, Gantt chart and docs in one tool Free Forever plan $9 per user per month (Core), billed annually Page shows $9 against a $12 regular price, so it may be promotional
Trello Small teams that want a simple board per plan section Free for up to 10 collaborators $5 per user per month (Standard), billed annually $6 per user per month if billed monthly

The Asana price comes from Asana pricing: the Personal plan is free for 2 users, and Starter is $10.99 per user per month when billed annually.

The ClickUp pricing page lists Core at $9 per user per month billed yearly, shown against a $12 regular price.

The Trello pricing page lists Standard at $5 per user per month billed annually, or $6 billed monthly.

Common project plan mistakes to avoid

Most plan failures come from a missing section, not from a section written badly. Check this list before you ask for sign-off.

  • Scope with no exclusions. A scope that never says what is out grows every week, and the date slips with it.
  • A WBS that lists activities, not deliverables. A tree of tasks with no named result cannot be checked, so no one knows when a piece is done.
  • No baseline saved. A plan that changes without a saved baseline cannot be measured, so no one knows if the project is late.
  • Risks with no owner. A risk that no one owns has no response, and it will be the problem that surprises the team.
  • A plan nobody reads. A plan that lives on one laptop is a private note, and the team will build from memory instead.

Sources

Frequently asked questions

What is a project plan?

A project plan is a formal, approved document that guides both project execution and project control. It says what the project will deliver, who will do the work, when it will happen, what it will cost and how changes are handled. The team follows it day to day, and the sponsor measures progress against it.

How long should a project plan be?

It depends on the size of the project. A three-week internal project needs about a two-page plan, while a six-month cross-team effort needs a 15 to 20 page plan, with the structure the same either way. A plan that is longer than the work it describes is a sign that the writer is padding it, not planning it.

What is the difference between a project plan and a project charter?

The charter authorizes the project and states the goal and the high-level scope, while the plan says how the work gets done in detail. The charter is short by design and comes first, owned by the sponsor. The plan comes after the charter is approved and is owned by the project manager.

What should a project plan include?

A complete plan includes the scope statement, a work breakdown structure, a schedule with milestones, a budget, a resource plan, a risk register, a communication plan and a change control process. Small projects can keep each of these to a page or a table, but none of them should be missing entirely.

Who approves a project plan?

The sponsor approves the plan, usually with the key stakeholders. Approval turns the draft into the baseline: the approved scope, schedule and budget that later progress is measured against. Once approved, the plan changes only through a recorded change request, not by quiet edits.

How often should a project plan be updated?

Update it whenever a change is approved, and review it at least once a week during the work. A plan that is never updated becomes fiction within two weeks, and the team stops trusting it. Small updates through the change log keep the plan honest without rewriting the whole document each time.

Is a tool missing or out of date? Tell us and we will review it. Submit a tool