Planning & Execution

Project Milestones: Definition, Gates, Payments, Example

By Vact Published · Updated

A project milestone is a point in time with no duration that marks the achievement of a key event or deliverable. The GAO Schedule Assessment Guide (GAO-16-89G, published 22 December 2015) puts it this way: “Milestones are points in time that have no duration but that denote the achievement or realization of key events and accomplishments such as program events or contract start dates.” PMI’s glossary wording (from the 2008 fourth edition of the PMBOK Guide, as reproduced in the SEBoK glossary) is shorter: “a significant point or event in the project.” A task consumes time and people; a milestone only records that something is now true. Everything else in milestone planning follows from that difference.

ItemTask (activity)Milestone
DurationHas an estimateZero days
ResourcesAssignedNone; GAO: “they should never be assigned resources”
Shown on a Gantt chart asA barA diamond
RecordsWork being doneA result, a hand-off or a decision
Example name”Test level 4 equipment""Level 4 test results report delivered”

The example names in the last row follow GAO’s naming advice: activities are verb-noun instructions, while milestone names “should be related to an event or a deliverable.”

What makes a milestone worth putting on the schedule

GAO’s guide sets three conditions that are easy to test against any draft milestone list.

  1. Major events or deliverables only. “A best practice is to include milestones only to reflect major events or deliverables.” Its examples are the start and finish of the design stage, the start and finish of subcontractor work, and key hand-off dates between parties.
  2. Clear conditions for completion. A milestone with no stated test for “done” cannot be reported honestly. GAO cites the Federal Aviation Administration’s standard program milestones, each documented with a description, completion criteria, WBS reference and decision authority.
  3. Not so many that they hide the work. Too many milestones “may mask the activities necessary to achieve key milestones.” GAO adds a warning that matters for tracking: “If work is represented by milestones, actual progress recorded in the schedule cannot be used to forecast the dates of key events.” A milestone cannot show how far along the work behind it is.

Two milestones belong on every schedule: the start and the finish. “No work should begin before the start milestone, and all project scope must be completed before the finish milestone.” A plan without a single start and a single finish “may produce an erroneous critical path.” The critical path method depends on that structure, and the work breakdown structure is where the deliverables that milestones mark come from. The NASA Work Breakdown Structure Handbook describes the sequence: once the WBS is defined, the team determines “the tasks (activities) and events (milestones) that are required to successfully complete the project objectives and products.”

Wording that can be checked

“Design phase complete” fails the completion test. “All UI wireframes approved by the Product Owner” passes, because someone can check it. “Sprint 3 complete” fails the significance test unless the sprint ends in a named deliverable; “User authentication deployed to staging” passes.

Milestone types and what each one controls

TypeExampleWhat it controls
DeliverableAPI v1 deployed to stagingOutput produced
Phase gateRequirements signed offWhether to commit to the next phase
DecisionGo/no-go for launchDirection and resources
Giver/receiver (hand-off)Vendor delivers hardware; test team receives itDependencies between teams or organisations
Contract/paymentDesign accepted; invoice releasableCash flow and legal obligation
CalendarQuarter end, budget cycleAlignment with business timing

Giver/receiver milestones deserve a note. GAO describes them as milestones defined between linked schedules, such as the government’s and the contractor’s, so that “integrated schedules reflect the same dates”; they represent dependencies between schedules, such as hand-offs between teams. In GAO’s example, a production schedule carries “receiver” milestones for material from outside suppliers and a “giver” milestone for delivering the produced article to the testing team, whose schedule has a matching receiver milestone. Where a supplier’s delivery is a date-constrained milestone, GAO cautions that this “may understate the risk in the procurement process.” Its alternative is to model the procurement as one activity or a sequence of activities, starting with ordering the product and ending with its receipt. A fixed-date milestone records what the supplier promised; the activity chain shows whether the promise is plausible.

Milestone charts and how to read one

A milestone chart is a schedule view that shows only the milestones, normally as diamonds on a time axis, sometimes with the dependencies between them. It is the summary layer. GAO describes three schedule levels: a summary schedule that gives decision makers a strategic view of progress toward key milestones, an intermediate schedule that can show the interim milestones needed before a major milestone decision, and a detailed schedule, the lowest level, that lays out the logically sequenced near-term work to achieve those milestones. Summary schedules are roll-ups of the lower levels, so the date of a key milestone in a summary chart should come from the detail beneath it, not be typed in separately.

