Productivity & Communication ⏱ 25–40 min to set up ✓ Tested March 2026

How to Auto-Draft Your Weekly Update So You Just Review and Hit Send

Every Friday, the same ritual: you sit down to write the weekly update for your team, your clients, or your investors — and you spend 45 minutes doing it. Not because it's hard. Because it's tedious. You have to remember what happened, check your notes, piece together what shipped, and write it in a way that makes sense to people who weren't in the weeds with you. This guide shows you how to hand that job to an AI. Friday morning, a draft lands in your inbox. You spend 5 minutes tweaking it. You hit send. Done.

Who This Is For

This setup works for anyone who sends a recurring update — doesn't matter if it's weekly, biweekly, or monthly:

The content of your update will be different, but the setup is the same.

What the AI Actually Does

Every Thursday night (or Friday morning before you wake up), the AI does five things:

  1. Pulls your completed tasks for the week from your task manager — anything you marked done since last Monday
  2. Scans your email threads for major decisions made, deliverables sent, or project milestones confirmed
  3. Checks what's still in progress — projects that are active but not yet closed
  4. Looks at next week's calendar for anything worth flagging (big meetings, deadlines, launches)
  5. Drafts the update in your voice using a template you set once and tweak over the first few weeks

The draft lands in your Drafts folder (or as a new email to you, depending on your setup). You open it, read through it, add anything the AI missed or didn't have access to, and send.

What the Draft Looks Like

Here's a real example of a draft this system produced for a solo consultant:

Weekly Update Draft — Week of March 3–7, 2026

Subject: Weekly Update — Riverside Project + 2 Completions This Week

✅ What We Completed This Week

Delivered the onboarding flow redesign to Acme Co — final assets sent Thursday via email. Sarah confirmed receipt; waiting on her review by EOD Friday.

Finished the Q1 performance report — 14-page document, sent to all stakeholders Tuesday. No follow-up items outstanding.

Resolved the login bug on the staging environment. The fix is deployed; confirmed working with three testers.

🔄 Currently In Progress

Riverside Bakery website build — on track for March 15 soft launch. Content from client still needed by Monday to stay on schedule.

Invoice automation setup — 60% complete. Blocked waiting on API credentials from their accounting software. Following up next week.

📅 Next Week Preview

• Monday: Kick-off call with Metro Supplies (new engagement)

• Wednesday: Quarterly review with your bookkeeper (add numbers before this)

• Friday: Soft deadline for Riverside Bakery content delivery

⚡ One Thing to Flag

The invoice automation project is running 5 days behind the original estimate due to a dependency on the client's side. If credentials aren't received by Wednesday, the March 21 completion date will slip.

That draft was written by an AI, in about 90 seconds, using data from a task manager and inbox. The consultant read through it, added one sentence about a conversation that happened over the phone, and sent it. Total time: 4 minutes.

Where the AI Gets Its Data

The draft is only as good as the sources it can read. Here's what works well:

Compatible Data Sources
Todoist (best integration)
Notion (tasks + databases)
Asana
Linear
Gmail / Google Calendar
Outlook / Office 365
Google Docs (manual export)
Trello (limited)

Green = full read access via API. The AI can pull task status, due dates, and completion data automatically. Yellow = partial — you may need to manually paste a snapshot into a shared note once a week. Still saves time; the AI still writes the draft.

Don't use a task manager at all? You can still make this work by keeping a simple running list in a shared Google Doc or Notion page — just jot what you worked on each day in one sentence. That's all the AI needs.

How to Set It Up

1

Write your "update template" once

This is the most important step and it takes 10 minutes. Write a sample weekly update by hand — ideally one you've actually sent before, or an ideal version of one. This is your template. It tells the AI what sections you include, how long each section should be, and what your tone sounds like. Paste it into a note that the AI can reference. You'll refine it after the first 2–3 runs, but your first version doesn't need to be perfect.

2

Connect your task manager

If you use Todoist, Notion, Asana, or Linear, connect it via API. Most of these have free read-only API access — you're not giving the AI permission to create or delete anything, only to read your task list. If you use a different tool or no tool, create a shared Notion page or Google Doc called "Weekly Log" and spend 3 minutes at the end of each day dropping in a bullet of what you did. That's your input source.

3

Connect email and calendar (read-only)

This is the same read-only connection used in the morning briefing setup — one click for Gmail or Outlook. The AI scans your sent items and received emails from the past 7 days to catch deliverables and decisions that didn't make it into your task manager. Your calendar provides next week's preview. Read-only means it cannot send or modify anything without you.

4

Set the draft generation schedule

Configure it to run Thursday evening (say, 9 PM) or Friday at 5 AM — whenever works for your send time. The cron schedule is simple: one job per week. The AI runs, compiles everything, generates the draft using your template, and saves it. On Thursday nights I run mine at 11 PM so it's ready when I open my laptop Friday morning. Takes about 45 seconds to generate.

5

Choose your draft delivery method

