Fixtures, knockouts, referees and live tables across every competition group at once. And when a team pulls out at eight in the morning, it rebuilds the entire day in ten seconds.
One volunteer builds the fixtures in Excel over a fortnight. On the day it's printed on a wall, results walk to the desk in someone's pocket, and the tables are twenty minutes out of date all afternoon. Then it rains, a team doesn't turn up, and the whole thing has to be redone by hand with forty people waiting.
Anyone can generate a fixture list. Zokko is built for the four hours where the plan falls apart.
Remove them and the whole day rebuilds — fixtures, pitches, kick-off times, knockout bracket — keeping every result already played. Ten seconds instead of an hour.
Push the day back, then see instantly what you'd need to trim to still finish on time. It tells you how to recover, not just that you're late.
A code on each corner post. Whoever's marshalling scans it, taps in the score, and it lands at your desk for approval. Nothing touches a table until you accept it.
U7s, U9s and U11s on their own pitches with their own match lengths, sharing your referees, in one timetable. Not three separate accounts.
Wall timetable, a card per manager, a sheet per pitch, registration list and certificates. Because the signal will die in a field, and paper never does.
Yellows and reds by shirt number, with suspensions carried into later games. A first-aid shout that goes straight to the desk. Registration ticked off as teams arrive.
Send it out with the entry email. A parent picks their child's team once, and from then on the page is only about them.
Each one shows a single thing that goes wrong on a tournament day, and what Zokko does about it.
Paste in your teams, pick your pitches and match lengths, and build the timetable. Do it in one sitting or come back to it over a fortnight — it saves as you go.
Wall timetable, a card for every manager, sheets for the pitches, registration list and codes for the corner posts. All from one button.
Keep it open on a laptop at the desk. Scores go in, tables move, and when something changes it works out the knock-on effects for you.
Zokko started because running a junior tournament is a genuinely hard scheduling problem that somehow still gets solved with a spreadsheet and a laminator. Nobody had built the thing that helps when it all goes sideways — and that's the part organisers actually dread.
It's one person building it, which cuts both ways. If you email about something annoying, you're emailing the person who can change it, and it'll probably be fixed that week. On the other hand, I'm not a call centre.
Zokko is still in beta. Right now the priority is getting it into the hands of real organisers, learning what breaks under pressure and making the live-day experience properly dependable before the paid version launches.
One person building Zokko in Lancashire — so feedback reaches the person actually changing it.
Zokko is in early beta while the live tournament workflow is tested with organisers. The public version will be paid, with straightforward tournament-based pricing rather than a bloated software subscription.
Pricing is not being locked in before the beta proves what organisers actually need. The plan is simple: create and prepare your tournament, then pay to take it live — clear, self-serve and proportionate to the event.
No. It's browser-based, so there's no app or software package to install. Organiser accounts are being added so your tournaments can be saved and managed in one place.
Print the pack beforehand and you can run the entire day on paper — timetable, pitch sheets, registration list, blank tables. That's not a grudging fallback; it's how tournaments have always worked and it should keep working.
Not yet. Right now it runs on one laptop at the desk. Live entry from pitch-side phones is the next thing being built.
It saves itself as you go and offers to bring it back when you return. You can also download a copy as a file — worth doing before the day, so someone else can pick it up if your laptop dies.
Yes, and that's the point. Each age group gets its own pitches and match lengths, they share your referees, and it all appears in one timetable. Rain affects the whole site, so recovery works across every group at once.
Points, then goal difference, then goals, then the head-to-head — or head-to-head first if that's what your rules say; it's a setting. Three teams level are compared as a proper mini-league. If nothing separates them it stops and asks you to toss for it, then records what you decided.
Zokko only uses the information needed to run and sync your tournament. Organiser accounts and saved tournaments are being built around that same principle: keep the data purposeful, limited and under the organiser's control.
The scheduling is the same problem for netball, hockey, rugby or cricket — it just says "pitch" a lot. If you run one of those and fancy trying it, get in touch.
Build the tournament, share the live view, collect scores from the pitches and recover when the day changes. No parent app to download and no referee login to remember.