Sound Stage and Studio Lot Software: Holds, First Refusal and the Recharges Nobody Bills

Why stage bookings are neither events nor leases

A line producer calls on a Tuesday and asks about stages four and five for eleven weeks starting in March, with an option on stage six for two of those weeks, and can you hold it while the show waits on a greenlight. Your booker writes it on a whiteboard grid, sends a hold confirmation email, and puts a note in a shared calendar. On Thursday a feature calls wanting stage five for six weeks starting in March, and asks whether it is available.

The honest answer is complicated, and the whole business lives in that complication. Stage five is on first hold to a show that may not exist. The feature can go on second hold, which gives them the right to challenge, which starts a clock on the first holder to confirm or release. That clock is usually 24 or 48 hours depending on what your booker said on the phone, and what your booker said on the phone is not written down anywhere. Meanwhile the general manager is in a meeting explaining to ownership why occupancy forecasting is difficult.

This is not an event booking problem, because events are days and stage deals are months with prep, shoot, hiatus and strike phases. It is not a commercial lease problem either, because Yardi and MRI have no concept of a hold that can be challenged, and a lease does not get released because a network passed on a pilot. It sits between the two, and that is exactly why the software you have been shown does not fit.

Across facility and venue projects Digital Heroes has delivered, the recurring cost in this category is not the booking itself. It is that availability lives in one or two people, so nobody else can quote, the general manager cannot forecast occupancy beyond what those people report, and every recharge that was not written on a work order simply does not get billed. That last one is the quiet number. On a busy lot, unbilled power, cleaning, security overtime and forklift hours add up to real money that nobody ever sees because it was never captured in the first place.

Problem 1: the hold ladder is the actual business

A stage is rarely simply booked or free. It carries a stack: a confirmed booking, a first hold, a second hold behind that, sometimes a third, each with a party, a date range, an expiry, and a challenge right. When a second holder challenges, the first holder has a defined window to confirm or drop. If they drop, everything below promotes. If they confirm, the challenger falls away or moves to another stage.

Now layer on how deals are actually shaped. A show takes stage four for prep from March, shoot through July, then goes dark for eight weeks between seasons but wants to keep the standing sets in place, which means the stage is occupied but not generating shoot rate. A feature wants three stages but will take two if it has to. An option on a second season sits over the whole thing and expires on a date buried in an agreement.

Farmerswife and Xytech MediaPulse are real systems and they are strong at scheduling resources, crew and equipment through post production and broadcast operations, where their heritage is. What they were not shaped around is a multi month tenancy with a challenge ladder, a hiatus rate, and an option to renew. So lots run holds on whiteboards and spreadsheets, and the whiteboard is authoritative.

What a custom build does: make the hold a first class object with a position in a stack, an expiry, a challenge policy and a full history of who moved it and when. Availability becomes a query anyone can run, showing not just free or busy but the exact hold position and what it would take to get the space. Challenge notices generate automatically with the clock attached, so the 48 hours actually runs rather than depending on someone remembering to chase. And every promotion or release stays in the record, which matters the first time a producer insists they were on first hold when they were not.

Problem 2: the recharges are metered, and nobody is metering

The stage rate is the headline. The margin is in everything around it. House power drawn through stage services, often sub metered per stage. Compressed air. HVAC run outside standard hours. Cleaning between units. Security overtime for a night shoot. Trash and recycling pulls. Telecom and network drops into production offices. Forklift and scissor lift hire with an operator. Stage manager or facilities technician hours. Parking beyond the allocated count. Water and waste for a special effects rig.

On most lots this gets captured on paper work orders, a clipboard in the facilities office, and a weekly conversation between a facilities manager and a billing clerk who reconstructs the month from memory and handwriting. The parts that are legible get billed. The parts that are not, do not.

What a custom build does: every rechargeable service is a work order raised against a booking, from a phone in the field, with the tenant, the stage, the service, the quantity and the authorising production contact captured at the moment it happens. Sub meter readings get logged on a schedule or read from your building system where one exists, with opening and closing reads bracketing each tenancy so the power bill splits by evidence rather than by argument. Rate cards vary by tenant and by deal, so the same service bills differently for a long term series and a two day commercial, which is exactly what your deal memos already say and your invoicing currently ignores. Then the invoice assembles itself from the record, and disputes get answered with a reading and a signature rather than a discussion.

Problem 3: a lot is more than stages

