A single game is a staffing problem. A weekend with games at several venues is a logistics problem: the same freelancers are in demand for every show, call times overlap, gear has to be in the right truck, and one late dropout can cascade into an empty camera position. The teams that handle these weekends calmly aren't luckier. They work from a plan that starts weeks out.
1. Start from the position list, not the people
Before you think about who, write down what each venue needs. A regional basketball broadcast and a football broadcast use very different crews, and a streaming-only game at a smaller venue might run on a fraction of either. For each event, list every position: cameras by number, A1 and A2, technical director, replay, graphics, utilities, stage manager, talent.
Building events from a standard set of positions for each production type makes this fast and keeps venues comparable. It also makes the weekend's total demand obvious: if three venues each need an A1 at overlapping times, you need three A1s plus a backup, and you can see that before you send a single offer.
2. Know your bench depth by role
The bottleneck on a busy weekend is almost never total headcount. It's specific roles. You might have twenty camera operators you trust and only four people who can TD your show. Tag every freelancer on your roster by the positions they can fill, then count how deep you are in each role against the weekend's demand.
- Thin roles (TD, A1, replay) get offers first and get a named backup.
- Deep roles (utility, camera) can be filled later in the week.
- Talent often has the least flexibility. Confirm them as early as you can.
3. Send offers early and track every response
Freelancers book the first solid offer they get. Send yours as soon as the schedule is final, and make it easy to say yes: one message with the date, call time, venue and position, and a single click to accept. Asking crew to reply to a group text or log in to a portal adds friction, and friction loses bookings to whoever made it easier.
Then track the replies in one place. For each venue you want to see, at a glance, which positions are confirmed, which are pending and which were declined. Pending is the dangerous state, so set a deadline (48 hours is common) and move to the next person on your list when it passes.
4. Treat call times and time zones as data
Multi-venue weekends often cross time zones, and a call time sent as "10:00" without a zone is a no-show waiting to happen. Store each event's call time with the venue's time zone, and send crew a calendar invite rather than a time in a message body, so their phone shows the right local time automatically.
Include the details crew actually need at the venue: address, parking or truck dock notes, credential pickup and who to report to. If you distribute a tech book or show rundown, send it to confirmed crew only, so the current version is what reaches the people working the show.
5. Plan for the dropout you know is coming
On a weekend with dozens of bookings, assume someone will drop. Have a short list of backups for every thin role, and know who's local to each venue. When a decline comes in, the fix should be one more offer, not a scramble through old message threads looking for a phone number.
6. Send gear with the crew plan
Crew and gear fail together. If the replay operator's kit went to the wrong venue, the booking didn't help. Assign cases and key equipment to each event alongside the crew, use packing manifests so nothing is left behind, and log shipments when kits travel between venues.
7. Remind, then confirm again
A reminder a few days out catches the people who double-booked themselves or forgot to block the day. It's also when you find out about the conflict while you still have time to replace them. Pair automated reminders with a quick check of your confirmation board the day before each show.
8. Debrief and reuse
After the weekend, note which roles were hardest to fill, who stepped in at short notice, and what the crew actually cost against budget. Next season's weekends follow the same pattern, so a reusable set of positions and an up-to-date roster turn that hard-won knowledge into a head start.
Putting it into practice
You can run this playbook with a spreadsheet and discipline, but it gets fragile as venues multiply. CrewdUp was built by people who staffed sports broadcasts: events with positions, a skill-tagged roster, one-click email invites that crew accept without an account, a confirmation view per event, calendar invites with the right time zone, reminders and gear tracking in one place. See how it works for sports broadcasting, or start free.