AI for Sports Clubs: Fixtures, Renewals and Other Committee Admin

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI for Sports Clubs: Fixtures, Renewals and Other Committee Admin.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI for Sports Clubs: Fixtures, Renewals and Other Committee Admin.

Give AI three committee jobs and keep everything else with named people: turning the league's fixture list into team calendars and messages, running renewal reminders from a membership sheet, and drafting agendas and minutes from the secretary's notes. Start with free tools, and keep names, contact details and children's data out of every prompt.

A volunteer committee has no spare hours, which is the whole case for this and also its main risk. A tool that saves six hours but leaks the junior membership list is a bad trade. So each job below is set up so the assistant sees structure and wording, never the people: it writes the template, and you merge the names in your own sheet.

Follow me on Instagram@sagnikteaches

Three jobs, and what stays with named people

The three jobs share two features. They repeat every season, and a mistake in them is annoying rather than harmful: a wrong kick-off time, a clumsy reminder, a misworded minute. That makes them good candidates. Anything that could affect a person's safety, money or standing in the club is not on the list, and stays with a named officer:

Connect on LinkedInSagnik Bhattacharya
  • Safeguarding concerns and welfare. Nothing from a concern, a report or a conversation with a parent goes into a prompt.
  • Discipline and complaints. Written by the officers who handled them, in their own words.
  • Money decisions. The treasurer approves refunds, hardship places and bank changes. An assistant may format a report; it never decides.
  • Selection and team decisions. Who plays is a coaching and fairness question, not a drafting one.
  • Anything with a child's photo, medical or dietary details.

Performance analysis, scouting and fan-engagement tools all exist. None of them helps with the Sunday-night job of working out who is playing where, and none of them chases a late subscription, which is why the committee's paperwork is the better place for a volunteer club to start.

Subscribe on YouTube@sagnikteaches

Free tools first: what a club can do at no cost

Most of what follows runs on free accounts. The table lists the limits worth knowing, as of October 2026, so a stalled upload is not a surprise. Free-plan limits change often, so confirm each one on the vendor's own page before you build a routine on it.

JobFree toolsLimit to knowWhen to pay
FixturesA free chat assistant, Google Sheets, Google CalendarChatGPT's free plan allows three file uploads a day, so paste the fixture text rather than uploading the PDFRarely
RenewalsGoogle Sheets plus a free email planMailchimp Free: 250 contacts, 500 sends a month, no scheduling or automation. MailerLite Free: 250 subscribers, 2,500 emails, 3 automations of 5 steps.When members pass 250, or you need scheduling
MeetingsGoogle Docs, a free chat assistantNo recording needed; typed notes are enoughRarely
Volunteer sign-upsGoogle Forms, or a free sign-up sheetWaitlists on one popular sign-up tool start on a paid tierOnly if a waitlist is essential

Check whether the club qualifies for nonprofit pricing before paying for anything. Google Workspace for Nonprofits lists a $0 edition with Gmail, Drive, Docs, Sheets, Calendar and Forms, and Google has offered the Gemini app to nonprofit accounts at no extra cost, so check what your edition includes when you apply. OpenAI lists ChatGPT Business Standard seats for nonprofits at $8 a user a month on annual billing, and Anthropic lists Claude Team for nonprofits at $8 a user a month with a two-seat minimum, both through an eligibility check. Eligibility rules vary and many sports clubs will not qualify, so treat these as worth a ten-minute check, not a plan.

Member data: what never goes into a chat

A membership list is personal data about adults and, in most clubs, about children. The rule that makes everything else workable is simple: the assistant gets structure, categories and counts, and never the people. Names, email addresses, phone numbers, addresses, dates of birth and anything medical, dietary or safeguarding-related stay in your own sheet, where you merge them into the finished messages yourself. Fixture lists published by a league and your own constitution are public or club documents, and are fine to paste.

Consumer chat plans let users switch off the use of their chats for model training in privacy settings, and business plans do not train on your content by default. That helps, but it is a second line of defence. Data-protection duties for a club that holds member and children's records vary by place, so ask your governing body or a data-protection adviser what applies to you. Then write the committee's answer on one page, to be reviewed at each annual general meeting (AGM):

[CLUB NAME] AI RULES - agreed [date] by the committee, reviewed each AGM

1. We may paste: league fixture lists, our constitution and policies, draft notices,
   anonymised counts (for example "38 adult members unpaid").
2. We never paste: names with contact details, dates of birth, addresses, medical or
   dietary information, safeguarding notes, bank details, or photos of children.
3. Member lists are handled in the club's Google Sheet using member IDs. The assistant writes
   the template; the membership secretary merges the names.
