Team Charter: An Agreement the Team Writes and Owns

Most friction inside teams is not disagreement about the work but about how the work is done: who decides when opinions split, how quickly a message should be answered, whether arriving five minutes late is acceptable. Nobody raises these questions openly, so each member answers them from personal habit and is then surprised their colleague answered differently. The resulting friction gets misread as a clash of personalities when it is really the absence of a written agreement on matters each side finds self-evident. The team charter converts those tacit norms into a written agreement — and its value in the Eighth Edition lies not in the document but in who writes it.

Definition and Foundation

The team charter is a document that establishes the values, agreements, and operating guidelines for the team. The Eighth Edition names six elements it may include:

• Team values — what members agree on as principles for working.
• Communication guidelines — how they communicate, through which channels and at what cadence.
• Decision-making criteria and processes — who decides and how the team reaches a decision.
• Conflict resolution processes — the agreed route when opinions diverge.
• Meeting guidelines — how meetings are run and what etiquette applies.
• Team agreements — what members commit to toward one another.

Its stated function is that it establishes clear expectations regarding acceptable behavior by team members. The guide ties timing to outcome directly: early commitment to clear guidelines decreases misunderstandings and increases productivity. Discussing codes of conduct, communication, decision-making, and meeting etiquette allows members to discover values important to one another — so the drafting process is itself an output, not just the document.

Tied to it are ground rules: expectations regarding acceptable behavior by project team members, defined in the team charter, setting the expected behavior for team members and other stakeholders with regard to stakeholder engagement. Ground rules are therefore not a parallel document but content inside the charter, and their reach extends beyond the team to those who deal with it. That reach is what makes them an instrument in managing conflict with external stakeholders rather than inside the team alone.

How It Works in Practice

Who writes the charter

Here is the governing condition: the team charter works best when the team develops it, or at least has an opportunity to contribute to it. That wording allows two levels — full collective drafting, or the minimum of an opportunity to contribute. The practical difference is large: a charter the manager writes and circulates fails the condition, while one presented to the team for comment and amendment meets it. One question settles which happened: did the team change anything in the text? If the document came out as it went in, there was no real opportunity to contribute.

Who is bound by it

All project team members share responsibility for ensuring the rules documented in the team charter are followed. That relocates the manager: they are not the charter's enforcer but one of the parties bound by it. A ground rule violation is the whole team's business rather than management's alone. In practice that means handling a breach starts inside the team by returning to a text everyone agreed to, not with an escalation that turns a behavioral disagreement into a management case prematurely.

When it is reviewed

The charter can be reviewed and updated periodically for two stated purposes: ensuring a continued understanding of the team ground rules, and orienting and integrating new team members. The second is intensely practical: a new member joining means the agreement no longer covers everyone, so it is reopened — not necessarily to change it, but to include them. The review is also a chance to test whether the rules still describe reality: a rule everyone breaks without objection is not a rule but dead text.

Its place in the processes

The team charter is a stated input to the Lead the Team process, alongside the resource management plan, issue log, lessons learned register, project schedule, resource calendars, work performance reports, and project team assignments. It is therefore not a founding document to be filed but a reference returned to in daily team management. Being an input to the process means it is read alongside the issue log and work performance reports, so behavior is interpreted against what was agreed rather than against the manager's impression. It also appears among the common aspects of team development: facilitating communication, problem-solving, and consensus building may include working with the team to develop a team charter and a set of operating guidelines or norms.

On the Exam

The 2026 ECO names ground rules outright in Domain I, People: Task 2, manage conflicts, carries two explicit enablers — "establish an environment that fosters adherence to common ground rules" and "manage and rectify ground rule violations." Alongside them sit the task's other enablers: identify conflict sources, analyze the context, implement an agreed-on resolution strategy, and communicate conflict management principles with the team and external stakeholders. Task 3, lead the project team, connects through establishing expectations at the team level and establishing clear roles and responsibilities.

The dominant pattern is a scenario describing a behavioral breach or a disagreement about how to work, and asking what to do. Four keys settle most of it:

• A ground rule violation → handled by returning to the charter, with responsibility for compliance shared.
• A manager who wrote the charter alone → the charter works best when the team develops it or contributes to it.
• A new member joining → review the charter to orient and integrate them.
• A dispute over who decides → decision-making criteria and processes are one of the charter's six elements, so the charter settles it rather than authority.

What deceives is options offering direct managerial fixes: escalating the violation to a functional manager, adding a new rule unilaterally, or ignoring the breach to preserve the relationship. All three bypass the agreed mechanism. So does conflating the two charters: the project charter grants authority and is issued by the sponsor, while the team charter organizes ways of working and is developed by the team.

Detailed Mistakes

Writing the charter without the team's contribution

The condition in the guide is explicit: the charter works best when the team develops it or at least has an opportunity to contribute. A document drafted in an office and circulated loses the process's second effect — allowing discussion to let members discover the values that matter to one another. The text survives and the understanding it existed for is lost. The sign is unmistakable: a charter nobody cites at the first disagreement never passed through the team at all.

Treating the charter as a document signed once

The guide states periodic review for two reasons: continued understanding of the ground rules, and orienting and integrating new members. A team that replaced half its members since drafting operates under an agreement half of it never joined. Review here is not organizational decoration but the condition for the agreement remaining in force, because commitment comes from taking part in setting the rules rather than from reading them.

Confining ground rules to the team

The definition reaches further: ground rules set the expected behavior for team members and other stakeholders with regard to stakeholder engagement. Rules about response times, escalation channels, and meeting etiquette concern those who deal with the team as much as its members. Confining them internally leaves the largest source of disruption — requests arriving from outside — with no rule governing it, so the team stays disciplined internally and exposed externally.

Where It Does Not Apply

A team charter presumes a relatively stable team able to agree on rules and hold to them. Where membership changes constantly — teams assembled for short assignments, or resources borrowed from other departments for a few weeks — review costs more than the agreement is worth, so a minimum of operating guidelines is kept and re-explained to each arrival. A structural constraint follows: in a centralized management structure where accountability is assigned to one individual, the rules a team sets remain subject to organizational policies and procedures — a team cannot agree on something that contradicts organizational policy. The charter is therefore an agreement inside a permitted space, not independent sovereignty. Promising a team that "we set our own rules" without stating that boundary sets up disappointment at the first collision with a higher policy. The honest formulation is: we set our rules on what is ours, and we comply with what the organization mandates elsewhere.