> 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-manage-contract-changes.md).
# How To - Manage Contract Changes
## Guide Overview
During delivery, projects evolve and sometimes your contract needs to evolve with it. Whether you’re requesting a modification, seeking a disbursement outside the smart contract, or raising a concern, this guide walks you through the correct process and who to contact at each stage.
## Modifying a Contract
{% stepper %}
{% step %}
### **1. Start with a Discussion**
Before submitting anything, reach out to the Delivery Assurance (DA) Team. Early collaboration helps both parties align on what needs to change and ensures the final request is accurate and mutually agreed.
{% endstep %}
{% step %}
### **2. Submit Your Request Using the Template**
Once aligned, send your modification request to the DA Team using the provided template. This ensures all required information is captured clearly.
{% endstep %}
{% step %}
### **3. Review and Update the Contract**
DA and Procurement will work with you to review the request and make the necessary updates. These changes will be formally recorded in either:
* an updated legal contract, or;
* a Statement of Work (SOW) addendum.
{% endstep %}
{% step %}
### **4. Update the Vendor Smart Contract**
Before the changes take effect, a modify action must be executed on your vendor smart contract instance. This ensures the update is transparent and visible to the community.
The process is as follows:
* Intersect initiates and signs the modification action.
* The action is then passed to the vendor and the oversight committee for their signatures.
* All signatures must be completed within 36 hours. If not, the action expires and must be resubmitted.
{% endstep %}
{% endstepper %}
***
## **Requesting a Disbursement**
In some cases, ADA payments via smart contracts may not meet the needs of your project. When this happens, you may request that funds be disbursed in Stablecoins or Fiat instead.
{% hint style="warning" %}
### **Important Note**
This process is exception‑only. Moving funds out of a smart contract reduces transparency, so it should only be used when absolutely necessary.
{% endhint %}
### **How to Request a Disbursement**
1. Contact your Delivery Assurance POC to explain the situation.
2. These requests are reviewed by the Intersect executive team and handled on a case‑by‑case basis.
### **Provide a Clear Rationale**
Your request must include a rationale explaining why funds need to be moved out of the smart contract. Once agreed, this rationale will be attached to the disbursement action.
***
## Need Templates or Supporting Documents?
{% columns fullWidth="false" %}
{% column width="33.33333333333333%" %}
{% endcolumn %}
{% column width="66.66666666666667%" valign="middle" %}
Find proposal templates, guidance documents, and downloadable resources to support your submission.
Visit the Resources PageVisit the Vendor Hub
{% 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-manage-contract-changes.md?ask=&goal=
```
`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.