Team Charter Template: How to Get Your Team on the Same Page
Quick Answer
A team charter is a short document that spells out why a team exists, what it's responsible for, its goals, who does what, how the team communicates and makes decisions, and how success is measured. Write it together with the team in a single working session, keep it to one or two pages, store it where everyone can find it and review it every quarter or whenever the team changes.
Most team problems aren't about effort. They're about assumptions. One person thinks the team owns customer follow-ups; another thinks sales does. One expects replies within an hour; another checks messages once a day. Nobody is wrong, exactly. They just never agreed.
A team charter is a simple fix. It's a short document, written together, that captures what the team is for, what it owns, how it works and how it measures success. This guide explains what to include, how to write one in about an hour, a free template and examples you can borrow.
What Is a Team Charter?
A team charter is a one- or two-page agreement that defines a team's purpose, responsibilities, goals, roles and ways of working. It can be written for a permanent department, such as customer service or operations, or for a temporary project team.
Think of it as the team's operating manual. A new team member can read it in five minutes and know what the team does, who to go to for what and how things get done.
| Team charter | Job description | Project brief | |
|---|---|---|---|
| Covers | The whole team | One role | One project |
| Focus | Purpose, ownership, ways of working | Duties and qualifications | Scope, timeline, deliverables |
| Written by | The team together | Manager or HR | Project owner |
| Lifespan | Ongoing, reviewed quarterly | Until the role changes | Until the project ends |
Related tools: the job description template for individual roles, and the project brief template for single projects.
Why Teams Need a Charter
- Shared purpose. Everyone can explain why the team exists in one sentence.
- Clear ownership. Fewer tasks fall between teams or get done twice.
- Fewer conflicts. Expectations about communication and decisions are agreed up front.
- Faster onboarding. New hires learn how the team works on day one.
- Better alignment. Team goals connect clearly to company goals. See how to share company goals with employees.
- A reference point. When disagreements come up, the team can go back to what it agreed.
What to Include in a Team Charter
| Section | Question it answers | Example |
|---|---|---|
| Purpose | Why does this team exist? | Keep every customer job on schedule from booking to completion |
| Scope | What do we own, and what don't we? | We own scheduling and dispatch; sales owns quotes |
| Goals | What are we trying to achieve this quarter or year? | 95% of jobs completed on the scheduled day |
| Roles | Who does what? | Dispatcher: daily schedule; Lead tech: job quality |
| Communication | How and how fast do we communicate? | Urgent: call. Everything else: team chat, reply same day |
| Meetings | When do we meet, and why? | Daily 10-minute huddle; weekly 30-minute review |
| Decisions | Who decides what, and how? | Dispatcher decides daily changes; manager decides overtime |
| Measures | How do we know we're succeeding? | On-time rate, callbacks, customer rating |
| Norms | How do we treat each other? | Raise problems early; no blame; help when someone is behind |
| Escalation | Where do problems go when we can't solve them? | Team lead, then operations manager |
You don't need every section. A small team might use five of them. A cross-department project team might need all ten.
Free Team Charter Template
[Team Name] Team Charter
Last updated: [date] | Team lead: [name]
1. Purpose
We exist to [what the team does] so that [who benefits and how].
2. Scope
We own: [list]
We don't own (and who does): [list]
3. Goals
• [Goal with number and date]
• [Goal with number and date]
Connects to company goal: [goal]
4. Roles
• [Name/role]: [responsibilities]
• [Name/role]: [responsibilities]
5. How we communicate
Urgent: [channel, response time]
Day to day: [channel, response time]
Updates: [where status lives]
6. Meetings
• [Meeting]: [when, how long, purpose]
7. How we make decisions
• [Type of decision]: [who decides]
8. How we measure success
• [Measure]: [target]
9. Team norms
• [norm]
• [norm]
10. When we're stuck
Escalate to: [name/role]
Agreed by: [team member names]
How to Write a Team Charter in One Hour
The best charters are written with the team, not handed to them. A single focused session usually does it:
| Time | Activity |
|---|---|
| 10 min | Purpose: each person writes one sentence on why the team exists; combine into one |
| 10 min | Scope: list what the team owns and what it doesn't; flag gray areas |
| 10 min | Goals and measures: agree on two or three goals and how to track them |
| 10 min | Roles: confirm who owns what |
| 10 min | Communication, meetings and decisions: agree on channels, response times and who decides |
| 10 min | Norms: each person suggests one; keep the ones everyone supports |
Have one person type as you go. Don't aim for perfect wording in the room. Send a clean draft afterward and give everyone a day to suggest changes before you finalize it.
Questions to Ask in the Session
- If our team disappeared tomorrow, what would break first?
- What do people outside our team most often ask us for?
- What do we keep doing that another team should own?
- What causes the most friction on our team right now?
- How do we want to handle disagreements?
- What would make this team great to work on?
Team Charter Examples
Customer Service Team
Purpose: Make every customer feel heard and get a clear answer within one business day.
Scope: We own customer emails, calls and complaints. Billing questions go to the office manager.
Goals: Reply to 100% of requests within one business day; customer rating of 4.5 or higher.
Communication: Team chat for questions; call the lead for escalations.
Decisions: Agents can approve credits up to $50; the lead approves more.
Norms: Never leave a customer without a next step. Ask for help early.
Field Service Crew
Purpose: Complete every job safely, on schedule and right the first time.
Scope: We own job completion and on-site quality. Scheduling belongs to dispatch.
Goals: 95% of jobs completed on the scheduled day; callbacks under 3%.
Meetings: 10-minute huddle at 7:00 AM. See the daily huddle template.
Norms: Safety first, always. Leave every site cleaner than we found it. Write a handoff note for any open item.
Cross-Department Project Team
Purpose: Launch online booking by March 31.
Scope: We own the booking tool setup, testing and staff training. Marketing owns the announcement.
Roles: Project owner: operations manager. Tech setup: office manager. Training: lead tech.
Decisions: Project owner decides scope changes; owner approves budget over $500.
Meetings: 30-minute check-in every Tuesday until launch.
Leadership Team
Purpose: Set direction, remove obstacles and make sure every team has what it needs to hit our goals.
Goals: Hit our three company goals for the year; keep first-year turnover under 20%.
Meetings: Weekly 90-minute leadership meeting. See the Level 10 meeting template.
Norms: Debate openly in the room, then support the decision outside it.
Team Norms Worth Considering
- We raise problems early, even when the news is bad.
- We reply to teammates within [time] during work hours.
- We start and end meetings on time.
- We disagree respectfully and in private, then commit to the decision.
- We give credit publicly and feedback privately.
- We keep task status up to date so no one has to ask.
- We ask for help before we fall behind.
- We assume good intentions.
Pick three to five. A long list of norms is hard to remember and harder to live by.
Using the Charter Day to Day
- Store it where everyone can find it, such as a shared folder, the team channel or your project system.
- Use it in onboarding. Walk new team members through it in their first week.
- Refer to it in disagreements. "What did we agree in our charter?" settles a lot.
- Connect it to roles. A RASCI chart can add detail for complex work.
- Review it quarterly, and any time the team changes significantly.
Common Team Charter Mistakes
- Writing it alone. A charter the team didn't help write is a memo, not an agreement.
- Making it too long. If it's more than two pages, people won't read it.
- Vague goals. "Do great work" isn't a goal. Add numbers and dates.
- Skipping scope. The "what we don't own" list prevents the most friction.
- Writing it and forgetting it. Charters that aren't reviewed go stale.
- No decision rules. Unclear decision rights cause more conflict than almost anything else.
Team Charter for a New Team
A charter is especially useful when a team is brand new, whether you've just hired your first few employees, split one team into two or started a project with people from different departments. New teams don't have habits yet, so the charter becomes the habit. For a new team:
- Write the charter in the first two weeks, before patterns set in.
- Focus first on purpose, scope and roles; norms can come a little later once people know each other.
- Plan a review after 30 days, since early assumptions often need adjusting.
- Include how new members will be onboarded as the team grows.
Team Charter for a Team That's Struggling
If a team is already in conflict, a charter session can reset expectations, but it needs care. Start by acknowledging that things haven't been working, without blaming individuals. Focus the conversation on the future: "How do we want to work together from here?" The scope and decision sections often matter most, because many conflicts come from unclear ownership or unclear authority. If tensions run high, a neutral facilitator from outside the team can help.
"I know the last few months have been frustrating. A lot of it comes from not being clear about who owns what and how we make decisions. Let's spend an hour agreeing on that, so we can stop stepping on each other and get back to doing good work."
Connecting the Charter to Company Goals
A team charter should show how the team's work moves the business forward. In the goals section, list the company goal each team goal supports. For example, if a company goal is "grow repeat customers by 15%," a customer service team goal might be "follow up with every customer within a week of their job." This link helps people see why their work matters and helps leaders spot teams whose goals don't connect to anything.
| Company goal | Team | Team goal in the charter |
|---|---|---|
| Grow repeat customers 15% | Customer service | Follow up with every customer within 7 days of their job |
| Grow repeat customers 15% | Field crew | Callbacks under 3% |
| Cut job time to 4 days | Dispatch | Schedule 90% of jobs within 2 days of booking |
| Keep first-year turnover under 20% | Managers | Weekly one-on-ones with every new hire for 90 days |
Signs Your Team Charter Is Working
- Fewer arguments about who owns what.
- New hires get up to speed faster.
- People refer to the charter on their own.
- Decisions get made at the right level instead of everything going to the leader.
- Team goals are tracked and discussed regularly.
A Quick Version for Very Small Teams
If you have three or four people, you can write a charter in 20 minutes with just five lines:
We exist to: [purpose]
We own: [scope]
This quarter we're aiming for: [one or two goals]
We talk: [channels and response times]
We agree to: [two or three norms]
Post it somewhere visible and look at it together once a month. Even this short version prevents many of the misunderstandings that slow small teams down, and it's easy to expand as the team grows.
Updating the Charter as the Team Changes
Teams change: people join and leave, goals shift and responsibilities move between departments. Each time something significant changes, take 15 minutes at a team meeting to walk through the charter and ask what no longer fits. Update the "last updated" date so everyone knows they're looking at the current version. A charter that keeps up with the team stays useful for years.
Put Your Team Charter Into Practice With Updoot
Updoot's project management makes the roles in your charter real: every task has a clear owner, due date and status, organized by priority. Meeting agendas keep the meetings you agreed on short and focused, with action items assigned to owners, and the KPI dashboard tracks the measures in your charter in real time, so the whole team can see how it's doing.