Why Live Production Is Still Managing Freelancers Like It’s 2015

The WhatsApp era

Walk into almost any production office and the booking process looks remarkably familiar. A job comes in. Someone opens WhatsApp, or their phone, or both, and starts working down a mental list of who they’d want and who might be free. Calls get made. Texts get sent. A group chat spins up. Somewhere there’s a spreadsheet, colour-coded, jealously guarded, and fully legible to exactly one person.

Then there’s the availability chase. You ring down the list and hope. The first three are already booked, the fourth doesn’t pick up, and by the time you’ve found someone it’s two days later and you’ve sent forty messages to fill one slot. Multiply that across a week of bookings and a chunk of your operations team’s time has quietly disappeared into the phone.

Why it worked – for a while

None of this is stupid. For years it was the right way to do it. When rosters were smaller, jobs were fewer, and compliance was simpler, one or two experienced bookers could genuinely hold the whole picture in their heads. They knew who was good, who was free, who you’d never put on the same job twice. It was fast, informal and human, and it worked precisely because the volume was manageable.

The problem is that nothing about live production has stayed at that volume.

Why it’s stopped working

Three things have changed underneath the old way of working.

The first is volume. More channels, more shows, more shifts, more jobs running at the same time. The informal system that coped with a handful of bookings a week starts to crack when it’s dozens, across overlapping productions, at short notice.

The second is compliance. Since the 2021 reforms, IR35 status determination, and the liability that comes with getting it wrong, sits with the engager, not the freelancer. The Employment Rights Act 2025 has raised the cost of misclassification again, and the reforms to umbrella company regulation and joint and several liability arriving in April 2026 add another layer of due diligence on top. A booking process with no consistent record was always untidy. Now it’s a risk position. A spreadsheet and a WhatsApp history don’t defend you in an HMRC enquiry.

The third is the single point of failure. When the person who “just knows” the roster is on holiday, off sick, or leaves for a competitor, the knowledge walks out with them. The system was never written down, so it can’t be handed over.

Everything else moved on. Why didn’t this?

This is the part that always strikes me. The same companies running cutting-edge remote production and cloud workflows, genuinely sophisticated technical operations, are managing the people behind all of it on tools that haven’t changed in a decade. We rebuilt the gallery, the playout chain and the distribution stack, and left the freelancer operation exactly where it was.

It’s not that anyone decided manual booking was good. It’s that it never broke loudly enough to fix. It just got slowly more painful, one extra job and one new regulation at a time.

What modern actually looks like

It doesn’t have to be this way, and it isn’t a huge leap. A modern freelancer management system does a handful of unglamorous things very well:

• Real-time availability, so you can see who’s free without making a single call.
• Bookings confirmed and contracted in a few clicks, with offers, acceptances and rebookings handled in one place, across multiple timezones.
• Robust compliance – IR35 status and right-to-work captured per engagement, with an audit trail that builds itself rather than being reconstructed after the fact.
• One dashboard for the whole roster, so the knowledge lives in the system instead of in one person’s head.
• Integrations that join the whole process up. A modern platform doesn’t stop at the booking, it connects to the systems around it, such as resource schedulers, IT and onboarding tools, so the booking triggers everything downstream automatically. Book Bob for Thursday and his kit is assigned, his IT accounts and logins are issued, and his access is provisioned, without anyone raising each request by hand.

This is exactly why we built Hive 25. Our own agency, Frame 25, was processing more than 1,500 freelancer bookings a month the old way, and the admin and compliance load had stopped being sustainable. We needed the tool to exist, so we built it.