> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/playbooks/build-your-monthly-business-review-deck.md).

# Build your monthly business review deck

Bring together Tability and business data to build a seven-slide monthly review focused on results, lessons, and decisions.

Turn your team's monthly results into a seven-slide business review: what happened, why it matters, and what you need to do next.

To start, share this page with Claude, ChatGPT, Grok, or another AI assistant with Tability connected through MCP, and say:

> Run this playbook

This playbook runs in your connected assistant, outside Tability AI Mode. Tability access is assumed. Connect other relevant sources, or provide exports, to include financial, customer, and operational results. Creating a slide file also requires presentation tools; the playbook provides a complete slide-by-slide draft if those aren't available.

The instructions below are for your assistant. You don't need to read or copy them.

***

### Instructions for AI assistants

If the user shares this page and asks you to run it, follow the steps below from start to finish. If they only ask you to read, summarize, or edit it, do that instead.

#### Ground rules

* **Ask one short question at a time.** Reuse known context and produce a first seven-slide draft within five discovery questions. Continue with labeled gaps if a source is missing.
* **Confirm the business, team, audience, and month.** Never assume them from the publisher or connected accounts. Resolve the user's Tability workspace URL to its name and ID, and confirm the scope unless already authorized.
* **Review the period that actually happened.** State the month, timezone, and data cutoff. Separate completed-month results, late-arriving data, current forecasts, and next-month plans.
* **Use evidence without inventing a story.** Label measured, estimated, and proposed figures. Distinguish documented causes from hypotheses. Missing data is not zero.
* **Prepare the review without changing the source records.** Creating a draft deck does not authorize updating Tability check-ins, targets, owners, or statuses. Don't send the deck or contact other people unless asked.
* **Match the output to available tools.** Verify slide files and source links before claiming completion. If a tool is unavailable, deliver the completed narrative and slide specification, with a clear next step.

### 1. Frame the review

Start with:

> Which team and month are we reviewing, and who will be in the room?

Then establish the business context, the decisions the audience needs to make, and the team or plan links in Tability. Ask for the previous MBR or an existing slide template if available. Reuse its terminology and useful comparisons.

Confirm the reporting timezone, month-end cutoff, and comparison period. If the month is still in progress, label the deck “month to date” and use a like-for-like comparison. Ask only for other sources that materially improve this review, such as finance, CRM, analytics, customer feedback, support, or delivery data.

### 2. Gather the month's evidence

Check access to the relevant sources early. Tability KPIs and KPI Views require Premium and permission to view the records; preparing this review does not require edit access. If KPI access is unavailable, continue with accessible goals, check-ins, and business exports, and state the gap.

Read the relevant Tability goals and targets, check-in history, KPI values and definitions, initiatives, owners, and previous review actions. Follow pagination and date filters. Retrieve observations for the review period rather than treating today's status as the historical month-end position.

Combine that evidence with the connected business sources:

* Finance or billing for revenue, cost, margin, budget, or cash where relevant.
* CRM and analytics for demand, sales, adoption, and retention.
* Customer feedback and support for experience, recurring issues, and service quality.
* Project or delivery systems for milestones, capacity, reliability, and dependencies.

Use only sources confirmed to belong to this business and team. If access is missing, ask for the smallest useful export or summary. Continue with the available evidence and identify what is missing. Do not infer business impact merely from completed tasks.

Create an evidence ledger with each claim or metric, source link or record ID, reporting period, unit, formula, extraction date, and caveat. Keep sensitive customer or employee detail out of the deck unless needed and appropriate for its audience.

### 3. Reconcile the numbers and choose the story

For each headline KPI, establish the actual, approved target or budget, prior comparable period, variance, and owner. Add year-over-year or a short trend only when the data is available and useful.

Check currencies, units, date boundaries, definitions, and aggregation. Calculate rates from their underlying totals where appropriate; don't average percentages with different denominators. When the previous value is zero, show the absolute change instead of an undefined percentage change. Identify whether a change in a rate is measured in percentage points or relative percent.

A Tability KPI View shows the latest actual in a period, which may not be the period total. Verify the KPI definition and underlying source before labeling a number a monthly result. If a historical status or target cannot be reconstructed, say so rather than substituting today's value.

Resolve conflicting numbers using the agreed source of truth. If unresolved, show the discrepancy and exclude it from definitive claims. Explain meaningful misses as well as wins, and distinguish measured impact from an owner's interpretation.

Choose the three most important messages for this audience. Each should lead to an implication, action, or decision.

### 4. Draft exactly seven slides

Use this structure. Adapt the measures and examples to the team, while keeping all seven purposes. There is no separate cover or appendix slide; put the team, month, and cutoff on slide 1, and put detailed evidence in speaker notes and the companion file.

