Team charter: template, example, and the five sections worth arguing about (2026)

A team charter is the document a team writes once, at the start, to say why it exists, what it is responsible for, who is in it, how it makes decisions and how it communicates. It is one page. It is agreed by the people it binds, not handed down. And it is the document a new member reads on their first morning to learn what this team is for — which is why the charter's real test is not the meeting that wrote it but the day, six months later, when someone who was not in that meeting opens it.

Most charters fail that test the same way: a facilitator runs a two-hour session, the result goes into a slide deck, the deck goes into a folder, and the team runs on whatever it was doing before. The charters that hold are short, specific about the things the team actually disagreed on, kept where the team already looks every day, and reviewed on a date someone owns.

This guide is the craft first — what a team charter is and what it is not, the five sections worth arguing about and the three that need no argument — then how to write one in a single meeting, a template you can copy, a filled-in example for a sales team of eight across three sites, the documented place the charter lives in the tools you already pay for, and one way the written version stays readable by every member who joins after it was signed.

What a team charter is — and what it isn't

A team charter is the founding agreement of a standing team: a department, a desk, a cross-functional group that will exist for longer than one project. It answers five questions — why, what, who, how we decide, how we talk — and nothing else. Everything a charter says should be true for a year; anything that changes every month belongs in a plan. How a group drawn from several functions then runs its projects between charter reviews — one owner, one channel, a meeting only for a decision — is in cross-functional collaboration.

The term has four neighbours, and most long charters are long because they absorbed one of them.

Two of the five are the team's own to write: the charter, and the norms as its "how we work" section written out in full. The team norms guide covers the norms; this one covers the charter they hang from. A charter that restates the mission statement, or lists every responsibility of every role, is a charter nobody finishes reading.

The five sections worth arguing about

A charter is only worth the hour it took if the team disagreed about something while writing it. Five sections produce the disagreement; the others are a frame. Write the five with the argument in mind, and when a section goes through without a single objection, ask whether it says anything.

1. Purpose, and the result the team is judged by. One sentence for why the team exists, and one measurable thing — a number, a date, a state of the world — that says whether it did its job this year. "Onboard every new distributor to its first order within thirty days" is a purpose with a judge built in. "Support our distributors" is a department name. The argument here is about the measure: the team that cannot agree on what it is judged by has found its first real problem.
2. Scope: what the team owns, and what it does not. The list of things this team is responsible for, and — the half most charters skip — the list of things nearby that it is not: the adjacent team's work, the requests it will decline, the decisions it hands upward. The argument is always about the second list. Every item on it is a conversation the team will otherwise have, one request at a time, for a year.
3. Members and roles, including who decides. Every member by name, their role in this team in one line, and for each kind of decision the team makes, who has the last word. Not a RACI matrix — a short list: pricing exceptions, the lead decides; the weekly plan, the team decides by the rule in section four. The argument is about the people on the edges: the colleague from another department who is half in, the client contact who reads the channel, the contractor. The charter should say whether they are members, with a role, or readers.
4. How decisions are made, and where they are written. The rule for a decision that affects more than one person: who proposes, how long the team has to object, what counts as agreement, and where the decision is recorded so that it can be found and revisited rather than relitigated. The argument is about the silence rule — whether two working days without objection in the channel is agreement — and about the place: a decision that is not written in the agreed place has not been made.
5. How the team communicates: channel, cadence, language. Where the team's messages live — one channel, and which people outside the team are in it; which meetings happen on which rhythm, and which written status replaces a meeting; and, for a team that writes in more than one language, what language the team writes in and what each member reads. The argument about language is the one most charters avoid, and in a team with an office in Valencia and a desk in Katowice it is the one that decides whether sections one to four are read at all.

The three sections that need no argument are the frame: the team's name and the sponsor it reports to; the date the charter was agreed and the names that agreed it; the owner of the page and the date it is next reviewed. Fill them in last, in two minutes, and never skip the last one — a charter with no review date is a charter with no expiry, which is the same as one with no authority.

How to write a team charter in one meeting

A charter written by the manager alone is a policy; a charter written by the team is kept. The process takes one 90-minute meeting, a week of silence, and one date in the calendar.

