Team Charter: How to Create One (+ Free Template)

Most teams never write down how they work. They inherit habits, absorb a few unspoken rules, and discover the rest through friction — a missed handover, a decision someone thought was theirs to make, a quiet disagreement about what “done” means. A team charter replaces that guesswork with a shared agreement the whole team has actually made together.

This guide explains what a team charter is, how it differs from working agreements and team norms, and how to create one step by step. There’s a free template you can copy, worked examples for different kinds of team, and a faster way to build it: as a live session where everyone contributes at once, rather than a document one person drafts alone.

What is a team charter?

A team charter is a short, living document that a team writes together to agree how it will operate: its purpose, who does what, the values it holds, the way it works, and what success looks like. Think of it as the team’s North Star — a shared point of reference you return to when a decision is unclear or a new person joins, not a form you fill in once and forget.

The word living matters. A charter is most useful when it keeps pace with the team: revisited when the work changes, refined when an agreement stops fitting, and consulted when people disagree. A charter that is written once and filed away describes the team you used to be, not the one you are now.

What a team charter includes

Charters vary, but the useful ones cover the same core sections:

Purpose and mission — why the team exists and the outcome it’s accountable for.
Scope and goals — what’s in and out of the team’s remit, and its near-term objectives.
Roles and responsibilities — who owns what, and where decisions sit.
Values — the handful of principles the team agrees to hold itself to.
Working agreements and norms — the explicit “how we work together” commitments.
Communication and decision-making — channels, response expectations, and how calls get made.
Success measures — how the team will know it’s doing well.
Review cadence — when and how you’ll revisit the charter.

Keep each section short. A charter people genuinely use is one or two pages — long enough to be clear, short enough that everyone has actually read it.

Why a team charter matters

A charter is not bureaucracy; it’s the cheapest way to prevent the most expensive problems. Almost every recurring team friction — duplicated work, decisions relitigated, the same misunderstanding twice — traces back to an assumption that was never made explicit. Writing it down once is far cheaper than colliding over it repeatedly.

A good charter pays off in four concrete ways. It aligns the team around a single purpose, so effort points the same direction. It speeds up onboarding, because a new joiner can read in ten minutes what would otherwise take months to absorb. It reduces conflict, because expectations are agreed in the calm before a deadline rather than argued in the heat of one. And it builds psychological safety: when a team has openly agreed how it gives feedback and makes decisions, people know where they stand and are more willing to speak up.

Team charter vs working agreements vs team norms

These three terms are used interchangeably, and even Google’s AI Overview conflates them. They are related but not the same, and seeing how they nest makes each one clearer:

A team charter is the whole foundational document — purpose, roles, values, agreements and success measures together.
Working agreements are the explicit commitments inside the charter about how you work together: meeting times, response expectations, how decisions get made, how you handle disagreement.
Team norms are the expected behaviours those agreements make visible. Every team already has norms — they’re just usually unspoken. Writing them down turns “the way things are done here” into something everyone can see, question and agree to.

The simplest way to hold it: norms live inside your working agreements, and your working agreements live inside the charter. You don’t need all three as separate documents. For most teams, a single charter with a strong working-agreements section is enough.

How to create a team charter (step by step)

Create the charter with the team, not for it. A charter handed down by a manager is just another policy; one the team co-creates becomes an agreement people feel ownership of. Work through these six steps in order — each builds on the last.

Step 1 — Define purpose and scope

Start with why the team exists and the outcome it’s accountable for, in a sentence or two. Then draw the boundary: what’s in the team’s remit and, just as importantly, what isn’t. Ambiguous scope is one of the most common sources of friction, so name it early.

Step 2 — Agree roles and responsibilities

Map who owns what, and where decisions sit. The goal is that every important area has a clear owner and no critical responsibility is assumed-but-unassigned. This is also where you surface the quiet question of who gets to decide what — far better answered now than mid-disagreement.

Step 3 — Set values and working agreements

Agree the handful of principles the team will hold itself to, then translate them into concrete working agreements: core hours, meeting etiquette, how you respond to requests, what “done” means, how you give and receive feedback. This is where your team norms become explicit. Keep the list short and behavioural — agreements you can actually point to later.

Step 4 — Decide how you’ll communicate and make decisions

Name your channels and what each is for, your response expectations across time zones, and how decisions get made — by whom, and how disagreement is resolved. For distributed teams this section does the heaviest lifting, because none of it can be picked up from being in the same room.

Step 5 — Define success and a review cadence

Agree how the team will know it’s doing well — a small set of measures or signals, not a dashboard. Then decide when you’ll revisit the charter: a light check-in each quarter, and a proper review whenever the team changes shape.

Step 6 — Get buy-in and keep it alive

Close by confirming everyone genuinely agrees — not just nods along. Make the charter easy to find, and bring it back into the open regularly so it keeps describing how the team really works. A charter nobody revisits quietly becomes fiction.

Run it as a live team session

Here’s the difference that makes a charter stick: build it as a workshop, not a document. When one person drafts a charter and circulates it, you get compliance at best. When the whole team adds input, discusses it, and votes on what makes the cut, you get a genuine agreement people own.

