Guide · Project planning

Project milestones: what they are, 40 examples and a template

A milestone is a checkpoint that says a part of the project is done. This guide explains what counts as one and what doesn’t, how many a project needs and how to set them in five steps, with 40 examples from app launches, theses, client work, books and events, and a template you can download and fill in.

By Yassine Zeriouh, developer of Milestones · Updated October 25, 2026 · 14 min read

What is a project milestone?

A project milestone is a checkpoint that marks a meaningful part of a project as done. “Beta in testers’ hands”, “chapter 3 approved”, “venue booked and deposit paid”: each one names a state of the project you can check on a given day. A milestone has a date but no duration of its own. The work happens in the tasks before it; the milestone is the moment you can say that stage is finished.

That makes milestones the coarse layer of a plan. A project with sixty tasks might have five milestones, and those five are what you look at when someone asks how it’s going, when you decide whether you’re on track, or when you plan the next month. Tasks tell you what to do today. Milestones tell you whether today’s work is adding up to anything.

Good milestones share three traits:

  • They describe a result, not an activity. “Design the onboarding” is a task, or a phase. “Onboarding design approved” is a milestone.
  • They’re checkable. On the due date, anyone could look and say yes or no. If the honest answer would be “sort of”, the milestone is too vague.
  • They matter. Reaching one should change something: you can start the next phase, send an invoice, show it to someone, or stop worrying about that part.

Project management textbooks call this a zero-duration event. In plainer words, a milestone is a finish line, and a project is a short series of them. It’s also exactly how the Milestones app defines a milestone: a checkpoint that groups its own tasks and shows how much of them is done.

Milestones vs tasks, deliverables, goals, phases and deadlines

These words get used interchangeably, which is how plans end up with forty “milestones” that are really tasks. The differences are simple once you put them side by side.

TermWhat it isExample
Task A piece of work that takes time and that someone doesWrite the App Store description
Milestone The moment a meaningful part of the project is doneApp submitted for review
Deliverable A thing you hand overThe finished build, the logo files, the report
Goal The outcome the whole project exists for1,000 downloads in the first month
Phase A stretch of the project with one purposeTesting, which ends at “beta feedback triaged”
Deadline A date something is due, often set from outsideThe conference talk on May 14

Two pairs cause most of the confusion.

Milestone vs deliverable. A deliverable is a thing, a milestone is a moment, and they often line up. “Logo files” is the deliverable; “client approved the logo” is the milestone. The milestone is the one that matters for your plan, because a delivered file that comes back with changes hasn’t finished anything yet.

Milestone vs goal. The goal is why the project exists; milestones are the checkpoints on the way to it. If you’ve written your goal as a SMART goal, with a number and a date, its milestones are the dates on which you’d check that you’re still on course. The SMART goal examples guide breaks 25 goals into exactly those checkpoints, and the SMART goal generator helps you write the goal in the first place.

A phase and a milestone belong together: every phase should end in one. “Testing” runs for three weeks; “beta feedback triaged and the release build ready” is the milestone that closes it. If you can’t name the milestone that ends a phase, the phase will quietly run on, because nothing ever says it’s over.

How many milestones does a project need?

Most personal and small-team projects work best with three to seven milestones. That range isn’t magic. It’s what keeps milestones useful for their two jobs: warning you early when the project slips, and letting you see the whole project at a glance.

A practical rule is one milestone every two to six weeks of work. Far fewer, and you lose the warning: if your only milestone is the launch date three months away, you’ll find out you’re late about two weeks before it, when there’s nothing left to cut. Far more, and they stop being milestones. Twenty checkpoints for a two-month project is a task list with extra steps, and you’ll stop updating it by week three.

Some quick calibrations:

  • A weekend project or a two-week sprint needs one or two milestones, or none. A task list is enough.
  • A one- to three-month project, such as an app update, a client website or a conference talk, usually lands at three to five.
  • A six-month to one-year project, such as a thesis, a book or a product launch, usually has five to eight, sometimes grouped into phases.
  • Anything longer is easier to run as several projects, each with its own handful of milestones.

The obvious objection is that some projects really do have dozens of checkpoints: a construction schedule, a regulated product release, a film shoot. Those are real, and they are what Gantt charts and dedicated scheduling tools are for, because their milestones depend on each other and on many people. If you’re reading this to plan your own project or a small team’s, you almost certainly don’t have one of those, and keeping the list short is the point.

Project milestone examples

Below are 40 milestones from eight kinds of projects. Each one is written as a result with a short “done when” that anyone could check, and each list links to a fuller walkthrough where one exists. Copy the shape and change the specifics.

App launch

The milestones an indie developer might set for shipping an app. The app launch checklist has every task between them.

  1. Prototype works on a real device: the core loop runs end to end; ugly is fine.
  2. Beta in testers’ hands: 20 people have the TestFlight build and know what to look at.
  3. Beta feedback triaged: every report is fixed, scheduled or explicitly dropped.
  4. App submitted for review: screenshots, description and privacy details are done.
  5. Launched: live on the App Store and announced where your audience is.

