# Team Charter

A jointly created document that clarifies a team’s purpose, boundaries, membership, decision rights, commitments, and measures of success.

- Type: artifact
- Domain: Leadership & teams
- Level: Foundational
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/team-charter/>)

## What it means

A team charter is a compact reference for why a team exists and how it intends to operate. Unlike a project plan, it emphasizes purpose, scope, authority, roles, stakeholders, success conditions, and core collaboration expectations. The team creates it together and revises it when its work or environment materially changes.

## Why it matters

Teams often inherit different assumptions about priorities, ownership, escalation, and acceptable tradeoffs. Making those assumptions discussable reduces avoidable friction and helps new members understand the operating context. A charter also gives sponsors and partner teams a clear basis for deciding what belongs inside or outside the team’s mandate.

## When to use it

Create one when forming a team, changing its mission, merging groups, starting a substantial cross-functional initiative, or recovering from persistent role confusion. Revisit it when membership, sponsorship, dependencies, or strategic goals change rather than treating it as an onboarding document that never moves again.

## How it works

1. Describe the purpose, intended beneficiaries, outcomes, and strategic connection in plain language.
2. Define scope, exclusions, constraints, dependencies, and the decisions the team may make without further approval.
3. Clarify member roles, sponsor responsibilities, stakeholder relationships, and how accountability is shared.
4. Agree how success will be assessed using outcomes and operating health, not only output volume.
5. Record a small set of collaboration and escalation principles, linking detailed working agreements where useful.
6. Review the draft with members and sponsors, publish it accessibly, and schedule revision triggers.

## A practical example

A new platform team writes a charter stating that it improves internal deployment reliability, owns the paved-road tooling, and does not approve every application design. It names product teams as customers, documents decision rights for standards, and tracks adoption, recovery time, and developer effort. Quarterly reviews prevent the platform mandate from expanding invisibly.

## Where it breaks

A charter cannot resolve structural contradictions such as two sponsors claiming final authority or a team receiving goals without capacity. Excessive detail becomes bureaucracy, while vague aspirations provide little guidance. The document may also legitimize an unreasonable mandate unless members can question scope, measures, and power arrangements during creation.

## Common mistakes

- Writing the charter for the team instead of creating it with the team.
- Listing activities without defining outcomes, boundaries, or decision authority.
- Publishing the charter once and ignoring changes in membership or mission.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/team-charter/#visualization-team-charter>)

## Sources

1. [Creating a Team Charter Guidance](<https://www.ppd.admin.cam.ac.uk/files/creating_a_team_charter_guidance.docx>) — University of Cambridge · University team guidance
2. [Creating Team and Project Charters](<https://www.bcit.ca/files/respect/teamandprojectcharters.pdf>) — British Columbia Institute of Technology · Institutional practical guide

## Related topics

- [Working Agreements](<https://wiki.soroush.uk/topic/working-agreements/>)
- [Delegation](<https://wiki.soroush.uk/topic/delegation/>)
- [Competency Matrix](<https://wiki.soroush.uk/topic/competency-matrix/>)
