Project status packs with Claude Cowork

TL;DR. Each week, assemble a status pack for active projects — progress vs plan, risks, decisions needed, asks. Distribute to sponsors without spending the project lead's Friday afternoon. About 2 hours per project per week saved. The ban on "on track" is what separates a useful pack from status theatre.

Job to be done#

Assemble the weekly status pack for active projects: progress, risks, decisions, asks. Make it exec-readable in two minutes.

Who runs it#

PMO, project lead, or chief of staff supporting cross-functional initiatives.

Inputs (inbox/)#

• Project plan (Gantt, milestones — Excel or MPP export)
• Latest contributor updates (markdown files or notes)
• Last week's pack for comparison

Outputs (output/)#

• status-[project]-[date].docx — exec-ready 1–2 pages
• dashboard-[project]-[date].xlsx — milestone status with traffic-light rollup
• actions-and-asks.md — appended to a running tracker

Prompt seed#

Read /inbox/project-plan.xlsx and /inbox/updates-[date]/*.md.
Compare to last week's pack in /archive/[project]/.
Produce /output/status-[project]-[date].docx covering:
- Progress vs plan (one paragraph)
- Top 3 risks with mitigation and owner
- Decisions needed and option set
- Asks of sponsors
Generate /output/dashboard-[project]-[date].xlsx with milestone-level
RAG status.
Append unresolved actions to /output/actions-and-asks.md.
House style: no marketing language, no "we're tracking on track" —
be specific.

Quality bar#

• "On track" is forbidden as a status; require specifics.
• Risks have an owner and a date.
• Decisions framed as choices, not as narratives.
• Common trip-up: optimistic spin from contributor updates. Add a calibration line in CLAUDE.md: "Restate aspirational claims as evidence-based statements or remove them."

Time saved (typical)#

About 2 hours per project per week.

Upgrade path#

• Connector to your project-management tool (Asana, Linear, Jira) for live data.
• Schedule the run for Friday morning so leads have time to review before sponsors see it.

Tinkso's take#

The ban on "on track" is what separates a useful status pack from status theatre. Push back on Cowork until the tone is concrete. Once the pattern is in CLAUDE.md, future runs default to specifics — and the team realises how much vague status language they had been tolerating.