More on planning software this way: Milestones for indie developers.

Thesis or dissertation

  1. Proposal approved: your supervisor has signed off on the question and the method.
  2. Literature review drafted: a complete, rough chapter exists.
  3. Data collected: surveys closed, experiments run, sources gathered.
  4. Full first draft sent to your supervisor: every chapter exists, however rough.
  5. Final version handed in: formatted, proofread and submitted before the deadline.

The dissertation planning guide works backwards from the hand-in date, and Milestones for students covers courses and coursework too.

Client project

  1. Brief and quote signed: scope, price and deadline agreed in writing.
  2. Concept approved: the client has picked one direction.
  3. First full version delivered: everything in scope exists, ready for one round of changes.
  4. Final changes approved: the client has signed off.
  5. Handed over and invoiced: files delivered, final invoice sent.

Milestones like these often map to payments, which is a good reason to write their “done when” carefully. The client project tracking guide sets up one project per client, Milestones for freelancers covers the tools and the method, and Milestones for freelance designers shows the same approach for design work.

Indie game

  1. Prototype is fun: playtesters ask for another round without being prompted.
  2. Vertical slice done: one level at final quality, art and sound included.
  3. Alpha: the game is playable from start to finish, placeholders and all.
  4. Beta: no known blockers; only polish and balance changes are left.
  5. Released: live on the store page with the launch trailer out.

More: Milestones for game developers.

Book

  1. Outline done: every chapter has a one-paragraph summary.
  2. First third drafted: the opening chapters exist end to end.
  3. First draft finished: every chapter exists.
  4. Revised after beta readers: feedback from three readers is worked in.
  5. Manuscript sent: to an agent, an editor or the printer.

More: Milestones for writers.

Event

  1. Date and budget fixed: both written down and agreed with whoever pays.
  2. Venue booked: contract signed and deposit paid.
  3. Speakers or acts confirmed: every slot has a name and a yes in writing.
  4. Tickets on sale: the page is live and the first announcement is out.
  5. Run sheet final: every slot on the day has a person and a backup.

More: Milestones for event planners.

Side business or SaaS product

  1. Problem confirmed: ten interviews in which people describe the problem without being led.
  2. First version live for early users: a handful of people can sign up and use it.
  3. First paying customer: one person has paid real money.
  4. Pricing and onboarding done: a stranger can find out the price and get started without help.
  5. Public launch: announced on the channels you chose, with a way to measure the result.

More: Milestones for solo founders.

Video series

  1. Season plan locked: topics and order for every episode decided.
  2. First three episodes recorded: raw footage exists for the opening run.
  3. Thumbnail and title templates ready: every episode can be packaged in ten minutes.
  4. Half the season published: a regular schedule is holding.
  5. Season finished and reviewed: numbers checked and a list of changes for next season written.

More: Milestones for content creators.

Notice what the 40 have in common. None of them is an activity like “work on chapter 3” or “marketing”. Each one would make sense as the answer to the question “where are you with the project?”

How to set project milestones in five steps

Five steps take most projects from an idea to a milestone plan in under an hour. Each one says what done looks like, and what to do if you get stuck.

  1. Start from the finish line. Write the last milestone first: the moment the whole project is done, with its date. “App live on the App Store by March 3”, not “launch the app”. Done when: you have one sentence with a date in it. If you’re stuck: the date is unclear because the scope is; cut scope until you could commit to a date.
  2. Work backwards to the checkpoints. Ask what has to be true just before the finish. Then what has to be true before that. Stop when you reach today. You’ll usually end up with three to seven. Done when: every checkpoint is a result, not an activity. If you have more than eight: merge the small ones; they belong inside a milestone as tasks.
  3. Write a “done when” for each one. One line anyone could check: “20 testers have the build”, not “beta going well”. Done when: nobody could argue about whether a milestone has been reached. If you can’t write one: the milestone is too vague; split it in two or rename it.
  4. Date them, from the end backwards. Estimate each stretch of work, add a buffer of about 20 percent, and check the dates against your real calendar: holidays, exams, other projects, client work. Done when: every milestone has a date and the first one falls within the next month. If the dates don’t fit: move the finish line or cut scope now, not in week eight.
  5. Break only the next milestone into tasks. Plan the tasks for the milestone you’re working toward in detail and leave the rest as headlines. You’ll know far more about milestone four by the time you get there. Done when: you could start work tomorrow without thinking about what to do first.

The whole exercise fits on one page, and it should. If your plan doesn’t fit on one screen, you won’t look at it when it matters.

A project milestone template

The simplest milestone plan is a table with one row per milestone. Copy the one below, or download it as a spreadsheet that opens in Excel, Numbers and Google Sheets.

