TeamDynamics
Sign InStart now

Template for Team Agreements

Create a team agreement with an editable template, a filled handoff example, section-by-section prompts, and a 30-minute workshop agenda.

Template for Team Agreements

Get my team agreement template

Available as PDF or Word.

By accessing this free resource, you agree to receive TeamDynamics tips, resources, and product updates. You may unsubscribe anytime.

TL;DR

Turn shared expectations into an agreement people can use: name the trigger, action, owner, exception route, and review date. Start with the free editable document and adapt the filled example below.

What is a team agreement?

A team agreement records how a particular group intends to work together: its purpose, responsibilities, communication, decisions, conflict process, meetings, and follow-up. A useful agreement turns broad intentions into actions people can recognize. It should be easy to revisit when the work or team changes.

The free Word and Google Docs template is editable; the PDF is useful for reference or printing. The document includes prompts for purpose and goals, roles, communication, decision-making, conflict, meetings, accountability, and review. The filled example below is on-page guidance, not a new edition of the pack.

What to include in a practical team agreement

Scroll horizontally to compare all columns. You can also focus the table and use the left and right arrow keys.
Team agreement sections and the question each should answer
SectionDecideMake it observable
Purpose and goalsWhat is this team responsible for?Name the outcome and the work outside its scope.
RolesWho owns work, input, and approval?Identify a decision owner rather than “everyone.”
CommunicationWhere does important information go?Name the channel, trigger, and expected response window.
DecisionsHow do we reach and record a choice?State who decides and what input is required.
ConflictHow do we raise and resolve a disagreement?Name the first conversation and escalation route.
MeetingsWhat needs shared meeting time?Require a purpose, preparation, and an output.
AccountabilityHow do we check commitments?Record an owner and a review date.

Choose rules the team can actually follow within its responsibilities. When a change needs authority or support elsewhere, record the request and its owner instead of pretending the agreement can create that authority.

A filled-in example for a team with incomplete handoffs

This illustrative agreement describes a small project team. It is not a customer contract or a claim of measured improvement. Adapt its timing, tools, responsibilities, and exceptions to your work.

Scroll horizontally to compare all columns. You can also focus the table and use the left and right arrow keys.
Example working agreement: a complete handoff
AreaExample agreement
PurposeDeliver the agreed project work and give the receiving teammate enough context to begin.
Ready to hand offThe sender links the current brief, names the next owner, and lists unresolved questions before marking the task ready.
AcceptanceThe receiver confirms what is missing in the task record before beginning work.
Urgent exceptionThe sender flags the missing item, its owner, and the risk; the decision owner confirms whether work should proceed.
Decision recordThe decision owner records the choice, reason, and remaining uncertainty where the team can find it.
ReviewThe team reviews the next four handoffs and decides whether to keep, adapt, or end the checklist.

Notice the difference from “communicate better”: the example identifies a trigger, an action, an owner, and a way to check it. A different team might need a rule about meeting preparation or how a decision is escalated.

Your TeamDynamics rapid result · 2 minutes

What makes your team tick?

Answer twelve quick questions about how your team works, then enter your email to see your free TeamDynamics preview.

When we have team meetings…

Question 1 of 12 · Choose an answer to start

Build your first version in 30 minutes

Scroll horizontally to compare all columns. You can also focus the table and use the left and right arrow keys.
Suggested 30-minute working-agreement session
TimeTaskOutput
0–5 minutesName one repeated work problem and bring a recent example.A shared scope.
5–12 minutesAsk each person what they expected and what happened.Different needs and constraints.
12–22 minutesDraft one or two observable agreements.Specific triggers, actions, and owners.
22–27 minutesCheck capacity, authority, and likely exceptions.A workable version and an escalation route.
27–30 minutesChoose where to try it and when to review.A small experiment and review date.

These timings are suggestions. For remote teams, collect independent notes first and put the agreement in a shared document. Give each participant time to raise a practical concern before closing the discussion.

Check an agreement before calling it finished

  1. Could a new teammate tell when the rule applies?
  2. Does it name an action rather than a personality quality?
  3. Does someone have responsibility and capacity to act?
  4. Can the team handle an exception without silently abandoning the rule?
  5. Is there a review date and an observable example to discuss?

Keep an agreement short enough to use. If nobody can find or explain it during the work, simplify it. Review it when the team, responsibilities, tools, or constraints change, rather than adding rules indefinitely.

Use assessment insights as a starting question

TeamDynamics can help a team discuss its shared Communicating, Processing, Deciding, and Executing habits. Individual preferences separately inform personal and CoDynamics insights. A profile can suggest a question to explore; it does not select the agreement for you or prove that one working style is best.

For example, the 2025 State of the Team report describes a difference between individuals’ preferences for detailed plans and teams’ reported behavior in its sample. That finding does not diagnose your team. It can prompt a question: “Where do we need a more explicit plan, and where should we preserve flexibility?” See the sample Team Discussion Guide or use the team norms worksheet for the next conversation.

Frequently asked questions

Questions, answered.

What should a team agreement include?

Purpose, roles, communication, decision-making, conflict, meetings, accountability, and review. Make each selected rule specific enough to recognize in the work.

How is a team agreement different from a list of values?

An agreement says what people will do in a situation. Values can explain why an action matters, but “be collaborative” does not specify a handoff or decision process.

How many rules should we start with?

Choose a small number the team has capacity to try and review. The suggested session starts with one or two agreements around a real work problem.

Can we use the agreement remotely?

Yes. Collect independent input, keep the document in a shared location, and make triggers, response expectations, owners, and exceptions explicit.

Is the filled example in the downloadable template?

The existing downloadable template is unchanged. The filled handoff example and workshop agenda are on-page additions.

Who should own a team agreement?

The team should understand and contribute to the agreement. Name an owner for each action and someone responsible for bringing the agreement back for review.

When should we review the agreement?

Set a review date when you create it. Revisit it when the team, responsibilities, tools, or constraints change, and use actual work examples to decide what to keep or adapt.