How to write joining agreements that protect your group culture

A coaching group's culture is decided in the first ninety seconds of week one and held together by the three rules you wrote before anyone arrived. The agreement is short, behavioural, and the difference between a cohort that finishes well and one that quietly drifts apart by week four.

Why do coaching groups need rules at all?

Most coaches resist writing rules because the word feels schoolteacher-ish, and most teachers resist because they have written too many in their careers already. Both groups are wrong about the document and right about the word.

What a group needs is a small, shared agreement that gives members two things: a predictable shape for the space, and a way to call out a breach without it landing as a personal attack. Without the agreement, the manager has to improvise every correction, and improvising in front of fifteen people tends to come out either too soft or too sharp.

Bruce Tuckman's 1965 model of group development — forming, storming, norming, performing — is fifty years old and still right that the norming phase happens whether you plan it or not. The choice is whether you write the norms or wait for the group to invent them under pressure, usually in week three after the first awkward post.

What should the joining agreement actually contain?

Six things, in this order, and nothing else. Anything longer than a single screen on a phone is skim-read, which means it does not exist.

1. Purpose, one sentence. What the cohort is for and what it is not for. "An eight-week accountability cohort for ten freelance writers building a regular writing practice; not a place for client work feedback."
2. Three behavioural norms. The ones members live by week to week.
3. Confidentiality commitment. One line: what is shared in the group stays in the group, including who is in the group.
4. The four breaches that lead to removal. Safeguarding risk, confidentiality breach, targeted attack on another member, and member-to-member promotion. Anything else gets a private conversation, not removal.
5. Manager's private route. How to reach you outside the group wall — a direct message, an email, a 15-minute slot.
6. Data and privacy promise. Who can see what, how long the cohort archive lives, and what happens when a member leaves.

How do you write three rules that actually hold up?

Three is the number. Two is a slogan and ten is a policy nobody reads. Each rule must pass two tests: it describes a behaviour, not a value, and a member could do it or stop doing it inside the next five minutes.

Useful examples we see hold up across coaching, teaching, and team cohorts:

• "We talk about our own week, not other people's." Stops a member naming an absent partner, colleague, or child in a way they could not defend if they were in the room.
• "We disagree with ideas, not with people." Lets disagreement happen, blocks the targeted attack version of it.
• "What is shared here stays here." Names confidentiality as a group norm, not just the manager's responsibility.

"Be respectful" fails both tests. So does "show up authentically", which is impossible to enforce and slightly mortifying to read aloud. If a rule cannot be named in a moderation conversation without sounding precious, it is not a rule, it is decoration.

Who should write the rules — the manager or the group?

The manager writes the first draft. The group is welcomed to suggest changes for the first two weeks. Then the rules are pinned and not edited again unless something serious happens.

This is the trade-off where we will take a clear position. We have watched coaches try the co-created-from-week-one approach for years, and it almost always produces a longer, vaguer document that nobody refers back to. The members do not yet trust each other enough to argue for a sharp norm; the manager hesitates to push back on a fuzzy suggestion in week one. The compromise output is the worst of both.

The opposite extreme — the manager hands down ten commandments and brooks no discussion — fails differently, by making the group feel like a regulated space rather than a shared one. The middle path, draft-then-refine for two weeks, gets both the sharpness of an experienced practitioner and the buy-in of a group that has been heard.

Consider Hannah Webb, a fictional but representative leadership coach running a 14-person manager development cohort for an NHS trust in Leeds. She arrives at week one with three drafted norms, opens the floor for ten minutes of comment, accepts one wording change ("disagree with ideas, not with people" was originally "challenge ideas not people"), and pins the agreed version at the top of the group by end of session. Two weeks of soft refinement followed; the rules have not been touched since.

How do you enforce the rules without sounding authoritarian?

Name the rule, not the person. "The third one, what is shared here stays here" lands very differently from "you broke a rule". The grammatical shift is small. The emotional shift is enormous.

Move the conversation to a private message before any public correction. A public reprimand in front of twelve people humiliates the member, chills the rest of the group for weeks, and trains everyone watching that the safe move is to post less. A short private message — name the norm, explain the impact in one sentence, ask how to put it right — resolves nine cases in ten.

By the half-term mark of any well-set-up cohort, members start naming the norms themselves. That is the moment the manager moves from enforcer to host, and the agreement starts paying back the time you spent writing it.

How does Bitir support a joining agreement in practice?

Bitir gives a group manager three surfaces that, together, make a joining agreement work without anyone having to remember it.

The pinned post is the simplest: the agreement lives at the top of the cohort, visible on first scroll, and stays there for the duration of the programme. New members joining mid-cohort see it before anything else. The pin survives archive and export, so the agreement is part of the cohort's record, not an attachment that gets lost.

The manager-only visibility toggle, covered in our post moderation guide, supports sensitive cohorts in the first two to three weeks while the agreement is still bedding in. The manager sees member posts, the rest of the group sees nothing, and the norms get used in private replies before they get used in public ones.

The two-tap removal, with a private note to the member explaining which norm applied, closes the loop on the four removable categories. The member sees the note; the group sees nothing, because the post was already gone before they refreshed. The same logic that runs underneath our member privacy guide applies here: the manager owns the controls, the member owns the conversation, the platform stays out of the way.

What Bitir does not do is decide what your three rules should be. That is the editorial judgement of the person running the group, and no setting can replace it.

Related reading: how a Bristol psychologist drafts the joining agreement for six anxiety support groups, and post moderation in coaching groups: why it matters and how to do it.