Team Charter Template
Why the team exists, who owns what, and how decisions get made.
Details
team charter templateUploads
Your logo
A photo or picture
Goes on this page only. Drag it anywhere and pull its corner to resize it.
Your signature
Draw it with a finger, a mouse or a trackpad, and it goes on the page like a picture.
Pictures and signatures stay on this device. Nothing is uploaded to a server.
Red highlights mark what is still blank. Click anything on the page to change it. Your draft is kept on this device as you work.
1. Why this team exists
[in one or two sentences — if it takes a paragraph, the team has two purposes]
2. Who is in it and what they own
| Name | Role | What they own |
|---|---|---|
| [add one member per line] |
3. How we work
[add one working agreement per line]
4. How decisions get made
[who decides what, and what goes upward]
5. Meetings
| Meeting | When |
|---|---|
| [add one meeting per line] |
6. What good looks like
[add one measure per line]
What is a Team Charter?
A team charter is a one-page statement of why a team exists, what it is responsible for, who decides what, and how the group will work together. It matters most when a team is new or has just been reorganised, because that is when everyone is operating on a private and slightly different understanding of the same brief. Writing it down surfaces the differences while they are still cheap to settle.
New teams at kick-off, project teams pulled from several departments, committees and working groups, and long-standing teams that have drifted after a reorganisation or a change of manager. Agile teams write one at formation and revisit it in retrospectives. Volunteer and community groups use them heavily, because there is no employment relationship to fall back on when someone stops turning up. Cross-functional teams get the most from it, since their members answer to different managers with different priorities and deadlines.
A charter sets expectations; it does not override contracts or law. Working hours, rest breaks, on-call and overtime are set by employment legislation and by any collective or enterprise agreement covering your staff — working time rules in the UK and EU, the Fair Labor Standards Act in the US, modern awards in Australia, state shops and establishments acts in India. In some countries, changes to working arrangements require consultation with employee representatives before they take effect. Where a charter touches hours or availability, check it against the contract and the applicable law first.
A charter is not a job description and not a performance standard. It says how the team works, not what any individual is measured on, and it should not be quoted at someone in a disciplinary conversation. It does not settle disputes either: it can say who has the final call on a technical decision, but it will not make a disagreement between two determined people evaporate. And it binds nobody outside the team — a charter cannot commit another department to a response time it never agreed to.
What to put in a Team Charter
These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.
| Field | What goes in it |
|---|---|
| Issuing organisation | For example: Maple Grove Homeowners Association |
| Organisation address | For example: 1420 Kinnear Road, Columbus, OH 43212 |
| Project name | For example: Barton Road trade counter fit-out |
| Why this team exists | For example: To keep trade orders moving from phone to van within four hours, and to own everything… |
| Members and roles | One per line: Name | Role | What they own |
| How we work | One per line |
| How decisions get made | For example: The team lead decides on priority and sequencing. Anything that changes cost, headcount… |
| Meetings | One per line: Meeting | When |
| What good looks like in six months | One per line |
How to write a Team Charter
State the purpose in two sentences
Why does this team exist, and what would be missing if it stopped? Write it plainly: 'We keep the payments platform running and hold the on-call rota for it.' Avoid mission language borrowed from the company website. The test is whether a new joiner could read the sentence and correctly guess what lands in the team's queue on a normal Tuesday.
Draw the boundary of the work
List what the team owns, and immediately below it list what it does not. The second list is the one that saves arguments: 'We do not own customer refunds; those go to support.' Where a boundary is genuinely shared, name the other team and the person on each side who handles the handover. Vague scope is the commonest cause of a permanently overloaded team.
Say how decisions actually get made
Different decisions want different rules. Technical calls might rest with a named engineer; spending above a limit goes to the manager; anything affecting another team needs their sign-off. Write which is which, including what happens when the group cannot agree — someone decides, and the charter should say who. 'By consensus' with no tiebreak is how a team stalls for a fortnight.
Agree the working norms you will keep
Meeting cadence, core hours across time zones, expected response time on messages, how leave is covered, where documents live. Keep it to the handful you will actually enforce. A charter listing fifteen norms is a wish list; one listing five that everybody follows changes daily behaviour. Where anything touches hours or availability, check it against contracts and local employment rules first.
Sign it, date it, revisit it
Have everyone named on the charter confirm it, and put the date on the page. Then set a review — at a quarter boundary, after a retrospective, or whenever a member joins or leaves. A charter agreed at kick-off and never reopened becomes a description of a team that no longer exists, and people stop citing it in the arguments it was written to settle.
Common mistakes
- Writing a purpose statement so general it would fit any team in the company, which leaves the team's actual remit undefined and open to constant negotiation.
- Listing what the team does without listing what it does not, so every unclaimed piece of work drifts towards whoever is most obliging.
- Saying decisions are made by consensus without naming a tiebreaker, which lets one unresolved disagreement hold up work for weeks.
- Setting availability or response-time expectations that conflict with people's contracts or with working time rules, creating a problem for HR rather than solving one.
- Treating the charter as a launch document, so nobody revisits it when the remit changes and it becomes misleading exactly when it is most needed.
Frequently asked questions
What is the difference between a team charter and a project charter?
A project charter authorises a piece of work: it names the sponsor, the objective, the budget and the end date, and it stops existing when the project does. A team charter describes an ongoing group — purpose, scope, decision rights, working norms. A project team may have both: one saying what it has been asked to deliver, one saying how it will operate while delivering it.
Who should write the team charter?
The team, with the manager or lead facilitating rather than dictating. A charter handed down is read once and ignored; the value comes from the disagreements that surface while writing it. A practical approach is for the lead to draft purpose and scope, then work through decision rights and working norms with everyone in the room in a single session.
How long should a team charter be?
One page, two at most. The constraint is functional: a charter is meant to be re-read, quoted in a meeting and handed to a new joiner on day one, and none of that happens with a ten-page document. If a section needs more depth — an on-call rota, an escalation path — give it its own document and reference it.
Is a team charter legally binding?
It is an internal working agreement, not a contract, and it does not change anyone's terms of employment. Where a charter conflicts with a contract, a collective agreement or employment legislation, those take priority. If you want to change something touching hours, pay or availability, that is a contractual change and belongs with HR or an employment adviser rather than in a charter.
When should a team charter be reviewed?
At a fixed interval — a quarter is common — and immediately when the team's remit changes, when it gains or loses a member, or when the same argument comes up twice. That last trigger is the useful one: a recurring dispute almost always points at a decision right the charter never made explicit.
This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.