Team Charter Template
A structured framework to establish team values, communication expectations, and decision-making protocols from day one.
In this resource
§1Core Components of a Team Charter
A project team charter acts as a foundational agreement for how a group of individuals will collaborate, make decisions, and resolve disputes throughout the project lifecycle.
By defining standard operating procedures upfront, the charter reduces ambiguity and prevents unstated assumptions from developing into active conflicts. A robust charter contains six essential dimensions:
1. Values & Principles
The behavioural guidelines that set the cultural baseline. These are non-negotiable standards covering respect, transparency, quality, and ownership.
2. Meeting Guidelines
Agreed cadences for synchronisation. This defines when the team meets, the expectation for agendas, required outputs (e.g. decision logs), and camera-on policies.
3. Communication Rules
Service-level agreements (SLAs) for internal and external communications. It identifies which channels to use (e.g. instant messaging vs email) and expected response times.
4. Decision-Making
The operational boundaries of authority. This section specifies who has the autonomy to make domain-level decisions and the escalation pathway for cross-domain conflicts.
5. Conflict Resolution
A step-by-step de-escalation protocol ensuring disagreements are addressed at the lowest possible tier before impacting project baselines.
6. Other Agreements
Logistical parameters such as core working hours, on-call schedules, vacation notice periods, and knowledge-sharing requirements.
§2Worked Example: Mary's Consulting Website
Below is a fully articulated charter established for a web development project. Notice the specificity in response times and escalation steps, leaving zero room for interpretation.
Team Values and Principles
- Respect — We treat each other and our stakeholders with respect, even under deadline pressure.
- Transparency — We surface issues and risks early rather than hide them; bad news travels faster than good news on this team.
- Quality — We hold ourselves to a high bar; accessibility and security are non-negotiable, not optional polish.
- Ownership — Each team member owns their domain fully; the Project Manager (PM) owns escalation, not micromanagement.
- Continuous improvement — We run retrospectives at the end of each phase and adjust how we work.
Meeting Guidelines
- Weekly team standup, Monday 9:30–10:00 AM, in-person or video.
- Sponsor steering, last Friday of each month, 30 minutes.
- Every meeting has a written agenda 24 hours in advance and a written outcome within 24 hours after.
- Camera-on default for video calls; turning off is fine when context calls for it.
- Decisions made in meetings are recorded in the Decision Log; if you are not in the room, you will see it there.
Communication Guidelines
- Instant messaging for fast sync; email for decisions and external stakeholders; ticket system for work tracking.
- Response expectations: Instant messaging ≤ 4 business hours; email ≤ 1 business day; tickets ≤ 2 business days.
- After hours: no expectation of response. Mark urgent issues with priority tags only when truly urgent.
- When stuck for > 2 hours, ask. Heroes-in-silence is an anti-pattern on this team.
- PM is the single point of contact for sponsor and external-stakeholder communication unless explicitly delegated.
Decision-Making Process
- Within team domain: Each team member has authority to make decisions within their domain (e.g. Bob — tech, Bill — design, Christine — content) without PM approval, provided the decision fits inside the approved scope, schedule, and budget.
- Cross-domain: Decisions affecting multiple domains are surfaced to the PM and decided by team consensus when possible. The PM has tie-breaker authority.
- Outside scope/baseline: Decisions that change scope, schedule, or cost go through the formal change-control process and require sponsor approval per the PM Plan.
- Decisions logged: All cross-domain or sponsor-level decisions are recorded in the Decision Log.
Conflict Resolution Process
- Step 1 (Direct conversation): The team members involved attempt to resolve the conflict directly within 1 business day.
- Step 2 (PM facilitation): If unresolved, the PM facilitates a discussion within 2 business days.
- Step 3 (Sponsor escalation): Conflicts that affect scope, cost, schedule, or quality and cannot be resolved by the PM are escalated to the Sponsor.
Tone: Disagree with ideas, not people. Focus on what is best for the project, not on personal preferences.
Other Agreements
- Working hours: Core hours 10:00 AM–3:00 PM; outside core hours, team members work flexibly.
- Vacation: Notify the team and PM at least 2 weeks in advance for vacations longer than 1 day.
- On-call: Rotations cover the 2-week hypercare window post-launch; normal rotation arranged afterward.
- Knowledge sharing: All design and code are stored in the organisation's shared repositories; no personal-drive-only artifacts.
- Living charter: This charter can be amended by team consensus and re-signed; review at each phase gate.
| Name / Role | Signature | Date |
|---|---|---|
| Andrew (PM) | Signed electronically | May 18, 2026 |
| Bob (Web Developer) | Signed electronically | May 18, 2026 |
| Bill (UX Designer) | Signed electronically | May 18, 2026 |
| Christine (Content Strategist) | Signed electronically | May 18, 2026 |
§3Quick Reference & Guidelines
Keep these principles in mind when drafting your organisation's charter.
Collaborative Drafting
Never write the charter in isolation. Use the kick-off meeting to define these parameters together, ensuring team ownership and genuine commitment to the SLAs.
Actionable Metrics
Avoid vague terms like "respond quickly". Quantify expectations (e.g. "≤ 4 business hours") so there is an objective baseline to reference during conflicts.
Living Document
A charter is not a static artifact. Schedule a brief review of the document at major phase gates to adapt rules that aren't serving the team's current velocity.