> 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/2-delivery-and-milestone-management/how-to-complete-your-milestone-acceptance-form-maf.md).

# How To - Complete Your Milestone Acceptance Form (MAF)

## Guide Overview

This guide walks you through the full process of completing your milestone, preparing your Milestone Acceptance Form, uploading your evidence, and understanding how Delivery Assurance reviews your submission.&#x20;

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

***

## **Process to complete a MAF**

{% stepper %}
{% step %}

### **1. Complete the Milestone Work**

Before preparing any documentation, confirm that you have delivered everything outlined in your legal contract. Your milestone evidence must directly reflect the acceptance criteria agreed upon.
{% endstep %}

{% step %}

### **2. Prepare Your Milestone Evidence**&#x20;

Use the **Milestone Acceptance Form (MAF) Template** to document your work clearly and thoroughly. The template guides you through each required section:

#### **Milestone Name and Number**

Identify the milestone exactly as it appears in your contract.

#### **Milestone Description**

Copy and paste the full milestone description from your contract without altering the wording. This ensures clarity and prevents misunderstandings about what was expected.

#### **Acceptance Criteria Met**

This is the most important part of your submission. For each acceptance criterion:

* List the criterion exactly as written in your contract
* Confirm that the work has been completed
* Provide direct, publicly accessible evidence such as:
  * links to live features
  * video demonstrations
  * public code repositories
  * technical documentation
  * test results
  * public attestations or community‑visible updates

Your goal is to **show the work**, not simply state that it is complete.

#### **Quality and Testing**

Explain how you ensured the milestone is functional, stable, and high‑quality. This may include:

* Manual testing
* Automated testing
* Performance checks
* Security measures
* Usability and design reviews

Where possible, include links to supporting evidence such as test plans, reports, or scan results.

#### **Public Communication Summary**

Write a clear, non‑technical summary that explains:

* The purpose of the project
* How this milestone fits into the overall goals
* What was delivered
* Why it matters to the community
* Where people can learn more or follow progress

This helps the community understand the value you have delivered.
{% endstep %}

{% step %}

### **3.** Share Your Milestone Acceptance Form for Review

Once your Milestone Acceptance Form is drafted:

* Share it with Delivery Assurance after it has been reviewed by the Third Party Assurer, or
* Share it with both at the same time through Slack or your agreed communication channel

Delivery Assurance will provide feedback. Make sure to address all comments before finalizing.
{% endstep %}

{% step %}

### **4.** Finalize, Sign, and Upload Your Milestone Acceptance Form

When Delivery Assurance confirms that your evidence is ready:

1. Request the formal signature from the Third Party Assurer
2. Upload the final, signed Milestone Acceptance Form as metadata to your milestone in the administration dashboard
3. Sign the Milestone Acceptance Form through the dashboard
4. Delivery Assurance will complete the final signature

This must be completed on or before the milestone delivery date.
{% endstep %}

{% step %}

### **5. Review & Outcome**

Delivery Assurance will verify that:

* the Milestone Acceptance Form is complete
* evidence is correctly uploaded
* acceptance criteria have been met

#### **If evidence is sufficient**

Your payment will become available to withdraw on the milestone payment date.

#### **If evidence is insufficient**

Delivery Assurance will work with you to resolve the issue. If the issue cannot be resolved, the milestone may be paused with senior approval. Once sufficient evidence is provided and uploaded, payment will resume.

All milestone evidence is visible to the community. If you need to share sensitive information, contact Delivery Assurance before uploading.
{% endstep %}

{% step %}

### **6.** Understanding Metadata, Milestone Acceptance Forms & Invoices

#### **Milestone Metadata**

You must attach your completed Milestone Acceptance Form as metadata to the milestone in the smart contract dashboard. This ensures:

* consistency across all vendors
* clarity for reviewers
* transparency for the community

It is recommended that you share your Milestone Acceptance Form offline first (for example, through Slack) so any issues can be corrected before uploading.
{% endstep %}
{% endstepper %}

***

## 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-target 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/aK6bFNSrcuQxEUA81Pin">/files/aK6bFNSrcuQxEUA81Pin</a></td><td></td><td><a href="https://drive.google.com/drive/folders/1TMML86qVxOOy-Eufm5QqhVKCIruCSdMp">https://drive.google.com/drive/folders/1TMML86qVxOOy-Eufm5QqhVKCIruCSdMp</a></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="https://drive.google.com/file/d/18Yfv9rwKgayv1cVPzSj3QNOJP37UbIxZ/view?usp=drive_link">https://drive.google.com/file/d/18Yfv9rwKgayv1cVPzSj3QNOJP37UbIxZ/view?usp=drive_link</a></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="/pages/drlMmSXF6gNTPNchkSnx">/pages/drlMmSXF6gNTPNchkSnx</a></td><td><a href="/files/hdiOEQspX3FNBTsf2Huc">/files/hdiOEQspX3FNBTsf2Huc</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/WIMUqiIpi7xlh1CHmynE" 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>   <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/2-delivery-and-milestone-management/how-to-complete-your-milestone-acceptance-form-maf.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.