MilestoneDone whenDueStatus
Prototype works on a real device The core loop runs end to end on an iPhoneNov 20Done
Beta in testers’ hands 20 testers have the TestFlight build and know what to look atDec 11In progress
Beta feedback triaged Every report is fixed, scheduled or droppedJan 15Not started
App submitted for review Screenshots, description and privacy details are doneFeb 5Not started
Launched Live on the App Store and announced where your audience isFeb 19Not started

Download the project milestone template (CSV)

Keep it this small. Columns for owner, budget and dependencies make sense for a team; for a project you run yourself, they’re just more cells to keep current. Status needs three values at most: not started, in progress, done. When a milestone is late, change its date instead of inventing a fourth status, and note the original date once in a comment, so you can learn later how far off your estimates were.

How to track progress against milestones

Tracking milestones takes about ten minutes a week when the plan is small. Three habits do most of the work.

Work toward one milestone at a time. Mark the one you’re working on as active and keep the next one out of the way until it’s done. Projects stall when four milestones are each 60 percent finished, because nothing can be shown, shipped or billed.

Measure progress as tasks done inside the milestone. “7 of 12 tasks done” for the active milestone is a better signal than a feeling about the whole project. It’s crude, since tasks aren’t equal in size, but it moves every day, and a number that stops moving for a week is the earliest warning you’ll get.

Review the dates once a week. Look at the active milestone’s due date and its progress side by side. If it’s 40 percent done with 20 percent of the time left, decide now: cut tasks, move the date, or ask for help. Moving a milestone is fine. Not noticing that it moved is how projects end up three months late.

When a milestone slips, move its date and every later date that depends on it, in one go. Leaving the later dates as they were makes the plan look on time until the final week, which is the most expensive moment to find out it isn’t.

Mistakes that make milestones useless

  • Milestones that are tasks. “Email the printer” is a task. If a milestone takes an afternoon, fold it into a bigger one.
  • No “done when”. “Website mostly done” will stay 90 percent done for a month. Write the check.
  • Dates set once and never touched. A plan with stale dates trains you to ignore it. Update dates every week, especially when the news is bad.
  • Every milestone in parallel. Five half-finished milestones feel productive and deliver nothing. Finish one, then start the next.
  • More milestones than weeks. Then you have a task list. Group them.
  • Only one, at the end. A single launch-date milestone gives you no warning at all. Add the two or three checkpoints in between.

Where to keep your milestones

Where the plan lives matters less than whether you open it every week. Here are the usual options, including the ones that tend to work against you:

  • A spreadsheet or the template above works for a one-off project and costs nothing. It falls apart once tasks and milestones need to stay in sync, because you update both by hand.
  • A to-do app such as Things, Todoist or Apple Reminders is great for tasks and weak at milestones. You can fake them with headings or sections, but nothing shows how far along each one is. The Things 3 alternatives guide goes into that trade-off.
  • A Gantt or scheduling tool such as OmniPlan or Microsoft Project is the right choice when milestones depend on each other across a team. For one person, it’s more drawing than doing.
  • A team project tool such as Asana, Linear or Monday handles milestones well when a team shares the plan. Alone, you pay per seat for features you’ll skip; Milestones vs Linear compares the two approaches.
  • A project planner built around milestones is the middle ground, and it’s why I build Milestones. Each project is split into milestones with a due date, their own tasks and a progress bar, one milestone is marked active, and the app runs natively on iPhone, iPad and the Mac. It’s free for two projects, made for personal projects and solo work, and it isn’t built for teams or Gantt charts.

Whatever you choose, the test is the same: in ten seconds, can you see which milestone you’re on and whether it’s on time? If you can, the tool works.

Questions

What is a project milestone?
A project milestone is a checkpoint that marks a meaningful part of a project as done, such as “beta in testers’ hands” or “chapter 3 approved”. It has a date but no duration of its own: the work happens in the tasks before it, and the milestone is the moment you can say that stage is finished.
What is an example of a project milestone?
“First draft of the thesis sent to my supervisor”, “app approved by App Store review”, “client signed off the homepage design” and “venue booked and deposit paid” are all milestones. Each one names a state you can check on a given day, not an activity.
What is the difference between a milestone and a deliverable?
A deliverable is a thing you hand over: a file, a build, a report. A milestone is the moment something is finished or accepted, and it often lines up with a deliverable. “Logo files” is a deliverable; “client approved the logo” is the milestone.
How many milestones should a project have?
Most personal and small-team projects work well with three to seven. As a rule of thumb, aim for one every two to six weeks of work: fewer and you lose the early warning they give you, more and they turn into a task list.
Do milestones have a duration?
No. A milestone is a point in time with no duration. The work leading up to it takes time, which is why a milestone sits at the end of a phase or a group of tasks rather than spanning it.
Should every milestone have a due date?
Yes. A milestone without a date can’t tell you that you’re late. If you don’t know the date yet, give it a rough one and move it when you learn more, rather than leaving it blank.

Plan your next project in milestones

Milestones is a project planner for iPhone, iPad and Mac: a milestone for each checkpoint, tasks for the work in between, and progress you can see. Free for two projects.

Download on the App Store

Free for two projects

All guides →