Projects

Project Plan Template

A project plan says what will be true when the project is done, what is in and out of scope, which milestones get you there by when, who owns each one, and what could go wrong. This template adds the part most plans skip: a dated record of every change.

Updated 2026-10-27

Copy and adapt

The template

Project planTemplate

Owner: [name] Sponsor: [the person who can approve changes] Start: [YYYY-MM-DD] Target finish: [YYYY-MM-DD] Last updated: {{date}} Status: [On track / At risk / Off track] Related: [[Project brief]], [[Team name]]

Objective

[One or two sentences: what will be true when this is done, and why now.]

Success measures:

[Metric]: from [current value] to [target] by [date]

Scope

In scope: [deliverables this project will produce]
Out of scope: [things people will assume are included but are not]

Milestones

[Milestone]: [what "done" means] (@[owner]) @due(YYYY-MM-DD)
[Milestone]: [what "done" means] (@[owner]) @due(YYYY-MM-DD)

Resources

People: [name, role, share of their time]
Budget: [total, broken down, and who approves spend]
Tools and access: [what the team needs on day one]

Dependencies

[What you need from another team or vendor, and by when] (contact: [name])

Risks

[Risk] Likelihood: [low / medium / high]. Impact: [what happens if it occurs]. Mitigation: [action] (@[owner])

Communication

Status updates: [who receives them, how often, where]
Decisions: [where scope, date and budget changes get approved]

Changes to this plan

[YYYY-MM-DD]: [what changed, why, approved by whom]

5 examples

Examples for different situations

The same structure, filled in for the situations people actually bring to it. Copy the one closest to yours.

1.Software migration with a hard deadline

When it fits: Use this when a system has to move before a fixed business date, the old system keeps running in the meantime, and the riskiest part is data nobody has looked at in years.

Software migration with a hard deadlineExample 1

Billing migration to Stripe Billing

Owner: Hannah Weiss (engineering) Sponsor: Marcus Lee (CFO) Start: 2026-10-05 Target finish: 2027-01-22 Last updated: 2026-10-27 Status: At risk (proration test results due Nov 6) Related: [[Billing migration brief]], [[Platform team]]

Objective

Move all 2,300 paying customers from the in-house invoicing system to Stripe Billing before annual renewals start on Feb 1, 2027, so finance stops reconciling invoices by hand.

Success measures:

Manual invoice corrections: from about 140 a month to under 10 by March 2027
Zero customers double-charged during cutover

Scope

In scope: subscriptions, invoices, card payments, dunning emails, the finance export
Out of scope: multi-currency (removed Oct 20, see changes), purchase-order customers (38 accounts, stay on manual invoicing until Q2)

Milestones

Customer and plan data exported and cleaned (@Hannah) @done(2026-10-23)
Proration matches the old system for the 12 test scenarios (@Diego) @due(2026-11-06)
Pilot: 100 monthly customers billed by Stripe (@Hannah) @due(2026-12-01)
Finance signs off on December reconciliation (@Marcus) @due(2027-01-08)
All remaining customers cut over, old system read-only (@Hannah) @due(2027-01-22)

Resources

People: Hannah (60 percent), Diego (full time), Ana from finance (one day a week)
Budget: $24,000 for a contractor to write the data migration scripts, approved by Marcus
Tools and access: Stripe test and live accounts, read access to the billing database

Dependencies

Support macros for billing questions, ready before the pilot (contact: Ravi, support)

Risks

Proration differs from the old system. Likelihood: medium. Impact: customers see unexpected amounts on upgrade. Mitigation: run all 12 scenarios side by side before the pilot (@Diego)
Old card tokens fail to migrate. Likelihood: low. Impact: failed renewals in February. Mitigation: migrate tokens in the pilot first and measure the failure rate (@Hannah)

Communication

Status updates: Friday written update to Marcus and the support lead
Decisions: scope or date changes go to Marcus, in writing, in the Friday thread

Changes to this plan

2026-10-20: Multi-currency removed from scope. Only 41 customers pay in EUR, and supporting it added four weeks. Approved by Marcus.

2.Customer conference with a fixed budget

When it fits: Use this when the date and venue are fixed months ahead, most of the money is committed through contracts with deadlines, and the plan has to show what is locked and what can still move.

Customer conference with a fixed budgetExample 2

Fieldwork Summit 2027

