How we plan a flyball training session (and keep it calm)
A simple framework our teams use to plan sessions, collect RSVPs and publish lanes—so practice starts on time, not in a rush.

Running a smooth flyball practice is half planning and half communication. This is the simple framework we use in Flyball Hub to keep sessions calm and predictable—for captains, trainers and members alike.
1) Create the session early
Pick the date, time and location, then publish the session so members can RSVP right away. Early visibility reduces the last-minute scramble and gives you a truer headcount.
Pro tip: include a short “focus” line in the description—e.g., “Box turns + 15ft passes”. It sets expectations and helps owners prep.
2) Collect RSVPs and nudge gently
Members can tap Going / Maybe / Not going from their phones. A day or two before practice, nudge non-responders. Clear counts make planning much easier.
3) Build a simple schedule
We start with blocks: Setup, Warm-ups, Lane work, Break, Cool-down. Then assign dogs to lanes based on ability, experience and training focus. Don’t over-tune—aim for a first pass you can tweak on the day.
Optional: save common templates (e.g., “Newcomers week,” “Pre-comp tune-up”).
4) Share the plan (and pin changes)
Publish the schedule so members know what to expect. If anything changes—venue, start time—post an Announcement and pin it on the dashboard. Fewer “What time again?” messages = happier captains.
5) Arrive ready
Because the plan and RSVPs are in one place, setup goes faster. We also keep a lightweight training prep checklist: box, balls, matting, first aid, timers, spare leads.
Why this works
- Clarity: everyone knows where, when and what we’re working on.
- Momentum: saved templates speed up planning week to week.
- Less noise: announcements and RSVPs reduce endless chat threads.
If you’re still planning in spreadsheets and group chats, try creating your next session in Flyball Hub and invite a couple of members. You’ll see the dashboard come to life—and practice start on time.
