Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Free Quote

How to Write a Team Charter: Template, Examples and a Workshop Agenda

A team charter is a one-page agreement about how a team works: what it is for, who decides what, how people communicate, and what happens when things go wrong. Most teams do not have one. The ones that do often have a document written by the manager in an afternoon, circulated once and never opened again.

This guide shows how to write a charter that a team actually uses. It gives you a seven-section template with example wording for each section, a 90-minute workshop agenda that produces the first draft with the whole team in the room, and the review rhythm that keeps it alive. It is written for team leads, new managers, HR partners and anyone forming a new team, merging two teams or resetting one after a hard year.

Key takeaways

A team charter works when the team writes it together, keeps it to one page and reviews it on a schedule.

  • Seven sections: purpose, scope, roles and decisions, ways of working, communication, conflict and review.
  • Write it in a 90-minute workshop with everyone present, not by the manager alone.
  • Use plain sentences a new joiner could follow on day one.
  • Put the review date in the calendar before the workshop ends.
  • A facilitated session produces a better charter than a manager-led one, because the manager gets to be a participant.
Plan a charter workshopWe respond in 15 minutes.

What a team charter is, and what it is not

A charter is an agreement, not a policy. It describes how this team has decided to work, in words the team chose. It is short enough to read in five minutes and specific enough that a new joiner could follow it on day one.

It is not a project plan, a job description, a list of company values or a mission statement. Those documents exist for other reasons. A charter sits between them: it takes the company's values and the team's goals as given, and answers the practical question of how the people in this team will work with each other.

A charter is most useful at four moments: when a team is formed, when two teams merge, when a team gets a new leader, and when a team has had a hard period and needs a reset. The team building after a merger guide covers the merger case, the team building for new managers guide covers the new-leader case, and the new year team reset guide covers the reset.

The seven sections of a team charter that gets used

Each section below has a purpose, a guide to length and an example of wording. The examples are illustrative; the team's own words will be better.

1. Purpose

One or two sentences on why the team exists and who it serves. Not a mission statement; a plain description. Example: "We run customer onboarding for mid-market accounts. Our job is to get a new customer live and confident within thirty days of signature."

2. Scope and boundaries

What the team does and, more usefully, what it does not do. Three to five lines. Example: "We own onboarding from signature to first value. We do not own renewals, which belong to account management, or product bugs found during onboarding, which we log and hand to engineering with a named contact."

3. Roles and decision rights

Who does what, and who decides what. The decision part matters more than the role part. Example: "Priya leads the team and decides scope changes and staffing. Each onboarding has one named owner who decides the plan and the schedule with the customer. Any team member can pause an onboarding for a quality issue; only the owner can restart it." The team operating model guide covers decision rights and handoffs across teams in more depth.

4. Ways of working

The practical rhythm: meetings, working hours, where work is tracked, how priorities are set. Five to eight lines. Example: "Stand-up at 9:15 daily, fifteen minutes, cameras on. Planning on Monday, retrospective every second Friday. Core hours 10 to 3 in the team's main time zone; outside those, people set their own schedule. All work is tracked on the board; if it is not on the board, it is not a commitment."

5. Communication norms

How the team talks: which channel for what, response expectations, how to flag urgency, how to disagree. Example: "Chat for quick questions, with no expectation of a reply within the hour. Email for anything a customer or another team needs to find later. A call for anything that has gone back and forth three times. 'Urgent' means a customer is blocked today; say it in the message and name the person you need."

6. Conflict and feedback

What happens when people disagree, and how feedback is given. This is the section most charters skip and the one that pays off most. Example: "We disagree in the open and decide fast. If two people cannot agree, the owner decides and the team backs the decision for the sprint. Feedback is given in private within a week, and it describes the behaviour and its effect, not the person." The Clear and Productive Feedback module is a facilitated way to build this habit, and the conflict resolution activities guide covers practice formats.

7. Review

When the charter is reviewed and how it can change. Two lines. Example: "We review this charter at the first retrospective of each quarter. Anyone can propose a change at any time; changes need the whole team present."

Team charter template at a glance
SectionAnswersLengthCommon mistake
PurposeWhy the team exists and who it serves1 to 2 sentencesWriting a mission statement
Scope and boundariesWhat we do and do not do3 to 5 linesOmitting the "do not" list
Roles and decision rightsWho does what, who decides what4 to 8 linesListing titles without decisions
Ways of workingMeetings, hours, tracking, priorities5 to 8 linesCopying the company handbook
Communication normsWhich channel for what, urgency, disagreement4 to 6 lines"We communicate openly"
Conflict and feedbackHow we disagree and how feedback works3 to 5 linesSkipping it
ReviewWhen and how the charter changes2 linesNever setting a date