Owner: Jordan Pike (events) Sponsor: Elena Varga (VP Marketing) Start: 2026-10-12 Target finish: 2027-04-30 (event Apr 15 to 16, wrap-up after) Status: On track Related: [[Summit 2027 brief]], [[Marketing team]]

Objective

Run a two-day customer conference in Austin for 250 attendees that produces at least 40 qualified expansion conversations for the sales team.

Success measures:

Registrations: 250 paid or comped by Mar 26
Expansion conversations logged by sales: 40 or more by Apr 30
Post-event survey score: 4.3 out of 5 or higher

Scope

In scope: venue, catering, AV, eight customer speakers, registration site, the evening reception
Out of scope: a virtual stream (decided Oct 26, see changes), partner sponsorships

Milestones

Venue contract signed and 30 percent deposit paid (@Jordan) @due(2026-11-20)
Hotel block of 180 rooms contracted (@Jordan) @due(2026-12-04)
Registration open (@Mia) @due(2027-01-12)
All eight speakers confirmed with talk titles (@Elena) @due(2027-02-05)
Final headcount to caterer (@Jordan) @due(2027-04-01)

Resources

People: Jordan (full time from February), Mia (registration and email), Elena (speakers)
Budget: $185,000. Venue $48,000, catering $62,500, AV $21,000, speaker travel $14,000, print and badges $9,500, contingency $30,000. Elena approves anything over $2,000.
Tools and access: registration platform, shared budget sheet

Dependencies

Customer list with account owners, from sales ops by Nov 13 (contact: Wes)

Risks

Hotel block attrition. Likelihood: medium. Impact: we pay for unused rooms if fewer than 80 percent are booked by Mar 15. Mitigation: negotiate the attrition date to Mar 29 and push hotel booking in every registration email (@Jordan)
Speaker drops out late. Likelihood: medium. Impact: a gap in the agenda. Mitigation: two backup speakers from the customer advisory board (@Elena)

Communication

Status updates: every second Monday to Elena and the sales director
Decisions: budget changes over $2,000 go to Elena

Changes to this plan

2026-10-26: Virtual stream dropped. Quote was $26,000 for an estimated 120 remote viewers; contingency stays at $30,000 instead. Approved by Elena.

3.Physical product launch with a supplier risk

When it fits: Use this when the launch date is promised to retailers, but the product itself is on a ship from a factory you do not control, and every other milestone depends on when it lands.

Physical product launch with a supplier riskExample 3

Ridgeway enameled Dutch oven launch

Owner: Carla Mendes (product marketing) Sponsor: Phil Ridgeway (founder) Start: 2026-10-19 Target finish: 2027-03-02 (launch day) Status: At risk (factory ship date unconfirmed) Related: [[Dutch oven line]], [[Spring 2027 wholesale]]

Objective

Launch the 5.5-quart and 7-quart enameled Dutch ovens on our site, Amazon and with 12 wholesale accounts on Mar 2, 2027.

Success measures:

3,000 units sold in the first 60 days across all channels
Amazon listing rated 4.5 or above after the first 50 reviews

Scope

In scope: product photography and video, site and Amazon listings, creator samples, wholesale sell sheets, launch email
Out of scope: the 3.5-quart size (2028), retail displays

Milestones

Pre-production samples approved (@Phil) @due(2026-11-13)
Photo and video shoot done (@Carla) @due(2026-12-11)
Factory ships 4,000 units (@Sunil, sourcing) @due(2027-01-15)
Stock received at the warehouse and at Amazon (@Sunil) @due(2027-02-12)
Samples delivered to 30 creators (@Carla) @due(2027-02-16)

Resources

People: Carla (lead), Sunil (sourcing), Ben (site and Amazon)
Budget: $95,000. Photo and video $18,000, paid social $40,000, Amazon listing content $6,000, creator samples $7,500, wholesale samples and sell sheets $8,500, contingency $15,000. Phil approves.

Dependencies

Final enamel color codes from the factory before the shoot (contact: Sunil)

Risks

Factory closes for Lunar New Year (Feb 6, 2027) before the order ships. Likelihood: high if the ship date slips past Jan 22. Impact: stock arrives in March, launch moves. Mitigation: pay the factory's $3,200 rush fee if samples are not approved by Nov 13 (@Sunil)
Color mismatch between photos and product. Likelihood: medium. Impact: returns and bad reviews. Mitigation: shoot with production samples only (@Carla)

Communication

