> For the complete documentation index, see [llms.txt](https://handbook.renaissancelabs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.renaissancelabs.org/programs-management/programs-schema/programs-department.md).

# Programs Department

<mark style="color:$danger;">**ROLES & RESPONSIBILITIES**</mark>

<table><thead><tr><th width="102">Stage</th><th width="373">Responsibilities</th><th>Timeline</th></tr></thead><tbody><tr><td><strong>Planning</strong></td><td>Define objectives, develop project charter, create budget, identify partners, and assign departmental roles.</td><td>4–6 weeks before event</td></tr><tr><td><strong>Pre-Event</strong></td><td>Monitor readiness, ensure resource allocation, conduct risk assessment, finalize event schedule.</td><td>2–3 weeks before event</td></tr><tr><td><strong>Event</strong></td><td>Supervise execution, handle coordination among departments, manage guests, troubleshoot issues.</td><td>Day(s) of event</td></tr><tr><td><strong>Post-Event</strong></td><td>Collect reports, conduct debrief sessions, develop post-event evaluation and recommendations.</td><td>Within 5–7 days after event</td></tr></tbody></table>

<mark style="color:$danger;">**CHECKLIST**</mark>

<table><thead><tr><th width="141">Category</th><th width="372">Task</th><th>Checkbox</th></tr></thead><tbody><tr><td>Objectives</td><td>Define event goals and success metrics</td><td>☑️</td></tr><tr><td>Budget</td><td>Draft and approve budget</td><td>☑️</td></tr><tr><td>Partnerships</td><td>Identify and confirm collaborators/sponsors</td><td>☑️</td></tr><tr><td>Schedule</td><td>Create full program timeline</td><td>☑️</td></tr><tr><td>Coordination</td><td>Weekly inter-departmental meetings</td><td>☑️</td></tr><tr><td>Documentation</td><td>Create attendance forms, program briefs, run sheet</td><td>☑️</td></tr><tr><td>Post-Event</td><td>Collect reports, debrief, write post-event evaluation</td><td>☑️</td></tr></tbody></table>


---

# 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://handbook.renaissancelabs.org/programs-management/programs-schema/programs-department.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.