The AI Weekly Planning Template Chiefs of Staff Use

Most chiefs of staff lose a Monday morning to the same ritual: reading every Slack thread, every Linear update, and every half-finished doc, then typing it all into a plan from a blank page. The AI weekly planning template below collapses that into a 20-minute session you run in Claude Cowork, where you paste the raw inputs and get back a structured synthesis of what moved, what slipped, and what your principal needs to decide. You keep the judgment. The template handles the assembly.

This isn’t a productivity hack you’ll abandon in two weeks. It’s a standing session pattern—the lowest-friction entry point in the Claude Cowork for chiefs of staff hub—that gets sharper every time you run it. The whole point of a template is that the format stays fixed so your attention can go to the content.

Why a Blank Page Is the Real Problem

Your weekly plan isn’t hard because the thinking is hard. It’s hard because the inputs are scattered and the starting point is empty. You’re reconciling five teams’ updates against last week’s commitments, hunting for the two things that actually need your principal’s attention, and doing it under the pressure of a Monday standup that starts in an hour.

The blank page tax is the time between “I have all the raw material” and “I have a first draft I can react to.” For most chiefs of staff that gap is 60 to 90 minutes of mechanical sorting. That’s the exact gap a template plus Claude Cowork is built to close. You stop typing the synthesis and start editing it.

A chief of staff at a 400-person SaaS company put it plainly: the synthesis was never the valuable part of her Monday. The decisions she surfaced from it were. The template lets her spend her time on the decisions.

The Template

Here’s the template. Paste it into Claude Cowork at the top of your session, fill the input slots with your raw material, and let Cowork produce the filled-out plan beneath it. Keep the headings fixed week to week so your principal learns to read the output fast.

# Weekly Operating Plan — Week of [DATE]

## INPUTS (paste raw material here)
- Last week's commitments: [paste the action items you tracked last week]
- Team updates this week: [paste raw updates from each team / channel]
- Metrics snapshot: [paste the numbers — revenue, pipeline, key KPIs]
- Principal's stated priorities: [paste any direction from your principal]

## INSTRUCTIONS TO COWORK
Read the inputs above and produce the four sections below.
Be specific and honest — flag what slipped, do not round it up.
Cite which team or input each point came from.

---

## 1. Closed the Loop
For each commitment from last week: DONE / SLIPPED / DROPPED, with one line of why.

## 2. What Moved and What Stalled
The 3–5 things that materially advanced, and the 3–5 that stalled.
Note the cause of each stall (blocked, deprioritized, under-resourced).

## 3. Decisions the Principal Needs to Make
The 1–3 items that actually require the principal's call this week.
For each: the decision, the options, your recommendation, the deadline.

## 4. This Week's Focus
The 3 priorities that should define the week, each tied to an owner.
Everything else goes in a "holding" list, not the focus list.

The structure does the work. Section one forces accountability on last week’s commitments instead of letting them quietly disappear. Section three is the one your principal cares about most—it’s the difference between a status report and a plan.

How to Run It in Cowork

Open a Cowork session and paste the full template, inputs included. The first instruction matters: tell Cowork to be honest about what slipped rather than rounding a yellow status up to green. Models default to a tidy, optimistic narrative, and an optimistic weekly plan is worse than useless because it hides the things you most need to act on.

Then read the output as an editor, not a reader. Cowork will get the assembly right and the framing roughly right. You correct the framing—whether a stall is really “blocked” or really “deprioritized,” whether a decision is genuinely the principal’s to make or yours. This is the same delegate-the-assembly, keep-the-judgment split that runs through every workflow in the hub, including using Claude Code as a chief of staff.

For the mechanics of feeding Cowork the right inputs without spending more time gathering them than the plan saves, the meeting prep workflow covers the same context-loading discipline. The instinct carries over directly: give the model the raw material once, in a consistent format, and let it do the sorting.

Make It Persist So You Never Start Cold

A template you retype every Monday is still friction. The fix is giving Cowork a standing brief—your template, your team list, your recurring priorities, the metrics definitions that never change—so each session starts already knowing your context. That one change is what separates a clever prompt from a workflow you actually keep.

This is the persistent-context pattern Anthropic documents for Claude Code memory, and it applies just as well to a recurring planning deliverable. Each week you paste only what’s new—this week’s updates and numbers—and Cowork already holds the structure and the background. The session that took 25 minutes in week one takes 15 by week four.

Keep one running file of the plans themselves. When you can scan eight weeks of “Decisions the Principal Needs to Make” in one place, patterns surface: the decision that keeps getting deferred, the team that’s been quietly stalled for a month. That longitudinal view is something no single Monday session gives you, and it’s where a planning template stops being admin and starts giving you the one thing the role is built on—visibility across everything you’re accountable for but can’t directly control.

Where This Connects

Weekly planning is the heartbeat, but it feeds the louder beats. The chiefs of staff who stay calm before a board meeting are the ones whose weekly plan already reserved incremental time for it, which is exactly the routine in the board prep playbook. A good weekly rhythm makes the quarterly scramble smaller every time.

Anthropic’s agentic workflow overview explains the broader pattern of handing multi-step assembly to an agent while keeping the decisions human, and the Claude Cowork product page shows how the same idea applies to office work rather than code. The template here is just that pattern, scoped to the one session you run every week.

Frequently Asked Questions

What makes this an AI weekly planning template and not just a checklist?

The structure is the same as a good checklist, but it’s written to be run by Claude Cowork against your real inputs. You paste in last week’s commitments, this week’s updates, and the metrics, and Cowork fills the template with a synthesis—what moved, what slipped, what needs a decision—instead of you typing it from a blank page. The template is the prompt and the output format at once.

How long should weekly planning take with this template?

Once the template is set up, most chiefs of staff get from raw inputs to a reviewed plan in 15 to 25 minutes. The first run takes longer because you’re tuning the inputs and the format. After two or three weeks it becomes a standing session you run on autopilot, with your judgment reserved for the decisions the synthesis surfaces.

Can I use this template if I’m not a chief of staff?

Yes. The template assumes you sit across multiple teams and have to translate their status into a coherent plan, which describes most operators, founders, and team leads as well as chiefs of staff. Drop the principal-update section if you don’t report into an executive, and keep the rest.

Does Claude Cowork keep my planning context week to week?

You can give Cowork a standing brief with your template, your team list, and your recurring priorities so each session starts informed rather than cold. The persistent-context pattern is the same one Anthropic documents for Claude Code memory, and it’s what turns a one-off prompt into a repeatable weekly rhythm.

Run it once this week. Take Monday’s raw inputs, paste them into the template, and let Cowork produce the first draft while you do the editing. If you want the guided version—with the standing brief set up and the longitudinal plan file built for you—the Claude Cowork course walks through the full weekly rhythm end to end.