Team playbook template
Keep a team's standards and routines in one place instead of tribal knowledge.
A good team playbook does one job: keep a team's standards and routines in one place instead of tribal knowledge. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.
Claude can turn your team's standards, recurring tasks, roles, coverage schedule, and the hard lines that shouldn't move into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.
What to include in the team playbook
- What's expected of anyone on this team, stated plainly.
- Roles and how coverage or shifts actually work.
- The recurring tasks or routines the team owns.
- The hard lines: what gets someone removed or corrected.
- Where to go with questions or escalations.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/team-playbook" skill.
How to create it with Send
Give Claude your team's standards, recurring tasks, roles, coverage schedule, and the hard lines that shouldn't move, plus any constraints, examples, or audience notes that matter. Ask it to create the team playbook with the Send connector so the output becomes a page instead of another loose document.
After you share it, Send helps you see whether the team open it, come back to it, or share it internally. You can update the same link when details change.
Team playbook structure
Standards
What's expected of anyone on the team.
Roles & coverage
Who does what, and when.
Routines
The recurring tasks the team owns.
Hard lines
What isn't negotiable.
Why send a team playbook as a page
A playbook only works if people actually read it and it stays current. Send keeps it as one link you can update in place instead of a stale doc buried in a drive.