A team charter is a one-page agreement that says what a team is for, what it owns and does not own, how it measures success, how it works, and how it decides. Below are six team charter examples for teams of three to twenty people, each filled in with real numbers and written in the same five parts, so you can copy the shape of the one closest to yours.
The examples are illustrations, not templates to paste: the useful part of a charter is the arguments a team has while writing it. For the goals a charter points at, see how to set team goals; for the one-sentence purpose on its own, see mission statement examples →
What goes into a team charter
Purpose
One sentence: who the team serves and what changes for them. It is the line you use to say no.
What we own, and what we don’t
The boundary with the teams next to you. Most charters skip the second half, and it is the half that prevents the arguments.
How we know it’s working
One number to hold in a range, and this quarter’s goal. The range stays for a year; the goal changes every quarter.
Working agreements
Two or three rules about how the team works that someone would actually notice being broken.
How we decide
Who decides what, and who breaks a tie. Written down before the first disagreement, not during it.
The test for every line is the same: does it settle a question the team would otherwise argue about? “We value collaboration” settles nothing. “Nobody ships alone on a Friday afternoon” settles one argument for good.
Using a purpose sentence to say no, which is what a charter’s first line is for, is lesson 2 of our free course. lesson 2 of 17 in From Zero to Goals: The mission as a veto. Use one sentence to reject the wrong work, and write yours so it can. You make the calls inside one realistic company, run the exercise on your own goals, and the course ends with a 15 question exam (12 to pass) and a certificate worth putting on your profile.
Team charter example: a leadership team of a 22-person company
Choose the few things the company does this quarter, and make sure everything else waits.
We own priorities, budget, and hiring plans. We don’t own how any team hits its goals: that stays with the team.
Held: cash runway above 12 months. This quarter: grow recurring revenue from $95,000 to $120,000 a month by December 31.
No new company priority mid-quarter unless one is dropped the same day. Decisions are written up within 24 hours.
Consensus for priorities; the CEO decides if we have not agreed by the end of the meeting. Each function head decides inside their own budget.
Team charter example: a marketing team of three
Bring the sales team qualified conversations with companies that fit, at a cost we can repeat.
We own the website, content, paid channels, and the definition of a qualified lead (agreed with sales). We don’t own pricing or the product roadmap.
Held: cost per qualified lead under $150. This quarter: raise qualified leads from 35 to 55 a month by the end of Q4.
Nothing publishes without one other person reading it. Every campaign has an end date before it has a launch date.
The person who owns the channel decides inside it. Spending over $2,000 on something new needs the team lead’s yes.
Team charter example: a product and engineering team of six
Ship the changes that keep paying customers using the product every week, without breaking what already works.
We own the product, its reliability, and the release schedule. We don’t own which customers get promised a feature: that conversation comes to us first.
Held: uptime at 99.9% or better. This quarter: lift weekly active accounts from 52% to 65% of paying accounts by the end of Q1.
Nobody ships alone on a Friday afternoon. Every bug a customer reports gets a reply within one business day, even if the fix takes longer.
The product lead decides what gets built; the engineer doing the work decides how. Anything that touches billing gets a second engineer’s review.
Team charter example: a customer support team of four
Make every customer who asks for help get unstuck quickly, and make sure the same question gets asked less next month.
We own the inbox, the help center, and refunds up to $500. We don’t own bug fixes, but we own making sure each one is reported clearly.
Held: first reply within four business hours. This quarter: cut tickets about setup from 120 to 60 a month by March 31.
No ticket closes without the customer’s problem being solved or a clear next step. The five most common questions get a help article every month.
Whoever has the ticket decides within our own limits. Anything above a $500 refund or touching a contract goes to the team lead the same day.
Team charter example: a sales team of five
Turn qualified conversations into customers who stay, at a price that leaves the business healthy.
We own the pipeline, the forecast, and discounts up to 15%. We don’t own the product promise: nothing gets sold that the product team has not confirmed.
Held: pipeline coverage of 3x the quarter’s target. This quarter: grow new-business revenue from $40,000 to $60,000 by the end of Q3.
Every open deal has a dated next step. Lost deals get one line on why, so the reason is countable at the end of the quarter.
Reps decide inside the discount limit. Anything above 15% or any custom contract term needs the sales lead and finance to agree.
Team charter example: a ten-week launch team pulled from four functions
Launch the new plan for agencies by November 30 with the website, billing, and support ready on the same day.
We own the launch date, the checklist, and the go or no-go call. We don’t own anyone’s day job: each person keeps their own team’s goals.
Held: the checklist is updated every Friday. Goal: 25 agencies on the new plan within 30 days of launch.
One 30-minute meeting a week, nothing else recurring. A slipped date is said out loud the day it slips, not at the next meeting.
The launch owner makes the go or no-go call one week before the date. The charter expires the day after launch.
Where team charters go wrong, honestly
The usual failure is a charter that reads like a values poster: true, pleasant, and impossible to disagree with, which means it decides nothing. The second is a charter written once at an offsite and never opened again; the goal line is out of date by the next quarter, and from then on nobody trusts the rest. The third is specific to small companies: a charter for every team of two. Below about three people, the team’s goals and one clear sentence about what it owns do the same job.
Working agreements deserve the same discipline as company values. The test in core values examples applies here too: if a rule would never cost you anything to keep, it is not doing any work. And the number in the third part should be one you can actually read every week: see KPI examples for small teams →
Celorly does not store your whole charter, and does not need to. It holds the part that changes every quarter: the team’s goals, each with an owner, a baseline and a target, and a link to the company goal it feeds, so the third part of the charter is always current instead of a line written at an offsite. Free while it’s just you. See what Celorly does →
How to write a team charter in one session
Ninety minutes with the whole team is enough for a first version. Five steps, in this order:
Start with the boundary, not the purpose
Spend the first 20 minutes on what the team owns and, harder, what it does not. Invite the lead of the team next door for this part if the line is disputed.
Write the purpose last, in one sentence
Once the boundary is clear, the purpose usually writes itself. Test it: would this sentence help you turn down a reasonable request? If not, it is too broad.
Pick one number to hold and one goal for this quarter
The number has a range and no end date; the goal has a baseline, a target, and a deadline. Two lines, not a dashboard.
Write agreements from arguments you have actually had
Each working agreement should settle a disagreement the team has already had at least twice. Rules invented for problems you do not have are the ones nobody follows.
Put a review date on it
Revisit the goal line every quarter and the rest once a year, or when the team changes size. A charter with no review date is out of date within six months.
If the charter sits under a company plan, the goal line should name the company goal it feeds: see aligning team goals with company goals and, for twenty-four goals a whole team can share, team goal examples →
Team charter examples: quick answers
What is a team charter?+
A team charter is a one-page agreement that says what a team is for, what it owns and does not own, how it measures success, how it works, and how it makes decisions. It is written by the team, not handed to it.
What should a team charter include?+
Five parts are enough for a small team: purpose, scope (what you own and what you do not), how you know it is working, working agreements, and how you decide. Anything longer tends not to be read a second time.
How long should a team charter be?+
One page. If it needs a second page, it is usually doing the job of a process document or a job description, and those belong somewhere else.
What is the difference between a team charter and a mission statement?+
A mission statement is one sentence about why something exists. A team charter starts with that sentence and then adds what makes it usable day to day: the boundary with other teams, the numbers, the working rules, and who decides.
How often should a team charter be updated?+
Update the goal every quarter and review the rest once a year, or whenever the team grows, shrinks, or takes on a new area. A project team’s charter should simply expire when the project ends.
Who should write the team charter?+
The team, in one working session, with the team lead holding the pen. A charter written by one person and sent around for comments gets agreed to and then ignored.