Production offices with a fit out period. Mill and construction space. Wardrobe and hair and makeup rooms. Basecamp and truck parking. Backlot exteriors with weather dependency. Screening rooms. Loading docks with time slots. Crew parking with a count per tenancy. Every one of these is bookable, most are billable, and they interlock: a show taking stage four expects office space near it, and if the offices next to stage four are held by someone else, the deal changes.

What a custom build does: model every space as inventory with its own type, capacity, rate structure and adjacency, then let a deal be a package across spaces that holds and confirms as a unit. If the package cannot be satisfied, the system says which element is the constraint. That single capability changes how a general manager negotiates, because a counter offer can be constructed in the meeting rather than the following week.

Problem 4: certificates of insurance and the gate

No production drives on without insurance in place. That means a certificate naming the correct entities as additional insured, with the right limits, the right endorsements including waiver of subrogation where your agreement requires it, and dates covering the tenancy. Certificates expire mid tenancy on long shows, and the renewal arrives late, and someone has to notice.

Then there is the gate. Drive on lists, crew badges, vendor deliveries, parking allocations, and the daily reality that a lot is a controlled site with visitors who change every day. On most lots this runs on emailed lists to security and a printer at the gatehouse.

What a custom build does: certificates attach to the tenancy with parsed dates, limits and named entities, and expiry generates escalating notice well before the lapse rather than after. Document extraction is one of the two places AI earns its cost on a lot, reading a certificate of insurance and pulling carrier, limits, endorsements, named insureds and dates for a coordinator to confirm, which turns a ten minute manual check into under a minute. The other is access: a production contact submits a drive on list against their booking, security sees it at the gate on a device, and the record of who was on the lot on a given day exists without anyone keeping a paper log.

What this costs and how long it takes

A first release covering space inventory across stages, offices, workshops and parking, the hold ladder with challenge handling, package bookings, phase based date ranges and an availability view anyone on the team can run, plus basic tenancy records, runs $60,000 to $125,000 and ships in 12 to 16 weeks in our delivery experience. A full platform adding work orders and rechargeable services with rate cards, sub meter reading, invoicing with accounting integration, certificate of insurance tracking, gate and access lists, turnaround scheduling and occupancy reporting runs $150,000 to $350,000 phased over 6 to 12 months.

What drives cost up: integration with a building management system for metering, which varies enormously depending on what is installed and how old it is. Accounting integration, since a lot running on Sage, NetSuite or QuickBooks each needs its own mapping for recharges and deposits. Multiple lots under one operator, which introduces cross lot availability and transfers. And any requirement for tenants to have their own portal access, which is worth doing but should follow the internal system rather than launching alongside it.

Build versus buy, and when buying is the right call

Buy or stay manual if you operate one or two stages let on short bookings, or if you are a studio whose stages exist mainly to serve in house productions rather than third party tenants. A shared calendar, a deal memo template and an invoice does the job, and software will not improve a business whose constraint is stage count.

Look seriously at Farmerswife or Xytech MediaPulse if your operation is really a post production or broadcast facility with edit suites, colour bays, machine rooms and crew scheduling, where stages are a smaller part of the picture. That is what those systems were built around and they do it well. Fighting them into a property shaped business is a poor use of everyone's time.

Build when several of these are true. You run more than about six stages plus supporting spaces. Your holds live on a whiteboard or in one person's head, and quoting availability requires finding that person. You recharge utilities and services and suspect the capture rate is poor. You track certificates of insurance in a spreadsheet with manual date checking. You operate more than one lot. Or ownership is asking for occupancy and yield reporting that nobody can produce without a week of assembly.

How to choose a developer for studio and stage booking software

Ask them to model a second hold challenging a first hold with a 48 hour clock, where the first holder confirms only part of the date range. If they treat bookings as rows on a calendar, the whole hold ladder will end up as a status field and you will be back on the whiteboard within a year.

Ask what they will do about capture in the field. Facilities staff raise work orders standing next to a genset in the rain, not at a desk. If the answer does not involve a phone, offline tolerance and about four taps, your recharges will keep going unbilled and you will have paid for the privilege.

Ask who owns the code and put it in writing before kickoff. You should own the repository, the infrastructure accounts and the right to hire any other firm. At Digital Heroes the client owns the code from the first commit. A lot whose availability data sits inside a vendor's account cannot quote a booking during a dispute, and on a facility where a single stage deal runs into seven figures, that exposure is not worth whatever the arrangement saved.