Status updates: Tuesday stand-up with Phil, written summary to wholesale accounts monthly
Decisions: launch date changes are Phil's call and go to wholesale accounts within 48 hours

Changes to this plan

2026-10-26: Launch moved from Feb 16 to Mar 2 to leave two weeks between stock arrival and launch. Approved by Phil.

4.Office move before a lease ends

When it fits: Use this when a building has to be empty by a fixed date, lead times belong to landlords, contractors and internet providers, and the plan's main job is to start the slow things first.

Office move before a lease endsExample 4

Office move to 410 Harbor Street

Owner: Dana Ortiz (operations) Sponsor: Neil Brennan (COO) Start: 2026-11-02 Target finish: 2027-03-26 (old lease ends Mar 31) Status: On track Related: [[Office move 2027]], [[Facilities]]

Objective

Move 40 people to the new office with no lost working days and be out of the old space by Mar 26, 2027, five days before the lease ends.

Success measures:

Internet and phones working at the new office on move day
Zero holdover rent on the old lease

Scope

In scope: build-out of meeting rooms, furniture, network cabling, movers, old-office cleanup
Out of scope: new phone system (separate project), signage on the building exterior

Milestones

Internet circuit ordered (lead time 60 to 90 days) (@Dana) @due(2026-11-13)
Build-out drawings approved by the landlord (@Dana) @due(2026-12-04)
Furniture ordered (@Priscilla) @due(2026-12-18)
Build-out complete, walk-through done (@Dana) @due(2027-03-05)
Move weekend (@Dana) @due(2027-03-13)
Old office cleaned and keys returned (@Priscilla) @due(2027-03-26)

Resources

People: Dana (lead), Priscilla (office manager), Theo (IT, half time from February)
Budget: $142,000. Build-out $78,000, furniture $31,000, network cabling and equipment $16,000, movers $9,500, contingency $7,500. Neil approves.

Dependencies

Landlord's contractor schedule, confirmed after drawings are approved (contact: Ms. Park, building manager)

Risks

Internet circuit not live by move day. Likelihood: medium. Impact: 40 people without internet. Mitigation: order in week two, and keep a 5G backup router on site (@Theo)
Build-out runs late. Likelihood: medium. Impact: move weekend slips toward the lease end. Mitigation: weekly check with the contractor from January, and a fallback move date of Mar 20 (@Dana)

Communication

Status updates: monthly note to all staff, weekly to Neil from February
Decisions: anything that changes move day goes to Neil

Changes to this plan

2026-10-27: Phone system moved to its own project. Vendor needs until April, and the move cannot wait for it. Approved by Neil.

5.Grant-funded program at a public library

When it fits: Use this when the money comes from a grant with reporting rules, the team is part time, and the plan has to satisfy both the people running the program and the funder reading the report.

Grant-funded program at a public libraryExample 5

Digital skills for adults, Eastside branch

Owner: Teresa Ng (adult services librarian) Sponsor: Raymond Cole (branch manager) Start: 2026-11-02 Target finish: 2027-06-30 (grant report due Jul 15) Status: On track Related: [[Digital skills grant]], [[Eastside branch]]

Objective

Teach basic computer and online safety skills to 120 adults over 24 weeks, using the $60,000 county grant, and report results by Jul 15, 2027.

Success measures:

120 adults complete at least six of the eight sessions
70 percent can complete the end-of-course task (set up an email account and a strong password) without help

Scope

In scope: two weekly classes, Chromebook and hotspot lending, flyers in English and Spanish, an outside evaluator
Out of scope: one-to-one tech help sessions (existing volunteer program)

Milestones

Two part-time instructors hired (@Teresa) @due(2026-12-11)
20 Chromebooks and 30 hotspots set up for lending (@Luis, IT) @due(2027-01-08)
First cohort starts (@Teresa) @due(2027-01-19)
Mid-point numbers to the county (@Raymond) @due(2027-04-02)
Evaluator's report received (@Teresa) @due(2027-06-30)

Resources

People: Teresa (one day a week), two instructors (6 hours a week each), Luis (IT, as needed)
Budget: $60,000. Instructor stipends $28,800, Chromebooks $7,000, hotspot service $5,400, outreach printing $2,300, evaluator $9,000, county admin fee $7,500. Raymond approves; changes over 10 percent of a line need county approval.

Dependencies

County IT approval for the hotspot plan before purchase (contact: Mei Lin)

