Weekly Reporting

Last verified: 13 February 2026 | Applies to: Pro, Max, Team, Enterprise

In 30 seconds

Most operators produce some version of a weekly report — status updates, metrics summaries, team briefings. This workflow shows you how to build a custom plugin that generates your specific report format automatically. Set it up once, then say “create my weekly report” and Claude produces exactly what your stakeholders expect.

Prerequisites

• Claude Desktop with Cowork enabled
• The Productivity plugin installed (for persistent memory — see Workplace Memory)
• A clear idea of what your weekly report should include (bring a previous example if you have one)

Step by step

Step 1: Define your report format

Before asking Claude to build anything, write down what your report should include. Here’s an example:

Weekly Ops Report for [Company Name]:

• Key metrics: revenue, orders, NPS
• Wins from this week (2-3 bullet points)
• Blockers and risks (2-3 bullet points)
• Next week’s priorities
• Asks from leadership

Audience-specific requirements:

• CEO wants bottom-line impact first
• CFO needs specific numbers, not ranges
• COO cares about blockers more than wins

Formatting: Under 500 words, bullet points only, lead with the number then the context.

Step 2: Ask Claude to build the plugin

In a Cowork session, describe exactly what you want:

Build me a plugin for creating weekly ops reports. It should include these sections: key metrics (revenue, orders, NPS), wins from this week, blockers and risks, next week priorities, and asks from leadership. Keep reports under 500 words, use bullet points, and lead with the number then the context. The CEO wants bottom-line impact first, CFO needs specific numbers not ranges, and COO cares about blockers more than wins.

Claude will ask a few clarifying questions, then generate a complete plugin with the proper folder structure, manifest, and skill definitions — packaged as a ZIP file.

Step 3: Install the plugin

1. Download the ZIP Claude generates
2. Unzip it
3. In Claude Desktop → Cowork tab → Plugins (left sidebar) → Upload plugin → select the unzipped folder
4. Done

You can also install via claude.com/plugins.

Step 4: Generate your first report

In a new Cowork session, type:

Create my weekly report.

Claude follows your exact format. Provide the raw data — metrics, notes, highlights — and Claude structures it according to your plugin’s rules.

If you’ve set up Workplace Memory: Claude already knows your team, projects, and acronyms. You can say things like “include the Shopify migration update” and Claude understands the context.

Step 5: Iterate and refine

Your first generated report probably won’t be perfect. That’s expected. Common adjustments:

• “The metrics section should always lead with revenue, then orders, then NPS — in that order.”
• “Blockers should include an estimated impact and a proposed resolution.”
• “Add a ‘team shoutouts’ section — we use this for recognition.”

You can either modify the plugin directly (ask Claude to update it) or refine your prompt each time. For recurring adjustments, update the plugin so you don’t have to repeat yourself.

How operators actually use it

What operators say

“I tested this for our weekly reporting workflow — the one where I always forget to include the same five things. My first attempt didn’t quite work — Claude got the folder structure slightly wrong. But after one round of feedback, it corrected itself and delivered a working version.”

Before: 45 minutes manually compiling data from multiple sources, formatting, and writing narrative. Frequently forgot sections or was inconsistent with format.

After: 10 minutes providing raw data to Claude, 5 minutes reviewing and adjusting. Consistent format every week.

Advanced: Connect data sources

If you’ve set up connectors, Claude can pull data directly:

Create my weekly report. Pull the latest metrics from our Google Sheet and check Slack #wins for team highlights from this week.

This reduces your input to reviewing and approving rather than compiling.

What to watch out for

• First attempt may need refinement. Plugin generation isn’t always perfect on the first try. Budget time for one or two rounds of feedback.
• Numbers need verification. If Claude is pulling data or calculating metrics, always verify the numbers before sending the report. Claude can misread or miscalculate.
• Plugin is only as good as its instructions. If your report format changes, update the plugin. Stale instructions produce stale reports.
• Cowork usage is higher than chat. Generating reports in Cowork consumes more of your plan’s usage than doing it in Chat. For simple reports, Chat may be sufficient.

Related

• Building a Plugin — the general workflow for creating custom plugins
• Workplace Memory — set up context that makes reporting faster
• Productivity Plugin — the memory and task management layer
• Connecting Your Tools — pull data from connected sources

---

Something wrong or outdated? Let us know →

Get weekly workflows — subscribe to the newsletter.