> ## Documentation Index > Fetch the complete documentation index at: https://docs.summation.com/llms.txt > Use this file to discover all available pages before exploring further. # Prepare a weekly business review > A two-page read on one team's week, built from operating data against plan and the prior week, then delivered on schedule. Output [Report](/features/artifacts/reports) and scheduled [workflow](/features/workflows) Cadence Weekly For Business-unit general managers, merchandising and category managers, FP\&A analysts and finance business partners, revenue and ops leads ## When to use it Every team has someone who builds this on Monday morning. They pull the numbers, compare them to plan, find what moved, and write it up before the meeting. The writing alone takes twenty minutes. Finding the one number that explains the week takes the rest of the morning. A weekly review should answer one question: what changed since last week, and what are we doing about it? The person who owns the number should get the answer in five minutes. That's the spec. Summation builds it every week, on your time. ## Understanding the demo When you delegate your WBR to Summation, you get the same two-page format every week. It opens with no more than five executive-summary bullets, elevating the most important information from your organizational data. A report titled 'Weekly Business Review' for the Bottoms category, week of 9-15 August 2026, FY26 W28. An Executive Summary lists five bullets: the new slim jean block's outer three sizes return at 55.6% against 33.3% in the middle of the range, a gap of 22.3 points that no other jean block has; that gap has cost $276.3K in additional returns since the block launched, $14.4K of it in this week alone; net sales came in at $627.8K against a plan of $654.6K, on 16,386 units; jeans held $21.2K of the shortfall, 79% of the week's total miss on 29% of the plan; and returns on jeans stepped to 41.8% from 34.7% for products sold from the week of 7 March. A 'Metrics Overview' table follows, headed 'Bottoms metrics, week ending 15 August 2026', with columns for Metric Type, Metric, two week-ending values, Status and Commentary, covering Net Sales, Gross Margin Rate, Estimated Return Rate, Units, Markdown % of Ticket and Weeks of Supply, each with an amber or green status dot and a short note. A 'View SQL' link and 'Data as of Aug 21' sit at the foot, above the start of a 'Plan to actual net sales' chart. 1. **Summary:** Up to five bullets explain what changed, why it matters, and what needs attention 2. **Metric scorecard:** Six core metrics compare the current week with the prior week and plan, with a status and short note for each. A bridge shows what contributed most to the gap between plan and actual results 3. **Highlights and lowlights:** Up to three of each explain the most important positive and negative changes, and say when the cause is still unclear 4. **Largest shortfall:** A focused analysis sizes the biggest gap, explores likely drivers one dimension at a time, and draws only conclusions supported by the data 5. **Upcoming initiatives:** One or two relevant items from the initiative calendar provide context for what happens next Every number links to its source query, and Summation checks [the sources, calculations, and written claims](/features/artifacts/verification) before delivery. ## How it works [Addison](/features/addison) takes you through a guided setup: 1. **Data:** Addison shows which tables it will use, and finds the reporting week from the dates in your data 2. **Metrics:** It suggests six metrics, each with its target and direction 3. **Focus:** Once the queries run, the changes are ranked by dollar impact and the biggest one is suggested for a closer look 4. **Build and verify:** Summation writes the review, then runs [verification](/features/artifacts/verification) on it. Reports are always verified before Addison hands one over: every cited figure is checked against the query that produced it, and every written claim against the data behind it. The shield badge in the toolbar carries the result, and the Verification Hub lists each check 5. **Send:** Save the review as a [Playbook](/features/artifacts/playbooks) and schedule a [Workflow](/features/workflows) to deliver it weekly. Each run rebuilds the review and verifies it again against that week's data ## What you need | Data | Required? | What it adds | | ---------------------------- | --------- | -------------------------------------------------------------- | | **Weekly transactions** | Yes | Compares this week with last week and finds the largest change | | **Plan or targets** | Optional | Shows whether results are on track | | **Margin** | Optional | Shows the dollar impact of each change | | **Product or customer data** | Optional | Helps explain what caused a change | | **Dated calendar** | Optional | Adds upcoming initiatives and events | Connect your [warehouse](/features/connectors) to keep the review current, or upload an Excel or .csv to run it now. ## Make it yours Keep your definitions in [Knowledge](/features/knowledge) so they stay consistent across every review. To change a paragraph, highlight it and use [Edit with AI](/features/artifacts/reports#ask-and-edit-with-addison); remember to refresh [verification](/features/artifacts/verification) before sharing. To save a correction for future runs, ask Addison to add to knowledge. Scheduled Workflows continue using their current version until you activate an update. ## Try it **In Summation:** * **Use the setup skill:** `/weekly-business-review` * **Or follow the guided setup:** Get started → Choose a ready-made job → **Prepare a weekly business review** → Explore demo → **Create with my data** **From another agent:** Open [summation.com/agents.md](https://summation.com/agents.md) and ask for a weekly business review. ## Next How a report is built, cited, and edited. How Summation checks accuracy before you share. Save the instructions so a run repeats exactly. Add a schedule and deliver by email or Slack.