Risks

Low turnout in the first cohort. Likelihood: medium. Impact: we miss the 120 target. Mitigation: flyers at the food bank and the two nearest schools, and a Saturday class if weekday sign-ups are under 15 (@Teresa)
Hotspots not returned. Likelihood: low. Impact: fewer devices for later cohorts. Mitigation: lend for four weeks at a time, with reminder calls (@Luis)

Communication

Status updates: monthly to Raymond, quarterly to the county grants office
Decisions: budget line changes go to Raymond, and to the county if over 10 percent

Changes to this plan

2026-10-22: Saturday class added as a fallback after the county agreed that weekend hours count toward the grant. Approved by Raymond.

What a project plan has to answer

A project plan template is useful only if the finished plan answers five questions for someone who was not in the planning meeting: what are we trying to achieve, what are we not doing, what has to happen by when, who owns each piece, and what could stop us. Each section in the template above answers one of them.

Objective with success measures. One or two sentences, plus a number you can check later. "Improve billing" is not checkable. "Manual invoice corrections from 140 a month to under 10" is.
Scope, in and out. The out-of-scope line prevents more arguments than any other sentence in the plan.
Milestones with one owner and one date. Outcomes someone can confirm, not activities.
Resources and budget. Who is working on it, how much of their time, and how the money breaks down. If the numbers do not add up to the total, someone will notice in a budget review, and it will not be you.
Risks with mitigations and owners. The two or three things most likely to move the date, and who is doing something about each.
A change log. Every change to scope, date or budget, with the date and who approved it.

How to write one in an afternoon

Start from the brief. If there is a project brief, copy its goal and budget into the plan. If there is not, write the objective first and get the sponsor to agree with that sentence before anything else.
Work backward from the fixed date. Most projects have one date that cannot move: a lease end, a renewal date, an event. Put it last and place the milestones before it.
Find the long lead times. Contracts, hardware, hiring, internet circuits and approvals take weeks. Put them in the first milestones even if they feel early. The office move example orders the internet circuit in week two for this reason.
Name owners in the room. Ask each person to confirm their milestone and date out loud. A milestone assigned by email is a milestone nobody agreed to.
Write three risks. Not ten. The three that would actually move the date.
Send it to the sponsor for approval. The approved version is your baseline.

Keeping the plan true after the first slip

This is what most project plan examples leave out. The plan is accurate on the day it is approved and starts drifting the next morning. Three habits keep it honest:

Update the plan, then report. Before each weekly status update, change any dates or statuses in the plan. The report then quotes the plan instead of contradicting it.
Log every change with an approver. When a milestone moves, edit the date and add a line under Changes to this plan: what moved, why, and who agreed. Do not keep the old date and a new date side by side in the milestone list; the change log holds the history.
Re-baseline on purpose. If more than a third of the milestones have moved, the plan needs a fresh approval, not more patches. Rewrite the milestones, get the sponsor to sign off again, and note the re-baseline in the change log.

Project plan, brief or status report

Three documents get confused. The project brief comes first and asks for a yes. The project plan comes next and says how the work will happen. The project status report comes every week or two and says how the plan is going. If you are kicking off with the whole team, the project kickoff meeting template walks through the plan together.

Common mistakes

A task list instead of a plan. Two hundred tasks hide the five milestones that matter.
No out-of-scope line. Everything that is not written down as excluded will be assumed included.
Owners that are teams. "Marketing" owns nothing. One name per milestone.
Silent date changes. Editing a date without logging it makes the plan look accurate and impossible to trust.
Risks without owners. A risk list nobody acts on is a list of excuses written in advance.

Customization tips

Milestones are outcomes, not activities
"Design work" is an activity. "Build-out drawings approved by the landlord" is a milestone: someone can say yes or no on a specific date. Five to eight milestones is enough for most projects. Tasks belong in a task list.
Name the sponsor who can say yes
Every plan needs one person who can approve a change to scope, date or budget. Without a named sponsor, changes get made in hallways and the plan stops matching reality within a month.
Write out-of-scope first
In-scope lists are easy and everyone agrees with them. The out-of-scope line is where the arguments are, so write it early and get it approved. Each example above has one thing people would assume is included.
Give every risk an owner
A risk without an owner is a worry. Give each risk a mitigation that someone will actually do, with their name next to it, and review the list at every status update.
Shrink it for small projects
For a two-week project, keep Objective, Scope, Milestones and Risks, and drop the rest. The built-in Scribelet Project Plan uses exactly that shorter shape.
Keep the change log at the bottom
When a date or scope moves, edit the plan and add one dated line under Changes to this plan. Six months later, that log is the only honest answer to "why did this take longer?"