4. Nothing generated is sent to members until a second officer has read it.
5. Everyone uses their own login. Prompts and templates live in the club's shared drive,
   not in a personal chat history.
6. Safeguarding, discipline and money decisions are never delegated to an assistant.

The fifth rule matters more than it looks. Committees change every year, and a chat history that holds the renewal wording and the fixture format goes with the volunteer who left. The tutorial on who owns AI chat history when someone leaves explains why prompts belong in a shared place from day one.

Job 1: from the league's fixture list to a team calendar

The league publishes fixtures as a PDF, a web page or a spreadsheet, and someone then retypes them into a team chat. That someone can paste the fixture text into an assistant and get a clean table, then a calendar file and the messages. This is the safest of the three jobs because a fixture list is public. A prompt, with the league text pasted below it:

Below is my club's fixture list pasted from the league's site. Convert it to a table with columns:
Team | Date | Start time | Home or away | Opponent | Venue | Meet time (45 minutes before start) | Notes.
Keep any fixture marked TBC or rearranged as "CHECK" in Notes. Do not guess missing times or venues.
Then list any clashes where one team plays twice on the same day, or two teams use the same
venue at the same time.
[paste fixture text]

Treat the table as a draft. Check three fixtures per team against the league's own page, and look twice at any start time near the weekend the clocks change, because that is an easy place for a time to go wrong. A realistic slip is a PDF with merged cells, where the assistant puts the away venue from one row against the next team. Spot-checking three fixtures per team catches this, and the "do not guess" line stops it from filling gaps with plausible venues.

Next ask for a file that members can import into their calendars. Google Calendar's import help asks for a header row in English with at least Subject and Start Date, and the other columns are optional. An example of what to request, with illustrative fixtures:

Subject,Start Date,Start Time,End Date,End Time,Location,Description
U12 v Opponent A (home),03/13/2027,10:30 AM,03/13/2027,11:30 AM,Sports Hall A,Meet 9:45 AM
U14 v Opponent B (away),03/13/2027,12:00 PM,03/13/2027,1:00 PM,[away venue],Meet 11:00 AM
Seniors v Opponent C (home),03/20/2027,2:00 PM,03/20/2027,3:30 PM,Sports Hall A,Meet 1:15 PM

Google's own example writes dates month first (05/30/2020), the layout used above. Import one event first and check it lands on the right day before you import the rest, because a date such as 03/04 reads as March to one person and April to another, and the assistant may have kept the league's own date order without converting it. Events imported from a CSV arrive as separate one-off events, not repeating series, which is fine for a fixture list but worth knowing if a coach hopes to edit them as one.

Import the file once, into a separate calendar for each team, and have members subscribe to that calendar rather than importing the file themselves. Google Calendar lets you create extra calendars and share them by email or by link. A file imported by forty parents becomes forty private copies, and when a match moves, every copy is wrong; with one shared calendar, the fixtures secretary edits the event once. Calendar apps that subscribe by link refresh on their own schedule, so a same-day postponement still needs the message below.

Availability asks, postponements and the match-day rota

Once the table exists, the assistant writes the messages. The availability message goes out each week, with a placeholder for the team and a single question:

[Team] v [opponent], [day] [date], meet [time] at [venue]. Please reply YES or NO by [day, time]
so we can pick the squad. If you are not sure, reply MAYBE and we will check with you on [day].

Postponements need a second template, because weather is the usual cause and the message has to be fast and clear: "[Team] match on [date] is postponed because of [reason]. The new date is not yet set. We will message again by [time]. Please do not travel until you hear from us." The decision to postpone, and any safety call such as lightning or a waterlogged surface, stays with the officer on duty or the match official. The assistant only writes what follows from that decision. For a longer look at bookings and pitch clashes, the tutorial on pitch and court hire without double-booking covers the venue side.

The match-day rota, for refreshments, scoring, setting up and clearing away, is a lookup problem the assistant handles well. Give it the list of volunteer slots and a list of volunteers by ID or initials, and ask for a rota with two rules: nobody is on more than twice in a month, and nobody does consecutive weekends. Then read it as a human, because it will not know that one family cannot do mornings. The sibling tutorial on volunteer sign-ups and rota reminders shows how to collect availability with a form so the assistant does not have to guess.

Job 2: renewals that chase themselves politely

Renewals are a bigger saving than fixtures, though most of the saving comes from the mail merge and the tracking sheet, not from the AI. The assistant's share is the wording and the structure: it writes the stages, adapts them for adults, parents and families, and gives you a tone that sounds like a person at the club. The sheet does the rest.