That traceability is the test of a good chart. GAO’s horizontal-traceability practice asks that if a milestone’s predecessor activity is “greatly extended relative to available float, the date of the key milestone should slip.” If extending an activity changes nothing on the milestone chart, the logic does not connect them. If a milestone date moves without any activity behind it moving, the date is an opinion.

Two technical rules keep milestone charts accurate:

  • Use finish-to-start links. GAO notes that “there is little reason to sequence milestones with any logic other than F-S, because milestones simply indicate a point in time.”
  • Do not tie everything to one milestone. Many predecessors converging on a major milestone may mean that “major milestones are used to ‘tie off’ many predecessor activities, some of which may be only marginally related to the actual milestone.” Link only the work that has to be finished for the milestone to be true.

For long tasks, GAO recommends incremental milestones, also called inch-stones: “objective, product-oriented progress on the task,” managed under a control process, that enhance “the performance visibility of the activity” rather than representing “arbitrary points in time.” A 30-day build with no intermediate evidence reports “almost done” for most of its life. Three inch-stones, such as schema merged, first endpoint passing tests and all endpoints passing, show real movement.

Stage-gate reviews: milestones that carry a decision

A gate is a milestone whose outcome is a decision. The best-known gate model is Robert G. Cooper’s Stage-Gate system for new-product development, set out in “Stage-gate systems: A new tool for managing new products” (Business Horizons, vol. 33, no. 3, 1990, pp. 44-54). Stage-Gate International says the term first appeared in print in 1988 and cites Cooper’s 1988 article “The new product process: A decision guide for management” (Journal of Marketing Management, vol. 3, no. 3, pp. 238-255). That page describes the current model as a Discovery phase followed by five stages, each preceded by a gate:

StageMain output
1. ConceptA clearly articulated concept
2. Build the Business CaseA robust business case
3. DevelopmentA fully functioning prototype (or equivalent)
4. Testing and ValidationEvidence from pilots, field trials and trial production that product, market and operations are ready
5. LaunchFull commercialization, ending with a post-launch review

Each gate typically has three parts, per the same page:

  • Deliverables: outputs from the prior stage, “clearly specified ahead of time.”
  • Criteria: project readiness for the next stage and business value, the latter often assessed with a risk-adjusted financial model such as Expected Commercial Value and a scoring model such as the Value-Based Scorecard.
  • Outputs: a decision, usually one of “Go, Kill, Hold, or Recycle.” A Go also confirms resources, timeline, key deliverables and the date of the next gate, to avoid “approval without resources.”

Gatekeepers are senior managers from the functions that control the resources the next stage needs, and the project team attends the gate meeting.

What carries over to any project, software or not:

  • The deliverables list exists before the work starts. The team knows what the gate will ask for.
  • Kill and Hold are real outcomes. A gate that always says Go is a status meeting. Phase-gate milestones are where “stop” is cheapest.
  • Resources are committed at the gate, so the gate record names budget, people and the next date.

The Stage-Gate model was built for new-product work, so a three-week website build does not need five gates. One gate, before launch, with named criteria and a named approver, captures most of the value. For the question of whether fixed phases suit a given project at all, see agile vs waterfall; iterative teams usually keep the release and decision milestones and drop most deliverable milestones.

Payment milestones in contracts

A payment milestone attaches money to a verifiable event. Public rules show what makes these clauses hold up.

US federal fixed-price contracts. FAR Subpart 32.10 (performance-based payments, as of FAC 2026-01) allows payment against objective, quantifiable performance, defined events or other quantifiable measures of results. Its milestone discipline is strict:

  • Each event must be a necessary part of contract performance and be identified in the contract with a description of successful performance.
  • Contract signing, option exercise and the passage of time cannot be triggers, because they do not represent meaningful efforts or actions (32.1004(a)(1)).
  • The government must be able to readily verify each event (32.1004(a)(1)), and the administering contracting officer cannot approve a payment until the event is successfully accomplished (32.1007(d)).
  • Total payments may not exceed 90 percent of the contract price, or 90 percent of a delivery item’s price (32.1004(b)(2)), so the last payment waits for delivery.
  • These payments are “contract financing payments that are not payment for accepted items” (32.1001(b)). Under the FAR 52.232-32 clause, approval of a payment request “does not constitute an acceptance by the Government,” and the contracting officer may reduce or suspend payments on substantial evidence of failure to meet a material requirement.