Two options: (a) the AI saves the draft directly to your Gmail Drafts folder, so you open your inbox Friday and it's already there waiting — just open, edit, send. Or (b) the AI emails the draft to yourself as a plain-text message, which you copy-paste into a new email and send. Option (a) requires a Gmail write scope and is smoother. Option (b) requires zero extra permissions and takes 90 more seconds. Pick whichever you're comfortable with.

6

Tune for the first three weeks

After each of your first three Fridays, spend 2 minutes noting what the draft got right and what it missed. Common tuning: adjusting how many email threads it scans (sometimes it includes too much; filter by sender or subject line), removing sections you don't actually use, and adjusting the tone if it's too formal or too casual. By week four, most people stop touching it.

The Exact Prompt Template

Copy this as your starting system prompt and adjust the bracketed sections for your situation. This is what I use for my own weekly review output:

# Weekly Update Draft Generator You are a business communications assistant drafting a weekly update email. Context about this business: [Describe your work in 2–3 sentences. E.g.: "I'm a freelance web designer. I work with 3–6 active clients at a time on website builds and ongoing retainers. My clients are small business owners, not technical."] Who receives this update: [E.g.: "My active clients — one email per client, personalized to their project. Friendly but professional tone."] # OR: "My team of 4 — casual tone, bullets preferred, no fluff." # OR: "My investors — formal tone, include metrics where available." Structure to follow (from my template): [Paste your sample update here] Data available: - Tasks completed this week: {completed_tasks} - Tasks in progress: {active_tasks} - Relevant emails from this week: {email_summary} - Next week's calendar: {calendar_preview} Instructions: 1. Write in my voice — direct, clear, no corporate jargon 2. Lead with the most important completion first 3. Flag any blocked items or slipping deadlines prominently 4. Keep the whole update under 300 words 5. If anything is unclear or missing, note it in brackets so I can fill it in 6. Do not make up specifics — only use what's in the data provided

The most important line: "Do not make up specifics — only use what's in the data provided." This prevents hallucination. The AI will occasionally flag a gap with a bracket like [confirm delivery date with client] — that's exactly what you want. It's telling you what it doesn't know so you can fill it in before sending.

Variations: Different Updates, Same Setup

Client Update (Freelancers)

Run the same system once per client, filtered to tasks and emails related only to that client. You get one draft per client. Review each one, send. Clients notice the consistency — same format, same day, every week — and it builds trust even on quiet weeks.

Investor Update (Founders)

Add a "metrics" section to your template and connect your revenue tool (Stripe, Paddle, or a spreadsheet you update weekly). The AI pulls numbers automatically. You still write the "what's coming next" paragraph by hand — that's strategy, which is yours. Everything else is automated.

Team Standup (Managers)

Shift from weekly to daily. Run the job every evening at 6 PM pulling just today's completions and blockers. Lands in your Drafts. Review in 2 minutes each morning, send to your team before 9 AM. Never miss a standup again because you "didn't have time to write it up."

What This Actually Saves You

Most people spend 30–60 minutes per week writing updates they already know. The thinking is already done — you lived the week. The bottleneck is just writing it down in a coherent way. That's exactly what AI is fast at.

30–50 min saved per week
The draft is done before you open your inbox. Your job is editing, not writing from scratch.
📬
Updates actually go out
When writing feels like work, it gets skipped. When reviewing takes 5 minutes, it gets done every week.
🎯
Nothing gets buried
The AI doesn't forget that the invoice project is blocked or that the client hasn't replied. It notes it. Every week.
📈
Clients and teams trust you more
Consistent communication, on schedule, every week. That's what separates dependable from flaky — and it's now fully automated.

Common Questions

What if my week was boring and nothing major happened?

That's fine — the AI will draft a shorter update. A "light week" update that honestly says "steady progress, nothing urgent, here's what's next" is better than no update. The template handles this gracefully if you add a note like: "If there are no major completions, still send a brief 'steady progress' note rather than leaving it blank."

What if the AI gets something wrong?

That's what the 5-minute review is for. It will occasionally misattribute a task, get a date slightly wrong, or miss something that happened over the phone. You catch it, fix it, send. The AI is writing the first draft, not the final one. Your eyes are still on it before it goes anywhere.

Does it need access to everything?

No. The more data sources you connect, the better the draft — but it works fine with just one. Even connecting only your task manager and running a basic summary produces a 70% complete draft. Add email and calendar and you're at 90%. That last 10% is context that only lived in a phone call or in your head — you add it before sending.

Can I personalize the draft per recipient?

Yes. If you send different updates to different people — clients getting project-specific summaries, your team getting the full picture, investors getting metrics — run the job multiple times with different filters and templates. Takes maybe 5 extra minutes of setup per variant, then it's automatic.

Get the exact config

Library members get the full working setup — cron job template, prompt file, Gmail Drafts integration, and the task manager connectors. Copy-paste and have it running in under 30 minutes.

Get Library Access — $9/mo →

30-day money-back guarantee. Cancel anytime.

← Back to the Library