How to automate your weekly report with AI

A weekly report is the ideal first automation. It repeats on a schedule, the structure barely changes, the inputs are usually numbers and short notes, and you can tell quickly whether the output is right. It is also a task most people find tedious, which makes the payoff obvious.

This guide, current as of September 2026, builds the routine in three levels. Each level works without programming. You can stop at any level: Level 1 alone often saves an hour a week.

What you’re really automating

A weekly report has four parts:

1. Gather the inputs (numbers, notes, updates).
2. Analyze what changed and why it matters.
3. Write the summary in a consistent format.
4. Deliver it to the right people.

AI is strongest at steps 2 and 3. Steps 1 and 4 depend on where your data lives and how comfortable you are connecting tools. That is why the levels below add automation one piece at a time. The design principle throughout is the one we teach in the class: trigger, AI processing, human review, output. Keep the human review.

Before you start: define the report

Spend ten minutes writing down:

• Who reads it and what decision they make with it.
• The sections you always include. Aim for four to six.
• The numbers that matter and where each comes from.
• What “good” looks like: paste your last two reports as examples.
• The one check that tells you the numbers are right, such as a total that must match another system.

Pick a task with low risk while you’re learning. A team status update is a better first project than a report that feeds a regulatory filing.

Level 1: A saved prompt and a weekly paste

This is the simplest version. You paste in the week’s inputs, and the assistant produces the draft.

Create a prompt you’ll reuse:

You write my weekly report for [audience, e.g., the leadership team]. Follow this structure exactly:

1. Headline: one sentence on how the week went.
2. Key numbers: a table with metric, this week, last week, change.
3. What moved: up to 4 bullets explaining the biggest changes, using only the notes provided.
4. Risks and blockers: up to 3 bullets.
5. Next week: up to 4 priorities.

