One calendar for every squad
Most academies hold a calendar in three places: a printed timetable on the office wall, a Google sheet the head coach maintains, and a WhatsApp message that goes out at 6pm the night before. By the time a question gets asked — “is the U14 squad on net 2 or net 3 tomorrow?” — three people have to be involved to get the answer. FlikVault replaces all of that with a single, authoritative calendar that every coach, parent, and player sees.
Sessions are first-class objects. Each one knows its squad, its coaches, its venue, its nets, its date and time, and which players are expected. Recurring sessions (the backbone of academy life) are scheduled once and repeat for the term. Ad-hoc sessions — camps, holiday programs, individual lessons — slot into the same calendar without breaking the pattern.
Planning that respects how cricket actually works
Generic scheduling tools don't know what a red-ball squad is. They don't understand the difference between a net session, a fielding session, and a centre-wicket match. FlikVault does. Sessions are typed (net, fielding, fitness, match, video review), which means coaches can pre-load drills and templates that match the session type, and directors can run reports like “how many fielding sessions did the U16 squad get this term?” without manually counting.
For each session, you can set:
- The squad(s) and which players are expected
- The lead coach and assistant coaches
- The venue, the nets, and any other resources
- The session focus (top-order batting, death bowling, slip catching)
- Notes for the coaching team that parents and players don't see
Coaches see today, not the whole calendar
A coach showing up at 4pm doesn't need to scroll through next month. The coach app opens on today's sessions, in chronological order, with the player list ready for attendance. Hand the phone to a junior coach and they can run the session without hunting for information.
Conflicts — the same coach scheduled in two places, or the same net booked for two squads — are flagged the moment you create them, not the morning of. That alone removes a category of weekly friction that most academies just live with.
Parents know when and where, automatically
When a session is created, scheduled, or moved, the relevant parents and players are notified through their FlikVault inbox (and email, if they opt in). No more “sorry I missed the WhatsApp”. The schedule lives at a permanent URL each parent can bookmark. Their kid's next session, this term's session count, and any cancellations are always one tap away.
Built for multi-site academies
If you run a parent organisation with multiple affiliated clubs, or a network of venues across a state, the calendar respects that structure. Each site has its own coaches, venues, and squads, but state-level directors can see across all of them and run comparison reports. Permissions ensure a head coach at one site doesn't see another site's private notes.
Cancellations and weather days, handled cleanly
Cricket gets weather-affected. When a session is cancelled, FlikVault marks it across the calendar, notifies parents and players, optionally credits the academy's attendance commitment, and (if you've configured it) prompts the director to propose a make-up session. The audit trail is preserved — the session was scheduled, cancelled, and the reason captured — so your governing body reporting is clean.
Pairs with attendance, reports, and video
Because a session is a first-class object, everything else attaches to it. Attendance is marked against the session. Coach notes are written against the session. Video clips are uploaded against the session and become part of the player's history. When you write a term-end report, you can pull from every session a player participated in without copying anything by hand.
That's the difference between a calendar tool and an academy management system: the calendar is the spine, and everything else hangs off it.