How to stop double-booking gear and crew

The clash was knowable three weeks earlier

Almost no double booking is a surprise at the moment it is discovered. The information that would have prevented it existed well before anyone noticed, sitting in a place the calendar could not see.

The usual shape is this. A client asks about dates. Someone pencils it somewhere private, a notebook, a personal calendar, a message thread. Weeks later a second job is quoted for the same week, because as far as the system is concerned those dates are free. Both jobs confirm within a day of each other and now there is one lighting package and two load-ins.

Provisional work is the whole problem

A calendar that only shows confirmed jobs is not a planning tool. It is a record of decisions already made.

The dates most likely to be sold twice are exactly the ones nobody has committed to yet, because those are the dates that look available. So the question is not whether your calendar shows confirmed work. It is whether a pencil is a first-class thing in it, visible to everyone, without being mistaken for a booking.

Four states, and the danger is collapsing them

Most double bookings come from collapsing the first two states into nothing at all, or from collapsing held and confirmed so that people stop trusting either.

Gear conflicts and crew conflicts fail differently

Equipment is finite and countable. Two jobs wanting the same twelve fixtures on the same day is arithmetic, and a system that knows your quantities can tell you before the truck is loaded.

Crew are not countable in the same way, because a freelancer saying they are probably free is not the same as being booked. Treating an availability reply as a booking is the crew equivalent of a double booking, and it is more common because the failure is social rather than physical. Nobody notices until the person does not arrive.

The checks worth running

• Before quoting: are the dates already held or confirmed for anything else?
• Before confirming: does the gear list clear against everything committed for those dates, including held work?
• Weekly: which holds are stale? A hold nobody released is a date you are not selling.
• Weekly: which crew were asked but never confirmed, on jobs that are now confirmed?
• After wrap: has the job stopped occupying availability?

Release holds on purpose

The failure mode that follows from taking holds seriously is holding everything forever. A calendar full of holds nobody released is as useless as one with none, because the team learns to ignore them.

Give a hold an expectation from the start: the date the quote goes out, the date you will chase, and the point at which the dates go back on the market. A stale hold costs real money, and it costs it silently.

What Flightcase does here

Holds are first class and can span several dates. A hold can become a quote while staying live, so the dates are not released the moment the conversation turns into a document, and confirmed work carries the equipment commitments that created it rather than a retyped copy.

Crew availability is kept deliberately separate from a confirmed call, so asking twelve people whether they are free never looks like twelve bookings.

One honest limit: fully automatic cross-show conflict alerting is a planned area rather than something we claim today. Commitments and shortages are visible against the job, and if guaranteed automatic detection across every show is the requirement that decides your purchase, test it directly in anything you shortlist, including us.