A live session maps neatly onto the steps above. Open a board with a column or section for each part of the charter — purpose, roles, values, working agreements, success measures. Give everyone a few minutes to add their own thoughts silently first, so the quietest voices land alongside the loudest. Group the themes, discuss the points of difference, and dot-vote to reach consensus on each section. For a distributed team, the same board runs asynchronously: people contribute over a day or two, then you meet briefly to resolve the open questions.

This is exactly what TeamRetro is built for — silent brainstorming, anonymous input and live voting on a shared board. You can generate a custom team charter board and run the whole session with your team in one sitting, or browse the retrospective templates for a collaborative format to adapt.

Team charter template

Copy the structure below as your starting point — fill each section in as a team, and cut anything that doesn’t earn its place.

Team name & purpose — One or two sentences: why we exist and the outcome we own.
Scope — In our remit / Not in our remit.
Goals — Our two or three near-term objectives.
Roles & responsibilities — Each role, its owner, and the decisions it covers.
Our values — The three to five principles we hold ourselves to.
Working agreements — How we work together (core hours, meetings, response times, “done”).
Communication — Which channel for what, and our response expectations.
Decision-making — How we make decisions and resolve disagreement.
Success measures — How we’ll know we’re doing well.
Review cadence — When and how we’ll revisit this charter.

Team charter examples

The structure stays the same; the emphasis shifts with the kind of team. Four short examples:

Agile software squad. Purpose framed around a product outcome; roles map to the scrum roles; working agreements cover definition of done, code review turnaround and ceremony times; success measured by delivery flow and team health, not just output.
Cross-functional project team. People drawn from several functions for a fixed goal, so the charter leans hard on scope, decision rights and communication — who represents which function, and how trade-offs between them get resolved.
Leadership team. Emphasis on values, decision-making and how the group disagrees well in private and presents a united front in public; success measured by the health of the wider org, not the team’s own output.
Remote / distributed team. The working-agreements and communication sections carry the most weight — core overlap hours, async-first expectations, response times across time zones, and how the team stays connected without a shared room.

Working agreements and team norms examples

Concrete agreements you can lift and adapt. The best ones are specific and behavioural — something you can actually point to later:

Meetings — We start and finish on time; every meeting has an agenda and an owner.
Communication — We reply to direct messages within one working day; we keep decisions in the open channel, not DMs.
Availability — We share core overlap hours and block focus time; we don’t expect replies outside working hours.
Decisions — We disagree and commit; once a decision is made, we back it.
Feedback — We give feedback directly and kindly, in private; we assume good intent.
Quality — We don’t mark work done until it meets our shared definition.
Conflict — We raise issues early and directly with the person involved, not around them.

These double as team norms: write down the behaviours your team already expects but has never said aloud, and you turn assumptions into agreements.

Keeping your charter alive

A charter earns its keep only if the team keeps returning to it. The easiest way is to fold it into rhythms you already have. Revisit your working agreements in a start, stop, continue retrospective — what should the team start doing, stop doing, or keep doing? Use a company culture retrospective when the values section needs a refresh, and a regular team health check to sense whether the team is living its charter or quietly drifting from it.

If a team agreement keeps getting broken, that’s a signal — not to enforce harder, but to revisit the agreement together. Our guide to running effective retrospectives covers how to turn that kind of signal into a concrete change, and our older piece on social contracts and team agreements goes deeper on making agreements that genuinely shift culture.

When you’re ready to put your charter to work, browse the health check templates to keep a pulse on how the team is doing against it.

Frequently asked questions

What is a team charter?

A team charter is a short, living document a team writes together to agree how it will work: its purpose, scope, roles, values, working agreements and what success looks like. It acts as a shared point of reference — a North Star you revisit as the team changes, rather than a one-off form you file away.

What’s the difference between a team charter, working agreements and team norms?

The charter is the whole foundational document. Working agreements are the explicit commitments inside it about how you work together — meeting times, response expectations, how decisions get made. Team norms are the expected behaviours those agreements make visible, so everyone holds the same picture instead of guessing. Norms live inside your working agreements, and your working agreements live inside the charter.

How do you create a team charter?

Create it as a team, not for the team. Agree your purpose and scope, then roles and responsibilities, then your values and working agreements, how you’ll communicate and decide, and finally what success looks like and when you’ll review it. Running it as a live session where everyone contributes and votes produces far more buy-in than one person drafting it alone.

Who should create a team charter?

The whole team, together. A charter written by a manager and handed down is just another policy; one the team co-creates becomes a genuine agreement people feel ownership of. The facilitator’s job is to draw out everyone’s input and help the group reach consensus, not to dictate the content.

What should a team charter include?

A useful charter covers purpose and mission, scope and goals, roles and responsibilities, shared values, working agreements and norms, how you communicate and make decisions, what success looks like, and a review cadence. Keep each section short — a charter people actually use is one or two pages, not a dozen.

How often should you review a team charter?

Treat it as a living document. Revisit it whenever the team changes shape — new members, a new project, a reorganisation — and check in lightly every quarter or during a retrospective. A charter that is never revisited quietly stops describing how the team really works, which is when it loses its value.