A readiness score tells you if you’re ready; these six templates are how you actually roll out. They’re the working documents behind a successful Claude Cowork pilot — a phased plan, a usage policy, a way to pick the right work, a pilot brief, the email that kicks it off, and a tracker that proves it worked. All free, all editable, nothing to fill in first — download the pack and start filling them in.
What’s in the pack — 6 editable templates
- 30/60/90-Day Rollout Plan
- Cowork Usage Policy
- Workflow Scorecard
- Pilot Team Brief
- Launch Comms Email
- Hours-Saved Tracker
Free · no email required · Word is editable, PDF is for printing or previewing.
The 6 Templates
Here’s what each one is and a preview of what’s inside. The full, editable versions are in the download.
1. 30/60/90-Day Rollout Plan
What it’s for: A phased plan that takes you from a single pilot team to Cowork being the default way work gets done — with a goal, actions, an owner, and a success signal for each 30-day window.
Who uses it: The champion and the executive sponsor, set together at kickoff.
- Days 1–30 · Pilot — prove value with one team and one first win.
- Days 31–60 · Expand — add a second cohort, connectors, and a shared workflow library.
- Days 61–90 · Embed — measure hours saved, formalize the policy, decide what’s next.
2. Cowork Usage Policy
What it’s for: A short, copy-paste policy that answers the question that stalls most rollouts: what data may go into Claude, who decides, and what has to be checked before output goes out.
Who uses it: Whoever owns data/security, co-signed by the champion. One page, pinned where the team can find it.
- Approved uses — drafting, summarizing, and analysis of non-sensitive material; brainstorming; research.
- Never put in — customer PII, secrets/credentials, or regulated data unless it’s been approved.
- The rule — review AI output before it’s shared externally; if unsure, ask the named owner.
3. Workflow Scorecard
What it’s for: A quick scoring grid to turn a vague sense of “Claude could help with stuff” into a ranked shortlist of the recurring work worth automating first.
Who uses it: The pilot team, in one working session. The disagreements are the useful part.
- Score each candidate workflow on frequency, time now, whether Claude can reach the inputs, and whether you have a ‘good’ example to steer quality.
- Sort by priority; start with a high-frequency, high-time task you can reach and judge.
4. Pilot Team Brief
What it’s for: A one-pager that pins down what the pilot actually is — who’s in it, what it’s pointed at, the first win, how you’ll know it worked, and the risks — so the pilot has a shape instead of drifting.
Who uses it: The champion drafts it; the sponsor signs off before day one.
- One page: pilot name, champion, members, dates.
- Three target workflows, one first win, two success metrics, known risks with owners.
5. Launch Comms Email
What it’s for: The email that kicks the pilot off — what’s happening, why, what you need from the team, and the ground rules — written so a champion can send it in two minutes.
Who uses it: The champion or sponsor sends it to the pilot team on day one.
- Subject: We’re piloting Claude Cowork — here’s what it means for [team]
- A ready-to-send body with placeholders: why now, what we need from you, the ground rules, and who to ask.
6. Hours-Saved Tracker
What it’s for: A simple log that turns “it feels faster” into a number you can take to leadership: minutes saved per task per week, rolled up to hours per month.
Who uses it: The champion maintains it; the whole pilot team drops rows in as they go.
- Log task, person, times/week, minutes before vs. with Cowork, and minutes saved.
- Roll up monthly: total minutes saved ÷ 60 = hours saved. Early numbers are estimates.
How the Templates Fit Together
The six aren’t a random grab-bag — they’re a sequence. Each one hands off to the next, from “are we ready?” through to “here’s the proof it worked.”
- Team Readiness Checklist — Are we ready to roll out at all?
- Pilot Team Brief + Usage Policy — Set the pilot up with a shape and safe data rules.
- Workflow Scorecard — Pick the recurring work worth automating first.
- 30/60/90 Rollout Plan — Sequence the rollout across the first three months.
- Launch Comms Email — Bring the team in and get them trying it.
- Hours-Saved Tracker — Prove what it saved — the number you take to leadership.
Frequently Asked Questions
Are the templates really free — and editable?
Yes. It’s a free download, no email required, and the pack ships as an editable Word (.docx) file so you can drop in your own team, dates, and workflows. There’s a PDF too if you just want to print or preview them.
How do these relate to the readiness checklist?
They’re the next step. The Team Readiness Checklist tells you whether you’re ready to roll out; these templates are the working documents you use once you are. Score first, then roll out with these.
Do I need all six?
No — take what fits. A small pilot might only need the Pilot Brief, a usage rule, and the tracker. Bigger rollouts use all six. If you want the reasoning behind the phased plan, the 30/60/90 rollout guide walks through it in depth.
Download the Template Pack
All 6 templates in one file — free, no email required. Word is editable; the PDF is for printing or previewing.
Related Resources
Team Readiness Checklist
Score your team across licenses, data rules, workflows, and adoption — the step before these templates.
All free resources
Browse the full resource library.
Cowork for teams guide
The complete guide to setting Cowork up for a whole team.
Want the Rollout Run With You — Not Just DIY?
These templates are everything you need to roll out yourself. If you’d rather have it run with you — cohort training, a governance session, and hours-saved measured — that’s what live team training is for.
Assembled by Peter Velinov, Claude Certified Architect – Foundations
Claude and Claude Cowork are trademarks of Anthropic. These templates are an independent training resource and are not affiliated with or endorsed by Anthropic.