Teams that select themselves from your league's rules, each player's preferences and fair game time, then post to WhatsApp on schedule. Match fees charge themselves too. Players tap once; the engine does the lot.
Running three league teams every week of the season at the home club.
One real match week, three teams and three fixtures, exactly as the engine runs it. This club plays in the North West Counties Squash League (NWCSL) on Thursdays, so its week runs Friday to Thursday; yours runs on your own match night. The players are made up; the screens and messages are the real ones.
The engine reads the next league match's fixtures and posts them to the club's league WhatsApp group, with a one-tap link to answer. No captain has typed a message.
The link opens their availability page, already signed in: I'll play, I'll reserve or Can't make it. Underneath sit their team preferences for the week (Play, If needed or Won't for each team), defaulting to their season sign-up.
They can see straight away which team they're provisionally in, and it updates as the rest of the club answers.
If anyone still hasn't answered, a reminder goes to the group with the running count. Captains also see exactly who's outstanding, with one-tap WhatsApp nudges.
Everyone answered already? Nothing is sent. The group only hears from the engine when there's something to say.
Nudges open WhatsApp with the message ready. Nothing is sent without a tap.
The engine ranks everyone who's in by live SquashLevels, fills the top team first, keeps every swap inside the order-of-merit window and honours each player's preferences. Rules, preferences and fairness, applied the same way every week.
Each team has its own style: strength picks strictly by level, fairness rotates borderline places to whoever has played least. The home club runs its first team on strength and the seconds and thirds on fairness; your club sets its own.
Full and legal? The sheet is posted as confirmed ✅. Short anywhere? It still posts what it has, clearly marked not final, and asks for help. Every name has a "why".
First reserves: Owen Stirrup (610), Max Threlfall (520).
Injury, work, life: they tap Can't make it (after the lock that needs a reason for the captains, and it's one way). The engine re-runs the selection, brings in the next player, up from a lower team or off the reserve list, and posts a short, text-only update naming just the team that changed.
Never a flood: more than two days out it's at most one update a day, and in the last two days changes go out as they happen, spaced apart.
After the matches, the treasurer ticks who played and signs off. Everyone is charged the match fee to the card saved on their account and gets a receipt by email.
Nobody carries cash. Nobody chases IOUs in February.
Nothing is charged until a treasurer presses the button.
Appearances by team feed the 75% and cup-tying checks. Availability, fees and the reasoning behind every selection are kept for the season and exported when the league asks.
| Player | G1 | G2 | G3 |
|---|---|---|---|
| Lewis Farrant75% check | 7 | 2 | 0 |
| Callum Redfern | 0 | 6 | 1 |
| Owen Stirrup | 0 | 1 | 5 |
| Sophie Tarrant | 0 | 0 | 8 |
Flags appear before a pick that needs the Match Secretary's say-so, not after.
The engine applies the current season's rules on every run (the North West Counties Squash League first, with other leagues' rules added as clubs join), without anyone having to remember them, and flags anything that needs the Match Secretary's say-so instead of quietly letting it through.
Teams are ordered strictly by level. Only players close enough in level may exchange places, and the engine never moves anyone across that line.
No gap in a senior team while an eligible player sits lower. Players are pushed up, never left short, and can only decline if their replacement is within the window.
A player who has mostly turned out for a higher team is flagged before being picked lower on that team's rest week, so the Match Secretary's say-so isn't skipped.
When a club's fixtures fall on different days, a player isn't quietly used twice. They're held to one team unless the committee has agreed otherwise.
Nobody is selected for two teams on the same evening, however short the lower team is.
Before the last three matches and the play-offs, the engine checks each player's earlier appearances in that division or below.
The order-of-merit rank, the swap window and the preferences behind the pick, shown to the player, the captain and the committee alike. No more "why am I in the thirds?"
Everything a league night needs, done automatically, with a person able to step in at any point.
Order of merit, the swap window, the 75% rule, cup-tying, one game a night: all applied on every selection without anyone having to remember, and flagged whenever a permission is needed.
Live SquashLevels order of merit, each player's preferences and fair game time, combined by the engine into a legal team sheet, on schedule, every week.
Set each team's style: pick on pure strength, or rotate borderline places to whoever has played least. The home club runs its first team on strength and the seconds and thirds on fairness.
Play, If needed or Won't for each team. Set once for the season, adjustable for any week until answers lock three days before the match, and every change is logged.
Fixtures six days out, a reminder four days out, the team sheet three days out, all posted to your league group with nobody pressing send.
One tap from the player, the engine re-selects, and one short message names only the team that changed. Never a re-post of the whole sheet.
The treasurer signs off who played; everyone is charged to their saved card and receipted by email. No cash, no IOUs, no chasing.
Tap ⓘ by any name for the order-of-merit rank, the swap window and the preferences behind it. Players, captains and committee all see the same answer.
Appearances by team, availability, fees and the reasoning behind every pick, kept all season and exported when the league asks.
Works with the league's Team Playing Squads system as well as open week-to-week selection from live levels.
Run it on the Squash Solutions platform under your club's name, or plug the engine in behind the website you already have.
Nothing needs a captain to happen, but a captain can adjust a pick, hold a message or pause the whole thing whenever they want to.
Your club gets its own availability page, team pages and league-group hook-up at yourclub.squash.solutions: your teams, your players, your name on it. Nothing to install and nothing to host.
Keep your site and your look: the engine runs behind it. Availability, the team sheet and the WhatsApp messages carry your domain, and your members never leave your website.
Your league, teams and divisions, roughly how many players, and which WhatsApp group the messages should land in.
Teams and fixtures go in, each team is set to strength or fairness, and your players are invited to sign up for the season with their preferences and a card.
The first fixtures message goes out, and the week runs itself from there.
A quick note about your club is all it takes. You'll get a straight answer from Dan, and a live look at a real match week if you'd like one.
Email the address below, or copy it into your mail app.
Players in the examples on this page are made up. The fixtures, screens and messages are real ones from the home club's 2026-27 North West Counties Squash League season.