A week before — collect the disagreements. Post one message in the team's channel: "We are writing our charter on Thursday. Reply with one thing this team should own that it doesn't, one thing it is asked to do that it shouldn't, and one decision from the last month that nobody can find." The answers are the agenda. Send a draft purpose sentence with the invitation so the meeting corrects it rather than discovers it; the meeting agenda template covers the form.

In the meeting — five sections, one decision each. Purpose first, with the measure, and do not leave it until the measure is a number or a date. Scope second, spending most of the time on what the team does not own. Members and roles third, naming the people on the edges. Decisions fourth, deciding the silence rule and the place. Communication fifth: the one channel, who outside the team is in it, the cadence, the language. Read the whole page back in the last ten minutes; the facilitator says each section aloud and the room corrects it while the people who argued about it are still there.

After the meeting — publish where the team looks. Post the charter as a note in the team's channel the same day and pin it, so it is the first thing a new member finds and the thing an existing member is sent to when scope is argued again. Two working days of silence in the channel after the post is agreement — the charter's own decision rule applied to itself. Members who join later read it on their first day; they can propose a change at the next review, not before.

On the review date — change the measure, not the purpose. The owner opens the page once a year, or when the team's sponsor, size or scope changes, and asks three questions: is the purpose still true, did we do what we are judged by, and which decisions this year were made outside the rule in section four. The result is usually a new measure, a line added to "we do not own", and one name changed. A charter rewritten from scratch every year is a team that never settled what it was for.

Team charter template

Copy the block below into the team's channel as a note, fill in the brackets, pin it. Every bracket is a decision; a charter with no brackets left to argue about was copied, not agreed.

[Team name] — team charter
Sponsor: [name, role] · Agreed: [date] by [names] · Owner: [name] · Review: [date, one year out, or on any change of sponsor, size or scope]

1. Purpose. [One sentence: why this team exists and for whom.]
Judged by: [one measurable result for this year — a number, a date, a state].

2. Scope.
We own: [three to seven responsibilities, each a noun phrase a stranger could check].
We do not own: [the adjacent work, the requests we decline, the decisions we hand upward — and to whom].

3. Members and roles.
[Name] — [role in this team, one line] · [Name] — [role] · …
Readers, not members: [the client contact, the contractor, the colleague from another department — and what they can see].
Who decides: [kind of decision] — [the lead / the team by the rule below / the sponsor].

4. Decisions. A decision that affects more than one person is proposed in [channel], with its reason. Silence for [two working days] is agreement. It is written in [channel, as a note or in the decision log] the day it is made. A decision not written there is not made.

