
You have a plan, a deadline and a team, but no clear way to say whether the project is where it should be. Milestones fix that. A milestone is a checkpoint with zero duration that confirms a phase or a key piece of work is done, such as “design approved” or “permits issued”. The project milestones examples below are grouped by phase, and each one comes with the condition that tells you it has actually been reached.
This guide gives you 13 milestones that fit almost any project, 13 milestones for a construction project, short lists for software, agency and consulting work, and a practical way to set project milestones and track the hours that lead up to each one.
What makes a good project milestone
PMI defines a milestone as a significant point or event in a project. In practice, a milestone has no duration and needs no work of its own: it is the moment when the work that leads to it is finished and someone confirms it. Scheduling tools treat it the same way, as a task with a duration of zero. If you want the full background first, read our explainer on what a milestone in project management is.
A milestone is useful when you can answer three questions about it without debate. Is it observable, so anyone can check that it happened? Does it have a single owner who confirms it? Does something depend on it, such as the next phase, a payment or a go or no go decision? If the answer to any of these is no, you are probably looking at a task or a goal.
| Term | What it is | Example |
|---|---|---|
| Milestone | A checkpoint with zero duration that confirms progress | Client signs off the final design |
| Task | Work that takes time and effort | Prepare three homepage mockups |
| Deliverable | A tangible output handed to someone | The approved design file |
| Goal | The result the project is meant to achieve | Increase online sign ups after launch |
A milestone often marks the moment a project deliverable is accepted, which is why the two are easy to confuse. The deliverable is the thing; the milestone is the date it was approved.
13 common project milestones examples
Most milestones sit at the end of a phase of the project life cycle, with a few smaller checkpoints inside each phase. A phase can mean more to one team than to another: the end of design is a big moment for designers and barely registers for the sales team that joins after development. That is fine. Pick the milestones that matter to the people who must act on them.
Milestones are used in most industries. Teams in engineering, technology, finance, law and healthcare rely on them heavily because their projects usually involve formal approvals and dependencies between groups.
Early stages
-
Funding approved.
Reached when the budget is signed off and available, ideally with a reserve for changes. Nothing else should start before this, because the team needs to be paid for its work.
-
Project plan approved.
Reached when sponsors sign the plan that sets objectives, scope, schedule and responsibilities. The plan will change later, but the team needs an agreed version to work from. A work breakdown structure makes this milestone easier to verify, because every piece of scope has a place in it.
-
Team trained.
Reached when everyone who needs new skills or knowledge has completed training, for example a knowledge transfer to an operations team. Training can be run in house or outsourced when specialist knowledge is required.
-
Design approved.
Reached when the design that answers “how will we build this” is reviewed and accepted. Depending on the project, it may be a set of sketches, web layouts or a prototype. Some teams set two milestones here: design review complete and design signed off.
Mid project and miscellaneous milestones
-
Resources secured.
Reached when the people, products and services named in the plan are in place, for example when a development team is deployed or a supplier contract is signed.
-
Working environment ready.
Reached when the lab, system or application the team needs is set up and usable. Ideally this happens early, but projects often start before the environment is complete, so it deserves its own checkpoint.
-
Integration complete.
Reached when a new component works inside the larger system alongside other technologies. It can also mark the point when two teams start working as one.
-
Kickoff or key communication event held.
Communication runs through the whole project, but a single event can be a milestone, such as an effective project kickoff meeting where stakeholders agree on scope and roles.
-
Process started or completed.
Reached when a defined process begins or ends. In a software project, for example, the start of the testing process is a common milestone.
Final stages
-
Deliverable accepted.
Reached when the client or sponsor accepts a piece of work. Deliverables often have commercial consequences, so this milestone frequently triggers an invoice or a payment to a vendor.
-
Objective achieved.
Reached when a goal from the plan is met. Not every goal deserves a milestone. Goals describe where the team is going; milestones are the reference points that prove the project is getting closer.
-
Testing passed.
Reached when the product works as intended in a controlled environment. Passing tests does not finish the project, but it means the product is ready for release or handover.
-
Handover to maintenance.
Reached when issues found after release are resolved and the product moves to the team that will support it. This is often the last milestone before the project is formally closed.
13 milestones of a construction project
Construction milestones are more standardized than in most fields because permits, inspections and contract payments depend on them. The sequence below is a typical one for a new building. Your contract, local building department or company system may name and number them differently, so always use the definitions written in your own contract documents.
| # | Construction milestone | What it confirms |
|---|---|---|
| 1 | Feasibility and site approved | The owner has the site and has decided to proceed |
| 2 | Design and construction documents approved | Drawings and specifications are final enough to price and permit |
| 3 | Permits issued | The authorities allow work to start |
| 4 | Contracts signed and notice to proceed issued | The contractor is engaged and the contract clock starts |
| 5 | Site preparation complete | Clearing, grading and utility connections are done |
| 6 | Foundation complete | Foundations are poured and inspected |
| 7 | Structure topped out | The structural frame has reached its full height |
| 8 | Building dried in | Roof, walls and openings keep weather out, so interior work can begin |
| 9 | MEP rough in complete and inspected | Mechanical, electrical and plumbing systems are installed inside walls and ceilings before they are closed |
| 10 | Interior finishes complete | Drywall, flooring, fixtures and paint are installed |
| 11 | Substantial completion | The owner can occupy or use the building for its intended purpose |
| 12 | Certificate of occupancy issued | The local authority allows the building to be occupied |
| 13 | Final completion and closeout | Punch list items are fixed, documents are handed over and final payment is made |
Substantial completion is the milestone that causes the most disputes, because warranties, retainage and delay damages often depend on its date. The widely used AIA A201 2017 general conditions describe it as the stage when the work is sufficiently complete under the contract documents so the owner can occupy or use it for its intended purpose, as summarized by Saul Ewing attorneys for NASBP. The order of milestones 11 and 12 also varies by jurisdiction, so check how your contract links the two.
A construction milestone schedule is simply this list with planned and actual dates for each row. Many contractors tie progress payments to it. If you are choosing software for that job, see our roundup of construction project management tools.
Milestone examples in other industries
| Industry | Example milestones |
|---|---|
| Software development | Requirements signed off, architecture approved, feature freeze, user acceptance testing passed, production release |
| Marketing or creative agency | Brief approved, concept chosen, first draft delivered, final assets approved, campaign live |
| Consulting and professional services | Statement of work signed, discovery complete, findings presented, recommendations accepted, engagement closed and invoiced |
| Product launch | Prototype approved, supplier contracts signed, pilot batch produced, launch date confirmed, product available to buy |
| Event planning | Venue booked, speakers confirmed, registration opened, final attendee list locked, event held |
In client work, it pays to align milestones with the scope of work and the billing schedule. When the client has to approve a milestone before the next phase starts, you get a natural point to discuss changes before they turn into unpaid work.
How many milestones a project needs
There is no standard number. A team manager picks milestones based on the size and expected duration of the project. Our rule of thumb is one milestone at the end of each phase, plus one for every external dependency or payment. Avoid making them too frequent. If the team hits a “milestone” every day, nobody treats it as meaningful, and you lose the motivation that comes from reaching a real checkpoint together.
Three mistakes come up again and again:
- Calling a task a milestone, for example “work on the homepage”, which has duration and no clear end.
- Setting a milestone without a completion condition, so people argue about whether it was reached.
- Tracking the milestone date but not the effort spent getting there, so you only learn about overruns when the date slips.
How to track project milestones
Tracking a milestone means comparing its planned date with the forecast date and the actual date, and acting early when they drift apart. You can do this in a spreadsheet, a Gantt chart tool or a time tracker, depending on what you need to see.
Start with a milestone chart
For a small project, a milestone chart is enough. List each milestone with its owner, completion condition, planned date, forecast date and actual date, then review it in every status meeting. You can download our free milestone chart template here:
Larger projects usually need dependencies between tasks and milestones, so a slipped task moves every milestone after it. That is what Gantt charts are for. Most project management tools with a timeline or Gantt view let you add milestones as zero duration items. In Microsoft Project, for example, you type 0 in the Duration field of a task to turn it into a milestone, according to Microsoft’s own guide.
Track the work behind milestones in actiTIME
A milestone chart tells you whether a date was hit. It does not tell you how much effort it took, or whether you are burning through the budget on the way. That is where actiTIME helps. It is not a dedicated milestone planner; it is a time tracker with project tracking built in, so you see the hours and costs that lead to each checkpoint.
A simple setup looks like this:
-
Group the work behind each milestone.
actiTIME organizes work as customer, project and task. Create the tasks that lead to a milestone in the same project, or name a task after the milestone itself, such as “Design approval”.
-
Add deadlines and estimates.
Give each task a deadline with reminders and an estimate in hours. Custom workflow statuses and the Kanban board show which tasks are still blocking the milestone.
-
Set a budget.
Add a time, cost or billing budget at the project or task level. The progress bar turns red when the budget is exceeded, so you see the problem before the milestone date.
-
Review actual against planned effort.
The Estimated vs. Actual Time Report shows where tracked hours differ from estimates, and the Time-Track Report groups hours by customer, project or user. See all actiTIME reports for details.
FAQ
What is an example of a milestone in a project?
“Client approves the final design” is a typical project milestone. It takes no time itself, it has a clear owner (the client), and the next phase depends on it. Other common examples are funding approved, testing passed and deliverable accepted.
What do you mean by key milestones?
Key milestones are the few checkpoints that sponsors and clients care about most, usually the end of each phase, contract signature, major approvals and final delivery. They go in status reports and contracts, while smaller milestones stay in the team’s working schedule.
What is a construction milestone schedule?
It is a list of the major construction checkpoints, such as permits issued, foundation complete, building dried in and substantial completion, with planned and actual dates. Owners and contractors use it to track progress and often to schedule progress payments.
What are the 13 milestones of construction?
There is no single official list. A typical sequence is: feasibility and site approved, design documents approved, permits issued, notice to proceed, site preparation, foundation, structure topped out, building dried in, MEP rough in, interior finishes, substantial completion, certificate of occupancy, and final completion. Your contract may define a different set.
How do you track milestones in a project?
Give each milestone an owner, a completion condition and a planned date. Review planned, forecast and actual dates in every status meeting, and track the hours and budget spent on the tasks that lead to each milestone, so you catch delays before the date slips.
How do you put a milestone in Microsoft Project?
Add a task and type 0 in its Duration field. To keep a duration but still show the task as a milestone, open Task Information, go to the Advanced tab and select “Mark task as milestone”.
Turn milestones into a schedule you can trust
A milestone earns its place when someone can confirm it happened and the next step depends on it. It only protects your schedule if you also watch the effort that leads up to it. Use the examples above as a starting list, cut the ones that do not fit your project, and add the completion condition for each.
To see the hours and budget behind every milestone, start a free 30-day trial of actiTIME, or book a demo if you want a walkthrough. You can also stay on the permanent free version for teams of up to 3 users.






