This guide covers everything you need to know about the team charter in PMBOK 8. The team charter is the agreement between project team members that defines the team’s shared values, working norms, communication expectations, decision-making processes, and conflict resolution approach — it is the social contract that enables a group of individuals to function as a high-performing team.
What Is the Team Charter?
The team charter is a document developed collaboratively by the project team that establishes the ground rules and behavioral norms the team agrees to follow. Unlike the resource management plan (which defines organizational roles and responsibilities), the team charter defines how the team will work together as human beings: how meetings will be run, how decisions will be made, how conflicts will be raised and resolved, what communication channels and response times are expected, and what values the team agrees to uphold.
The team charter is most effective when it is created by the team, not imposed on the team. When team members participate in developing their own working agreements, they are more likely to honor them. A charter created by the project manager alone and handed to the team is not a team charter — it is a list of rules.
PMBOK 8 treats the team charter as a foundational people-management tool, recognizing that technical project management competence is necessary but not sufficient for high team performance. Teams without explicit working agreements default to implicit norms, which are often inconsistent, unspoken, and a source of ongoing friction.
Team Charter in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the team charter belongs to the Resources Performance Domain and is produced during the Plan Resource Management process. It is developed early in the project — ideally at the kickoff meeting — when the team is forming and norms are most malleable.
The team charter complements the resource management plan: the plan defines formal roles, responsibilities, and authority; the charter defines the interpersonal and cultural norms within which those formal structures operate.
Key Elements of the Team Charter
A well-structured team charter typically includes:
- Team Values — the principles the team commits to (e.g., transparency, accountability, continuous improvement)
- Communication Norms — expected response times, preferred channels, and meeting etiquette
- Decision-Making Process — how team decisions are made (consensus, consultation, or unilateral with notification)
- Meeting Norms — meeting frequency, agenda requirements, start-on-time expectations
- Conflict Resolution Process — how disagreements are raised, discussed, and resolved
- Team Commitments — specific behavioral agreements signed by all team members
Team Charter Example — Project Phoenix
The Project Phoenix team charter was developed in a 90-minute workshop at the project kickoff meeting on January 8, 2024. The team agreed on four core values: transparency (problems are raised immediately, not hidden), quality ownership (everyone is responsible for quality, not just the QA engineer), respect for schedules (meetings start on time, deadlines are kept), and continuous improvement (feedback is a gift, not a criticism).
Communication norms included a 4-hour response time for Slack messages and 24-hour response time for emails during working hours. The decision-making process specified that technical architecture decisions required Sam Lee’s lead with John Tran consulted; project management decisions were Alex’s with team input; and creative decisions required Daniel Reyes’s lead with Sarah Chen’s approval. All five team members signed the charter at kickoff. Sam Lee later cited it in the lessons learned register as “the single most effective team tool on this project.”
You can download the complete filled-in example below — it shows exactly how the team charter was built for a real project.
Download Free Team Charter Template and Example
We have prepared two free resources to help you create a team charter for your own projects:
- Download the Team Charter Template — PMBOK 8 (blank, ready to fill in)
- Download the Team Charter Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Team Charter — Best Practices and Common Mistakes
Develop the charter with the team, not for the team — the process of creating it is as valuable as the document itself. Keep it concise: a two-page charter that the team actually remembers and follows is more valuable than a ten-page document that no one reads after kickoff. Revisit the charter when new team members join or when the team enters a significantly different project phase.
The team charter is most effective when it is treated as a living agreement, not a one-time document. Teams that skip or rush the team charter process often spend weeks discovering and resolving implicit norm conflicts that could have been addressed in a single 90-minute workshop.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Project Management