Safeguarding concern chat and voice line for grassroots clubs
Problem
A parent worried about a child's welfare usually has one route: the welfare officer's personal mobile number, if they were ever given it. Many were told it once at a preseason meeting they missed, or never told at all. The alternative is raising it in the club's general messaging group, in front of every other parent, or waiting for a committee meeting weeks away. If the welfare officer is at work, on holiday, or asleep, there is no fallback and no queue. When something is said pitchside instead, at pickup or in passing, it lives only in whoever heard it, with no timestamp, no record of who was told what, and nothing to hand over if that volunteer later steps down.
Product idea
A dedicated chat and voice line, published on the website, in the welcome pack and on pitch signage, that anyone connected to the club can use to raise a welfare concern at any hour, not only when the welfare officer happens to be free. It asks a fixed set of questions: who is raising the concern, who it concerns, what was seen or heard, and when. If the answers indicate a child is in immediate danger, it stops the conversation there and tells the caller to contact emergency services directly rather than continuing to gather detail. Every other report becomes a structured, timestamped record sent straight to the welfare officer and a named deputy, so cover exists when one of them is unreachable. It does not appear in the club's general messaging group and does not attempt to assess, resolve or advise on the concern itself.
Who it is for
Parents, players, coaches and volunteers who need to raise a concern, and the welfare officer, backed by a named deputy, who sponsors the line and receives every report.
Possible first version
A single published phone number and chat widget with a fixed intake script covering who is raising the concern, who it concerns, and what happened, plus an immediate-danger branch that redirects to emergency services instead of continuing the conversation. Completed reports are timestamped and sent to the welfare officer and one named deputy. Out of scope for version one: any integration with a national governing body's safeguarding portal or case management system, any attempt to grade severity itself, and any language beyond the club's default. Escalation beyond the deputy stays a manual, human decision.
- Build classification
- Workflow application
- Rough effort
- 3-5 week first release
- Roles involved
- Welfare officer, Club secretary, Volunteer coordinator
- Relevant to
- Academy & youth, Federation / governing body, League office
- Systems in play
- Messaging groups, Paper consent and medical forms
- Product framing
- Voice or chat interface
Questions we get asked
What happens if someone contacts this line about a child in danger right now?
The line does not try to handle that itself. It tells the caller to contact emergency services first and stops the intake there rather than continuing to gather detail. That instruction sits at the very top of the script, before any other question, because a form should never be the thing standing between someone and an emergency call.
Our welfare officer already gives their number out at the start of the season. Why do we need this?
Many clubs do exactly that, and a number read out once at a preseason meeting is exactly what does not survive contact with a parent who joined mid-season, missed that meeting, or simply forgot it by October. This gives one route that is published and permanent, rather than depending on everyone having correctly retained a number they heard once.
Who has access to what gets recorded, and how long is it kept?
Access is restricted from the start to the welfare officer and their named deputy. Nobody else at the club, including other committee members, sees reports by default. Because these records concern children's welfare, retention and access decisions need to be agreed with whoever holds safeguarding responsibility for the club before this goes live, not decided by whatever a form builder defaults to.
Will a parent really open a chat window to report something this serious, rather than just talking to someone?
Some will not, and that is fine. This is not meant to replace a parent who feels comfortable pulling the welfare officer aside at pickup. It exists for the parent who does not know who the welfare officer is, is not confident naming names in a group chat, or has a concern arise on a weekday evening. It is a second route in, not a replacement for the first.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Grassroots, community & youth sports
- Away fixture transport matching for grassroots clubsA workflow that matches players needing a lift to an away fixture with parents offering a seat, replacing ad hoc requests in the group chat.
- Club compliance register for insurance, certificates and affiliationsA single register that tracks every club-level obligation with an expiry date, an owner and evidence, so nothing lapses when the volunteer who knew about it moves on.
- Matchday squad eligibility gate for grassroots clubsA workflow that checks every name on a weekly team sheet against consent, medical and background check records before it can be finalised, and logs any override to the welfare officer.