Team Charter
What is a Team Charter?
A team charter is a document the team writes together covering its purpose, scope, goals and measures, roles, decision rights and working norms. It is drafted when a team forms and updated when its mission or members change.
Updated November 2026 · 3 min read
A team charter is a short document, written and agreed by a team, that sets out why the team exists, what it is responsible for, how it will measure success, who does what and how members will work together. It is created when a team forms or takes on a new mission, and revisited when that mission or membership changes.
The value of a charter lies mostly in the conversation needed to write it. Agreeing on purpose, scope, decision rights and working norms surfaces disagreements early, when they are cheap to resolve, rather than in the middle of a deadline. The finished document then serves as a reference for new members and for stakeholders who need to know what the team does and does not own.
What a team charter includes
| Section | What it answers |
|---|---|
| Purpose or mission | Why the team exists and who it serves |
| Scope | What the team owns and, just as important, what it does not |
| Goals and measures | The outcomes the team is accountable for and how they are measured |
| Members and roles | Who is on the team and what each person is responsible for |
| Decision making | Who decides what, and how disagreements are resolved |
| Working norms | Meetings, communication channels, response expectations, how work is tracked |
| Stakeholders and dependencies | Who the team works with or relies on, and how |
| Resources and constraints | Budget, tools, time commitments and limits |
Team charter vs. project charter
A project charter formally authorizes a project, names a sponsor and project manager, and sets scope, budget and timeline. It is usually approved by leadership. A team charter is written by the team itself and focuses on how a group works together. A temporary project team may have both: the project charter defines the work, and the team charter defines how the team will do it.
How to create a team charter
- Hold a working session. Bring the whole team together for one to two hours. A charter written by one person and circulated misses the point.
- Agree the purpose. Draft a one- or two-sentence mission and test it against the work the team actually does.
- Set boundaries. List what is in scope and out of scope, especially where other teams overlap.
- Define goals and measures. Choose a small number of outcomes, ideally linked to company objectives.
- Clarify roles and decisions. Use a simple RACI matrix for recurring decisions.
- Agree working norms. Cover meetings, communication, availability, and how conflicts are raised.
- Share and revisit. Publish the charter where stakeholders can see it, and review it each quarter or when the team changes.
A team charter example
Consider a hypothetical cross-functional onboarding team of seven: a product manager, a designer, four engineers and a customer success lead. Its charter states:
- Purpose: Help new customers reach their first successful project quickly.
- Scope: Sign-up, setup wizard, templates and first-week in-app guidance. Out of scope: billing and enterprise implementation services.
- Goal: Reduce median time from sign-up to first completed project from 21 days to 10 days by the end of the second quarter.
- Decisions: The product manager decides priorities after consulting the team; engineers decide technical approach; disagreements on priorities go to the group product lead within one week.
- Norms: Planning every two weeks, written updates on Fridays, a 24-hour response expectation on the team channel during working days.
When a sales leader later asks the team to build a custom import for one large prospect, the scope section gives the product manager a clear reason to route the request elsewhere.
Common pitfalls
- Writing it for the team instead of with it. Members who did not help shape the charter rarely follow it.
- Vague goals. "Improve onboarding" cannot be measured or prioritized against.
- Skipping out-of-scope items. Most conflicts with other teams happen at the boundaries.
- Filing it away. A charter nobody looks at after week one has little effect. Refer to it in planning and retrospectives.
A team charter complements team roles and responsibilities and team structure, and its goals often connect to company objectives and key results.
Frequently asked questions
What should a team charter include?
A team charter typically covers purpose, scope including what the team does not own, goals and how they are measured, members and roles, decision rights and how disagreements are resolved, working norms for meetings and communication, stakeholders and dependencies, and resources and constraints. Explicit out-of-scope items matter because most conflicts with other teams happen at the boundaries.
What is the difference between a team charter and a project charter?
A project charter formally authorizes a project, names a sponsor and project manager, sets scope, budget and timeline, and is usually approved by leadership. A team charter is written by the team itself and describes how the group will work together. A temporary project team can have both, one defining the work and the other defining how it gets done.
How do you write a team charter?
Gather the whole team for a one- to two-hour working session rather than having one person draft it alone. Agree a short mission, list what is in and out of scope, choose a few measurable goals, clarify roles and decision rights, and set working norms. Publish it where stakeholders can see it and revisit it each quarter or when membership changes.
Related terms
RACI Matrix
Who is Responsible, Accountable, Consulted and Informed for each task.
Team Structure
How people and teams are grouped, led and divided up.
Stream-Aligned Team
A long-lived team that delivers one flow of value end to end.
Team Topologies
Four team types and three interaction modes for organizing technology teams.