If you run a rental company with more than a handful of jobs per week, you're working with freelancers. The events and AV industry runs on a flexible workforce - technicians, riggers, operators, drivers who work across multiple companies and juggle their own schedules.
Managing this workforce with spreadsheets, WhatsApp groups, and phone calls works up to a point. That point is usually around 10-15 regular freelancers and 20+ jobs per month. Beyond that, the administrative overhead starts consuming hours that should be spent on actual work.
The spreadsheet spiral
It always starts reasonably. A spreadsheet with names, contact details, day rates, and skills. Maybe a shared Google Sheet that the ops team updates when they book someone. It's functional. It's free. It works.
Then it grows. Columns for availability. Colour coding for confirmed vs tentative. Notes about who's reliable, who needs supervision, who has their own transport. A separate sheet for rates because some people charge differently for different roles. Another sheet tracking hours worked for invoicing.
Before long, you have a monster spreadsheet that only one person truly understands, and when that person is on holiday, everything slows down. Worse, the spreadsheet can't tell you what you actually need to know in the moment: who is available, qualified, and affordable for the job you're trying to crew right now?
The WhatsApp problem
WhatsApp is how the events industry communicates. It's fast, everyone has it, and it works. But it's terrible as a system of record.
When you send "Anyone free next Thursday for a corporate load-in?" to a group of 30 freelancers, you get a flurry of responses. Some say yes. Some say maybe. Some don't reply until you've already booked someone else. Some reply to you directly, some reply to the group. Information gets lost in the scroll.
A week later, when you need to confirm who's actually booked and send call sheets, you're scrolling through message history trying to piece together commitments. It's inefficient, error-prone, and doesn't scale.
What a proper system looks like
Managing freelance crew properly requires a system that handles five core functions:
1. A crew database with useful detail
Not just names and numbers. Skills and certifications (IPAF, PASMA, CSCS, first aid). Equipment they own. Vehicle access. Preferred roles. Day rates by role type. Availability patterns (never Mondays, always available in August, etc.).
This data lets you search and filter intelligently. "Show me all freelancers who are IPAF-certified, own PPE, have their own transport, and are available next Wednesday" should be a query you can run in seconds, not something that requires you to check three spreadsheets and send twelve messages.
2. Availability management
Freelancers should be able to set their own availability. Mark dates they're unavailable. Indicate tentative holds with other companies. Update in real time so you're not offering work to people who can't take it.
This is a two-way benefit. You stop wasting time on unavailable crew. They stop getting calls and messages for dates they've already blocked out. Everyone's time is respected.
3. Job offers and confirmations
When a job needs crewing, the process should be: select the role, see available qualified crew, send the offer, get a response. All in one place. All tracked.
The crew member receives a notification with the key details: date, location, call time, role, rate. They accept or decline. If they decline, you see it immediately and offer to the next person. No chasing. No ambiguity. No "I thought Dave confirmed but he was talking about a different job."
4. Call sheets and job information
Once crew are confirmed, they need to know the details. Venue address. Parking instructions. Site contact. Equipment list. Schedule. Health and safety information. Dress code if applicable.
This information should go out automatically when a crew member is confirmed, not manually assembled and emailed the night before. Updates should propagate instantly - if the call time changes, everyone on the crew list gets notified without someone having to remember to tell them.
5. Time tracking and payment
After the job, hours need recording and rates need calculating. Overtime thresholds, travel allowances, meal breaks - these vary by person and by job type. A system that captures hours on site and applies the correct rate automatically eliminates the reconciliation headache at month-end.
Freelancers want to get paid quickly and accurately. If your process involves them submitting a timesheet that then sits in someone's inbox for two weeks before getting processed, they'll prioritise other companies who pay faster. Speed of payment is a competitive advantage in attracting the best crew.
Building loyalty without employment
The freelance model gives flexibility but creates a loyalty challenge. Your best freelancers are also everyone else's best freelancers. They'll naturally gravitate toward companies that make their lives easier.
What freelancers value:
- Advance notice - offers for next month, not just next week
- Clear information - everything they need to know in one place
- Prompt payment - 14 days or less, consistently
- Respect for their time - not calling at 11pm unless it's genuinely urgent
- Transparency - if a job is cancelled, let them know immediately
- Consistency - regular work builds a working relationship
A good crew management system supports all of these behaviours by making them the path of least resistance. It's easier to send advance offers when you can see your schedule months ahead. It's easier to pay promptly when timesheets are digital and pre-approved.
Handling the admin reality
Freelance crew create administrative overhead that permanent staff don't. Each one needs: a record of their right to work documentation, insurance certificates, certification copies, emergency contact details, tax status (CIS vs self-employed vs limited company), and rate agreements.
Keeping this information current is a compliance obligation, not optional. Certifications expire. Insurance renews annually. Right-to-work checks have specific requirements. A system that tracks expiry dates and alerts you before documents lapse prevents the situation where you discover mid-job that someone's IPAF card expired three months ago.
The ROI of getting this right
A company crewing 30 jobs per month with an average of 4 freelancers per job makes 120 individual crew bookings monthly. If each booking takes 15 minutes of admin time (availability checking, offering, confirming, sending info, tracking hours), that's 30 hours per month - nearly a full-time role spent on crew coordination alone.
A proper system can cut that to 5 minutes per booking. That's 20 hours per month recovered. Over a year, that's 240 hours - six full working weeks - redirected from administration to productive work.
The spreadsheet is free. But the time it costs isn't.