How to Write a Team Charter in English for Project Collaboration

You sit down for your first project meeting. Someone says, "Let's draft the team charter." Your mind goes blank. What is that? And how do you write one in English?

Relax. A team charter is just a one-page agreement. It answers basic questions: Why are we doing this? Who does what? How do we work together?

Here is exactly how to write a team charter in English, with phrases you can steal and use today.

1. Start with the Project Mission

This is the "why." One or two sentences. If you cannot explain why the project exists, the charter is pointless.

Phrases to use:

• "The purpose of this project is to..."
• "We are working together to..."
• "By the end of this project, we will have delivered..."

Example:

"The purpose of this project is to redesign the company website so that page load time decreases by 30% and mobile conversion rate increases by 15%."

Keep it short. No fluff.

2. Define Roles Clearly

Role confusion kills projects. Say exactly who is responsible for what. Use the RACI model if your team knows it. If not, keep it simpler.

Phrases to use:

• "[Name] is responsible for..."
• "[Name] will make final decisions on..."
• "Everyone else will provide input but [Name] has the final say."

Example:

• Maria (Project Lead): Makes final decisions on timeline and budget.
• James (Developer): Builds the front-end. Has final say on technical choices.
• Sara (Designer): Creates all visuals. Approves final design.
• Everyone else: Reviews and gives feedback within 48 hours.

Don't be vague. "Everyone helps with everything" is a recipe for disaster.

3. Agree on How You Communicate

This section prevents a hundred Slack messages asking the same questions. Write down the rules.

Phrases to use:

• "We will use [tool] for daily updates."
• "All major decisions must be documented in [tool]."
• "Response time should be within [timeframe]."
• "Meetings will happen [frequency]."

Example:

• Daily updates: Slack, in the #website-redesign channel.
• Decision log: Google Doc, updated after every meeting.
• Response time: During working hours, reply within 4 hours.
• Meetings: Every Monday at 10 AM. 30 minutes max.

Be specific. "We communicate well" means nothing. "We reply within 4 hours" means something.

4. Set the Ground Rules

This is where you prevent conflict before it starts. Think about what drove you crazy on past projects. Write the opposite.

Phrases to use:

• "If there is a disagreement, we will..."
• "We will not..."
• "The team agrees to..."

Example:

• If there is a disagreement about a feature, the project lead makes the final call.
• We will not send emails after 7 PM unless it is urgent.
• The team agrees to test every change before pushing to production.

No list here is wrong. But get it in writing. Future you will thank present you.

---

Here is a simple visual of how the charter flows together. Think of it as the skeleton of your document.

5. List Deliverables and Deadlines

Finally, write down the concrete outputs. Each deliverable should have one owner and one deadline.

Phrases to use:

• "The key deliverables are..."
• "[Deliverable] will be completed by [date]."
• "[Name] is responsible for delivering [thing] by [date]."

Example:

• Wireframes completed by Feb 10. Owner: Sara.
• First draft of homepage code by Feb 20. Owner: James.
• User testing completed by March 1. Owner: Maria.

Be honest with dates. Optimistic deadlines help no one.

A Quick Template You Can Adapt

Here is the simplest structure. Copy it, fill it in, and you have your charter.

Project Mission: [One sentence.]

Roles:

• [Name] – [Role and decision power]
• [Name] – [Role and decision power]

Communication:

• Tool: [Slack/Teams/Email]
• Response time: [X hours]
• Meetings: [Day and time]

Ground Rules:

• [Rule 1]
• [Rule 2]

Deliverables:

• [Thing] by [Date]. Owner: [Name].
• [Thing] by [Date]. Owner: [Name].

That is it. One page. Everyone signs. You move on to the actual work.

Writing a team charter in English gets easier the more you do it. The first time feels awkward. By the third time, you will wonder how you ever started a project without one.

Ready to test your business English skills? Take a free English level test on English Measure. Check your reading, listening, writing, and speaking. It takes about 15 minutes, and you get a clear score. No sign-up tricks. Just real feedback. Test your English here.