Set up the sheet first, one row per member: member ID, first name, email, category (adult, junior, family), paid this season (yes or no), and last reminder sent. When you ask for wording, give only the categories and the stages:

StageWhenPurposeWho sees it
1Six weeks before the seasonAnnounce renewals, fees, how to pay, the deadlineEveryone due to renew
2Two weeks beforeGentle reminder with the same detailsMembers who have not paid
3Due dateShort, plain: "Your membership runs out today"Members who have not paid
4One week afterA personal note from the membership secretaryMembers who have not paid, sent by a person
Write four renewal emails for a volunteer-run club for these categories: adult, junior (addressed to
the parent or guardian, never the child) and family. Stage 1: six weeks before the season, stage 2:
two weeks before, stage 3: on the due date, stage 4: one week late. Under 120 words each. Friendly
and plain, no guilt, British English. Use these placeholders only: [first name] for adults, [parent
first name] for junior and family emails, [season], [amount], [deadline], [how to pay], [reply-to name].
Mention hardship help only as: "If the fee is a problem, reply and [name] will talk to you in confidence."

Notice the separate placeholder for the parent's first name and the instruction never to address the child. A first draft of a junior reminder can easily begin "Hi [first name], it's time to renew your membership!" with the child's name merged in. The fix is the line in the prompt, and a check before sending: preview three junior emails and read the greeting. Merge in your sheet or in your email tool's merge feature, and send stages 2 to 4 only to members still marked unpaid.

A quick sum shows whether a free email plan copes. For 140 members, stage 1 is 140 emails; if 60 are still unpaid at stage 2 and 40 at stage 3, that is 240 sends spread over about six weeks, inside Mailchimp Free's 500 a month and its 250-a-day cap. Stage 4 goes from the membership secretary's own inbox, so it never touches the plan. Mailchimp's free plan has no scheduling, so put the three send dates in the committee calendar and name the officer who presses send on each.

The same sheet reconciles payments. Export payments from the bank or payment tool with a member reference, and ask the assistant to write a lookup formula that marks each row as paid, without giving it the export itself. For a club of 140 members that is an hour of setup, then ten minutes per week in the renewal month. Keep the treasurer, not the assistant, as the person who decides whether a late payment or a part-payment counts.

Do not publish lists of non-payers or message them as a group. Stage 4 should read like a person wrote it, because a person did. The tutorial on a sports club treasurer's report in plain English covers the money side that sits next to renewals, and a player and parent code of conduct makes a useful first attachment to a renewal email.

Job 3: agendas, minutes and an action list

The third job is the least glamorous and still takes a large share of a committee's hours. Agendas are built from last meeting's open actions plus new items, and minutes are a faithful short record of what was decided and who does what. Both are well suited to an assistant working from the secretary's own notes, because it never has to know anything the secretary did not write.

Here are the action points from our last meeting and the new topics for this one. Build an agenda
for a 90-minute committee meeting: apologies, minutes, matters arising (open actions with owners),
then the topics, with a suggested time for each, then any other business and date of next meeting.
Open actions: [list]. New topics: [list]. Do not add topics I did not give you.

For minutes, the secretary types short bullets during the meeting and asks for a standard format afterwards. The key instruction is that the assistant adds nothing:

Turn these notes into minutes. Format: attendance, decisions (numbered), actions (what, who, by when),
and matters for next time. Use only what is in the notes. If a decision or owner is unclear, write
"UNCLEAR: confirm with [secretary]" rather than filling it in. Do not use "agreed to buy" unless
the notes say buy.
NOTES: nets - look at prices, Sam to ask 3 suppliers; fees - keep same for juniors, adults up $5?;
AGM date 14 Sept?

That last instruction exists for a reason. A common slip is for an assistant to turn "nets: look at prices" into "The committee agreed to purchase new nets", which overstates a decision and could commit the club's money in the minutes. The "UNCLEAR" rule exists for the same reason: the fee note has a question mark, and a careless summary would present it as settled. A good result lists the fee as UNCLEAR, shows "look at prices" as an action for Sam, and flags the AGM date as unconfirmed. The chair then approves the minutes at the next meeting, and that approval is the real check. The tutorial on whether a note-taking tool can write board minutes safely covers recording and transcription, which a small committee can skip.

Keep a simple action tracker in the shared sheet: action, owner, due date, status. Before each meeting, ask the assistant to list overdue actions by owner and draft a one-line reminder for each. For an AGM notice, paste the relevant clause of your constitution and ask for a notice that meets it, then have an officer check the wording against the clause. The assistant does not know your constitution unless you give it, and the notice period is a legal and procedural question, not a drafting one. A grant application is a fourth possible job, though it needs more care; what funders expect in a sports club grant application goes through it.