| Slide                                 | Purpose                                     | Include                                                                                                                                                                                                    |
| ------------------------------------- | ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **1. Executive summary**              | Give leaders the month in one minute        | A takeaway headline, three evidence-backed messages, overall outlook, and the most important decision or ask.                                                                                              |
| **2. Performance scorecard**          | Show results against expectations           | 5–7 relevant KPIs with actual, target or budget where available, prior comparable period, variance, and freshness. Make missing or provisional values explicit.                                            |
| **3. Goals and delivery**             | Show whether strategic commitments advanced | The top 3–5 commitments from Tability, outcome evidence, material milestones achieved or missed, and follow-through on last month's actions. Separate delivery from impact.                                |
| **4. Customers and market**           | Explain the external signals                | Customer or beneficiary outcomes, adoption, retention, service experience, and a few representative qualitative insights. For an internal team, use the people or teams it serves.                         |
| **5. Financial and operating health** | Show whether performance is sustainable     | Relevant economics, spend versus budget, capacity, efficiency, and quality. For a team without a P\&L, use its budget or resource constraints and operating health; mark unavailable finance data clearly. |
| **6. Risks, causes, and lessons**     | Explain what could change the outlook       | The top three risks or material variances, evidence about their drivers, lessons learned, mitigation, owner, and expected impact. Label untested explanations as hypotheses.                               |
| **7. Next month and decisions**       | Turn the review into commitments            | Three priorities with owners, dates, and success measures. List decisions needed, recommended options, tradeoffs, decision owners, and deadlines.                                                          |

For every slide, provide a takeaway title, concise on-slide content, one useful visual or table where it helps, speaker notes, and source references. Prefer a specific supported conclusion to a generic heading. Don't use a causal headline when the evidence only shows correlation.

Keep slides readable: one main message, short bullets, consistent periods and units, and clear labels. Describe each chart's axes, series, and data source. When evidence is missing, keep the slide's purpose and state what cannot yet be concluded instead of filling it with generic praise.

Save `{team-name}-{yyyy-mm}-mbr.md`, marked Draft, containing all seven slides and the evidence ledger. Present the key messages and unresolved gaps, and ask for corrections or approval before finalizing the narrative.

### 5. Create the deck

Once the narrative is approved, create an editable seven-slide deck using the available presentation tools and the user's preferred format or template. Use the same supported figures, titles, and caveats as the approved draft. Put citations beside the relevant claim or in its speaker notes.

If presentation creation is unavailable, deliver the full seven-slide Markdown draft, chart data, and notes ready to paste into PowerPoint or Google Slides. State that the content is ready but a presentation file has not been created. Don't require a particular assistant vendor to complete the content.

Preserve the evidence ledger separately so the deck can stay concise. It is a companion document, not an eighth slide.

### 6. Check the review before handing it over

Verify:

* The deck has exactly seven slides and covers all seven purposes.
* Figures match their sources, periods, units, and calculations. Targets and historical comparisons use the correct dates.
* Titles accurately reflect the evidence, and provisional data and hypotheses are visible.
* Important misses and risks haven't been omitted to make the story more positive.
* Next-month priorities and asks have owners, dates, and measurable outcomes, or explicit gaps.
* Charts, text, and tables are readable and unclipped. Render and inspect the slides if the tools allow it; state any visual verification limitation.
* The saved deck opens, its links work where verifiable, and speaker notes retain the sources.

Keep the review read-only in Tability unless the user separately asks you to record approved actions or updates there.

### 7. Wrap up and make next month easier

Share the deck, companion file, three key messages, and decisions to prepare for. Flag any gaps that materially limit the review.

Include a reusable next-month prompt with the actual team, workspace links, sources, template, timezone, and metric definitions filled in:

> Run this monthly business review playbook for \[team] for \[month]. Use \[workspace and plan links], \[data sources], and \[template]. Carry forward the previous review's actions, compare equivalent periods, and produce exactly seven slides plus an evidence ledger. Flag missing data and prepare a draft for my review.

Only offer or configure recurring preparation if the user wants it and the assistant's scheduler can access the needed sources. Verify any requested schedule. A scheduled draft should stay a draft and should not be sent to the leadership team automatically.

***

### Companion file outline

```markdown
# {Team}: monthly business review — {YYYY-MM}
Status · Business · Audience · Workspace · Period · Timezone · Data cutoff

## Three key messages
## Slide 1: Executive summary
## Slide 2: Performance scorecard
## Slide 3: Goals and delivery
## Slide 4: Customers and market
## Slide 5: Financial and operating health
## Slide 6: Risks, causes, and lessons
## Slide 7: Next month and decisions
## Evidence ledger and calculations
## Missing data and caveats
## Deck link and verification
## Next-month prompt and source map
```

**END OF PLAYBOOK**
