Team charter: how your team works, on one page everyone agreed to

Most teams settle how they work in week one, out loud, and then spend months re-arguing it. A team charter puts that agreement on paper so the argument happens once.

Short answer: A team charter is a short document a team writes together that records why the team exists, who is on it and in what role, how decisions get made, and how people communicate. A good team charter fits on one page, takes about an hour to write as a group, and ends the recurring debates about ownership and ways of working.

What is a team charter?

A team charter is the team's written agreement about purpose and ways of working, made at the start and kept current. It answers the questions that otherwise come back every few weeks: what are we here to do, who decides, what does "done" mean, and where do we talk about what.

It is not a project plan. A plan says what happens next sprint; a charter says how the team behaves in every sprint. It is also not an org chart: reporting lines live in HR tools, while the charter records working roles the team actually uses day to day.

What goes in a team charter?

Six sections cover almost every team. Keep each one to a few lines.

• Purpose. One or two sentences on why the team exists and what it owns. If you cannot write this, the charter meeting just found its real topic.
• Members and roles. Who is on the team and what each person is accountable for, in working terms rather than job titles.
• Success measures. Two or three outcomes the team will be judged on, specific enough that an outsider could check them.
• Ways of working. Meeting rhythm, how work gets picked up, and what "done" means for this team.
• Decision rules. Which decisions one person can take alone, which need the group, and who breaks a tie.
• Communication agreements. Which channel is for what, expected response times, and when it is fine to be unreachable.

How do you write a team charter?

Write it with the team in one working session, not alone at a desk. A charter nobody helped write is a charter nobody follows.

1. Block 60 to 90 minutes with the whole team, and put the six sections up where everyone can see them.
2. Start with purpose. Let each person write their version first, then merge. Disagreement here is the most useful part of the meeting.
3. Fill in roles and success measures next. For roles, a separate RACI chart helps when one activity has many hands on it.
4. Agree decision rules and communication last. These go fast once purpose and roles are settled.
5. Read the whole page out loud, fix what sounds wrong, and set a review date three months out.

How is a team charter different from a project charter?

A team charter describes a standing team; a project charter describes one piece of work with an end date. Teams often need both, and they stay short because each answers different questions.

Three documents, three jobs

|Document|Describes|Ends when|

|---|---|---|

|Team charter|How a standing team works|The team changes or disbands|

|Project charter|Scope, budget and timeline of one project|The project ships|

|RACI chart|Who does what on specific activities|The activities change|

How do you keep a team charter alive?

A charter stays alive by being used at specific moments, not by being re-read on a schedule. Three triggers do most of the work: a new person joins and reads it in their first week, a disagreement about ownership gets settled by pointing at it, and a quarterly review asks which line no longer matches reality. If a line is ignored three times in a row, change the line or change the behaviour; a charter that contradicts practice is worse than none.

Where should the charter live?

Keep the charter where the team already works, so it gets pointed at instead of forgotten. In SketchMind, an AI whiteboard, you can describe your team in the Create with AI dialog, pick Frames, and get 4–8 editable frames on your board in about 40 seconds: one frame per charter section, ready to edit in the session itself. The board is shared by link with unlimited viewers on every plan, so the charter is one click away from any discussion it needs to settle. Comments with @mentions sit on the board and can be resolved, which suits the quarterly review: each proposed change becomes a comment, and the ones the team accepts get edited in. The Free plan includes 5 AI boards as a one-time allowance with 2 editors per board, which is enough to try the charter session on a real team.

Last updated: October 19, 2026. Checked against the current SketchMind app.

How long should a team charter be?

One page. Six sections of a few lines each is enough; anything longer stops being read and starts being archived.

Who writes the team charter?

The whole team, in one working session. One person can tidy the wording afterwards, but the content should come from the group, or it will not be followed.

How often should you update a team charter?

Review it quarterly in about 15 minutes, and immediately when membership or the team's scope changes. Change any line that no longer matches how the team actually works.

Is a team charter the same as a team contract?

They overlap. A team contract usually stresses the commitments members make to each other; a charter adds purpose and success measures on top of those agreements.

Do small teams need a team charter?

From about three people it starts paying off. A pair can usually keep it to two sections: decision rules and communication agreements.