Managing roles in a coaching group: leader, helper, member
A group coaching programme runs on three roles: a manager who owns the goals, assignments and moderation; a helper who supports the group without full admin control; and members who do the work. Meredith Belbin's team-roles research, set out in Management Teams: Why They Succeed or Fail (1981), identified nine distinct contributions in effective teams — the practical lesson for a coaching group is narrower, but it starts in the same place: clarity about who does what.
TL;DR
Most coaching groups need exactly three roles. The manager (owner) sets goals, posts assignments, runs check-ins, and moderates. A helper is a trusted co-leader or engaged member given a narrow set of extra rights — usually moderating and posting — without billing, settings, or member-removal access. Members participate, track their own goals, and post. Keep the count low: in groups under 30, a fourth bespoke role almost always causes more confusion than it solves. In Bitir you assign these in the role editor, where every capability is a separate toggle, so a helper gets exactly what the job needs and nothing more.
What are the different roles in a group coaching programme?
Three roles cover nearly every group: manager, helper, member.
The manager is the person whose name is on the programme. They create the group, set each member's goals, post the weekly assignment, open and close check-ins, moderate posts, manage the joining agreement, and control settings and any billing. In most small programmes the manager is the coach, the teacher, or the team lead, and there is one of them.
The member is everyone the programme is for. A member posts and comments, tracks their own goals, completes assignments, answers check-ins, and sees the shared group space — and, crucially, sees only their own private progress, not anyone else's. That last point is what makes the group safe enough for people to be honest in it.
The helper sits between the two. A helper is a co-coach, an assistant teacher, or a trusted member given a defined slice of the manager's powers — enough to keep the group running when the manager is not looking, and no more. The hard part of role design is not naming these three; it is being disciplined about what the helper can and cannot touch.
Why should more than one person have admin rights?
Because a single admin is a single point of failure.
If only one person can moderate, then the night a post needs removing is the night that person is asleep, ill, or on a flight. A group that has to wait twelve hours for the one admin to wake up is a group that has, for those twelve hours, no one looking after it. For anything safeguarding-adjacent — a youth group, a school cohort, a therapy-adjacent wellness programme — that gap is not acceptable.
There is a softer reason too. A manager who tries to be the only voice in the group burns out, and the group learns to wait for them rather than help each other. A well-chosen helper models the behaviour you want: someone who welcomes a new member, answers an easy question, and pins the thing everyone keeps asking about.
We'd argue for one helper per eight or so members as a working ratio. A 12-person cohort is fine with the manager alone or with one helper; a 40-person institution split across classes wants a helper (often the class teacher) per group, not one overworked director moderating everything.
What can a helper do that a member cannot?
A helper does a named subset of the manager's job, and the discipline is in the word subset.
A sensible helper can: pin and remove posts, welcome and orient new members, post announcements, and answer questions on the manager's behalf. A helper should not be able to change group settings, see billing, remove members, or edit other people's goals. Those are owner-level decisions, and spreading them around is how a group ends up with two people quietly disagreeing about who is in charge.
This is exactly where a per-capability model beats a fixed tier. In Bitir's role editor, every right is a separate toggle — moderate posts, post announcements, manage members, edit goals, view settings — so you build the helper role to fit the actual job rather than choosing from "member" or "co-owner" and hoping one of them is close enough. A tutoring agency might give a senior tutor moderation and announcements but withhold member management; a sports club might do the opposite.
How do you avoid giving members too much or too little control?
Set the floor low and raise it on purpose.
The right member default is: participate freely, control nothing structural. Post, comment, track your own goals, answer check-ins, see the shared space. That is enough to do the work and to feel like a full participant. It is also the level that keeps the group honest, because no member can remove another's post or peer into another member's private progress.
Too much control breaks safety. The moment any member can see everyone's goals or delete posts, people stop writing the honest, slightly embarrassing check-in that coaching depends on. Too little control breaks engagement: a group where members cannot post is not a coaching group, it is a newsletter with extra steps.
The decision you actually face is not "how much power do members get" but "who, among the members, earns the helper role, and when." Promote sparingly, and promote for behaviour you have already seen — the member who naturally answers others' questions is a better helper than the one who asks for the title.
When should roles change during a programme?
Roles are not fixed for the life of a group. The two moments worth planning for are the mid-programme promotion and the post-programme handover.
Maya Brennan, a career coach in Cardiff, runs a 12-week cohort of 11 people. For the first three weeks she keeps every right to herself while she learns the group. Around week four she promotes one member — usually whoever has been quietly welcoming newcomers and answering the practical questions — to helper, with moderation and announcement rights only. By week eight that helper is running the welcome ritual for any latecomers and Maya is moderating far less.
Coaches we speak to often say things like: "I resisted handing anything over for years, and the day I finally made one member a helper, the group got warmer, not messier. It turns out people want to look after the thing they're part of."
At the end of a programme, if a cohort wants to keep meeting informally, the cleanest move is to hand the manager role to a member who will carry it on, strip the structural rights you no longer need to hold, and step back to member yourself. Bitir's two-tap removal and capability toggles make both the promotion and the handover quick, so the role structure can follow the group's life rather than freeze at week one.
Questions we're asked about coaching group roles
What are the different roles in a group coaching programme?
A group coaching programme usually runs on three roles. The manager (also called leader or owner) sets goals, posts assignments, runs check-ins, moderates posts, and controls settings. The helper is a trusted co-leader or engaged member granted a narrow set of extra rights, typically moderating and posting, without access to billing, settings, or member removal. The member participates, tracks their own goals, completes assignments, and posts. For groups under 30 people, those three roles cover almost every need; adding a fourth bespoke role usually causes more confusion than it solves.
Should a coaching group have more than one person with admin rights?
Yes, once the group is large enough to feel the manager's absence. A single admin means that if that one person is ill, on holiday, or asleep when something needs moderating, the group has nobody to act. Granting one helper limited rights removes that risk without diluting control. The rule of thumb that works in practice is one helper per eight or so members, and never give a helper more than they need for the specific job you have asked of them.
What can a helper do that a member cannot?
A helper can do a defined subset of what a manager does, and nothing more. In a typical setup a helper can pin and remove posts, welcome new members, post announcements, and answer questions on the manager's behalf. A helper should not be able to change group settings, see billing, remove members, or edit other people's goals. In Bitir, each of these is a separate capability in the role editor, so you grant exactly the ones the helper needs and leave the rest off.
How do you avoid giving members too much or too little control?
Start members on the lowest set of rights that still lets them do the work — post, comment, track their own goals, answer check-ins — and add rights deliberately rather than by default. Too much control breaks the safety that makes a group honest; too little turns a coaching group into a broadcast channel. The right default is participate freely, control nothing structural.
Build the role structure your group actually needs
Bitir's role editor turns every permission into a separate toggle — moderate, announce, manage members, edit goals — so a helper gets exactly the rights the job needs and nothing more. Promote and hand over in two taps.
Start Your Group