> 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/pr-marketing.md).

# PR/Marketing

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

<table><thead><tr><th width="103">Stage</th><th width="377">Responsibilities</th><th>Timeline</th></tr></thead><tbody><tr><td><strong>Planning</strong></td><td>Develop communication strategy, design media/publicity plan, define target audience.</td><td>4–6 weeks before event</td></tr><tr><td><strong>Pre-Event</strong></td><td>Launch promotional campaign, create media kits, manage social media and press relations.</td><td>2–3 weeks before event</td></tr><tr><td><strong>Event</strong></td><td>Coordinate press/media coverage, manage branding materials, live social media updates.</td><td>During event</td></tr><tr><td><strong>Post-Event</strong></td><td>Publish recap content, share photos/videos, E-Journal, track engagement analytics, and maintain media relationships.</td><td>Within 5 days post-event</td></tr></tbody></table>

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

<table><thead><tr><th width="135">Category</th><th width="412">Task</th><th>Checkbox</th></tr></thead><tbody><tr><td>Branding</td><td>Develop event theme identity (logo, design)</td><td>☑️</td></tr><tr><td>Media</td><td>Create press release and invitation</td><td>☑️</td></tr><tr><td>Social Media</td><td>Roll out campaign (pre-event hype)</td><td>☑️</td></tr><tr><td>Content</td><td>Prepare promotional materials (flyers, videos)</td><td>☑️</td></tr><tr><td>Event Coverage</td><td>Set up media team, live stream, real-time updates</td><td>☑️</td></tr><tr><td>Post-Event</td><td>Publish thank-you posts, recap video, engagement analytics</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/pr-marketing.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.