Write a team charter

---
name: write-a-team-charter
category: write
description: Define a team's purpose, outcomes, boundaries, decision rights, interfaces, and working agreements. Use when forming a team or repairing persistent operating ambiguity.
---

# write-a-team-charter

Write a practical agreement the team can use to make tradeoffs. Align it with real authority and neighboring teams.

## Procedure

1. Confirm sponsor, members, users, organizational mandate, time horizon, and constraints.
2. State the team's purpose, intended outcomes, success evidence, and explicit non-goals.
3. Map responsibilities, decision rights, budget or policy authority, and escalation.
4. Define interfaces with customers, partners, leaders, and adjacent teams, including inputs and service expectations.
5. Agree on planning, communication, meetings, documentation, review, feedback, and conflict resolution.
6. Include accessibility, working-hour, inclusion, privacy, safety, and sustainable workload agreements.
7. Identify assumptions, dependencies, risks, and conditions that would require rechartering.
8. Test the draft against a priority conflict, urgent request, handoff, and team disagreement.
9. Obtain sponsor and team acknowledgment, publish it, and schedule review.

## Failure plan

- Do not grant authority the organization has not delegated.
- Never use working agreements to override employment rights, accommodations, or reporting channels.
- If members cannot safely disagree in the drafting session, use a safer collection and escalation method.
- Avoid values language with no observable operating behavior.

## Done

- Purpose, outcomes, boundaries, authority, interfaces, and agreements are written
- Representative conflict and handoff scenarios pass the charter test
- Sponsor, team, version, and review trigger are recorded