Team charter examples for three common situations

These are illustrative examples, written for this guide, not FullTilt client documents.

A newly formed product team of eight. Purpose: ship the mobile app's payments feature by the end of Q2. Scope: design, build and test; not pricing, which belongs to the commercial team. Decisions: the product lead decides scope; the tech lead decides architecture; the designer decides interface within the agreed scope; anyone can raise a risk at stand-up and it goes on the board the same day. Ways of working: stand-up at 9:30, demo every Friday, no meetings on Wednesday mornings. Communication: chat for the team, a weekly written update for stakeholders. Conflict: disagreements are raised at the retrospective, not in chat. Review: end of the first month, then quarterly.

A merged customer support team of twenty after an acquisition. Purpose: one support experience for both products. Scope: tier-one and tier-two support; escalations go to the named engineering contact for each product. Decisions: the two former team leads co-lead for one quarter, with one named as the decision-maker for process and the other for staffing; the whole team votes on the shared tooling choice. Ways of working: both teams keep their shift patterns for a quarter; one combined weekly meeting. Communication: a single channel from day one, old channels archived. Conflict: a "two ways of doing it" list is kept in the open, and one way is chosen each week. Review: monthly for the first quarter.

A leadership team of six resetting after a hard year. Purpose: run the company's operating plan and model the behaviour it asks of others. Scope: company-level decisions; functional decisions stay with each leader. Decisions: a decision is made in the room, recorded in one line, and not reopened without new information. Ways of working: a weekly ninety-minute meeting with a written agenda sent the day before; one monthly half day out of the office. Communication: no decisions by email; concerns raised with the person first, then the group. Conflict: a disagreement is stated as a question to the group within a week. Review: quarterly, at the off-site. The executive team building guide covers how an off-site produces a working agreement like this.

A 90-minute workshop agenda to write the charter together

A charter written by the manager and circulated is a policy. A charter written by the team in a room is an agreement. The workshop below produces a first draft in ninety minutes with everyone present, in person where possible.

90-minute team charter workshop
TimeStepHow it runsOutput
0 to 10 minWhy we are doing thisThe lead explains the four moments a charter helps and which one this is; the facilitator explains the seven sectionsShared understanding
10 to 25 minPurpose and scopePairs draft one sentence of purpose and three "we do not" lines on cards; the group merges themSections 1 and 2
25 to 45 minRoles and decisionsOn a wall: a column per role, a card per decision; the team moves cards until every decision has one ownerSection 3
45 to 60 minWays of working and communicationEach person writes one thing that works and one that wastes time; the group turns the top items into rulesSections 4 and 5
60 to 75 minConflict and feedbackThe facilitator reads two example disagreements; the team writes how it wants each handledSection 6
75 to 85 minRead-throughOne person reads the whole draft aloud; anyone can flag a line that a new joiner would not understandPlain-language draft
85 to 90 minReview date and ownerDate in the calendar; one person owns the clean version by the end of the weekSection 7 and a named owner

Three rules make the workshop work. First, the manager participates and does not facilitate; a facilitator, from HR or outside the team, holds the pen. Second, every section is drafted by the people doing the work, not by the loudest voice. Third, the draft is read aloud before anyone leaves; the sentences that sound wrong when spoken are the ones that will be ignored.

For a team that has never done structured work like this, pairing the workshop with a short activity first changes the room. Thirty minutes of a build challenge or a problem-solving task, followed by a debrief on who decided what, gives the roles-and-decisions section a shared reference point. The team building workshops guide covers skills-based formats, and the half-day team building guide shows how an activity and a working session fit into one morning.

Want the workshop facilitated, so the manager can take part?

FullTilt facilitates team charter and working-agreement sessions for corporate teams, with an activity, a debrief and the written agreement produced in the room. Share your team size, situation and location.

Plan a charter workshopWe respond in 15 minutes.

Keeping the charter alive after the workshop

Most charters die in the week after they are written. Five habits keep them alive.

Clean it up within a week. The named owner turns the cards and notes into one page, in the team's words, and sends it to everyone. Anything that needs explaining gets rewritten.

Put it where the work is. Pinned in the team channel, on the first page of the team's board, printed in the room. Not in a folder.