In the app

How to do this in Scribelet

Create a new note and pick Project Plan from the template strip. It is one of the five built-in templates, with Objective, Scope, Milestones, Resources and Risks, and it adds the #project and #planning tags.
Want the fuller version on this page? Open Desk Settings, then Templates, tap Add Template and paste it with the category set to Planning. {{title}} becomes the note's title and {{date}} stamps the last-updated line.
Write milestones as - [ ] Venue contract signed (@Jordan) @due(2026-11-20). They show up in the Tasks view and on your daily note until ticked, and @remind(2026-11-18 09:00) sends a push reminder two days ahead.
Link every status update, meeting and decision with [[Office move 2027]]. The plan's backlinks panel then shows the project's whole history in one place.
Ask the AI chat "what changed in the billing migration plan since October?" It answers from your notes with citations. On Pro, the stale checker flags plans nobody has reviewed in a while.

Templates, template variables and AI generation are documented in Note templates.

Frequently asked questions

How do I write a project plan?

Start with the objective in one or two sentences, then write what is out of scope, then list five to eight milestones with an owner and a date each. Add the resources, dependencies and risks last. Get the sponsor to approve it, and from then on change it only with a dated line in the change log.

What should a project plan include?

At minimum: an objective with a measure of success, scope (in and out), milestones with owners and dates, resources and budget, and risks with mitigations. Larger projects add dependencies, a communication plan and a change log. The template above has all of them; the five examples show how much detail each section needs.

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

A project brief is written before the project is approved: it explains the problem, the goal and the rough budget so someone can say yes. A project plan is written after the yes: it turns the brief into milestones, owners, dates and risks. Most projects need both, in that order.

Do agile projects need a project plan?

They need a lighter one. Keep the objective, scope, a handful of milestones (releases or dated outcomes rather than tasks) and risks, and let sprint planning handle the work in between. The plan answers "what are we trying to achieve and by when"; the sprint planning template answers "what are we doing this sprint".

Can I use this project plan template in Excel, Word or Google Docs?

Yes. It is plain Markdown, so headings, lists and checkboxes paste cleanly into Word, Google Docs, Notion or Obsidian. If you need a Gantt chart for dependencies between dozens of tasks, keep the schedule in a spreadsheet or project tool and link to it from the plan.

How often should a project plan be updated?

Whenever a milestone date, the scope or the budget changes, and at least once a week on an active project. A good habit is to update the plan right before writing the weekly project status report, so the two never disagree.

A project plan that still matches the project in March

Start from the built-in Project Plan template in Scribelet, track milestones as tasks with due dates and reminders, and link every status update back to the plan. Encrypted, free to start.

Start your project plan

or get the app

Download on theApp Store

Free plan, no credit card. See pricing

Projects

Project Brief Template

A project brief fits on one page and gets a yes: what problem this solves, what will be true when it is done, what is in and out, what it costs, and who approves it. Copy the template, or start from the example closest to your project.

Projects

Project Status Report Template

A status report tells readers in thirty seconds whether the project is on track, what changed since last time, and what you need from them. This template defines green, amber and red up front, so the color means the same thing every week.

Meetings

Project Kickoff Meeting Template

A kickoff meeting should leave behind one page everyone can point to later: why the project exists, what success looks like, what is in and out of scope, who decides what, and which assumptions could sink it. This template is the agenda before the meeting and that page after it.

Work

Decision Log Template

A decision log is a running record of what was decided, why, by whom, and what you expected to happen. This template adds the two fields most logs leave out: who disagreed, and a date to check whether the decision worked. Copy it for a team, or use the decision journal example for your own choices.

Product

Sprint Planning Template

Sprint planning goes wrong in two places: the team commits to last sprint's velocity with this sprint's people, and unfinished work rolls over without anyone deciding it should. This template does the capacity math in the open, makes a decision on every carried-over item, and ends with a sprint goal someone could check on demo day.

Projects

Lessons Learned Template

Most lessons learned documents are written once and never read again. This template compares plan to actual, writes each lesson as an instruction for next time with its evidence, and ends by naming the checklist, template or estimate each lesson should change.