Construction in England, Wales and Scotland. The Housing Grants, Construction and Regeneration Act 1996, section 109 entitles a party to a construction contract to payment by instalments, stage payments or other periodic payments, unless the work is specified or agreed to last less than 45 days. The parties are free to agree the amounts and intervals; in the absence of agreement, the Scheme for Construction Contracts applies.

Taken together, the two sources give a checklist for a private services contract:

  1. Define each payment event by a deliverable that a third party could check, not by a meeting or a date.
  2. Name who accepts the evidence and how long they have to respond.
  3. Distinguish a payment on progress from acceptance of the work, and say which one the milestone is.
  4. Hold back a final share until delivery and acceptance. The federal 90 percent ceiling is a rule for federal contracts, but it shows the logic.
  5. State what happens when evidence is incomplete: partial payment, a cure period or a hold.

Contracts involving real money should be reviewed by someone qualified in the relevant jurisdiction.

A worked milestone plan: help center launch

The plan below is an illustrative example built from the rules above, not data from a real project. It assumes a fixed-price contract of 40,000 for a help center of 12 articles, with payments tied to evidence. Baseline is the committed date and forecast is today’s expectation; they are stored separately, because the schedule should “be continually monitored so as to reveal when forecasted completion dates differ from baseline dates” (GAO, Best Practice 10).

#Milestone (event or deliverable)Acceptance evidenceAcceptsBaselineForecastPayment
M0Start: scope and brief signedSigned brief with the 12 article titlesSponsorWk 0Wk 00
M1Information architecture approvedNavigation map and article outlines reviewedProduct ownerWk 2Wk 24,000 (10%)
M2Template and layout acceptedAccessible page layout passes checklist; sample page live on stagingDesign leadWk 4Wk 58,000 (20%)
M3First 6 articles approved6 articles signed off with sourcesSubject expertWk 6Wk 78,000 (20%)
M4All 12 articles approved12 articles signed off, links checkedSubject expertWk 8Wk 98,000 (20%)
M5Launch approved (gate)Go/no-go record; owner named for correctionsSponsorWk 9Wk 108,000 (20%)
M6Final acceptance30 days live, open issues resolvedSponsorWk 14Wk 154,000 (10%)

Payments through M5 total 36,000, which is 90 percent of the price; the remaining 10 percent is released at M6, echoing the federal rule that financing stops at 90 percent until delivery.

Reading the table:

  • M2 slipped a week. M3 to M6 depend on the template, so the forecast for each moves with it. The sponsor sees the effect in the forecast column without searching.
  • M3 and M4 are separate on purpose. They split a 12-article effort into two verifiable steps, acting as inch-stones. If nine articles are ready and three lack screenshots, M4 is not met. The accepting person may approve a smaller release, move the date or resolve the dependency, and the plan records which choice was made. Redefining “ready” to keep the status green defeats the milestone.
  • M5 is the gate. It describes the accepted result, “launch approved”, not the meeting. A Tuesday review can occur with incomplete evidence. Put the preparation and review work on the schedule as activities so that the milestone has something to depend on.
  • Contingency sits before the committed date. GAO describes schedule contingency as “a gap in time between the finish date of the last activity (the planned date) and the finish milestone (the committed date).” Wk 14 is the commitment and the activities may finish earlier; M6’s Wk 15 forecast shows the one-week slip has used up that margin.

Keeping milestones honest during execution

Report forecast beside baseline. The weekly update shows the next significant milestone, its forecast, the evidence already complete and the dependency most likely to move the date. Use status reports with green, amber and red markers tied to the forecast gap, such as amber when the forecast has slipped but float remains.

Treat external approvals as risks. A date typed into a planning tool does not commit an outside reviewer. Record the expected response window and who follows up; if the date is unknown, keep the forecast unknown. Dependencies of this kind belong in the risk register.

Change dates openly. A moved milestone gets a reason and an owner. GAO says the baseline schedule is “subjected to a configuration management control process,” so the baseline changes only through an approved decision while the forecast moves freely.

Run a short review at each milestone. Four questions: Were the criteria met? What was learned? Is the remaining plan still valid? For gates, proceed, pivot or stop?

Avoid decorative milestones. Weekly checkpoints are fine if each marks a distinct, verifiable result. Checkpoints that mark only the calendar tell the sponsor nothing and make the real ones harder to find.

Sources