skills/kpi-reporting/references/report-templates.md

# Report Templates

Use this reference after the output format is selected. These are starting patterns, not mandatory layouts.

These optional patterns shape the final artifact, not a pre-preview gate. Analysis, validation, and operating implications come from the KPI Reporting workflow; complete the requested analysis after showing the first useful app version.

## Inline Written Update

Use for a short chat, email, or memo-style update. Lead with the answer, then include the headline actuals, comparison or pacing context, main drivers, and the operating implication or next step.

## Document Or Report

Route document and report outputs through $build-report. Use this reference to shape the KPI content passed into that workflow: summary, KPI snapshot, driver analysis, business context, implications, caveats, and reader-relevant source or calculation notes.

## Single Slide

Use for one concise readout. Follow the user's requested surface: $build-report for the shared report app, or the native presentation surface when the user needs a slide file. Ask which path they want when unclear. A single-slide story should have one main message, a compact view of the headline metrics, and only the driver, risk, or action detail needed to support that message.

## Executive Business Review Deck

Use for larger executive readouts, such as weekly, monthly, or quarterly business reviews. Follow the user's requested surface: $build-report for the shared report app, or the native presentation surface when the user needs a deck file. Ask which path they want when unclear.

- Give a concise executive summary of overall status, what changed, and what needs attention.
- Use KPI cards, a scorecard, or another compact summary format that makes headline performance easy to scan; move dense detail into supporting sections.
- Organize the body around the main drivers of performance. Each section should connect the driver evidence to the operating takeaway, with action, risk, or follow-up when one is warranted.
- Keep detailed evidence, large tables, and deeper cuts in supporting sections or an appendix.
- Include prior follow-ups when they are useful for a recurring readout, with ownership and current status.
- End with the prioritized actions or open questions leaders need to resolve.

## Scorecard Or KPI Card Component

Use a compact scorecard when the reader needs to compare multiple KPIs at once. Include the actual, relevant comparison, target or pacing context when available, status, and a short driver or interpretation. Expand the explanation below the table when the driver story needs more room.