What it means
Begin with clear criteria before the milestone is due, stating the deliverable, quality standard, required documents, testing method, decision-maker and allowed exceptions. Avoid vague labels such as "phase nearly finished", because if the contract names a specific certificate or customer sign-off, a project manager's internal email may not replace it.
Conversely, an internal planning checkpoint may not need a formal customer signature, so match evidence to the actual purpose of the gate. Collect records while work happens, linking test results, drawings, photos and meeting decisions to the correct site, asset and revision, since a photo without context may show a completed wall but not prove hidden electrical work passed inspection.
A document labelled final might refer to an old design, so use version control and timestamps and preserve who performed and reviewed the test. Keep restricted customer data in the approved repository rather than copying it into an open spreadsheet.
Check exceptions, because a milestone may be achieved with a defined punch list if the agreement permits it, and the outstanding item, risk, owner, due date and effect on payment or use should be documented. Do not quietly redefine a failed test as a minor item to release an invoice.
If the customer rejects evidence, record the reason and next step rather than deleting the earlier submission, and contract owners should resolve disputed interpretations. Connect evidence to downstream actions, since finance should know which milestone can be billed and whether payment depends on customer acceptance, procurement may need confirmation before releasing a supplier payment, and operations may need a safe-to-use certificate before taking custody.
Where a milestone controls more than one action, communicate the specific status for each, because physical completion, internal approval and customer acceptance can occur on different dates. Review timeliness and quality, because late evidence can hold up cash even when work was done on time, so track missing documents by source and fix the process, such as requiring test records before crews leave site.
A pile of uploaded files is not a useful handover unless someone checks completeness and can retrieve the decisive record. Standard templates help if they leave room for the actual contract's conditions.
For owners, milestone evidence turns progress claims into decisions the business can rely on. It reduces premature spending and awkward customer billing, and it makes delays easier to explain and resolve without arguing from memory.
In practice
Real-world examples.
Example
A contractor links a passed inspection report to the completion milestone before requesting the next project payment.
Example
A software team records a customer-approved test result for release 2 rather than using a screenshot from release 1.
Example
A project lead keeps a permitted minor-defect list attached to conditional acceptance with owners and deadlines.
Formula
Calculation
Milestone evidence completeness = Required evidence items verified / Required evidence items for the milestone x 100
Worked example. An invented installation gate requires five items: a test certificate, training record, as-built drawing, customer review and safety sign-off. Four are verified.
- Completeness = 4 / 5 x 100 = 80%.
- If the missing item is safety sign-off, the gate is not passed just because the percentage looks high.
The contract's actual acceptance criteria, not the percentage alone, determine whether the milestone is achieved.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Beacon Installations, an invented warehouse automation contractor. Its team finished mechanical work and marked a milestone complete in the project tracker. Finance prepared an invoice, but the customer asked for a commissioning test and training record required by the contract. The site crew had left, and the test results sat in a technician's personal folder. Beacon retrieved the results, checked that they matched the installed version and completed a missing training session.
It sent an indexed evidence pack to the named customer reviewer and obtained the required acceptance through the agreed process. Finance adjusted its forecast and issued the milestone invoice only after the criteria were met. The project tracker began showing separate fields for physical work, evidence review and customer acceptance. The owner saw that finishing work and proving completion were both part of delivery. Future crews received a checklist for the records they had to capture before leaving site.
Watch out
Common mistakes.
- Treating a manually changed status field as proof of a contractual milestone.
- Using evidence from the wrong asset, site or revision.
- Billing or releasing the next stage while critical acceptance conditions remain unverified.
Questions
People also ask.
Does every milestone need customer sign-off?
No. Follow the relevant contract or internal gate; some require a customer decision and others only a verified internal record.
Can a milestone pass with minor work open?
Only if the agreement permits conditional acceptance and the remaining work is documented with owners and dates.
What if evidence was collected late?
Check its authenticity and relevance, record actual dates, and avoid backdating completion to make a deadline look met.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%