What is a team charter, and how does a leadership team write one that sticks?

A team charter is a short, written agreement a team makes about how they'll work together: how they'll communicate, how they'll make decisions, how they'll disagree, and how they'll hold each other to account. It's specific to that team, written by that team, and it only works if they actually use it.

I've helped a lot of leadership teams write their charter, and I love this piece of work. It's often the moment a group of capable individuals starts to feel like one team. But I've also seen plenty of charters end up in a drawer. So here's what goes into one that lasts.

How is a team charter different from company values?

This one trips people up, so it's worth getting clear on.

Your organisation's values and behaviours are universal. They're the standard for everyone, from the newest starter to the boardroom, and they describe how things are done across the whole business.

A team charter is much more local. It's one team's rules of engagement at their own table. Things like what our meetings are for, what "no surprises" means for us, how we disagree and then commit, who owns what, and what we say when something's gone sideways between us.

The two are connected. A good charter is really that team's way of living the organisation's values day to day. But they're different documents, with a different scope and a different audience, and mixing them up usually means you end up with neither.

What goes in a team charter?

Keep it short. One page is plenty. If it's longer than that, nobody will reach for it in the middle of a busy week.

Most good charters cover the same few areas: why the team exists, how it communicates, how it decides, how it disagrees and how it holds each other to account. The strongest ones also name what's out of bounds, and how the team repairs things when it goes wrong between two people.

The magic is in turning each commitment into behaviour you could actually see. "We respect each other" is lovely, but nobody can tell whether it's happening. "We don't interrupt, and we raise concerns in the meeting, not after it" is something the whole team can notice and call out.

Why does the team have to write it themselves?

Because people keep promises they've made themselves. A charter handed to a team rarely survives its first hard week.

You can download a template, or ask an AI to generate a charter in about thirty seconds, and it'll probably read well. But nobody will feel any ownership of it, and the first time it's tested, it'll fold.

The value of a charter is the conversation that creates it. When a team sits together and works out, honestly, what's getting in their way and what they're prepared to commit to, the words on the page carry the weight of that conversation. That's why it sticks.

This is also where having someone skilled in the room helps. The hardest part is getting people to say the thing they've been avoiding, and doing it in a way that brings the team closer rather than splitting it.

How do you keep a team charter alive?

This is where most charters live or die, and it's the part I wish more teams planned for.

One leadership team I worked with did this beautifully, and the ideas were all theirs. Once the charter was finished, the director gave everyone one last chance to change anything, then locked it in. He put it on the agenda of their regular leadership meeting so it became part of normal business. He put it in writing that the team should expect to challenge each other when behaviour didn't match what they'd agreed. And they all signed it together, then framed the signed copy as a reminder of who they are and what they stand for.

A few habits I'd suggest to any team:

• Put it on the agenda. Even five minutes a month. Which commitment are we doing well on, and which one is slipping?
• Use it in the moment. When a meeting goes off track, point to the charter. It takes the heat out of it, because you're pointing to something everyone agreed to.
• Review it properly every six months or so. Teams change and priorities shift. A charter you never revisit slowly turns into decoration.
• Bring new people into it. When someone joins, walk them through the charter, and let them add to it. Otherwise it slowly becomes "the old team's charter".

Where do you start?

Start with an honest conversation about how your team is actually working right now. If you want help running it, that's a big part of what I do. Most of my team alignment sessions finish with a charter the team wrote themselves and will actually use. If that sounds like your team, send me a message.

If you'd rather run it yourself, my Team Charter Framework is how I run a charter session. The leader brings a draft purpose and vision, and the team shapes the behaviours and ways of working. It's on Leaders Impact, along with some free tools to get you started.