Sports club team management: cancellations, logged hours and the availability chase

A club is not one team. It is several overlapping ones, with different contracts and different levels of obligation, sharing the same rooms and the same hours.

A mid-sized club runs with two or three salaried staff, a dozen coaches paid by the session, a reception rota, maintenance, a kiosk on match days, and volunteers whose availability depends on when their own child plays. A salaried receptionist is expected to work the shift they were given. A freelance coach is offering availability, not accepting an instruction. A volunteer is doing the club a favour and can withdraw without consequence.

Standard scheduling tools assume one contract type and one authority relationship. Clubs have neither, and demand is not flat either: term time and holidays look nothing alike, competition weekends double the staffing need for two days, and a single school holiday can invalidate a rota built on a Sunday evening.

The visible cost is the session. The real cost is the chain reaction.

Someone has to work out who is qualified for that age group, who is not already working, who is not injured or away, and who has not been asked three times this month. That information rarely sits in one place. It lives partly in a spreadsheet, partly in the head of the person who has been there longest, and partly in a group chat where the answer scrolled past two weeks ago.

Then comes the chase: five or six messages, two calls, one person who accepts if they can leave early. Then comes the part nobody counts. The replacement has worked two unplanned hours, and whether that gets recorded depends on two people remembering to mention it.

The clubs that suffer most from cancellations are not the ones with unreliable coaches. They are the ones where every replacement has to route through one person’s phone. When the manager is the only channel a shift can move through, the manager becomes the bottleneck at the exact moment they have least time.

Building the schedule takes an hour or two. Collecting the information needed to build it takes days.

Coaches are students with exam periods, professionals with day jobs, parents with school runs. Availability changes month to month and arrives in whatever form suits the sender: a text, a comment after training, an email with three dates and a maybe, a verbal "I told you I can’t do Thursdays" that may or may not have happened.

So the administrator becomes a collection agent. Send a request, a third reply. Send a reminder, another third. Chase the rest individually, and by then the picture has changed because someone picked up a shift at their other job. A rota built on incomplete availability is a rota that will need fixing later, usually at 17h40 on a Tuesday.

Availability management works when the information flows the other way: people declare when they cannot work, in one place, before the schedule is built, and it stays there. That removes most of the chasing, and it removes the "I did tell you" argument, because there is now a record either way.

A coach says they worked 34 hours last month. The club has 29. Neither party is lying.

The five hours are made of things nobody schedules: the session that ran over, the setup and clear-up either side, the Saturday tournament agreed verbally in a corridor, the trip to buy cones. Scheduled hours describe an intention. Worked hours describe what happened, and in a club the work spills at both ends of every session.

The problem is that the gap is usually discovered at month end, in a conversation, with no evidence on either side. That leaves two bad options: pay what is claimed and lose control of the wage bill, or dispute it and damage a relationship with someone the club depends on.

Tracking logged hours fixes this, and for a club it almost never means a clocking terminal on the wall. Coaches move between a pitch, a hall and an away venue, so a fixed punch-in point is useless to them. What works is that the person who did the work records what they actually did, at the end of the session, on their phone. The manager sees planned and worked side by side and can question a difference the same week rather than four weeks later. Most hours disputes disappear at that point, not because anyone is caught out, but because there is a shared version of events.

There is a compliance dimension too. Employers must keep working time records for employed staff, and in Switzerland those records have to be retained for five years. A chat history and a mental note do not meet that standard.

Almost every club runs on one, which is what makes it dangerous. A group chat carries information but holds no state. Nobody can look at it and answer "who is working Saturday" without reading backwards. Requests have no status: a time off request answered with a thumbs up is not approved in any useful sense, and both parties will remember it differently.

It also has no boundaries. Staff get messages on days off and at midnight, and session-paid coaches start to feel permanently on call for work they are not being paid for. That is one of the quieter reasons clubs lose good people.

The clubs that have this under control are not better organised by temperament. They share four habits, and none of the four requires enterprise software.

What it does require is that the information stops living in one person’s memory and one group chat.