Six editable templates for the document a team writes about itself: how it meets, communicates, decides, and holds itself to commitments. A full working agreement, a manager-written team expectations document, remote, meeting and feedback versions, plus a signature and review log. DOCX, no signup.
The first team argument I had to referee at FirstHR was not about the work. It was about a message sent at 11 p.m. that one person read as a question for the morning and another read as a fire. Both of them were right, because we had never written down which one it was.
A team working agreement is the document that answers those questions in advance: how this team meets, which channel carries which kind of message, how fast people reply, who decides what, and what happens when two people disagree. The team writes it, not the founder, which is the entire reason it works.
These six templates cover the range. A full working agreement, a manager-written team expectations document, a remote and hybrid version, a meeting norms agreement, a feedback and disagreement agreement, and a signature and review log. Each downloads as an editable Word file, free, with no email required.
TL;DR
A team working agreement is a one to two page document a team writes about itself: meeting norms, channels and response windows, who decides what, how commitments are tracked, and how disagreement ends. It is written by the team rather than issued by management, and it carries signatures and a review date. Download six free templates as editable Word files.
What a Team Working Agreement Is
A team working agreement is a short written record of how a specific team works together, created by the people on that team. It covers meetings, communication channels, response times, decision rights, how commitments are tracked, and how disagreement gets resolved. It ends with a review date and signatures from everyone on the team.
You will see the same document called team norms, ground rules, or a social contract. A team charter is a close relative that leans harder on purpose, scope and decision rights; a working agreement leans on behavior. Either way the label matters less than the authorship. Harvard Business Review makes the case for the format directly in a piece on turning company values into working agreements, reporting that 80 percent of employees work at organizations with stated values while only 23 percent agreed they could apply those values to their everyday work.
That gap is the whole reason this document exists. A value tells you to communicate openly. An agreement tells you that chat gets answered within four hours during your scheduled hours and that an urgent item is a phone call. One of those can be followed on a Tuesday afternoon; the other cannot be broken, which means it also cannot be kept.
Half the Workforce Cannot Say What Is Expected of Them
Gallup found that 49 percent of US employees strongly agreed they know what is expected of them at work in the first half of 2026, up two points from 47 percent, while overall engagement held at 31 percent (Gallup, Employee Engagement Remains Flat as AI Adoption Accelerates). Clarity of expectations is the item Gallup treats as foundational, and on a small team it is the one an owner can fix in an afternoon rather than a fiscal year.
One boundary worth stating up front: a working agreement is not a policy and does not replace one. It sits underneath your communication policy and your code of conduct, and where the two disagree, the policy wins. Say that in the document itself, in one line, so nobody has to guess.
What Goes Into One
A working agreement covers four areas: what the team is for, how it communicates and meets, how it decides and disagrees, and how it takes on new people and keeps itself current. Everything else is padding. The groups below are what the full template on this page is built from.
Purpose and ownership
What this team is accountable for, in one sentence
The outcomes it is judged on this quarter
One named owner and a date on every commitment
Meetings and messages
Which channel carries which kind of message
Response windows tied to scheduled hours
Agenda rule, notes rule, and the right to decline
Decisions and disagreement
Who decides what, written down before it is needed
The path from thread to call to a named decider
Supporting a decision in public after arguing against it
Joining and reviewing
What someone new is given, and by whom
A fixed review date, plus triggers for an early one
A log of what changed and what was deleted
The test for every line is whether a person could either follow it or fail to follow it on a given Tuesday. Response within four hours passes. Respect each other's time does not, because two people can follow it in opposite directions and both believe they complied.
Keep the material that belongs elsewhere out. Conduct rules live in the code of conduct, eligibility for working from home lives in the remote work policy, and how someone is assessed lives in the expectations document. An agreement that absorbs all three stops being readable, and an unread agreement changes nothing.
Team Expectations vs a Working Agreement
The difference is authorship, and it decides everything else. A working agreement is written by the team together and signed by everyone in it. A team expectations document is written by the manager and states what is required, what the team gets in return, and how performance is assessed. Both are legitimate; they solve different problems.
A team expectations template answers a different need: a quality bar, a turnaround standard, an escalation rule that is not up for a vote. That need is real, and it is not a working agreement. Handing a team a finished document and calling it an agreement produces a policy in softer typography, and teams recognize the difference immediately.
Team expectations document
Team working agreement
Who writes it
The manager or owner
The whole team, in one session
What it settles
Standards, priorities, and the floor
Habits, channels, and shared defaults
Typical content
Quality bar, turnaround, escalation, how performance is assessed
Meeting rules, response windows, decision rights, how disagreement ends
What the reader signs
An acknowledgment that they received it
An agreement they helped write
When it changes
When the manager changes it
At the quarterly review, by the team
Fails when
It is written but never said out loud
It is written by one person and handed down
Best used for
Non-negotiables, and new managers setting a baseline
Everything the team has to invent for itself
Most small teams need both, which is why the download includes each as a separate file. My rule of thumb: if you would overrule the team on it, put it in the expectations document where the authorship is honest. If you would not, put it in the agreement and let them write the wording.
There is a second reason to keep them apart. The expectations document is where the manager promises something back, and that half is what makes the first half survive contact with reality. A commitment to a one-to-one you never cancel and a decision within two business days does more for a team than another paragraph about ownership.
Which Template Should You Use?
Start with the full working agreement unless you have a specific narrower problem. The remote version is for distributed teams, the meeting version is for a calendar that has quietly filled up, the feedback and disagreement version is for a team that avoids the hard conversation, and the expectations document is for setting a floor.
Team Working Agreement (Full)
The one to start with
Eight sections the team fills in together: what the team is for, how it meets, communicates, decides, holds itself to commitments, disagrees, onboards someone new, and reviews the whole thing. Ends in signatures.
Team Expectations Document
Written by the manager
The other half of the pair. What the manager expects on work and behavior, what the team can expect back, how performance is assessed, and an acknowledgment line. Use it when someone has to set the floor.
Remote and Hybrid Agreement
Overlap hours and async
Time zones, a shared overlap window, response windows tied to scheduled hours, meeting norms across zones, and a visibility section that measures output rather than green dots.
Meeting Norms Agreement
For calendars that filled up
A meeting inventory with the monthly hours calculated, the cancellation rule, the three roles every meeting needs, the four lines that leave the room, and a quarterly audit.
Feedback and Disagreement
The section teams skip
How feedback is given and within what window, what to do with feedback you disagree with, the four steps an argument follows to an ending, what we never do, and the things that go straight to a manager instead.
Acknowledgment and Review Log
Why it stays true
The signature page, a new joiner log, a review log with four questions, the five triggers for an immediate review, and version history. The part that keeps the agreement from going stale.
Two Files Cover Most Teams
Download the full working agreement and the acknowledgment and review log, and you have the whole system: the document itself plus the mechanism that keeps it true. The other four are for specific shapes of team. Distributed teams should take the remote version instead of the full one, since it is the same structure with time zones, overlap windows and async defaults built in rather than bolted on afterward.
6 Free Team Working Agreement Templates
Download all six as one file or take the one you need. Every version is a fill-in-the-blanks Word document, with the tables already drawn and the awkward sections already written, because those are the ones a team skips when it is drafting from scratch.
Download All 6 Team Working Agreement Templates
Full working agreement, team expectations, remote and hybrid, meeting norms, feedback and disagreement, and the acknowledgment and review log. Six editable Word files in one download.
Template 1: Team Working Agreement (Full)
The default. Eight sections the team fills in together, from what the team is accountable for through meetings, channels, decision rights, commitments, disagreement, and what someone new is owed. Ends with a review date and a signature block.
Team Working Agreement (Full)
TEAM WORKING AGREEMENT
[Team Name] at [Company Name]
Written by the team on: _ Next review: _ (suggested: 90 days)
Document owner: _
This agreement is written by the people who have to live with it. It is not a company
policy and it does not replace one. Where this agreement and a company policy disagree,
the policy wins.
1. WHAT THIS TEAM IS FOR
In one sentence, what this team is accountable for:
[Example: we keep every installed customer running, and we answer them the same business
day.]
The three outcomes we are judged on this quarter:
1. _____
2. _____
3. _____
2. HOW WE MEET
Standing meetings we keep:
| Meeting | Day and time | Length | Who runs it | Who has to be there |
| | _____ | ______ | ____ | _____ |
| | _____ | ______ | ____ | _____ |
| | _____ | ______ | ____ | _____ |
•Every meeting has a written purpose and something to decide, or it is cancelled.
•If there is no agenda by [5 p.m. the day before], the meeting is cancelled.
•Notes and decisions are posted in [location] within [one business day].
•Anyone may decline a meeting they are not needed in, without explaining why.
•We cancel a standing meeting rather than fill it.
3. HOW WE COMMUNICATE
Channel by purpose:
•[Chat tool]: questions that can wait a few hours, and daily coordination.
•Email: anything external, or anything that needs a durable record.
•A call: anything that has gone back and forth in writing more than twice.
•[Shared docs]: anything a person joining in six months would need to read.
Response windows, during each person’s scheduled hours only:
•Chat: within [4 hours].
•Email: by the end of the next business day.
•Marked urgent: within [30 minutes], and urgent means a phone call, not a label.
Nobody is expected to answer outside their scheduled hours. If you send something late,
say in the message that it can wait until morning.
4. HOW WE DECIDE
For each recurring decision, name the type and the person:
| Decision | Type: owner decides / owner consults / whole team agrees | Who decides |
| _ | | ____ |
| _ | | ____ |
| _ | | ____ |
•Default when the type is not written down: [role] decides after hearing the team.
•Once a decision is made and written down, we support it in public, including the ones
we argued against.
•A decision that is not written down within [one business day] did not happen.
5. HOW WE HOLD EACH OTHER TO IT
•Every commitment has one named owner and a date. Two owners means no owner.
•If a date is going to slip, the owner says so before the date, not after.
•We ask for help at [half] the time budgeted, not at the deadline.
•Work in progress is visible in [tool], so nobody has to ask what is happening.
•Every recurring task has a named backup, and the backup has been told.
6. HOW WE DISAGREE
•Disagree in the thread once, in writing, with the reason.
•If it is still open after that, take it to a call the same day.
•If it is still open after the call, [role] decides and writes down why.
•We argue about the work, not about the person. Personal conduct issues go to
[manager or owner] rather than into a channel.
7. WHAT WE OWE SOMEONE NEW
•This agreement is shared before their first day and walked through in week one.
•A named buddy for the first [30] days: _______________
•The three documents they should read first: _______________
•They are invited to challenge anything in here at the first review after they join.
8. REVIEW AND SIGNATURES
We revisit this document every [90] days, and immediately whenever the team gains or
loses a person, changes what it is accountable for, or changes how it works.
Name: __ Signature: __ Date: ____
Name: __ Signature: __ Date: ____
Name: __ Signature: __ Date: ____
Name: __ Signature: __ Date: ____
NOTE ON RIGHTS: This agreement covers how we work together. It is not intended to
interfere with anyone’s right to discuss pay, hours, or working conditions with coworkers,
to raise concerns with the company or a government agency, or to act together with
colleagues on terms and conditions of employment.
DISCLAIMER: This is a sample document for general informational purposes only. It is not
legal advice and not a guarantee of compliance. Response-time and availability language
can create compensable working time for employees who are not exempt from overtime, and
workplace rules interact with federal labor law. Have qualified US employment counsel
review anything you adopt.
Template 2: Team Expectations Document (Manager to Team)
The manager-written half of the pair. What is expected on the work and on behavior, what the team can expect back, how performance is assessed, and an acknowledgment line. Use it for the standards that are genuinely not up for a vote.
Team Expectations Document (Manager to Team)
TEAM EXPECTATIONS
[Team Name] at [Company Name]
Written by: _ (manager) Date: _ Next review: ____
This document says what I expect of this team and what the team can expect of me. It is
written by the manager, unlike a working agreement, which the team writes together. Use
both: this one sets the floor, the working agreement sets the habits.
1. WHAT THIS TEAM IS ACCOUNTABLE FOR
[One sentence. Then the two or three measures we are judged on, with the current number
and the target.]
Measure: _ Today: Target: By when:
Measure: _ Today: Target: By when:
2. WHAT I EXPECT ON THE WORK
•Quality bar: [what finished looks like for the most common piece of work].
•Turnaround: [the standard we hold, stated as a number].
•Ownership: you own a task from the moment you accept it until it is done or handed
over in writing.
•Escalation: bring me a problem as soon as you know the date is at risk, not the day
it is due. Nothing said early is ever held against you here.
•Documentation: [what has to be written down, and where].
3. WHAT I EXPECT ON BEHAVIOR
•Say the hard thing in the room rather than after the meeting.
•Disagree with me directly. I would rather be corrected than agreed with.
•Cover for each other without being asked, and say so when you do.
•Keep commitments to teammates at the same standard as commitments to customers.
4. WHAT YOU CAN EXPECT FROM ME
•A [30] minute one-to-one with each of you every [two weeks], which I do not cancel.
•A decision within [two business days] of you asking for one, or a date by which I
will have it.
•Feedback within [a week] of the thing it is about, in person, not saved for a review.
•Clear priorities. If everything is urgent, that is my failure to fix, not yours.
•Straight answers about the business, including the uncomfortable ones I am allowed
to share.
5. HOW PERFORMANCE IS ASSESSED
•What is measured: _______________________________________________
•How often we review it: _______________________________________________
•What good looks like: _______________________________________________
•What happens if the standard is not met: [the normal process, applied consistently].
6. ACKNOWLEDGMENT
I have received these team expectations and had the chance to ask about them.
Employee name: __ Signature: _ Date: ____
NOTE ON RIGHTS: This agreement covers how we work together. It is not intended to
interfere with anyone’s right to discuss pay, hours, or working conditions with coworkers,
to raise concerns with the company or a government agency, or to act together with
colleagues on terms and conditions of employment.
DISCLAIMER: This is a sample document for general information only and is not legal
advice. Have qualified US employment counsel review anything you adopt.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Template 3: Remote and Hybrid Team Working Agreement
Time zones, a shared overlap window, response windows tied to scheduled hours, meeting norms when one person is remote, and a visibility section that measures output rather than status dots.
Remote and Hybrid Team Working Agreement
REMOTE AND HYBRID TEAM WORKING AGREEMENT
[Team Name] at [Company Name]
Written by the team on: _ Next review: _
This adds to the general team working agreement. It covers the questions distributed
teams answer badly by accident: when people are reachable, what has to be written down,
and what a meeting is actually for.
1. WHERE AND WHEN WE WORK
| Person | Time zone | Scheduled hours | In office on |
| ______ | __ | _ | _____ |
| ______ | __ | _ | _____ |
| ______ | __ | _ | _____ |
•Shared overlap window when everyone is reachable: [10 a.m. to 1 p.m. Eastern].
•Outside the overlap window, written communication is the default.
•Changes to your scheduled hours go in [calendar or tool] before they happen.
2. ASYNC BY DEFAULT
•Written first: decisions, updates, and anything a person on leave would need.
•Live only for: decisions that are stuck, sensitive conversations, and new work that
is easier drawn than typed.
•Every live conversation that produces a decision gets a written summary the same day.
•If a message needs a reply within the hour, it is a call.
3. RESPONSE WINDOWS
During each person’s scheduled hours:
•Chat: within [4 hours].
•Email: by the end of the next business day.
•Anything marked urgent: a phone call, within [30 minutes].
Outside scheduled hours, nobody is expected to read or answer anything. Set your status
and turn notifications off. Sending late is fine; expecting an answer is not.
4. MEETINGS ACROSS TIME ZONES
•Recurring meetings sit inside the shared overlap window, or they rotate.
•Agenda posted [the day before], or the meeting is cancelled.
•One person joining remotely means everyone joins from their own screen.
•Camera norm: [on for discussion, off for updates and long sessions]. Nobody is asked
to explain a camera that is off.
•Notes posted in [location] within [one business day], every time.
5. VISIBILITY WITHOUT SURVEILLANCE
•We measure output, not green dots.
•Work in progress lives in [tool] so status is readable without asking.
•A short written update on [day] from each person: shipped, stuck, next.
•If you are heads down for a stretch, say so rather than going quiet.
6. IN-OFFICE DAYS
•Days the whole team is in: _______________
•What those days are for: [the work that is genuinely better in a room].
•What those days are not for: [status meetings that could stay written].
7. REVIEW AND SIGNATURES
Reviewed every [90] days and whenever someone changes time zone or schedule.
Name: __ Signature: __ Date: ____
Name: __ Signature: __ Date: ____
Name: __ Signature: __ Date: ____
NOTE ON RIGHTS: This agreement covers how we work together. It is not intended to
interfere with anyone’s right to discuss pay, hours, or working conditions with coworkers,
to raise concerns with the company or a government agency, or to act together with
colleagues on terms and conditions of employment.
DISCLAIMER: This is a sample document for general information only and is not legal
advice. Availability and response-time language can create compensable working time for
employees who are not exempt from overtime. Have qualified US employment counsel review
anything you adopt.
Template 4: Meeting Norms Agreement
For teams whose calendars filled up without anyone deciding they should. It starts with an inventory that calculates the monthly hours each recurring meeting costs, which is usually the moment the conversation changes, then sets the cancellation rule and the quarterly audit.
Meeting Norms Agreement
MEETING NORMS AGREEMENT
[Team Name] at [Company Name]
Agreed on: _ Next meeting audit: _
A short agreement about meetings alone, for teams whose calendars have quietly filled up.
Fill in the inventory first. The inventory is usually the argument.
1. MEETING INVENTORY
| Meeting | Frequency | Length | People | Hours per month | Still worth it? |
| | __ | ______ | ______ | _ | _ |
| | __ | ______ | ______ | _ | _ |
| | __ | ______ | ______ | _ | _ |
| | __ | ______ | ______ | _ | _ |
Hours per month = length x frequency x number of people. Write the number down before
anyone argues about whether the meeting is useful.
2. THE RULES WE AGREE TO
•No agenda by [5 p.m. the day before] means the meeting is cancelled, by anyone.
•Every meeting states its purpose in one line: decide, plan, solve, or inform.
•A meeting whose purpose is inform becomes a written update instead.
•Default length is [25 or 50 minutes], so people can reach the next one.
•Anyone may decline a meeting they are not needed in, with no explanation required.
•Anyone may leave once the part that needed them is done.
3. ROLES IN EVERY MEETING
•Facilitator: keeps the agenda moving and closes each item. Usually the person who
called it.
•Note taker: records decisions and owners, not a transcript. Rotates: ___________
•Timekeeper: [role, or the facilitator].
4. WHAT LEAVES THE ROOM
Every meeting produces the same four lines, posted in [location] within [one business
Template 5: Team Feedback and Disagreement Agreement
The section teams skip when drafting from a blank page, pulled out on its own. Feedback windows, what to do with feedback you disagree with, and a four-step path an argument follows to an ending. Sits alongside your approach to conflict resolution, without replacing any complaint procedure.
Team Feedback and Disagreement Agreement
TEAM FEEDBACK AND DISAGREEMENT AGREEMENT
[Team Name] at [Company Name]
Agreed on: _ Next review: _
The section teams skip when they draft from a blank page, written out on its own. It
covers how we give each other feedback, how an argument ends, and what happens after a
decision goes against someone. Nothing here replaces the company process for conduct
complaints; that route stays open at all times.
1. HOW WE GIVE EACH OTHER FEEDBACK
•Feedback goes to the person first, before it goes to anyone else, unless it involves
conduct that has to be reported.
•Within [a week] of the thing it is about. Saved-up feedback is a list of grievances,
not feedback.
•Say what happened, the effect it had, and what you would like instead. Three sentences.
•Feedback about work goes wherever the work is discussed. Feedback about behavior goes
in a private conversation.
•Asking for feedback is normal here. Everyone asks at least [once a month]: what is one
thing I should do differently?
2. WHAT WE DO WITH FEEDBACK WE DISAGREE WITH
•Say thank you, then take [24 hours] before responding.
•You are allowed to disagree with feedback. You are not allowed to make giving it
expensive.
•If two people give you the same feedback independently, treat it as a fact about how
you are read, whatever you believe about your intent.
3. HOW A DISAGREEMENT ENDS
Step 1: State the disagreement in writing, in the thread, with the reason. Once.
Step 2: Still open, take it to a call the same day, with both positions summarized first.
Step 3: Still open after the call, [role] decides and writes down the reason.
Step 4: Everyone supports the decision in public, including the people who argued
against it. Disagree and commit is the standard here.
Time limit: no disagreement about the work stays open longer than [three business days].
4. WHAT WE NEVER DO
•Reopen a settled decision in a side channel instead of at the review.
•Give feedback about a person to their teammates before giving it to them.
•Let a disagreement about the work become a running comment about the person.
•Use silence as a position. If you have an objection, it belongs in step 1.
5. WHEN IT IS NOT A DISAGREEMENT
Some things do not belong in this process at all and go straight to [manager, owner, or
the reporting channel named in the handbook]:
•Anything involving harassment, discrimination, or safety.
•Anything a person has asked to keep confidential.
•Anything about pay, hours, or terms of employment that needs a decision from the
company rather than from the team.
6. THE STANDING CHECK
Once a [month], in [meeting], two questions, answered out loud:
•What is one thing this team should start doing?
•What is one thing this team should stop doing?
Answers recorded on: _ Anything acted on: _
Name: __ Signature: __ Date: ____
Name: __ Signature: __ Date: ____
Name: __ Signature: __ Date: ____
NOTE ON RIGHTS: This agreement covers how we work together. It is not intended to
interfere with anyone’s right to discuss pay, hours, or working conditions with coworkers,
to raise concerns with the company or a government agency, or to act together with
colleagues on terms and conditions of employment.
DISCLAIMER: This is a sample document for general information only and is not legal
advice. It does not replace your complaint, harassment, or discipline procedures. Have
qualified US employment counsel review anything you adopt.
Template 6: Working Agreement Acknowledgment and Review Log
The signature page, a log for people who join after the agreement was written, a review log with four questions, the five triggers for an immediate review, and version history. This is the file that keeps the other five from becoming historical documents.
Working Agreement Acknowledgment and Review Log
TEAM WORKING AGREEMENT: ACKNOWLEDGMENT AND REVIEW LOG
[Team Name] at [Company Name]
Use this alongside whichever agreement you adopted. The signature page records who agreed
to what and when. The review log is the part that keeps the document from going stale.
1. ACKNOWLEDGMENT
I helped write, or have read and discussed, the [Team Name] working agreement dated
_. I understand it describes how this team works together, that it is not
a company policy, and that I can raise anything in it at the next review or sooner.
| Name | Role | Signature | Date | Version |
| ____ | ____ | __ | ____ | |
| ____ | ____ | __ | ____ | |
| ____ | ____ | __ | ____ | |
| ____ | ____ | __ | ____ | |
| ____ | ____ | __ | ____ | |
2. NEW JOINERS
| Name | Start date | Agreement shared on | Walked through by | Signed on |
| ____ | ___ | _____ | ___ | __ |
| ____ | ___ | _____ | ___ | __ |
A new person is invited to challenge any part of this agreement at the first review after
they join. An agreement they only inherited is a policy, not an agreement.
3. REVIEW LOG
| Review date | Who was there | What changed | What we removed | Next review |
| ____ | ______ | _____ | _ | ____ |
| ____ | ______ | _____ | _ | ____ |
| ____ | ______ | _____ | _ | ____ |
Four questions for every review:
1. Which line did we actually follow? Keep it.
2. Which line did we quietly ignore? Delete it or fix the reason.
3. What broke this quarter that this document should have prevented?
4. What has changed about the team, the work, or the hours?
4. TRIGGERS FOR AN IMMEDIATE REVIEW
•Someone joins or leaves the team.
•The team changes what it is accountable for.
•Someone changes time zone, schedule, or working pattern.
•The same disagreement happens twice.
•A commitment slips and nobody knew until the deadline.
5. VERSION HISTORY
| Version | Date | Owner | Summary of change |
| | ____ | _____ | ___ |
| | ____ | _____ | ___ |
DISCLAIMER: This is a sample document for general information only and is not legal
advice. Have qualified US employment counsel review anything you adopt.
Working Agreement Examples That Hold Up
A clause holds up when a person could be shown to have broken it. That is the only reliable filter. Below are seven examples from the templates on this page, each paired with the reason it survives contact with a real week, because the reasoning is more portable than the wording.
Meetings
If there is no agenda posted by 5 p.m. the day before, anyone on the invite can cancel the meeting, and nobody has to justify doing it.It moves the cost of an unprepared meeting onto the person who called it, and it gives the most junior person on the invite explicit permission to act.
Response times
Chat within four hours during your scheduled hours. Email by the end of the next business day. Urgent means a phone call, not a label on a message.Most response-time anxiety comes from not knowing the number. Writing it down also stops urgent from becoming the default setting on every message.
Availability
Nobody is expected to read or answer anything outside their scheduled hours. If you send something late, write in the message that it can wait until morning.It separates the sender’s convenience from the reader’s obligation, and for employees who are not exempt from overtime it keeps evening messages from turning into unpaid working time.
Decisions
A decision that is not written down in the shared channel within one business day did not happen, and anyone can reopen it.The most expensive meetings are the ones re-litigated three weeks later because nobody recorded the outcome. This makes writing it down the cheaper option.
Commitments
If a date is going to slip, the owner says so before the date, not after. Nothing said early is ever held against you here.The second sentence is the one that makes the first one work. Without it, the rule is a trap and people stay quiet until the deadline passes.
Disagreement
Disagree in the thread once with the reason. Still open, take it to a call the same day. Still open after that, the team lead decides and writes down why.It gives an argument a finite number of moves and a named ending, which is what keeps a small disagreement from becoming a standing grudge.
Coverage
Every recurring task has a named backup, and the backup has been told they are the backup.The second clause is the whole clause. Most coverage plans exist only in the head of the person they are meant to protect.
The pattern across all seven: each one converts a value into an observable behavior and names who acts. Compare the two columns below. The left is what teams write in the first draft, and the right is what the same intention looks like once it has been made checkable.
What the first draft says
What the second draft says
We communicate openly
Decisions are written in the shared channel within one business day, including the unpopular ones
We respect each other’s time
No agenda by 5 p.m. the day before means anyone can cancel the meeting
We are responsive
Chat within four hours during your scheduled hours, email by the end of the next business day
We hold each other accountable
If a date is going to slip, the owner says so before the date, not after
We assume good intent
Disagree in the thread once, then a call the same day, then the lead decides and writes down why
We support each other
Every recurring task has a named backup, and the backup has been told
We value focus time
Nobody is expected to read or answer anything outside their scheduled hours
Two of these do more work than the rest. The agenda rule is the only line that reliably shrinks a calendar, because it hands the cheapest possible veto to whoever is least senior on the invite. And the slipped-date clause only functions with its second sentence attached: nothing said early is ever held against you. Without that promise, the rule is a trap and people stay quiet.
Teams that already talk straight will find these easy to adopt, and teams that do not will find the writing session revealing. That is not a failure of the document. It is the same signal you would get from any honest conversation about psychological safety, arriving earlier and in writing.
Running the Session That Writes It
Book ninety minutes with the whole team, print the blank template, and fill it in together in one sitting. Splitting it across several meetings is how these documents die, because the energy that carries a team through the awkward sections does not survive a two-week gap.
Everyone who does the work attends. That includes part-time people and any contractors who sit in the daily flow, since a norm they never heard is a norm that gets broken in week one. If the team is larger than about eight, draft in two groups and merge, rather than running a session where half the room says nothing.
1
Agree what the team is for
One sentence, said out loud, plus the two or three outcomes the team is judged on this quarter. Every later rule gets tested against it.
2
Fill in the numbers before the values
Response windows, meeting lengths, the agenda deadline, the review cadence. Numbers are faster to agree on than adjectives and they settle more arguments.
3
Name a decider for every recurring decision
Do this before a contested decision arrives, when nobody has a stake in the answer. Include the default for anything the list does not cover.
4
Write the disagreement path
Thread, then call, then a named person who decides and records why. An argument with a finite number of moves does not become a grudge.
5
Read it back and delete the aspirational lines
If two people could follow a line in opposite directions and both feel compliant, it is a value, not a norm. Cut it in the room.
6
Sign it and book the review
Everyone signs before leaving, the review date goes in the calendar, and one named person owns the document from that moment.
Bring the structure and let the team bring the content. This is the part founders get wrong, myself included: the temptation to arrive with a filled-in draft is enormous, and it converts the exercise into a policy rollout. If you need to set something yourself, put it in the expectations document where the authorship is visible.
The awkward sections are the valuable ones. What happens when a date slips, how we disagree, and what we owe someone new are the three that teams skip when drafting from a blank page, and they are the three that pay for the session. For distributed teams, the equivalent hard question is what has to be written down.
Two Traps Before You Write Rules About Availability
Two clauses that look harmless in a team-written document can create real exposure for a US employer: availability language that reaches outside scheduled hours, and norms that discourage people from discussing pay or working conditions. Both are easy to avoid once you know they exist.
The first is wage and hour. If your agreement asks people to answer chat within thirty minutes in the evening, that is time worked for anyone who is not exempt from overtime. The Department of Labor is explicit that work an employer suffers or permits must be counted, whether or not anyone asked for it, and the same fact sheet treats attendance at meetings and training as working time unless four narrow conditions are all met at once.
The fix takes one sentence and costs nothing: write every response window as applying during each person's scheduled hours, and state plainly that nobody is expected to read or answer anything outside them. Every template on this page is written that way. If your team genuinely needs evening coverage, that is a paid on-call arrangement to design with counsel, not a norm to slip into a team document.
Do Not Write a Norm That Discourages Pay Talk
The second trap looks even more innocent: a line asking the team to keep frustrations inside the team, or to leave compensation out of team channels. Federal labor law protects employees who act together on wages, hours and working conditions, and that protection reaches most private employers whether or not anyone is in a union (National Labor Relations Board, Concerted Activity). Keep both out of the document, add the short rights note the templates include, and have counsel review anything you adopt. This is general information, not legal advice.
Neither trap stops you from setting real standards. You can require an agenda, name a decider, and hold people to dates. What you cannot do is convert a team habit into unpaid working time, or into a rule that discourages a protected conversation. If your draft touches either, that line belongs in a reviewed policy rather than in a document the team wrote together on a Thursday.
Sign, Store, and Revisit
An agreement earns its keep when it is signed by everyone on the team, given to every new person before their first day, and reviewed on a date that was set before anyone forgot. Those three habits are the difference between a live document and a nice afternoon.
Write it in one session
Ninety minutes with the whole team and a printed blank. Fill in the numbers together, and stop at the point where every line has a name or a figure attached to it.
Share it as an onboarding step
Every new person gets the current version before their first day, alongside the handbook, and walks through it with someone in week one.
Capture the sign-off
Collect a signature from everyone on the team, including people who joined after it was written, so there is a dated record of who agreed to which version.
Review it on a date you already set
Thirty minutes every quarter, plus an immediate review whenever the team gains or loses a person, changes what it owns, or changes how it works.
The review is where most of the value sits, and it is short. Thirty minutes, four questions, and a bias toward deletion. A line the team quietly ignored all quarter should come out, because leaving it in teaches everyone that the rest of the document is optional too. Record what changed and what was removed, so the next review can see the pattern.
The agreement dies because nobody owns it
A document written in a good ninety-minute session and never opened again is worse than no document, because it teaches the team that written commitments are decorative. The fix is unglamorous: one named owner, a review date already in the calendar before the session ends, and a review log that records what got deleted as well as what got added. Deleting a line the team quietly ignored is the most useful thing a review does, because it is an honest admission that the rule never fit. Give the review thirty minutes, not an afternoon. Four questions is enough: what did we follow, what did we ignore, what broke that this should have prevented, and what has changed about the team.
Rules written by one person are policies wearing a costume
The reason a working agreement produces different behavior from a policy is that the people bound by it wrote it, argued about it, and signed it. Hand a team a finished agreement and you have written a policy with softer typography, and they will treat it accordingly. This matters most for the small business case, where the owner has strong opinions and a short calendar. My advice: bring the structure, not the content. Print the blank template, run the session, and let the team fill in the numbers. If you need to set the floor yourself on something, use the separate team expectations document, which is honest about who wrote it.
Someone new inherits a document they never agreed to
Every hire quietly changes the team, and an agreement that predates half the room stops being an agreement. Two habits fix it. Share the document before the first day, as part of the same packet as the handbook, and walk through it in week one with a real conversation rather than a signature request. Then invite the new person to challenge any line at the first review after they join. This is where a platform earns its place. FirstHR ships the working agreement as an onboarding step, captures the acknowledgment with built-in e-signature, and stores the signed version on the employee record, so the current version is the one people are actually holding. Applicant tracking is coming soon to FirstHR.
The templates above work on paper. To run this without chasing signatures, FirstHR delivers the working agreement as an onboarding step, captures each acknowledgment with built-in e-signature, and stores the signed version on the employee record through document management, so the version people signed is the version you can produce. FirstHR is an onboarding and HR platform, not a law firm, so pair it with counsel for the legal review. Applicant tracking is coming soon to FirstHR.
One last habit worth stealing. Read the agreement aloud at the first meeting after every review, which takes four minutes and does more for adoption than any amount of formatting. Teams that do this consistently end up with the kind of team culture that survives a hiring wave, because the norms get said in front of everyone rather than absorbed by whoever happened to be sitting nearby.
Key Takeaways
A team working agreement records how one team meets, communicates, decides, and handles disagreement, and the team writes it rather than receiving it.
Every line has to be something a person could follow or fail to follow on a given day; values statements cannot be broken, so they cannot be kept.
A team expectations document is the manager-written companion that sets the floor and states what the team gets back; most small teams need both.
Write response windows as applying during scheduled hours only, because availability language can create paid working time for employees who are not exempt from overtime.
Keep out any norm that discourages employees from discussing pay, hours, or working conditions with each other.
Sign it, give it to every new hire before day one, and review it quarterly with a bias toward deleting the lines nobody followed.
Frequently Asked Questions
What is a team working agreement?
A team working agreement is a short written document in which a team records how it will work together: how it meets, which channel carries which kind of message, how quickly people reply during their scheduled hours, who decides what, how commitments are tracked, and what happens when two people disagree. The defining feature is authorship. The team writes it, argues about the wording, and signs it, which is what separates it from a company policy issued from above. It is usually one or two pages, it names people and numbers rather than values, and it carries a review date. It goes by several other names, including team norms, ground rules, and a social contract. It does not override employment policies; where the two disagree, the policy wins.
What should be included in a team working agreement?
Eight things cover almost every useful version. What the team is accountable for in one sentence. How it meets, including the agenda rule and the right to decline. Which channel carries which message, with response windows tied to each person’s scheduled hours. Who decides what, written down before a contested decision arrives. How commitments are tracked, with one named owner and a date each. How disagreement is escalated and ended. What someone joining is given and by whom. And a review date with signatures. Leave out anything you cannot state as a name, a number, or an observable action. A line like we communicate openly is not a norm, because two people can follow it in opposite directions and both believe they complied.
What are some working agreement examples?
The useful examples are specific enough to be checked. On meetings: if there is no agenda posted by 5 p.m. the day before, anyone on the invite can cancel it. On messages: chat within four hours during your scheduled hours, email by the end of the next business day, urgent means a phone call. On availability: nobody is expected to read or answer anything outside their scheduled hours. On decisions: a decision not written down within one business day did not happen. On commitments: if a date is going to slip, the owner says so before the date, and nothing said early is held against them. On coverage: every recurring task has a named backup, and the backup has been told. Each of those replaces a value with an observable behavior, which is the whole trick.
How is a team working agreement different from a team expectations document?
The difference is who wrote it. A working agreement is authored by the team together and signed by everyone in it, which is why it changes behavior: people follow rules they helped write. A team expectations document is authored by the manager and states what the manager requires, what the team can expect in return, and how performance is assessed. Both are legitimate and they solve different problems. Use the expectations document when someone genuinely needs to set a floor, such as a quality bar, a turnaround standard, or an escalation rule that is not negotiable. Use the working agreement for the habits the team has to invent for itself. Most small teams end up with both, which is why the download on this page includes each one as a separate file.
Can a team working agreement create legal problems?
It can, in two specific ways worth knowing about. First, availability language. If your agreement asks people to respond within a set window in the evening or on weekends, that time can count as working time for employees who are not exempt from overtime, because federal wage and hour rules require employers to count work they suffer or permit. Write response windows as applying during each person’s scheduled hours, and say plainly that nobody is expected to answer outside them. Second, norms that discourage employees from discussing pay, hours, or working conditions with each other can run into federal labor law, which protects that activity at most private employers whether or not anyone is in a union. Keep both out of the document, and have counsel review anything you adopt. This is general information, not legal advice.
How long should a team working agreement be?
One or two pages, and shorter is usually better. The constraint that keeps it honest is that every line has to be something a person could either follow or fail to follow on a given Tuesday. Values statements are easy to write and impossible to break, so they pad the length without changing anything. If the draft runs past two pages, the usual cause is that it has absorbed material that belongs somewhere else: conduct rules belong in the code of conduct, remote work eligibility belongs in the remote work policy, and how performance is assessed belongs in the expectations document. A tight agreement with eight enforceable lines outperforms a thorough one with forty aspirational ones, because the short version is the one people can actually recall in the moment it matters.
How often should a team working agreement be reviewed?
Every quarter on a fixed date, plus immediately on five triggers. The triggers are: someone joins or leaves the team, the team changes what it is accountable for, someone changes time zone or working pattern, the same disagreement happens twice, and a commitment slips without anyone hearing about it in advance. The scheduled review only takes thirty minutes if you ask four questions: which lines did we actually follow, which did we quietly ignore, what broke this quarter that this document should have prevented, and what has changed about the team or the work. Deleting an ignored line is the most valuable outcome of a review, because a rule everyone breaks teaches the team that the whole document is optional. Record what changed and what was removed in a review log so the history is visible, and keep the signed current version on the employee record rather than in one person’s downloads folder. Applicant tracking is coming soon to FirstHR.
Do small teams really need a working agreement?
It is optional, and it pays off earlier than most owners expect, usually around the point where the team stops fitting in one conversation. Below that size, norms travel by osmosis because everyone hears everything. Past it, people start inferring different rules from the same behavior, and the disagreements that follow look like personality clashes when they are actually undocumented expectations. Writing one costs about ninety minutes. The return is fewer repeated arguments, faster onboarding because a new hire can read how the team works rather than deduce it, and a shared reference for the awkward conversation about the meeting nobody needs. Gallup measured only 49 percent of US employees strongly agreeing they know what is expected of them at work in the first half of 2026, so the assumption that everyone already understands the rules is a costly one.
