4.4
2,100+ reviews on G2
A project plan is a written document that defines a project’s goals, tasks, owners and dates, so everyone knows what has to be done and when. A plan that works does four things:

One sentence that says what done looks like at the end.
Break work down until each task has one clear result.
A name, not a team, so someone is accountable.
A due date for each task and a date for each phase.
Keep the plan in Evernote. Turn the brief into a task table, draw the timeline, and assign tasks.
Write one sentence that says what the project will deliver and how you will know it is done.
Name the things the project must produce, such as a website, a report or a moved office. Each deliverable becomes a group of tasks.
Split each deliverable into tasks small enough for one person to finish. A work breakdown structure does this in levels, from the whole project down to work packages.
Give each task a duration and a cost. Use the estimates to set the schedule and the budget, then save that version as your baseline.
Put a name next to each task. The owner is the person who finishes it, not the person who checks it.
Put the tasks on a timeline that ends at your deadline. Mark the end of each phase with a milestone.
Share the plan with the team and the people who approve it. Review it on a fixed date, compare what is done with what the plan said, and update it.
| Task | Owner | Due |
|---|---|---|
| 3Content audit | Ana | Nov 13 |
| 3New site map | Ben | Nov 17 |
| 5Write page copy | Ana | Nov 26 |
| 5Design and build | Chris | Dec 4 |
| 6Test on phones | Ben | Dec 9 |
| 6Launch | Chris | Dec 10 |
The plan is a note, so the brief and the kickoff notes sit in the same notebook.
The format changes how you see the work, not what the work is. Pick the one the team will actually open.
| Format | Best for | Watch out for |
|---|---|---|
| Task list | Small projects with one owner and a short timeline. | Dependencies and dates are easy to miss. |
| Gantt chart | Work with several tasks that overlap or depend on each other. | Needs a date and a duration for every task. |
| Kanban board | Work that moves through stages, such as design, build and test. | Less useful for long-term dates. |
Formats described in the project planning guide by ProjectManager. A Gantt chart places tasks and durations on a timeline.
Copy it, or save it to your Evernote account and fill in one row for every task.
| Task | Owner | Due | Status |
|---|---|---|---|
| Plan | |||
| Write the goal | $ | $ | $ |
| List the deliverables | $ | $ | $ |
| Break down the tasks | $ | $ | $ |
| Estimate time and cost | $ | $ | $ |
| Assign owners | $ | $ | $ |
| Set dates and milestones | $ | $ | $ |
| Track | |||
| Review status | $ | $ | $ |
| Update the plan | $ | $ | $ |
4.4
2,100+ reviews on G2
4.4
8,200+ reviews on Capterra
4.4
73,000+ reviews on App Store
248M
Registered users
A project plan is a series of documents that define how a project will be executed and controlled. ProjectManager describes it as the document that answers the who, what, where, why, how and when of the project. It covers scope, cost and schedule, plus the risks and the people who need updates.
A goal, the deliverables, the tasks, an owner for each task, dates, a budget and the main risks. ProjectManager also lists a communication plan and a change process, so the team knows who approves a change and who hears about it.
The end of one project phase and the beginning of the next. ProjectManager defines it that way, and notes that a milestone helps with tracking and morale.
A work breakdown structure breaks the project scope into phases, subprojects, deliverables and work packages that lead to the final deliverable.
Long enough to cover the goal, tasks, owners, dates and risks, and short enough that the team will read it. ProjectManager notes that teams rarely produce each subsidiary plan as a separate document; the plan should cover the important elements of each.
The schedule is one part of the plan. The plan also covers scope, cost, risk and communication. The schedule places the tasks and their durations on a timeline, as ProjectManager describes a Gantt chart.
Update it when a task, owner or date changes, and at every status review. Atlassian suggests status reports from weekly to monthly depending on the project and the people who need them, so match the update to that cadence.
Write down what you assume to be true and what you will decide later. ProjectManager recommends documenting assumptions, so a change later is a change to a stated assumption rather than a surprise.
Keep the project brief in a note, then let the AI Assistant turn it into a plan you can share.
Open the brief note and ask the AI Assistant to make a project plan with tasks, owners and due dates in a table. It creates a new note with the table.
Ask it to add a gantt chart of the plan. It writes a Mermaid diagram under the table, so the team can see which tasks overlap.
Ask it to turn each row into a task assigned to its owner. Each person sees their tasks with the due dates, and the note list shows how many are done.
Turn the brief into a plan, give every task an owner, and check the timeline before the next meeting.
Start for free