One season in numbers: a 140-member junior club

Take a volunteer-run junior basketball club with 8 teams, 140 members, five committee officers and a 22-week league season. The figures below are illustrative and come from the committee estimating its own time. Time yours for a month before you trust any estimate, including these.

JobVolumeMinutes beforeMinutes with AISaved
Fixtures22 weeks550 (25 a week)220 (10 a week)330
Renewals140 members840 (6 each)175 (30 to draft, 40 for two chase batches, 105 for 35 replies at 3 each)665
Meetings8 meetings1,040 (130 each)440 (55 each)600
Total2,4308351,595

That is 1,595 minutes, about 27 volunteer hours a season, or roughly five hours for each of the five officers. The cost is zero on free tools. Two honest notes go with it. First, much of the renewals saving would come from a mail merge and a tracking sheet even without an assistant; the AI shortens the writing and the fixing, not the sending. Second, the minutes saving is real but depends on the chair approving them; if that step is skipped, the saving is a risk.

Other clubs will look different. A running club has no fixtures and its time goes into renewals and race-day volunteers. A tennis club's biggest load is court bookings and membership categories, which is where dedicated club software starts to earn its fee. A swimming club's galas add entry forms, lane lists and parent messages. The three jobs above still apply; the proportions change.

When to pay, and who owns the account

Stay on free tools until a specific limit blocks a job, and name the limit before you ask the committee for money. Three signs are enough: uploads keep being refused on a job where pasting text will not work, the member list has passed the free email plan's contact cap, or two or more volunteers need to share the same prompts and files. A paid individual plan lists at about $20 a month, so a nine-month season is about $180. If that removes a blocker that costs the committee more than a few hours a month, it is easy to justify. If it is for convenience, it is not.

On ownership, give each volunteer who uses an assistant their own login, because both OpenAI's terms and Anthropic's consumer terms bar sharing login details. Hold the prompts, the templates and the AI rules page in the club's own drive, so they survive the next AGM. If the club does buy a team plan, name one officer as the owner, and agree who removes a leaving volunteer's access.

One month in: wrong dates, payment stages and corrected minutes

At the end of the first month, check four things. How many sent messages contained a wrong date, time or venue (the target is none)? What share of members paid after each renewal stage (this shows which reminder is doing the work and which can go)? How many of the minutes needed a correction at the next meeting? And did a second officer read everything that went to the whole membership, as rule 4 of your AI rules page says?

If the answers are good, add one more job next season. If a wrong date got out, tighten the check before you add anything. The pattern for a committee is deliberately modest: three jobs, free tools, a second pair of eyes, and the member list staying in the sheet where it belongs.

Questions club committees ask before trying AI

Is it safe to paste our member list into ChatGPT?

No. Replace names, emails, phone numbers and dates of birth with member IDs before anything goes into a chat, and give the assistant structure and categories instead of people. Consumer plans let you switch off model training in privacy settings, but the safest data is the data the assistant never receives. Children's details and safeguarding notes never go in at all.

Can the whole committee share one ChatGPT or Claude login?

Avoid it. OpenAI's terms and Anthropic's consumer terms both bar sharing login details, and a shared account means nobody owns the history when a volunteer leaves. Keep the prompts and templates in the club's own shared drive, and let each person who needs an assistant use their own account.

Do we need to record our meetings to get minutes?

No. A volunteer typing bullet notes during the meeting is enough, and the assistant turns them into minutes. Recording needs the agreement of everyone present and creates a file that holds personal details, so decide that as a committee first. Whatever the source, the chair should approve the minutes at the next meeting.

When is it worth paying for an AI plan?

When a specific limit blocks a job, such as repeated upload refusals, a member list above a free email plan's contact cap, or a need to share work between volunteers. Paid individual plans list at about $20 a month. Check first whether your club qualifies for nonprofit pricing, because eligibility rules vary and some clubs do not meet them.

Further reads

Sources: Google Calendar's help page on importing events; Mailchimp and MailerLite pricing pages; ChatGPT's file-upload FAQ; OpenAI for Nonprofits and Claude for Nonprofits pages; OpenAI and Anthropic terms on shared logins; Google Workspace for Nonprofits (October 2026). The hours and club figures in the examples are illustrative.

Want your committee's admin mapped before the new season?

On a 1:1 call we'll list the jobs your committee repeats every season, pick the three worth handing to AI, and set them up with free tools your volunteers can run themselves.

Book a 1:1 call with me