Rules:
- Use only the data and notes below. Never estimate or invent a number.
- If last week's number is missing, write "n/a" and don't calculate a change.
- If something looks off (a sudden 5x jump, a negative where that's impossible), list it under "Check before sending" at the end.
- Tone: plain and factual. No hype. Under 300 words.

Last week's report (for style and comparison):
[paste]

This week's numbers:
[paste table or copy from your spreadsheet]

This week's notes:
[paste bullets from your team or your own notes]

Save this in a document called “Weekly report prompt.” Each Friday, replace the three pasted parts and run it. The “Check before sending” clause is doing quiet work: it asks the assistant to notice oddities rather than smoothing them over.

Check the output

1. Recompute the changes for at least three metrics.
2. Confirm every number in the text also appears in your input. Ask: “List every number in your report and where it came from in my data.”
3. Read the ‘what moved’ bullets and confirm each reason came from your notes, not from the assistant’s imagination. AI will happily supply a plausible cause that nobody mentioned.
4. Compare tone with previous reports.

Level 2: Connect your data so you stop copy-pasting

Level 2 removes the gathering step. The right approach depends on where your data lives.

Spreadsheet source. If your numbers live in a spreadsheet, keep one tab that always holds the current week in the same layout. Then your assistant, or a spreadsheet tool with AI built in, reads that tab. Our guides on AI with Excel and AI for Google Sheets show how to structure it and how to have the assistant write the summary table.

Files in a folder. If exports land in a shared folder each week, some assistants can be connected to file storage so you can point at the folder instead of uploading. Connectors use a standard called MCP; the question page on MCP explains it in plain language. Connect only what the report needs and start with read-only access if the option exists.

Email updates from your team. If your inputs arrive by email, our Gmail guide shows how to have Claude gather and summarize them.

At this level, your Friday routine becomes:

Using the data in this week's tab and the notes in this week's folder, write the weekly report using my saved structure. Compare with last week's report. Show me which files and cells you used.

The last sentence matters: asking for sources keeps you able to check.

Check the output

• Confirm the assistant used the right files and the right week. Wrong-week errors are the most common failure here.
• Spot-check three numbers against the source.
• Confirm nothing was pulled from files it shouldn’t have seen.

Level 3: A scheduled job that drafts the report for you

At this level, the report is drafted before you sit down. There are two routes.

Route A: an agent tool you run on a schedule. Tools such as Claude Code can build a small routine from a plain-English description, and some offer scheduling options. Our guide to Claude Code for non-programmers walks through building a report page from a spreadsheet export, including the plan-first, approve-changes and check-the-numbers habits. For scheduling, check the current documentation for your chosen tool, because options and plan requirements change.

Route B: a script inside your existing tools. If your data lives in Google Sheets, an assistant can write an Apps Script that builds the summary table and emails you a draft on a schedule. See the Apps Script section of AI for Google Sheets.

A description to give a builder tool or assistant:

Build a weekly report routine.

Inputs: the newest file in the /Reports/exports folder (CSV) and the notes in /Reports/notes.txt.
Steps: (1) validate that the file has the columns Metric, ThisWeek, LastWeek, and stop with a clear message if not; (2) calculate the change for each metric; (3) write the report in the structure in /Reports/template.md; (4) save it as a draft in /Reports/drafts with the date in the filename; (5) list anything unusual under "Check before sending".
Rules: never send anything. Never overwrite an existing file. Log every run to /Reports/log.txt.
Explain what you built in plain English before running it, and show me a test on last week's data.

Notice the guardrails: validate the input, write drafts only, never overwrite, keep a log. These are what make an automation safe to leave running.

Check the output

• Run it on last week’s data first, where you know the right answer.
• Read the log the first few weeks to make sure it ran on the expected files.
• Make one deliberate error test: feed it a file with a missing column and confirm it stops instead of guessing.

Keep a human in the loop

Even at Level 3, the routine should produce a draft. Someone reviews, edits and sends. Reasons:

• The AI can’t know that a number is off because a system was down on Tuesday.
• Reports carry your name. Errors reach your boss or a client under your signature.
• Reviewers spot business context the data doesn’t show.

A useful review ritual takes ten minutes: read the headline, check three numbers, read the “Check before sending” list, edit the ‘what moved’ bullets, then send. If several weeks pass with no corrections, you can consider loosening the review on low-risk reports, but that is a decision to make deliberately.

Handle the edge cases

• Missing data. Tell the routine to say “n/a” and never fill gaps.
• Format changes. If the export format changes, the routine should fail loudly. The validation step covers this.
• Sensitive data. Confirm the report contents may go through your chosen tool. See our company AI policy template.
• Different audiences. Keep one master report and ask for shorter or more formal versions for other readers rather than building separate pipelines.
• Version drift. Keep the prompt or template in one place, note the date you change it, and don’t let copies multiply.

Measure what you saved

At the end of the first month, note how long the report took before and after. Include your review time and the time you spent fixing errors. This turns “it feels faster” into a number you can share, and it tells you whether the next level is worth building. It is also the evidence that helps you propose the same approach for other recurring work.

What the scheduling documentation says

Scheduling limits from Anthropic and Google, which set how often and where a report routine can run.

• Anthropic says a Claude Cowork scheduled task can run hourly, daily, weekly, on weekdays, or manually.
• Anthropic says that if a scheduled task requires local files or apps, it will only run locally.
• Anthropic says scheduled tasks run on their cadence even when your computer is asleep or the Claude Desktop app is closed.
• Google says time-driven triggers in Apps Script allow scripts to execute at specific times or intervals.
• Google lists a total trigger runtime of 90 minutes a day for consumer accounts and 6 hours a day for Google Workspace accounts.
• The National Institute of Standards and Technology defines confabulation as the production of confidently stated but erroneous or false content.

Common mistakes

• Automating a report nobody reads. Confirm the report is useful first.
• Skipping the template. A consistent structure makes checks quick.
• Letting the tool explain causes. Reasons should come from your notes.
• No log. Without one, you can’t tell what happened when something breaks.
• Full automation on day one. Build trust with drafts.

For the short version, see how to automate weekly reports with AI. Strong prompts make the first level much better, so start with how to write AI prompts that work.

In our two-day class, everyone builds the same weekly report generator from a written specification on provided data, and learns a worksheet for estimating hours saved on workflows of their own.

Sources

• Anthropic Help Center, Schedule recurring tasks in Claude Cowork: “hourly, daily, weekly, on weekdays, or manually”
• Anthropic Help Center, Schedule recurring tasks in Claude Cowork: “If a scheduled task requires local files or apps, it will only run locally”
• Anthropic Help Center, Schedule recurring tasks in Claude Cowork: “run on their cadence even when your computer is asleep or the Claude Desktop app is closed”
• Google for Developers, Installable Triggers (Apps Script): “Time-driven triggers allow scripts to execute at specific times or intervals”
• Google for Developers, Quotas for Google Services (Apps Script): “Triggers total runtime 90 min / day 6 hr / day”
• NIST, AI 600-1: Artificial Intelligence Risk Management Framework: Generative AI Profile: “erroneous or false content”