> For the complete documentation index, see [llms.txt](https://admin-services.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://admin-services.docs.intersectmbo.org/guides/vendor-guides/1-contracting-and-onboarding/how-to-write-milestones-within-your-statement-of-work.md).

# How To - Write Milestones Within Your Statement of Work

## Guide Overview

Submitting milestone evidence is a key part of ensuring transparency, accountability, and timely payment. 

**You will find links to the Milestone Acceptance Form Templates and Milestone Acceptance Form Examples at the bottom of this page.**

{% hint style="info" %}

## Download forms

To download the forms related to this page from [here](#downloads-and-resources)
{% endhint %}

***

### What is Considered a Good Example?

<table><thead><tr><th valign="middle">Good Example</th><th width="181">Milestone (Reference Name)</th><th width="212">Acceptance Criteria</th><th>Deliverables</th></tr></thead><tbody><tr><td valign="middle"><strong>Example</strong></td><td><strong>Milestone 1</strong> – Development of Constitutional Committee candidates registration.</td><td>Delivering a secure, reliable, and user-friendly production-ready platform that allows candidates to successfully register and enables administrators to efficiently manage and verify applications in full support of the Constitutional Committee election.</td><td>Deliver registration functionalities for CC candidates, test them, and make them production ready to support the CC election.</td></tr><tr><td valign="middle"><strong>Why is this a good example?</strong></td><td><p><strong>It is specific:</strong> The name clearly states the scope ("candidates registration") and its sequence in the project ("Milestone 1"), making it easy to understand and track.</p><p><br><strong>It is outcome-based:</strong> It focuses on the creation of a tangible capability rather than a vague period of work.</p></td><td><p><strong>It is measurable and objective:</strong> Success is defined by clear, testable actions like "candidates can successfully register" and objective qualities like "secure." These can be verified without personal opinion.</p><p><br></p><p><strong>It is binary:</strong> The criteria establish a clear pass/fail state. The platform either meets these conditions or it doesn't, leaving no room for ambiguity about whether the milestone is complete.</p></td><td><p><strong>They are tangible outputs:</strong> The deliverables are concrete results—a "production-ready" system with working "functionalities"—not just a list of ongoing tasks.</p><p><br></p><p><strong>They are verifiable:</strong> A reviewer can see the delivered functionalities, check the test results, and confirm the system is ready, providing clear proof of completion.</p></td></tr></tbody></table>

### What is Considered a Bad Example?

<table><thead><tr><th width="125" valign="middle">Bad Example</th><th width="181">Milestone (Reference Name)</th><th width="228">Acceptance Criteria</th><th>Deliverables</th></tr></thead><tbody><tr><td valign="middle"><strong>Example</strong></td><td><strong>Milestone 1</strong> - <strong>Phase 2</strong> Further Platform Development.</td><td>The platform's core features are mostly done and the UI is better. The system should be robust enough for some initial users to try out.</td><td><p></p><ul><li>Work on the smart contracts.</li><li>Continue design of the user interface.</li><li>Investigate different integration options.</li></ul></td></tr><tr><td valign="middle"><strong>Why is this a bad example?</strong></td><td><p><strong>It's not specific:</strong> What does "Further Platform Development" include? This name is generic and provides no clear scope. Stakeholders have no idea what is actually being built.</p><p><br><strong>It's not outcome-based:</strong> It describes a period of ongoing work ("Phase 2") rather than a specific outcome or achievement.</p></td><td><p><strong>It's not measurable or objective:</strong> Words like "mostly done," "feels better," and "robust enough" are subjective and depend on opinion. What one person considers "mostly done," another might see as half-finished.</p><p><br><strong>It's not binary:</strong> It cannot be answered with a simple "yes" or "no." This ambiguity leads to disputes over whether the milestone is actually complete.</p></td><td><p>They are tasks, not outputs: Phrases like "Work on," "Continue design," and "Investigate" describe ongoing activities, not finished, tangible items. It's impossible to confirm when "Work on" is actually complete.</p><p><br><strong>They are not verifiable:</strong> There is no finished product to hand over. How do you deliver "Continue design"? A good deliverable would be "Finalized UI Mockups" or "Deployed Smart Contract V1 on Testnet."</p></td></tr></tbody></table>

## Downloads and Resources

<table data-view="cards"><thead><tr><th></th><th data-type="files"></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>Download MAF Template</h4></td><td><a href="/files/3beOo6bGFzTIXat38C1G">/files/3beOo6bGFzTIXat38C1G</a></td><td></td><td><a href="/files/aVddcIPJZSe40CY3y4Ix">/files/aVddcIPJZSe40CY3y4Ix</a></td></tr><tr><td><h4>Download MAF Examples</h4></td><td><a href="/files/vXDEbBKjMBnt75SijHd9">/files/vXDEbBKjMBnt75SijHd9</a></td><td></td><td><a href="/files/Fpa5FiKPKDO4kKtraFxP">/files/Fpa5FiKPKDO4kKtraFxP</a></td></tr><tr><td><h4>Best Practice Policy</h4></td><td></td><td><a href="/pages/drlMmSXF6gNTPNchkSnx">/pages/drlMmSXF6gNTPNchkSnx</a></td><td><a href="/files/rENfdDemiImAB60CnRoz">/files/rENfdDemiImAB60CnRoz</a></td></tr></tbody></table>

***

<h3 align="center">Need Templates or Supporting Documents?</h3>

{% columns fullWidth="true" %}
{% column width="41.66666666666667%" %}

<figure><img src="/files/VDmdSeoDbaEsoM5IfdiW" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="58.33333333333333%" valign="middle" %}
Find proposal templates, guidance documents, and downloadable resources to support your submission.

<a href="/pages/CvfnEUjQR4xKXogPgv67" class="button secondary">Visit the Resources Page</a>  &#x20;

<a href="/pages/6ISsRyVdsEdxmqiIe0bI" class="button primary">Visit the Vendor Hub</a>

{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://admin-services.docs.intersectmbo.org/guides/vendor-guides/1-contracting-and-onboarding/how-to-write-milestones-within-your-statement-of-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.