> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/getting-started/implementation/milestone-signoff-project-acceptance-document.md).

# Milestone Signoff / Project Acceptance Document

Objective: Ensure customer confirmation of milestone/project completion

After a project is complete, we must send the customer a PDF via DocuSign agreeing that the milestone/project has been accepted and completed per the SOW.

Inform customer that no signature or response after 5 business days will assume milestone/project has been completed.

Make a copy of the Acceptance Form TEMPLATE, move the copy to the appropriate Google Drive project folder, and fill in the details in blue. Then make a PDF of the document and send it via Docusign.

This document must be sent immediately after written or verbal confirmation that every task in SOW or related change order(s) has been completed.

[Milestone Signoff Document](https://docs.google.com/document/d/12Vsezam7oA-VpKhf1TLhl1nrO09gGHrxdnGjNUHdX3k/edit)


---

# 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://community.threekit.com/getting-started/implementation/milestone-signoff-project-acceptance-document.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.