Team Charter

A team charter is a foundational working agreement that a group produces—usually in its first one or two meetings—to make explicit how it will operate. For research teams, delegations, and policy units, the charter functions less like a legal contract and more like internal terms of reference: it reduces ambiguity, surfaces disagreements early, and gives members something concrete to point to when expectations slip.

Most charters cover a common set of elements:

• Purpose and objectives — why the team exists and what success looks like (often expressed as 2–5 measurable deliverables).
• Scope and boundaries — what is in and out of remit, and what requires escalation to a sponsor or supervisor.
• Roles and responsibilities — lead, deputy, rapporteur, subject-matter leads; sometimes mapped using a RACI (Responsible, Accountable, Consulted, Informed) matrix.
• Decision rules — whether the team operates by consensus, majority, or lead-decides-after-consultation, and how to break deadlocks.
• Communication norms — meeting cadence, channels (e.g., Slack vs. email), response-time expectations, and confidentiality.
• Resources and timeline — budget, key milestones, and review points.
• Signatures or sign-off — confirming each member has read and agreed.

In a Model UN context, a bloc or working group may draft a lightweight charter before negotiating a draft resolution: who holds the pen, who liaises with the chair, who speaks in unmoderated caucus, and how amendments are vetted. In think-tank and policy-research settings, charters are often required by project managers and align closely with the Project Management Institute's PMBOK Guide, which treats the project charter as a formal authorisation document.

Charters are most useful when treated as living documents: revisited at midpoints, amended when membership or scope changes, and archived as part of project documentation. A charter that is written once and never reopened typically loses force within a few weeks.