Building a Coaching Team You Can Actually Trust: A Delegation Playbook for Small Clubs

She had been running the club for three years. Four nights a week — Monday, Tuesday, Thursday, Friday — plus the occasional Saturday grading or trial day. It had grown from eleven members to sixty-three, which was genuinely something to be proud of. The problem was that every single operational decision still ran through her.

She took the register. She handled the cash at the door. She replied to the parent messages on Tuesday morning asking whether a child who had missed last week needed to catch up on anything. She chased the overdue fees. She booked the next grading date with the venue. She sent the monthly newsletter.

She had two coaches who were excellent on the mat. They were also excellent at showing up for a session, delivering a great class, and then going home. They did not have the system access, the context, or the confidence to do anything else. That was not their fault. They had never been given the tools.

She wanted a Saturday off. The first one in three years. Her plan was to ask her senior coach to cover. But as she thought through what that would actually require — the register, the cash, the parent queries that might come in, the edge cases — she realised she did not trust anyone to handle it.

Not because her coaches were untrustworthy people. Because she had never built a system that made delegation possible.

The bottleneck is not recruitment

This is the mistake most small club owners make when they feel the pressure of running everything themselves. They think the answer is finding more people. Another assistant, another helper, a more capable senior coach.

More people do not solve a delegation problem. A delegation problem is a systems problem. If the system requires the owner to be present for every decision, adding more people just means more people waiting for the owner.

The fix is designing a system where different people have different levels of access, accountability, and authority — and where everyone understands what they are responsible for and what they are not.

That sounds corporate. It is not. In a small club, it is a matter of deciding: who can take the register? Who can handle the cash? Who can message parents? Who can change the session schedule? The answers do not need to be elaborate. They need to exist.

The four levels of authority

Think about club operations as four concentric rings, from least to most authority.

Level 1 — Observe only. This person can see what is happening but cannot change anything. A parent observer, a prospective coach doing a trial session, an external auditor. Read access, nothing more. In most club management systems, this is not a formal role — observers simply do not have accounts.

Level 2 — Take the register. This person can mark attendance for a session. They can see who is expected, mark who turned up, and record who was absent. They cannot see payment information, send messages to parents, or change any settings. This is the simplest delegation you can make, and it is often the most impactful — handing register duty to a trusted parent or junior coach frees you to run the warm-up, greet new members, or manage an issue at the door.

Level 3 — Take the register, handle cash, and send messages. This person can do everything in Level 2 and additionally: record fee payments, send a message to parents before or after a session, and see basic member contact information. This is an assistant coach role. They have enough access to run a session operationally without you, but they cannot change prices, add or remove members, or access anything sensitive.

Level 4 — Full coaching authority. This person can do everything in Level 3 and additionally: add new members to the club, enrol members in classes, manage the waiting list, view financial summaries, and in some configurations set session details. This is a full coach or studio manager. They are trusted with the operational substance of the club.

Above Level 4 sits the Owner or Admin role — someone who can do everything a coach can do, plus change club settings, manage billing, and in the case of an Admin role, do everything short of deleting the club itself.

Most small clubs need only two or three of these levels in active use. The point is not to create bureaucracy. It is to have a clear answer to the question “what can this person do?” for every person on your team.

Starting with the register helper

The register helper pattern is the lowest-risk entry point for delegation, and it is where most club owners should start.

A register helper is typically a trusted parent — someone who has been with the club for at least a year, whose child is a long-standing member, who shows up reliably and is organised. They get access to the attendance system for a specific session. They can see the member list and mark attendance. That is it.

The club owner sets this up in five minutes. The register helper gets a login, sees only what they need to see, and on the nights when the owner is teaching or dealing with a grading situation, the register is still taken correctly.

Why does this matter? Because accurate attendance is the foundation of almost everything else. Parents calling in an absence need confirmation it was recorded. The register is the audit trail for who was at a session. Insurance documentation in the event of an incident requires a record of who was present. None of this happens reliably when it depends on the coach keeping a mental note between demonstrations.

The register helper pattern also builds confidence — yours and theirs. If the trusted parent handles two months of registers without incident, you have a track record to build on. That track record is the basis for giving them more.

Promoting a register helper to assistant coach

The promotion from register helper to assistant coach is a decision to trust someone with parent communication and payment handling. These are materially different levels of access.

Parent communication means they can send a group message saying “next Thursday’s session is moved to 7pm” or “children should bring water for the grading warm-up.” It also means they are the first point of contact if a parent messages in about an absence. You want to be confident they will handle these interactions in a way that reflects well on the club.

Payment handling means they can record that a parent paid cash at the door, or mark an invoice as received. It does not mean they can see your full financial history or change your payment settings. But it does mean that if a payment is recorded incorrectly, it affects your accounts.

Before making this promotion:

