> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/oss-dapps/backoffice/step-5-marking-a-milestone-as-done.md).

# Step 5: Marking a Milestone as Done ✅

{% embed url="<https://youtu.be/SaTlwkC7DXI>" %}

This step is done by the **Service Provider** once they have successfully delivered the product or service.

📌 **Why is this step important?**

* This confirms that the work has been completed.
* The **Approver** will later check and approve this milestone before funds are released.

***

#### **1. Go to the "Service Provider" tab**

* In the **escrows section**, navigate to the **Service Provider** tab.
*

```
<figure><img src="/files/ZdtK8MF8bbScXyQK7APU" alt=""><figcaption></figcaption></figure>
```

* This tab will only show escrows where your **logged-in wallet** is assigned as the **Service Provider**.

***

#### **2. Open the escrow modal**

* Click on the **escrow you want to update**.
* This will open a **modal** displaying the escrow details, including:
  * Escrow title & description
  * Roles assigned to different addresses
  * Current milestone status

<figure><img src="https://2074000817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDg2e2YCRmNlhCnxxmEb6%2Fuploads%2F3gsCRhzV7gWECqS2EWVu%2Fimage.png?alt=media&amp;token=7e2c65bb-42ee-4766-bd86-dfffcf9fe291" alt=""><figcaption></figcaption></figure>

***

#### **3. Click "Complete" on the milestone**

* You will see a **blue button labeled "Complete"** next to the milestone.
* Click **"Complete"** to proceed.

***

#### **4. Sign the transaction**

* A **Freighter wallet** transaction request will pop up.
* This request confirms that you are **marking the milestone as completed**.
* Click **"Sign"** to approve the transaction.

<figure><img src="https://2074000817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDg2e2YCRmNlhCnxxmEb6%2Fuploads%2F3Ex8ztMVMksUnHGhDV5Y%2Fimage.png?alt=media&amp;token=6f3c3aae-f1b5-4afb-8f52-a2cfc29759d9" alt=""><figcaption></figcaption></figure>

***

#### **5. Milestone status updates**

* Once the transaction is signed, the **milestone will be marked as "Completed"**.
* The **progress bar** in the escrow modal will update, showing that this step is done.

<figure><img src="https://2074000817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDg2e2YCRmNlhCnxxmEb6%2Fuploads%2FCRfWO8KiIQJ2h53Jhfln%2Fimage.png?alt=media&amp;token=86ad5123-f8c2-4154-bf1c-ecebb16a0f97" alt=""><figcaption></figcaption></figure>

***

🎉 **Success! The milestone is now marked as completed.**\
The **next step** will be **approving the milestone**, which is done by the **Approver**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlesswork.com/trustless-work/oss-dapps/backoffice/step-5-marking-a-milestone-as-done.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.