Use it in onboarding. Every new joiner reads the charter on day one and asks three questions about it. The questions usually reveal the lines that need fixing. The team building for new hires guide covers the rest of the first ninety days.

Reference it when it matters. When a decision is reopened, someone points to section three. When chat turns into a three-day argument, someone points to section five. The charter earns its place by being used, not by existing.

Review it on the date. Quarterly at a retrospective, with three questions: what in here did we actually do, what did we ignore and why, and what has changed. Change the document, not the date. The employee engagement survey action plan guide shows how to turn team feedback into specific changes, and the HR team development operating plan shows where team-level agreements sit in a yearly plan.

Charter versus working agreement versus team norms

The three terms are used loosely and often mean the same thing. If a distinction is useful: a team charter covers purpose and scope as well as behaviour, and is the document for a new or re-formed team. A working agreement covers behaviour only, and is common in agile teams that already have a clear purpose. Team norms are the informal rules a team actually follows, written or not. The point of a charter is to make the norms explicit and chosen.

Whichever word the team uses, the test is the same: could a new joiner read it in five minutes and know how to work here tomorrow. The effective trust building activities guide covers the trust that makes a written agreement hold, and the why cross-functional teams fail guide covers the handoff problems a charter's scope section is meant to prevent.

When a facilitated session produces a better charter

A team can write its own charter with the agenda above. There are four situations where a facilitated session produces a better result.

The manager needs to participate. A manager who facilitates cannot also contribute, and the team watches the manager's reaction instead of saying what it thinks.

Two teams are merging. A neutral facilitator stops the session becoming one team's rules applied to the other.

The team has had a hard year. The conflict section needs someone in the room who is not part of the conflict.

The team has never done this. An activity before the workshop, with a debrief, gives people a shared experience to build the agreement on.

FullTilt facilitates working-agreement sessions as part of team development training, often paired with a short activity and a debrief, in offices, hotels and venues across the US and Canada. The Cross-Boundary Communication module suits merged or cross-functional teams; the Mission, Vision, Values module suits leadership teams writing the purpose section; the 8 Productive Practices module suits teams writing the ways-of-working section. Total event pricing starts at $3,000; the per-person figure varies with headcount, venue and format, so confirm it in your quote. The team building cost guide explains what drives the number.

Hypothetical planning example, not a FullTilt client case, delivered program or quote: a new director inheriting a 14-person team from two former managers books a half-day facilitated session in the office. The morning opens with a 40-minute build challenge and a debrief on who decided what, followed by the 90-minute charter workshop with the director as a participant. The facilitator holds the pen, the team drafts all seven sections, the clean version is pinned in the team channel within the week and the first quarterly review is in the calendar before the session ends.

Frequently asked questions

What is a team charter?

A team charter is a short written agreement, usually one page, that states a team's purpose, scope, roles and decision rights, ways of working, communication norms, how it handles disagreement and when it reviews the agreement. It is written by the team, in its own words, and used as a reference when decisions are reopened or communication breaks down.

What should a team charter include?

Seven sections: purpose, scope and boundaries, roles and decision rights, ways of working, communication norms, conflict and feedback, and a review date. The decision-rights and conflict sections are the ones most charters skip and the ones that pay off most.

How long should a team charter be?

One page. If a new joiner cannot read it in five minutes and know how to work with the team tomorrow, it is too long. Each section is between two and eight lines of plain sentences.

How do you write a team charter with the team?

Run a 90-minute workshop with everyone present: pairs draft purpose and scope, the team maps decisions to owners on a wall, each person names one thing that works and one that wastes time, the team writes how it wants two example disagreements handled, and one person reads the draft aloud before the review date is set.

Who should write the team charter?

The whole team, in a workshop, with the manager participating rather than facilitating. A charter written by the manager alone and circulated is a policy, not an agreement, and it is usually ignored.

How often should a team charter be reviewed?

Quarterly, at a retrospective, with three questions: what did we actually do, what did we ignore and why, and what has changed. Review it sooner when the team changes leader, merges with another team or takes on a new scope.

What is the difference between a team charter and a working agreement?

A charter covers purpose and scope as well as behaviour, and suits a new or re-formed team. A working agreement covers behaviour only and is common in agile teams that already have a clear purpose. Both make the team's norms explicit and chosen.

Write the charter in a room, with the manager at the table

Share your team size, situation and location. FullTilt will send a plan for a facilitated charter session, with an activity, a debrief and the written agreement produced on the day, in your office or at a venue.

Plan a charter workshopWe respond in 15 minutes.

‍