• Have an explicit conversation about what the role involves. Write it down.
• Make sure they have read your club’s communications style — how you address parents, what tone you use, what information you share and do not share.
• Run a session with them in the assistant coach role while you are present. Watch how they handle it. Debrief afterwards.

This is not a test. It is training. The goal is to bring them in with context, not throw them in and hope.

Promoting an assistant to full coach

A full coach is someone who can operate the club in your absence. They can register new members, manage enrolments, send substantive communications, and view the financial position of their sessions.

This is a significant delegation. Before making it:

DBS and safeguarding first. A full coach in a club with under-18 members must have a current enhanced DBS and current safeguarding training. This is non-negotiable, and it should be documented in your records before they operate in this capacity.

Access to information brings accountability. A full coach will see member contact details, medical notes, fee histories. They need to understand the data protection obligations that come with this. Run them through your club’s GDPR position — who can see what, what information stays within the club, how you handle requests from parents. This does not need to be a formal training programme. It needs to be an explicit conversation.

Define their scope. A full coach at Tuesday’s advanced session does not necessarily need access to all members across all sessions. Most club management systems allow you to scope a coach’s access to specific sessions or groups. Use this. A coach who only sees what they need to see is a coach who is less likely to inadvertently misuse information they did not need.

The audit trail matters. Every action taken by a coach — attendance marks, payment records, messages sent, enrolments added — should be logged against their account. If there is ever a dispute about what happened in a session, the audit trail is how you establish the facts. A system where actions are attributed to accounts, not to a generic club login, is materially better for this purpose.

The Admin role

An Admin has almost every capability the Owner has, with one specific exception: they cannot delete the club or transfer ownership. This is the role for someone who genuinely runs operations on your behalf — a studio manager, a head coach who handles all of the administrative work, a co-founder who is equal in operational authority.

Admin access should be given to very few people. In most small clubs, the answer is one: the Owner, and possibly a single trusted deputy.

The reason to be conservative with Admin access is not distrust. It is clarity. When something changes in the club — a setting, a price, a template — you want to be able to identify who changed it. When every team member is an Admin, every change is equally attributable to everyone, which means every change is attributable to no one.

One practical rule: if your entire team has Owner or Admin access because “it was easier to set everyone up that way,” that is not delegation. That is abdication. Every person should have the minimum access they need to do their job well.

Why role permissions matter for safeguarding

The safeguarding argument for role-based access is under-discussed.

An audit trail tied to individual accounts answers a specific question: who had contact with a specific child, and when? If a safeguarding concern is raised about an incident that occurred during a Wednesday session three months ago, you need to be able to say who was listed as the responsible coach for that session, who marked the attendance, who sent messages to that child’s parent, and whether any concerns were logged at the time.

A system where actions are taken under individual accounts, and those actions are timestamped and retained, answers all of these questions. A system where two coaches share a login answers none of them.

This is not about assuming wrongdoing. It is about having the evidence infrastructure that a safeguarding review or insurance investigation will require. The audit trail is your protection as much as it is the club’s.

Mistake patterns to avoid

Giving everyone Owner access because setup is faster. This is the most common mistake. When everyone is an Owner, nobody has defined authority and everyone is responsible for everything. The club runs on whoever is most conscientious on a given day — which is usually the original owner, right back where they started.

Not removing access when someone leaves. A coach who left six months ago should not still have a login with their session-level access. Former coaches are not typically malicious, but an active account for someone who no longer has a relationship with the club is a security and data protection risk. Run a quarterly review of active accounts and remove access the day someone’s role ends.

Not training before delegating. Handing over access without handing over context is setting someone up to make mistakes. A 30-minute walkthrough of the system, specific to the role you are giving them, covers the scenarios they will encounter. The alternative is learning by error, which is more expensive for everyone.

Creating a role without a conversation. Access without context is a problem. If you add someone as an assistant coach and never tell them what that means, you cannot be surprised when they handle a situation differently than you would have. Write down what the role is, what decisions they can make independently, and what they should escalate to you.

Building confidence to take that Saturday off

The club owner who wanted a Saturday off did eventually take one. It took her about eight weeks from the decision to the day.

She started by setting up her senior coach as a register helper for two sessions. It went well. She then gave him assistant coach access and walked him through the payment recording workflow. She sent a few test messages through his account to see how they landed. She was present for a session where he ran operations solo, and they debriefed for 20 minutes afterwards.

By the time the Saturday came, she knew exactly what he could handle, because she had seen him handle it. He knew what to escalate because they had discussed it. She had her phone with her, but she did not need to use it.

That is delegation. Not trusting blindly, and not micromanaging. Building a system where the right people have the right access, the right training, and the right understanding of their role.

---

Adminished’s role and permissions system supports register helpers, assistant coaches, coaches, and admins — each with scoped access appropriate to their level. Add your team, set their roles, and take a Saturday off. See team roles and permissions.