> 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/managing-your-implementation/status-report-template.md).

# Status Report Template

**Usage Instructions**

Completed by the Project Manager\
Delivered weekly at mutually agreed to timing (suggested is Monday or Tuesday)

*Steps to complete:*

1. Update project dashboard.
   1. Identify high-level project narratives & value items
2. Update project workstream information
   1. Project workstream examples are: modeling, configuration, integration, materials
   2. Include delivery dates and highlight milestones
   3. Call out any individual risks or issues related to each workstream
3. Compile all workstream risks & issues
   1. Each risk or issue must have a suggested mitigation plan & estimated completion timing
4. Deliver via email to all project stakeholders
   1. Internal and external stakeholders
   2. include dashboard screenshot in body of email

*  [Status Deck TEMPLATE.pdf](https://files.threek.it/training/CommunitySite_Resources/Status%20Deck%20TEMPLATE.pdf)


---

# 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:

```
GET https://community.threekit.com/getting-started/managing-your-implementation/status-report-template.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.