In this guide
- 01Agree purpose and boundaries
- 02Name roles and decisions
- 03Rehearse a conflict
- 04Review in real work
A team charter is a working agreement about the team’s purpose, boundaries, responsibilities and way of coordinating. It should help members decide what to do when work conflicts or information is missing. A signed page that nobody uses is weak evidence of shared understanding.
Use a charter when a project brings together people with different roles, reporting lines or assumptions about collaboration. Begin with the task and its dependencies. A values exercise may support the discussion, but it cannot substitute for clear decision authority and usable commitments.
Understand the claim behind the tool
Mathieu and Rapp’s research on team charters and performance strategies examines their use in MBA teams working through a business simulation. The setting matters: it does not establish that every workplace team will perform better after completing a charter. Purpose, strategy and actual team practice remain important.
This guide offers an original practical agreement rather than a reproduction of the research instrument. It is suitable for ordinary project coordination, with additional organizational requirements handled through the relevant processes.
GOV.UK’s multidisciplinary team guidance emphasizes relevant skills and access to decisions. A team with varied job titles may still lack a necessary capability or depend on someone outside the room. Make those dependencies visible in the charter instead of assuming that collaboration can compensate for them.
Agree purpose, boundaries and decisions
Imagine a hypothetical team preparing a small exhibition. Design, installation, visitor support and scheduling colleagues contribute different knowledge. They share an opening date but may disagree about which decisions the team can make and which require approval from elsewhere.

Write a purpose that describes the result and the people it serves. Then list the important boundaries: scope, resources, required conditions and decisions outside the team’s authority. Avoid a purpose so broad that any activity can be justified under it.
Use change contracting if the sponsor and team disagree about the assignment. A charter should not quietly resolve a contested mandate by leaving it vague. Record the unresolved issue and who can decide it.
For the fictional exhibition, the team might choose how to prototype a visitor route while needing specialist approval for installation requirements. It could recommend a scope change without having authority to approve extra expenditure. Those are different decision rights, and the agreement should say so.
Make responsibilities and dependencies concrete
Name who owns the next action, who contributes expertise and who must make a decision. Avoid giving everyone joint responsibility for work that nobody can actually move. Equally, avoid treating a named owner as a reason to exclude other people’s necessary knowledge.
A useful charter can remain compact:
| Area | Agreement to make |
|---|---|
| Purpose | The result, audience and reason for the team |
| Scope | What is included, excluded and still unresolved |
| Decisions | What the team decides and what it escalates |
| Roles | Owners, contributors and external dependencies |
| Coordination | Shared records, contact routes and expected responses |
| Disagreement | How concerns are heard and unresolved issues decided |
| Capacity | Availability, competing work and replacement cover |
| Review | When the agreement is checked and changed |
The table is a planning aid, not a maturity score or a requirement to collect unnecessary personal information. Keep enough detail to operate the work, with specialist records linked rather than duplicated.
Ask each member what the agreement requires from another role. A designer may need timely installation advice; a visitor-support colleague may need a stable explanation of the experience. Record these as commitments with owners and conditions, rather than general requests to communicate more.
Agree how decisions and disagreement work
Choose a decision approach appropriate to the question. Some choices need a named accountable decision maker after consultation. Others may be delegated to the person doing the work. Consensus should not be implied when a sponsor retains the final choice.
Explain how a concern reaches the decision. Ask members to describe a risk, missing fact or conflicting obligation, and make time to examine it. If a decision proceeds despite an objection, preserve the material reasoning and explain what would trigger reconsideration.
Edmondson’s psychological-safety research concerns shared beliefs about interpersonal risk and their relationship with team learning. It does not mean that a statement in a charter creates safety. Members will judge the agreement partly by what happens when somebody actually raises a difficult issue.
Use feedback conversations for specific behaviour and systemic questions when the problem lies in patterns of interaction. Avoid using the charter as a weapon to declare one person uncollaborative before investigating the work.
Make the agreement work when priorities conflict
Rehearse a realistic difficulty. In the fictional exhibition, a late component change might conflict with installation capacity and visitor communication. Ask who can decide, who needs to be consulted and what happens if the decision maker is unavailable.

Walk through the agreement rather than asking whether everyone likes it. If the team cannot identify an escalation route or a receiving owner, revise the charter. A reassuring sentence about mutual respect does not resolve an authority gap.
AHRQ’s briefing guidance discusses roles, goals, resources and current operating issues in a healthcare team. Applied cautiously to a non-clinical project, a short working brief can keep those practical questions current. It is different from rereading the whole charter at every meeting.
At a brief, ask what has changed, which commitment is at risk and which decision is needed. Use the shared record to update owners and dependencies. Where work crosses team boundaries, agree an interface rather than assuming the charter binds people who never participated in it.
Keep the agreement alive without creating overhead
Review the charter when membership, scope, authority or working conditions change. Use the experience of a real decision or disagreement to identify an amendment. Avoid scheduling elaborate reviews solely to demonstrate that a document exists.
New members need more than access to the page. Explain why the agreements were made and walk through an ordinary task and an exception. Knowledge transfer helps make that handover practical. Invite the new person to question an agreement that no longer fits.
Check whether the charter is helping the team complete its work. Useful evidence might include clearer ownership of a previously ambiguous task or an escalation that reaches the right decision maker. A completion checkbox or a satisfaction score alone says little about operational usefulness.
Evidence limits and the first version
The research evidence cited here concerns a particular student-simulation setting; institutional sources provide team-design and briefing guidance rather than proof of this exact charter. The exhibition narrative is hypothetical. No improved performance, actual meeting or participant agreement is claimed.
Draft the first version with the team, then test it against one difficult scenario. Resolve missing authority and capacity before asking everyone to endorse the document. Keep the version short enough to use during real work, and make the next review depend on what the team learns from using it.
Sources:
- John E. Mathieu and Tammy L. Rapp (2009). Laying the foundation for successful team performance trajectories: The roles of team charters and performance strategies.
- Government Digital Service (n.d.). Have a multidisciplinary team.
- Agency for Healthcare Research and Quality (2024). TeamSTEPPS Sharing the Care Plan: Brief.
- Amy Edmondson (1999). Psychological Safety and Learning Behavior in Work Teams.



