Make a weekly report that drafts itself

Exit

Lesson 1 · 9 min

Make a weekly report that drafts itself

By the end

Tested instructions and a five-line plan for a Monday report that drafts itself and waits for a person’s check.

  1. 1Learn
  2. 2Try it
  3. 3Human check
  4. 4Quick check

Learn · 4 min

A trigger, some steps and a pause

An automation tool such as Zapier or Make does two things: it waits for a trigger (an event, or a time like Monday at 8am), then runs a list of steps in order. “AI in the middle” just means one of those steps sends text to an AI model with instructions you wrote once, and passes its answer to the next step.

A weekly report fits on five lines:

  • Trigger: every Monday, an hour after your sales or bookings data is updated.
  • Step 1: read a small summary tab in your spreadsheet.
  • Step 2: an AI step turns those numbers into a short draft, following your saved instructions.
  • Step 3: email the draft, marked DRAFT, to one person.
  • Pause: that person checks it and sends it on. Nothing reaches the team automatically.

Let the spreadsheet do the math

Don’t send the AI step hundreds of raw rows and ask for totals. Models can misread long tables and slip on arithmetic, and you can’t see how they got a number. Build a summary tab instead: five to eight numbers you care about, each with this week, the week before and the change, all worked out by formulas.

The AI step then only puts those few cells into words. Every number in the draft traces to a cell, checking takes a minute, and far less of your data leaves the spreadsheet.

One instruction matters more than the rest: don’t explain why a number moved. Ask an AI for a reason and it will often offer a plausible one (the weather, a holiday) whether or not it’s true. Reasons come from a person who knows.

The three questions every automation answers

Before anything runs on its own, write down who approves, what happens if nobody does, and how you’ll know it broke. For a bakery’s weekly sales report:

  • Who approves: the owner reads the draft, checks each number against the summary tab, and forwards it to the team.
  • If nobody does: the draft waits. The team gets nothing rather than something unchecked, and a backup gets a reminder at noon.
  • How you’ll know it broke: the owner expects the draft by 9am, so no draft means checking the tool’s run history (its record of every run). Turn on the tool’s error emails and send them to a named person.
  • The quiet failure: someone renames a tab or moves a column, and the automation reads the wrong cells without any error. The owner’s number check is what catches it.

Run it alongside before you switch

For the first two weeks, write the report the old way too, and compare. Switch over when the drafts need only light edits. If you keep making the same edit, add it to the instructions. Keep the old way written down for the week the automation fails.

Try it on your business

5 min

Run the AI step by hand before you build anything. If a draft from your real numbers is good, your prompt is ready to become the automation’s instructions. Tool cost: none for this dry run; running it every week may need a paid plan of your automation tool, and the AI step can cost extra.

  1. 1

    Pick five to eight numbers you already track weekly, and copy this week, the week before and the change for each from your real spreadsheet.

  2. 2

    Paste them into the prompt, run it in your assistant, and check every number in the draft against your sheet.

  3. 3

    Note each fix you had to make: every fix becomes a line in the instructions.

  4. 4

    Write your automation in five lines: trigger (day and time), steps, who approves, their backup, and who gets the error emails.

You draft the weekly report for [BUSINESS], read by [WHO READS IT].
Here is the summary for the week of [DATE] (metric, this week, the week before, change in %):
[PASTE 5 TO 8 ROWS FROM YOUR SPREADSHEET]

Write a draft of no more than [150] words:
1. One line on the week overall.
2. The three numbers that moved most, with both values.
3. Anything that looks odd, marked [CHECK].

Rules: use only the numbers above, exactly as written. Don't calculate new ones. Don't explain why anything changed; I'll add reasons. Start with "DRAFT for review".

Human check: before you use it

Quick check · question 1 of 2No grades

Where should the numbers in an AI-drafted weekly report come from?

Ask the Distillery

Answers come from The Distillery’s own pages, with sources.

If the Distillery doesn’t know, it says so and points you to a person.