> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/getting-started/getting-started-in-slack/prep-your-weekly-status-update-or-team-meeting-from-slack.md).

# Prep your weekly status update or team meeting from Slack

Every week someone rebuilds the same picture by hand: what got done, what slipped, what needs a decision. Whether your team calls it a status update, a weekly sync or a leads meeting, it's the same work, and it usually lands on whoever has the least time for it.

Rhythms gathers updates across your connected tools and prepares the weekly brief, so your team spends less time chasing status and more time deciding what happens next.

{% hint style="success" %}
**The short answer**

In any channel Rhythms is in, post `@Rhythms prep this week's status update`

Rhythms drafts an update from the sources it can access and chooses a format based on the information it finds. You can refine the content and format in the same thread.
{% endhint %}

<p align="center"><a href="https://api.rhythms.ai/slack/add?cta_id=gitbook_how_to_weekly_update" class="button primary" data-icon="slack">Try for Free in Slack</a></p>

***

### Before you start

* [**Set up Rhythms in Slack**](https://help.rhythms.ai/getting-started/getting-started-in-slack/getting-started-with-rhythms-in-slack.md)
* **Connect Rhythms to channels and tools your team works in:** The more context Rhythms can read, the less chasing you have to do

***

## Step 1: Ask for the update

#### If you know what you want

Ask Rhythms in a team channel or a DM.

**Try it:** `@Rhythms prep this week's status update`

> **Also works:** *"prep the agenda for our weekly team meeting" · "what's open going into Monday's sync?" · "build the agenda for our leads meeting"*

#### If you want it to find the work

Ask Rhythms to look. It comes back with the recurring updates and meetings it can see your team assembling by hand, and you pick.

**Try it:** `@Rhythms find a recurring status update or meeting you could prep for my team`

{% hint style="warning" icon="lightbulb-on" %}
**Tip:** Connect your team's calendar and tools for the most actionable results. Rhythms can use project, customer, and reporting data to make updates more specific.

[Manage your connectors →](https://help.rhythms.ai/connectivity/manage-connectors-for-your-workspace.md)
{% endhint %}

***

## Step 2: Provide context, review the draft, and make it yours

#### Provide context

Connect tools where your teams do their work. Then point Rhythms to the channels, projects, documents and reports that matter for this update.

<details>

<summary>See examples here!</summary>

<table><thead><tr><th width="189.640625">Your function</th><th>Worth connecting</th><th>What it adds to the update</th></tr></thead><tbody><tr><td>Leadership and Operations</td><td>Google Sheets, Google Drive</td><td>Performance against plan and each team's review inputs</td></tr><tr><td>Program management</td><td>Jira, Asana</td><td>Milestones, dependencies and cross-team blockers</td></tr><tr><td>Engineering</td><td>Jira, Linear, Datadog</td><td>Delivery progress, blockers and slipped commitments</td></tr><tr><td>Marketing</td><td>HubSpot, Mixpanel</td><td>Campaign pipeline and conversion</td></tr><tr><td>Product</td><td>Linear, Mixpanel</td><td>Launch progress, adoption and retention</td></tr><tr><td>Sales</td><td>HubSpot, Salesforce</td><td>Pipeline movement, closed deals and renewal risks</td></tr></tbody></table>

</details>

#### Review the draft

Rhythms drafts from context it sees. If it asks for the team, period or missing updates, supply those and review the draft.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FjP3v164tKPUHhz1OE6zt%2Fweekly-sales-update.png?alt=media" alt=""><figcaption><p>A sales update organized around the available context</p></figcaption></figure>

#### The format

Rhythms chooses a format based on the information it finds. You can customize the sections, order and level of detail to suit the way you work.

A popular format for a weekly status update is:

* **What changed:** progress and changes since the last update
* **What's at risk:** blockers, delays and what they could affect
* **What needs a decision:** the choice to make, who needs to decide and by when

You can choose to use it as a starting point or adapt it to your liking. For a meeting agenda, you might put decisions and blockers first.

**Try it:** `@Rhythms use three sections: What changed, What's at risk, and What needs a decision. Keep it under 150 words.`

> **Also works:** *"group it by workstream" · "group it by person" · "put blockers first"*

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FdOQjU2lBdNyUmjj3xTOk%2Fweekly-custom-format.png?alt=media" alt=""><figcaption><p>A status update using the three-section format</p></figcaption></figure>

#### The cadence

For recurring prep, specify the meeting time, schedule and destination you'd like it delivered.

**Try it:** `@Rhythms prepare this update every Thursday at 9 a.m. Central and send it to me in a DM for review`

> **Also works:** *"send it to me first, then post it to the channel"*

***

## Step 3 · Optional: Share notes and follow-ups after the meeting

Share the meeting notes in the thread or connect the source where they’re captured

**Try it:** `@Rhythms after the meeting, post the notes and follow-ups here`

Rhythms proposes owners based on who was involved and flags anything nobody owns. You confirm before it posts.

<p align="center"><a href="https://api.rhythms.ai/slack/add?cta_id=gitbook_how_to_weekly_update" class="button primary" data-icon="slack">Try for Free in Slack</a></p>

## Make it a habit

**Confirm the recurring setup.** Check that a playbook was actually created, which sources it uses and how it delivers. An approved recurring playbook can post automatically; ask explicitly if every draft should come to you for review first.

**Try it:** `@Rhythms do this before every weekly sync`

**Keep working in the thread.** Every update Rhythms posts is a thread you can keep working in.

**Try it:** `@Rhythms how does the referral decision affect our launch timeline?`

> **Also works:** *"add this to next week's agenda" · "find the working doc for the partner directory and break it into tasks"*

**Get a pre-brief for yourself.** The update is for the group. Ask in a DM for the one that's for you: the decision someone's waiting on you for, or the item that's slipped two weeks running.

**Try it in a DM:** `What do I need to know before the marketing sync?`

***

## Worth knowing

**Provide the right context.** Rhythms works best from accessible sources. Share notes in the thread or connect the tools where your team does the work.

**Check coverage, channel by channel.** Adding Rhythms lets you talk to it there. Reading channel history also requires a working connection and the appropriate access.

**It works best for recurring meetings with a channel behind them.** Weekly team meetings, sprint reviews, pipeline reviews, leads meetings. The value comes from the week of activity between meetings that you'd otherwise reconstruct.

***

## If something didn't work

**The draft is thin or says it cannot read the channel.** Check the Slack connection and channel access. Make sure Rhythms is added to channels where your team works

**You asked for a recurring update but have not received one.** Ask what was actually configured. Confirm the schedule, destination and review requirements before relying on it. You can also see all recurring automations on the playbooks tab on web.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/getting-started/getting-started-in-slack/prep-your-weekly-status-update-or-team-meeting-from-slack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