5. Communication.
Channel: [one channel], with [who from outside the team] in it.
Cadence: [the weekly, its day and length]; [written status, its day and time]; [what replaces a meeting].
Language: each member writes in [their own language / the team's working language] and reads [in their own]; anything the whole team must act on is written in [channel], not only said in a call.

Changes: proposed in [channel], decided at the review. New members read this page on day one.

The template is plain text, so it pastes into a Word document, a Google Doc, a Slack canvas or a chat message without reformatting. Keep it to one page; a second page is a plan or a norms document trying to get in.

A filled-in example: a sales team of eight on three sites

An exporter of ceramic tiles with its office in Castellón, a two-person logistics desk in Katowice, a sales representative in Milan, and the order clerk of its largest German distributor reading the team's channel for the whole season. Eight people, three languages inside the team and a fourth outside it, one channel.

Distributor sales — team charter
Sponsor: Carmen, commercial director · Agreed: 2 November 2026 by Carmen, Álvaro, Nuria, Pau, Ines, Marek, Agata, Luca · Owner: Álvaro · Review: 2 November 2027, or when a distributor is added or dropped

1. Purpose. Keep every active distributor ordering each season and bring each new distributor to its first order within thirty days of signing.
Judged by: 100 % of the fourteen active distributors with at least one order per season; three new distributors to first order within thirty days this year.

2. Scope.
We own: price lists and seasonal terms for distributors; the order from confirmation to the loading date; stock allocation between distributors when a line is short; distributor onboarding; the monthly forecast to production.
We do not own: pricing to end customers (the distributor's); production scheduling (production's — we send the forecast, they answer with dates); transport claims after loading (logistics in Katowice decides with the carrier and tells the channel); credit limits (finance — we ask, in the channel, with the order number).

3. Members and roles.
Álvaro — team lead, allocation and pricing exceptions · Nuria — Spain and Portugal accounts · Pau — France and Benelux accounts · Ines — onboarding and the forecast · Luca — Italy and DACH accounts, Milan · Marek and Agata — logistics desk, Katowice: loading dates, documents, carrier.
Readers, not members: Herr Beck, order clerk at the Hamburg distributor — reads the channel and his own orders' threads for the season; proposes nothing, is asked before an allocation touches his lines.
Who decides: pricing exceptions and short-stock allocation — Álvaro; the weekly plan and anything about process — the team by the rule below; new distributor terms — Carmen.

4. Decisions. Proposed in #distributors with the reason and the orders it affects. Silence for two working days is agreement. Written as a note in #distributors the day it is made, with the date and the owner. A decision made by phone with a distributor is written in the thread before the end of the day, or it did not happen.

5. Communication.
Channel: #distributors, with Herr Beck in it for the season; one thread per order, from confirmation to loading.
Cadence: Monday 09:30 CET, 25 minutes, allocation and the week's loadings; written status Thursday 10:00 — done, next, blocked — instead of a second meeting; the monthly forecast as a note on the first working day.
Language: everyone writes in their own language — Spanish, Polish or Italian — and reads the channel in theirs; Herr Beck reads it in German. Anything a distributor is promised is written in the order's thread, not only said on the phone.

Changes: proposed in #distributors, decided at the review. New members read this page on day one.

Two of the five sections took most of the ninety minutes. Scope, because the Katowice desk had been handling transport claims for a year without anyone saying it owned them, and the forecast had two authors who disagreed every month. And members, because nobody had decided whether the Hamburg clerk was in the team or only reading it — the answer, "reader, asked before an allocation touches his lines", ended a season of surprises on both sides. Purpose took ten minutes once the measure was a count of distributors rather than a revenue figure the team did not control.

Where the charter lives in the tools you already use

Each suite has a place to keep a page the team reads, and each stops at a different point. The language of the page is the same everywhere: the one it was typed in. Documented behaviour only, from the vendors' own pages, with the month each fact was checked:

The pattern is the same in all four. The charter exists once, in the language it was typed in, and the member who reads another language reads that or a copy somebody made. The translation each suite documents belongs to the reader's own screen or to the call while it runs, not to the record — which is why the Castellón team's charter would have needed a Polish copy and an Italian copy, each a version behind the Spanish one. What a meeting leaves behind follows the same rule; where the transcript and summary go after the call is the longer version.

How the charter stays the first thing a new member reads

InterMIND is a communication space where a team's work lives in a channel, so the charter has an obvious home: the channel of the team it founds — the distributor desk, the clinic's front office, the agency's account group — and that channel is where the Monday call, the Thursday status and the decisions of section four happen too. Posted as a note — a rich-text message with headings and bold lines, edited later from its own menu — the charter is read by each member in their own language, with the original a toggle away, and pinned so the current version is the first thing a new member finds; with edit history switched on, the earlier wording of a changed section appears above the current text with its timestamp, which is the review trail the "agreed" and "review" lines point to. A decision under section four is a note in the same channel, or a line in a decision log kept there, and it is read by the Katowice desk in Polish the day it is written in Spanish. During the Monday call the charter, or the allocation list written under it, goes on everyone's screen next to the video tiles with Share to conference, and each participant reads it in their own language while the sharer edits live. When the call ends, the recap is written from the meeting itself — the summary, the decisions read back, the action items with owners — and arrives by email, as a message in the channel and as a link in the calendar event, readable by every signed-in member in their own language; any member can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session next to the charter that governs it. If the master copy stays in a document tool, its updates land in the channel by email: the channel's host gives it an address of its own, and a message sent there appears as a regular message with the sender named and attachments kept.

The people a charter names are not always employees. The distributor's order clerk who reads the channel for a season, the freelance agent, the colleague from finance who is a reader and not a member: an external member of the channel joins by email onto a free account and reads the charter, the threads and their history like everyone else, in their own language. A person without an account is a guest of one meeting — they join the Monday call by link, from a phone, at no cost, hear it live in their own language, and get no record afterwards.

The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat or asked the assistant. Members who go quiet keep their access at no cost, which is what a charter needs: the colleague who comes back from leave in spring still finds the page, and the review date, where they left them.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

A team charter as a craft survives every tool: somebody still has to get eight people to agree what they own, what they do not, and who decides. What does not have to survive is the second job — keeping a translated copy of the charter, the decisions and every recap by hand, one language at a time, for the desk that reads the other one.

FAQ

What is a team charter?

A team charter is the one-page founding agreement of a standing team: why the team exists and what it is judged by, what it owns and what it does not, who is in it and in what role, how it makes decisions and where they are written, and how it communicates — the channel, the cadence and the language. It is agreed by the people it binds, dated, owned by one person and reviewed on a set date, and it is the document a new member reads on their first day.

What should a team charter include?

Five sections worth arguing about — purpose with a measurable result, scope with an explicit "we do not own" list, members and roles including who decides what, the decision rule and where decisions are recorded, and communication: one channel, the meeting cadence, the written status and the language — plus a frame of three lines that need no argument: the name and sponsor, the date and names that agreed it, and the owner with the review date. One page; the template above is this list with the blanks.

What is the difference between a team charter and a project charter?

A project charter founds one project: its objective, scope, sponsor, budget, milestones and the authority of the project manager, and it ends when the project ends. A team charter founds a standing team — a department, a desk, a cross-functional group — and says how that team works across all its projects: purpose, scope, members, decisions, communication. A team may run several projects, each with a project charter, under one team charter; the kick off meeting guide covers what a project's first document must contain.

Who creates the team charter?

The team, in one meeting, with the lead facilitating and the sponsor present or reading the draft before it is published. A charter written by the manager alone is a policy — it is obeyed where it is checked and ignored where it is not. The lead's job is to bring the draft purpose sentence and the disagreements collected the week before; the team's job is to argue the five sections to one answer each; the sponsor's job is to confirm the purpose and the measure and to say what the team hands upward.

How long should a team charter be?

One page. Five short sections and three frame lines fit on it if scope is a list of noun phrases rather than paragraphs and roles are one line per person. A charter that runs to a second page has usually absorbed the team norms — the everyday rules of answering, meeting and writing — or a plan; move them to their own page and link it. The test is whether a new member reads the whole charter before their first coffee.

What is the difference between a team charter and team norms?

The charter says why the team exists, what it owns, who is in it and how it decides and communicates — the things that stay true for a year. Team norms are the everyday rules under the charter's "how we communicate" section written out in full: response times, how meetings run, how feedback is given, what language the team writes in — each observable day by day. Many teams keep both on one pinned page, the charter above the norms; the team norms guide covers the lower half.

Where should a team charter be kept?

Where the team already looks every day: pinned in the team's channel, as a note members can read on a phone without asking anyone, not as a slide deck in a shared drive. In Teams, Slack, Google Workspace and WhatsApp the page lives in the channel, canvas, Doc or group chat in the language it was written, and a member who reads another language reads a per-reader translation or a copy. InterMIND keeps the note, the chat and every meeting's recap in one channel, read by each member in their own language, next to those tools rather than instead of them.

Sources: Microsoft — Take meeting notes in Microsoft Teams; Microsoft — Translate a message in Microsoft Teams; Google Chat — Use Automatic Translation in Chat; Google Meet — "Take notes for me" in Google Meet; Slack — Pricing; Slack — Customize data retention in Slack; Slack — Export your workspace data; Slack — Guide to AI features in Slack; Slack — Meeting agenda template (canvas); WhatsApp — How to export your chat history; WhatsApp — Privacy policy; WhatsApp blog — Introducing message translations. The Teams meeting-notes page, the Slack canvas template page and the Google "Take notes for me" page checked October 2026; the Teams message-translation page, the Slack pricing, retention, export and AI-features pages, the Google Chat translation page and the WhatsApp pages checked August 2026. Vendors change plans, features and language lists over time; check their pages for the current state. The example team is illustrative.