Blueprint · Operations & Reporting · Difficulty: Beginner · 18 min read
A step-by-step, no-code workflow for managers and team leads who want AI to pull updates from their project management tools, write a professional weekly status report, and deliver it automatically every Monday morning. Built for Monday.com, Asana, ClickUp, and Notion environments. No developers required.
Summary Card
- What it does: Automatically collects task updates, milestones, and blockers from your project management tool, feeds them to AI to write a clear status report, and delivers the finished report to Slack, email, or a shared doc – every week, on autopilot
- Who it’s for: Project managers, team leads, department heads, and operations managers who spend 1-3 hours every week manually assembling status updates from scattered tools
- Time to implement: 30-60 minutes for the manual workflow; 2-3 hours for the fully automated version with Make or Zapier
- Tools required: Your existing project management tool (Monday.com, Asana, ClickUp, or Notion) + ChatGPT or Claude + Make or Zapier for automation
- Cost estimate: $20/month (ChatGPT Plus or Claude Pro) for the manual workflow; $20-50/month additional for Make or Zapier if automating
- Difficulty: Beginner – no code, no API keys (for the manual version), no IT department needed
- Last tested: April 2026 with Claude Sonnet 4, ChatGPT 5.3, Monday.com, Asana, and Make
What the research says
A 2025 Asana Anatomy of Work study found that knowledge workers spend 58% of their time on “work about work” – status updates, check-ins, and searching for information. Monday.com’s 2026 AI Report confirms that AI-generated status summaries save managers an average of 3.5 hours per week. The bottleneck is not the reporting itself – it is the manual collection and synthesis of scattered updates. That is the exact problem this blueprint solves.
Every manager knows the Friday afternoon ritual. You open Monday.com or Asana. You scroll through boards, looking at what moved this week. You check Slack threads for context on the blockers someone mentioned on Tuesday. You open your email to find that vendor update from Wednesday. Then you sit down and type a status report that synthesizes all of it into something your leadership team can read in two minutes.
The report itself is not hard to write. The painful part is the collection – pulling data from five different places and holding it all in your head long enough to write something coherent. That is exactly the kind of work AI is built for.
This blueprint builds a workflow that collects your project data automatically, feeds it to AI with a prompt that knows how your organization likes its status reports formatted, and delivers the finished report wherever your team reads it – Slack, email, or a shared document. You can run it manually in 15 minutes or set it to run on autopilot every Monday morning.
Choose Your Automation Level – Three Options From Manual to Fully Automated
Before you start building, decide how automated you want this to be. Each level works. The right choice depends on how comfortable you are with automation tools and how many reports you produce each week.
This blueprint walks through all three levels. Start with Level 1, get the report quality right, then upgrade when you are ready.
How the Weekly Status Report Workflow Works – Architecture Overview
Here is how the four-step workflow fits together, from raw project data to a delivered status report.
Workflow Overview
Collect
Pull task data from your PM tool
Structure
Format data for AI input
Generate
AI writes the status report
Deliver
Send to Slack, email, or doc
The beauty of this workflow is that each step is independent. You can do Step 1 manually and automate the rest. You can change your project management tool without rebuilding the AI prompt. You can switch from Slack delivery to email delivery in five minutes. The modular design means you are never locked in.
Which Tools to Use – Our Tested Recommendations
You do not need to buy new software. This workflow plugs into whatever project management tool you already use. Here is what we tested and what worked best for each role in the workflow.
Recommended Tool Stack
For project data (use whichever you already have):
- Monday.com – Best native AI features for status summaries. Built-in AI Blocks can generate board summaries without leaving the platform. If you already use Monday, start here.
- Asana – Clean data exports and strong Zapier/Make integration. Asana’s native AI can draft status updates directly in the platform.
- ClickUp – Built-in AI assistant can summarize tasks, but the export-to-external-AI workflow in this blueprint gives you more control over formatting.
- Notion – Notion’s Custom Agents (launched February 2026) can run scheduled automations that compile status updates across databases. Excellent if your team lives in Notion.
For AI writing:
- ChatGPT (GPT-5.3) – Best for conversational, stakeholder-friendly reports. Handles messy input data gracefully. $20/month for Plus.
- Claude (Sonnet 4) – Best for structured, detail-heavy reports. Follows formatting instructions more precisely. Excels at longer reports with multiple project sections. $20/month for Pro.
For automation (only needed for Level 2 and Level 3):
- Make (formerly Integromat) – Our top recommendation for this workflow. Visual scenario builder makes it easy to see exactly how data flows. Free tier includes 1,000 operations/month, which covers about 4 weekly reports. Paid plans start at $10.59/month.
- Zapier – Simpler interface, fewer steps to set up. Built-in AI actions mean you can skip a separate AI subscription in some cases. Free tier limited; paid starts at $19.99/month.
Quick-start recommendation
If you are setting this up for the first time, use Monday.com + Make + ChatGPT. Monday.com’s data structure exports cleanly, Make’s visual builder is beginner-friendly, and ChatGPT handles varied input formats well. If you already use a different PM tool, keep it – the prompts in this blueprint work with data from any of them.
Step 1: Collect Your Project Data
The first step is getting your task data out of your project management tool in a format AI can work with. This is the step most people overcomplicate. You do not need a perfect data export. You need enough context for the AI to understand what happened this week.
Option A: Monday.com
In Monday.com, go to your board and apply a filter for items updated in the last 7 days. Then select all visible items, click the three-dot menu, and choose “Export to Excel.” This gives you a spreadsheet with task names, statuses, owners, and dates.
Alternatively, if you use Monday.com’s AI features (available on Pro and Enterprise plans), you can use a built-in AI Block to generate a board summary directly. Go to your board, click the AI icon in the toolbar, and select “Summarize board.” This gives you a paragraph summary – but the export approach gives you more control, which matters when you want consistent formatting week over week.
Option B: Asana
In Asana, open your project, click the dropdown arrow next to the project name, and select “Export/Print → CSV.” This gives you every task with its status, assignee, due date, section, and completion status. For a more targeted export, apply a filter for tasks completed or modified in the last 7 days before exporting.
Option C: ClickUp
In ClickUp, go to your Space or List view, click the three dots in the upper right, and select “Export.” Choose CSV format. Filter by “Date Updated” to capture only this week’s activity.
Option D: Notion
In Notion, open the database view for your project tracker. Apply a filter where “Last Edited” is within the past week. Then click the three-dot menu in the top right corner of the database and select “Export → Markdown & CSV.” Choose CSV for this workflow.
What your export should include
At minimum, your export needs these columns: Task name, Status (completed / in progress / blocked), Assignee, Due date, and ideally a Notes or Comments column. If your tool includes a priority field or project/phase grouping, include those too – they help the AI write a more useful report.
Step 2: Structure Your Data for the AI Prompt
Now you need to format your exported data so the AI can make sense of it. If you are doing this manually (Level 1), this step takes about two minutes.
Open your exported CSV in Google Sheets or Excel. Copy all the rows (including headers). That is it. You do not need to clean it, reformat it, or summarize it yourself. The whole point is letting the AI do that work.
If your export is messy – merged cells, blank rows, inconsistent status labels – spend a quick minute cleaning the obvious issues. But do not overthink it. Both ChatGPT and Claude handle messy spreadsheet data surprisingly well.
Pro tip: Add context the spreadsheet does not capture
Before pasting your data into the AI, add 2-3 sentences of context that the spreadsheet cannot convey. For example: “We had a client escalation on Wednesday that shifted priorities” or “The design team was short-staffed this week due to PTO.” This context is what separates a generic status summary from a report that actually tells your stakeholders what happened.
Step 3: The AI Prompt That Writes Your Status Report
This is the core of the workflow. The prompt below is what I use in production. It has been refined over four months of weekly use across multiple project types. Copy it exactly, then customize the sections in brackets.
Status Report Generator – System Prompt
You are a senior project manager writing a weekly status report for [STAKEHOLDER AUDIENCE - e.g., "the VP of Marketing" or "the executive leadership team" or "cross-functional department heads"].
Your writing style is:
- Clear and direct. No filler, no corporate buzzwords.
- Focused on outcomes and decisions, not activity lists.
- Honest about risks and blockers - do not bury bad news.
REPORT FORMAT:
## Weekly Status Report - [Project/Team Name]
**Week of:** [Auto-detect from the data or use current week]
**Prepared by:** [YOUR NAME]
### Executive Summary
Write 2-3 sentences that a busy executive can read in 30 seconds and understand: (1) overall status, (2) the most important thing that happened this week, (3) anything that needs their attention.
### What Got Done This Week
Group completed tasks by project area or workstream. Use plain language, not task IDs. Focus on outcomes ("Launched the new landing page" not "Completed task #4521").
### In Progress
List the 3-5 most important items currently being worked on, with expected completion dates.
### Blocked or At Risk
List anything that is stalled, delayed, or at risk of missing a deadline. For each item, state: what is blocked, why, and what is needed to unblock it. If nothing is blocked, say so - do not invent problems.
### Key Decisions Needed
If any items require a decision from leadership or another team, list them here with enough context for the decision-maker to act. If no decisions are needed, omit this section.
### Next Week Preview
List the 3-5 most important deliverables or milestones expected next week.
RULES:
- Keep the total report under 500 words unless the data warrants more.
- Do not fabricate information. If the data does not include something, do not invent it.
- Use the metric system or imperial system consistent with a US audience.
- If the data is ambiguous, flag it as "[Needs clarification]" rather than guessing.
- Write dates in Month Day format (e.g., April 7).
How to Use This Prompt (Level 1 – Manual)
Open ChatGPT or Claude. Paste the system prompt above. Then paste your exported data below it with a line that says: “Here is this week’s project data. Write the status report based on the format above.”
If you have additional context (the client escalation, the PTO situation), add it after the data.
Hit enter. Review the output. Make any edits. Send it.
The first time takes about 15 minutes. After a few weeks, when the prompt is dialed in for your team’s style, it takes five.
Customization tips
Change the audience: If your report goes to a technical team, swap the Executive Summary for a “Technical Progress” section with more implementation detail.
Change the frequency: This prompt works for daily standups too – just change “weekly” to “daily” and reduce the expected length to 150 words.
Add a RAG score: Some teams include a Red/Amber/Green status at the top. Add this line to the prompt: “Start the Executive Summary with an overall RAG status (Red, Amber, or Green) based on whether the project is on track.”
Step 4: Automate the Entire Workflow With Make
Once your prompt consistently produces good reports (give it 2-3 manual runs to dial in), it is time to automate. This section walks through building the automation in Make. If you prefer Zapier, see the Zapier alternative section below.
Why Make Over Zapier for This Workflow
Both work. I recommend Make for three reasons. First, Make’s visual scenario builder lets you see the entire data flow at a glance, which makes debugging easier. Second, Make’s free tier (1,000 operations/month) is enough to run this workflow weekly without paying anything beyond your AI subscription. Third, Make handles multi-step data transformations – like combining data from two boards before sending to AI – more naturally than Zapier’s linear step structure.
Building the Make Scenario Step by Step
Make Scenario – Module by Module
Module 1: Schedule Trigger
Add a “Schedule” trigger module. Set it to run every Monday at 7:00 AM (your local time zone). This is what kicks off the entire workflow automatically.
Module 2: Pull Data from Your PM Tool
Add the appropriate module for your tool:
- Monday.com: Use the “List Board Items” module. Connect your Monday.com account, select your board, and add a filter for items where “Last Updated” is within the last 7 days.
- Asana: Use the “Search Tasks” module. Filter by project, modified since last Monday.
- ClickUp: Use the “Get Tasks” module with a date filter.
- Notion: Use the “Search Objects” or “Query a Database” module with a “Last Edited Time” filter.
Module 3: Format the Data
Add a “Text Aggregator” module. This combines all the individual task items into a single text block. Map in the task name, status, assignee, due date, and any notes fields. Separate each task with a line break. The output should look like a simple text list that AI can parse.
Module 4: Send to AI
Add an OpenAI or Anthropic module:
- For ChatGPT: Use Make’s “OpenAI – Create a Completion” module. Paste the system prompt from Step 3 in the System field. Map the aggregated task data into the User Message field.
- For Claude: Use Make’s “Anthropic (Claude) – Create a Message” module. Same approach – system prompt in System, data in User.
Module 5: Deliver the Report
Choose your delivery channel:
- Slack: Add a “Slack – Send a Message” module. Select your channel. Map the AI’s response as the message text.
- Email: Add a “Gmail – Send an Email” or “Email – Send an Email” module. Set the recipient to your distribution list. Map the AI response to the body.
- Google Docs: Add a “Google Docs – Create a Document” module. Name it “Weekly Status Report – [date]” and map the AI response as the content.
That is the entire scenario. Five modules. When it runs Monday morning, it pulls your data, formats it, sends it to AI, and delivers the finished report – all before you have had your first cup of coffee.
For the tech-curious: API-level alternative
If you want more control (custom data transformations, error handling, multi-source aggregation), you can build this workflow with Make’s HTTP modules calling the Monday.com GraphQL API and the OpenAI or Anthropic API directly. This lets you pull specific columns, filter by custom fields, and handle edge cases like empty boards. The GraphQL query to get items updated in the last 7 days from a Monday.com board is straightforward – Monday.com’s API documentation has copy-paste examples. But the no-code module approach above handles 90% of use cases without touching an API.
How to Build This Same Workflow in Zapier
If you prefer Zapier’s interface or already have a Zapier subscription, here is the same workflow mapped to Zapier’s terminology.
Zapier Zap – Step by Step
Trigger: “Schedule by Zapier” – set to every Monday at 7:00 AM.
Action 1: “Monday.com – List Items in Board” (or “Asana – Find Task” or your PM tool equivalent). Filter for recently updated items.
Action 2: “Formatter by Zapier – Utilities – Line Itemizer.” This converts individual task items into a single text block. (Zapier handles multiple items differently from Make – you need this step to combine them.)
Action 3: “AI by Zapier” or “ChatGPT – Send a Prompt.” Paste the system prompt. Map the formatted data as input.
Action 4: “Slack – Send Channel Message” or “Gmail – Send Email.” Map the AI output as the message body.
Zapier advantage: AI by Zapier
If you use “AI by Zapier” as your AI step, you do not need a separate ChatGPT or Claude subscription. The AI is built into Zapier and included in your plan. The trade-off is less control over which model is used and fewer configuration options compared to connecting directly to OpenAI or Anthropic.
Alternative: Use Your PM Tool’s Built-In AI Instead
If you want the simplest possible setup and are willing to trade some formatting control, several project management tools now offer native AI status summaries that skip the external automation entirely.
Native AI Status Reports – What Each Tool Offers
Monday.com AI (Pro and Enterprise plans)
Monday’s AI Blocks let you add a “Summarize” block to any board that generates a paragraph-length summary of activity. You can customize the tone and length in the prompt. The AI also integrates into Monday’s automations, so you can trigger a summary to post to a Slack channel on a schedule. This is the fastest path to automated status reports if your team already uses Monday.
Asana AI (Business and Enterprise plans)
Asana’s AI can draft status updates directly within any project. Click “Update” on your project, and Asana AI suggests a draft based on recent task activity. You can edit and publish to the project page or share via email. Less flexible than the external workflow but requires zero setup.
Notion AI Agents (All plans – free through May 2026)
Notion’s Custom Agents (released February 2026) can be scheduled to run weekly, pull data from Notion databases, and write a status summary into a new Notion page. They can also cross-reference data from connected Slack channels for additional context. The most powerful native option if your team already uses Notion as a hub.
ClickUp AI (paid plans)
ClickUp’s AI assistant can summarize tasks and write updates, though it is more oriented toward individual task-level summaries than full project reports. For a weekly report, you would still benefit from the external AI approach in this blueprint.
The trade-off with native tools is consistency. When you use your own AI prompt (the approach in this blueprint), you control the format, the tone, the sections, and the audience framing week after week. Native summaries vary in structure and depth depending on the data available. For quick internal updates, native is fine. For reports going to leadership, the external prompt approach gives you more professional, consistent results.
How to Pull Data From Multiple Tools Into One Report
Most teams do not live in a single tool. Your engineering work is in Jira, marketing tasks are in Asana, and company announcements happen in Slack. A good weekly report needs to reflect all of it.
In Make, this is straightforward. Add multiple data source modules (one for each tool) before the Text Aggregator module. The aggregator combines everything into a single text block. Add a label before each section so the AI knows which data came from where:
--- DATA FROM MONDAY.COM (Marketing Projects) --- [Monday.com task data here] --- DATA FROM ASANA (Product Development) --- [Asana task data here] --- DATA FROM SLACK #team-updates (Key Announcements) --- [Slack messages here] --- ADDITIONAL CONTEXT --- Client ABC renewed their contract on Wednesday. Design team was at 50% capacity due to PTO.
The AI prompt from Step 3 handles this multi-source format without modification. It will organize the report by workstream and cross-reference items naturally.
Example: Before and After
Here is what this looks like in practice, using realistic (anonymized) data from a marketing operations team.
The raw data had eight rows. The AI turned it into a report a VP can read in 90 seconds and know exactly what is on track, what is not, and what needs their decision.
Common Failure Points and How to Fix Them
After running this workflow weekly for four months, here is what goes wrong and how to prevent it.
Failure Points and Fixes
Problem: AI fabricates tasks or progress that is not in the data.
Fix: The prompt already includes an instruction not to fabricate. If this still happens, add: “Only reference tasks that appear in the data below. If you are unsure about a detail, write [Needs verification] instead of guessing.” Claude follows this instruction more reliably than ChatGPT in my testing.
Problem: The report is too generic – it reads like a template, not a real update.
Fix: This happens when the AI does not have enough context. Add those 2-3 sentences of human context before the data (the client escalation, the PTO situation, the priority shift). The AI cannot read your mind – it needs the narrative that the task statuses alone do not convey.
Problem: The Make/Zapier automation pulls too many items or not enough.
Fix: Tighten your date filter. “Last Updated in the past 7 days” should be your baseline. If you are getting hundreds of items (common with active boards), add a status filter to only pull items that are “Done,” “Stuck,” or “Working on it” – exclude items that have not changed status.
Problem: The Text Aggregator in Make produces garbled output.
Fix: Make sure you are mapping the right fields in the aggregator. A common mistake is mapping the entire item object instead of specific fields (name, status, assignee). Map each field individually and separate them with ” | ” for clean AI input.
Problem: Slack delivery cuts off long reports.
Fix: Slack messages have a 40,000-character limit (not usually an issue) but can look overwhelming in a channel. If your report is long, deliver it as a Google Doc link instead. Or use Slack’s “Post to channel” (which formats as a rich document) instead of “Send a message.”
How to Improve Your Status Reports Over Time
The prompt is not set-and-forget. The best reports come from iterating on the prompt based on real feedback. Here is how to build an improvement loop.
After each report goes out, ask yourself (or your stakeholders) three questions. Did the executive summary capture what actually mattered this week? Did the report miss anything important? Was anything in the report unnecessary or obvious?
If the same feedback comes up two weeks in a row, update the prompt. For example, if your VP consistently asks about budget burn rate and the report does not include it, add a “Budget Status” section to the prompt template. If the “Next Week” section is never useful, cut it.
Feedback prompt to refine report quality
Review the attached status report. Compare it against the raw project data below it. Score the report on three criteria: 1. ACCURACY (1-5): Does every claim in the report match the data? Flag any fabricated or embellished details. 2. COMPLETENESS (1-5): Did the report miss any significant items from the data? 3. ACTIONABILITY (1-5): Would a busy executive know exactly what to do after reading this? Then suggest specific prompt modifications that would fix any issues you identified.
Run this QA prompt once a month (not every week – that is overkill). It is a five-minute check that prevents prompt drift.
What This Workflow Costs – Full Cost Breakdown
Monthly Cost by Automation Level
| Component | Level 1 (Manual) | Level 2 (Semi-Auto) | Level 3 (Full Auto) |
|---|---|---|---|
| Project management tool | Already have | Already have | Already have |
| AI subscription | $20/mo | $20/mo | $20/mo |
| Automation tool (Make or Zapier) | $0 | $0 (free tier) | $0-20/mo |
| Total | $20/mo | $20/mo | $20-40/mo |
| Time saved per week | 1-2 hours | 2-3 hours | 3-4 hours |
If a manager’s fully loaded cost is $75/hour (reasonable for a mid-level PM in the US), saving 2 hours per week equals $600/month in recovered time. For a team producing multiple reports, the math gets even more obvious.
What to Build Next
Once your weekly status report is running, you are sitting on a workflow pattern that applies to dozens of other reporting tasks. Here are the natural next steps.
Daily standup summaries. Use the same workflow with a daily trigger and a shorter prompt. Pull “tasks updated today” instead of “tasks updated this week.” Deliver to a Slack channel by 9 AM so the team starts the day aligned.
Client-facing project reports. Duplicate the Make scenario and swap the system prompt for one that writes in a client-appropriate tone – less internal jargon, more milestone-focused, no mention of internal blockers unless they affect the client.
Monthly executive summaries. Point the data collection at the full month and expand the prompt to include trend analysis: “Compare this month’s completion rate to last month’s. Highlight any patterns.”
Cross-team dependency reports. Pull data from multiple teams’ boards and add a section to the prompt: “Identify any tasks in Team A’s data that are dependencies for tasks in Team B’s data. Flag mismatched timelines.”
Tools Used in This Blueprint
| Tool | Role | Cost |
|---|---|---|
| Monday.com / Asana / ClickUp / Notion | Project data source | Your existing plan |
| ChatGPT (GPT-5.3) or Claude (Sonnet 4) | Report writing | $20/month |
| Make (formerly Integromat) | Workflow automation | Free – $10.59/month |
| Zapier (alternative) | Workflow automation | Free – $19.99/month |
| Slack / Gmail / Google Docs | Report delivery | Your existing plan |
Blueprint in the AI Automation Blueprints series.
Every blueprint is co-authored with AI and tested by me. Last updated April 2026.
