Team Charter

What is a team charter?

A team charter is a shared agreement that sets out why a team exists and how it will work together, usually captured on a single canvas covering purpose, values, roles, working agreements, and success measures. It is created by the team, for the team, and acts as the reference point everyone returns to when priorities or behaviors drift.

Building a charter early gives a new or reforming team a common understanding before the work starts. Instead of assuming everyone shares the same picture of the goal, the roles, and the rules of engagement, you make them explicit and agree them out loud.

Key takeaways

• A team charter defines a team’s purpose and how it will work together.
• Core sections: purpose, values, roles, working agreements, success measures.
• The whole team should build it together so everyone commits to it.
• It is most valuable when a team forms, reforms, or changes direction.
• Treat it as a living document and revisit it as the team evolves.

Why use a team charter?

A team charter is a simple tool that helps a team:

• Align on a shared purpose so effort points in one direction.
• Make roles and responsibilities explicit, reducing overlap and gaps.
• Agree working agreements up front, so friction is designed out rather than fought over later.
• Define what success looks like, giving the team a clear target.
• Onboard new members quickly, because the “how we work” is written down.

Who should use a team charter?

Any team benefits, but charters are especially valuable for newly formed teams, cross-functional project teams, and teams that have grown or changed and lost their shared understanding. They suit team leads and scrum masters setting a team up for success, and any group experiencing friction over unclear roles or expectations.

A charter works only if the team owns it. It should be built collaboratively, in a session where everyone contributes and the wording is agreed together — not handed down as a policy document.

Team charter sections

A typical team charter canvas has five sections:

Worked example: a new cross-functional product squad

A newly assembled squad of engineers, a designer and a product manager runs a charter session in their first week:

• Purpose — “Help small teams make decisions faster by shipping a great collaborative planning tool.”
• Values — Customer first, disagree and commit, no blame, done over perfect.
• Roles — PM owns the roadmap, tech lead owns architecture, designer owns the experience, the whole squad owns quality.
• Working agreements — Standup at 9:30, no meetings on Wednesdays, decisions default to the owner but anyone can call for a group decision, assume good intent.
• Success measures — Deliver the beta by the agreed date, keep the bug backlog under ten, and score 4+ on the team-health survey.

Written down and agreed together, the charter becomes the squad’s contract with itself — something they can point to when a disagreement or a new joiner needs grounding.

How to run a team charter in GroupMap

GroupMap’s ready-made Team Charter Template gives you four sections — Team Mission, Values, Achievements and Responsibilities. Invite the team in with a link or password and everyone adds their ideas under each section at the same time, so you capture every voice, not just the loudest. Roles and working agreements both sit naturally under Responsibilities, and your success measures under Achievements.

Then group similar contributions, discuss, and converge on the wording the team can commit to. Because it is built live and together, people own the result. Capture any follow-ups as actions, share the finished charter, and revisit it as the team grows or its goals change.

Limitations of a team charter

A charter helps a team align, but it is not a fix-all. Keep these limits in mind:

1. A charter that is written once and never revisited quickly becomes irrelevant.
2. It sets intentions, not behavior — the team still has to live the agreements.
3. If it is imposed rather than co-created, people ignore it.
4. Too much detail makes it a document nobody reads; keep it to roughly one page.

Related templates

• Team canvas
• Start, stop, continue retrospective

References

• The five dysfunctions of a team — Patrick Lencioni
• The Team Canvas

Set your team up for success with GroupMap

A team charter works best when it is created by everyone and stays visible. GroupMap lets the whole team contribute to each section at once, group and discuss the ideas live, and agree the wording together, so the charter genuinely belongs to the team. Kept as a living reference and revisited as the team changes, it becomes the shared agreement people actually use — not a document that gets filed and forgotten.