What a working agreement actually is
New teams often rush straight into the work.
There is a project, a deadline, and a shared chat, so it feels like the setup is done.
Then the first disagreement arrives: someone expects a reply within the hour, someone else checks messages once a day, and nobody knows who decides when the group is split.
A working agreement is the short document that prevents exactly this.
The question is not whether agreements are useful in theory, but whether your team should write one now, before the work starts, or wait until problems appear.
A working agreement is a written record of how your team communicates, meets, decides, and escalates problems.
It is not a contract and not a process manual.
Atlassian describes it as a team-level document covering communication channels, meeting plans, and an escalation process Atlassian Team Playbook.
It is built from each member's preferences and the challenges the team already faces.
The key word is written.
Verbal agreements fade.
When the rules live in a shared document, a new freelancer, a contractor, or a volunteer who joins later can read them instead of guessing.
Why the timing matters
There are two natural moments to create an agreement: at the very start of a collaboration, or after the first painful misunderstanding.
Both can work, but they produce different documents.
An agreement written before the work starts is preventive.
It captures expectations while everyone is still optimistic and nothing has gone wrong yet.
An agreement written after a conflict is corrective.
It tends to be sharper about the actual failure, but it can also feel like an accusation, because someone's behavior prompted it.
Atlassian's project kickoff guidance places this conversation at the beginning of a project Project Kickoff Play.
That is when the team aligns on purpose, roles, and how they will work together.
The reasoning is simple: clarifying roles and setting norms early improves communication, coordination, and trust, while unclear requirements lead to rework later.