> 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/stakeholder-meeting.md).

# Stakeholder Meeting

**Usage Instructions**

Completed by the Project Manager\
Delivered weekly at mutually agreed to timing (suggested is once a month)

Steps to complete:

Create Meeting Deck containing the following -

* Current overall project status
  * Supporting information for each area (budget/timeline/resources)
  * Identification of high-level project narratives & value items
* Review Project workstream information
  * Project workstream examples are: modeling, configuration, integration, materials
  * Call out any individual risks or issues related to each workstream
  * Review all workstream risks & issues that require stakeholder attention/intervention
  * Each risk or issue must have a suggested mitigation plan & estimated completion timing
* Review Timeline that Includes delivery dates and milestones
  * Review upcoming phases
  * Discuss planning for next phases (i.e. UAT)
* Open the floor for questions/feedback
*  [Stakeholder Meeting - TEMPLATE.pdf](https://files.threek.it/training/CommunitySite_Resources/Stakeholder%20Meeting%20-%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/stakeholder-meeting.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.