Film Location Management Software: How Do You Stop One Missing Permit From Killing a Shoot Day?

Why a location department fails on the day rather than in prep

It is 5:40am at base camp on a residential street. The unit moves to a second location at 2pm, and the locations manager has just learned two things at once. The road closure rider for that address was submitted, but the fire safety officer required by the rider was never booked, so the closure is not valid. And the certificate of insurance on file names the production company rather than the single purpose entity the show set up for this season, so the homeowner's property manager will not release the gate. Two hundred people are already on the clock. The first AD wants an answer in the next ten minutes.

Nothing about that morning is unusual. The information needed to prevent it existed: the rider condition was in a PDF, the certificate was in an email, the owner's requirement was in a phone call somebody remembers. It was simply spread across four systems and three people, and none of them had a view that says this shoot day is not clear yet. One lost shoot day costs more than the entire software project described in this guide, which is why locations is one of the few production departments where a custom build pays back inside a single season.

The typical stack is a shared drive of scouting photos organized by whoever took them, a spreadsheet of addresses and rates, DocuSign for location agreements, a folder of certificates from the insurance broker, email threads with each city film office, and a production accounting system that knows nothing about any of it. Reel Scout and LocationsHub sit alongside that in some organizations. The department runs on the locations manager's memory, and the memory is loaded at 5:40am.

Problem 1: your location library is a photo drive with no rights attached

A location is not a set of images. It is a legal and operational record: who has authority to grant access, what the agreement says about hours, noise, alterations, pets, smoking and the use of the address in dialogue, what the day rate and prep and strike rates are, whether the owner refused a prior production and why, which neighbor complained last time, whether there is a holdback on filming for a competing brand, and whether the parking that made it viable is still available since the building next door started construction.

Reel Scout and LocationsHub are real tools and they do their job. That job is discovery: a searchable library of locations with photographs, contact details and basic attributes, used heavily by film commissions to market a region and by productions to find candidates. They are not built to hold your negotiated terms per production, your agreement versions, your restriction rules or your owner relationship history. So the moment a location moves from candidate to booked, the record leaves the tool and reappears in a folder.

A custom build keeps one record from scout through wrap. The location carries geography, ownership and authority chain, agreement versions with signature status, rate card with prep, shoot, strike and overtime rates, restriction rules expressed as data rather than prose, an availability calendar, and a relationship log. Two years later, when a different show wants the same warehouse, you know what it cost, who to call, and that the landlord will not allow pyro.

Problem 2: permits are a different animal in every jurisdiction

Los Angeles goes through FilmLA. New York City goes through the Mayor's Office of Media and Entertainment. A state highway may need a Caltrans or equivalent department of transportation approval. Federal land needs a National Park Service or Bureau of Land Management permit with its own lead times. Drone work needs a Part 107 certificated pilot and, in controlled airspace, an authorization. Intermittent traffic control means police, not just a form. A stunt, pyrotechnics or an animal handler each drag in a separate rider, sometimes a separate agency.

Every one of those has a different form, a different lead time, a different fee structure and a different definition of what counts as submitted versus approved. Productions handle this with a coordinator who has learned three or four cities and a checklist that lives in their head. Move the show to a new state and the institutional knowledge resets to zero.

What a build does is model a jurisdiction as a configurable object: required documents, riders triggered by activity type, lead times measured in business days, fee schedule, submission channel and the humans who sign off. Then a shoot day is checked against it automatically. If Thursday involves a drone over a public park in a city that requires a parks department rider with seven business days notice, the system flags it on the previous Monday, not on Wednesday night. Adding a new city becomes configuration by a coordinator rather than a code change, which is the difference between a tool that survives your next location and one that does not.

Problem 3: certificates of insurance expire quietly and stop you at the gate

Owners, city offices and equipment vendors all want a certificate of insurance, usually naming them as additional insured, sometimes with specific limits, sometimes with a waiver of subrogation. Each one is a separate request to your broker, each has an expiry, and each is bound to a specific named insured entity. Productions that create a new entity per season or per title break this constantly, because a certificate issued for last season's entity looks correct at a glance and is worthless at the gate.

A build attaches certificate requirements to the location and the jurisdiction, tracks the issued document with its named insured, additional insured, limits and expiry, and evaluates coverage against the actual shoot date and the actual production entity. The check runs nightly across every scheduled day. A missing or mismatched certificate becomes a red item on the shoot day readiness view a week out, alongside the permit status and the signed agreement. That readiness gate, one screen that says whether a given day is legally clear, is usually the feature the department falls in love with.

Problem 4: neighbors, notifications and the complaint you did not log

Most jurisdictions require written notification to residents and businesses within a defined radius, sometimes with a signature threshold before a permit is issued. Producing those letters means resolving an address list around a point, merging the notice text with permit specifics such as dates, hours, equipment and parking restrictions, and recording delivery. Teams do this manually with a mapping tool and a mail merge, and the record of who was notified is a stack of paper in a production office that will be recycled at wrap.

That record matters twice: when a complaint escalates during the shoot, and when the same production or the next one returns to the same street. A build generates the radius list from parcel or address data, produces the notification pack, logs delivery, and then keeps a complaint register tied to the location and the address. The next time anyone scouts that block, the history is on the record. Location departments live on goodwill with communities, and goodwill is much easier to maintain when you can see who was unhappy last time and why.

Problem 5: owner money and damage claims that surface after wrap

Location fees are only part of it. There are prep and strike days at different rates, holding fees for dates you optioned and did not use, utility reimbursements, cleaning, and the restoration costs that appear two weeks after wrap when the owner notices the driveway. Payment sits in production accounting, the agreement sits in a signing tool, and the damage photos sit on a coordinator's phone.

A build binds the money to the record: agreement terms generate the payment schedule, wrap triggers a condition capture with before and after photography attached to the location, and a claim opens with a status, an owner, a reserve and correspondence. When the same owner is approached for a future production, whoever calls can see that the last claim was settled in full and closed. That is a small thing that determines whether a location says yes.

What this costs and how long it takes

A first release covering the location library with agreements and restrictions, jurisdiction configured permit workflows, certificate of insurance tracking and a shoot day readiness view runs $60,000 to $130,000 and ships in 10 to 16 weeks in our delivery experience. A full platform adding scout pack building with photo sets and sun path data, neighbor notification generation, owner payments and holdbacks, damage claims, and a mobile app for scouts working without signal runs $150,000 to $350,000 phased over 6 to 12 months.

What drives price up in this category specifically: the number of permitting jurisdictions you must model, since each is real configuration work and the first few require someone to read the actual rules. Address and parcel data for radius notifications, which is straightforward in some cities and painful in others. Integration with production accounting such as Movie Magic Budgeting or an entertainment payroll provider.

What keeps it down: starting with your two busiest jurisdictions, the library, and the readiness gate. That covers the failure mode that costs real money.

Build versus buy, and when buying is right

Do not build if you shoot mainly on a lot or stage with occasional controlled exteriors in one city. A shared drive, a spreadsheet and an experienced coordinator handle that, and the money is better spent on the coordinator. If you are a film commission whose job is to market a region and route inquiries to local businesses, LocationsHub or Reel Scout is aimed exactly at you and a custom build would be duplication.

Build when two or more of these hold. You work across three or more permitting jurisdictions with materially different rules. You run more than roughly 60 shoot days a year, or multiple units, so the readiness question is asked several times a week. You return to the same locations across seasons or titles and keep relearning the same terms. You have had a shoot day compromised by a permit, certificate or notification failure in the last two years. Or you are a studio or streamer with several productions whose location knowledge dies with each show's wrap, which is the most expensive version of this problem and the least visible.

The honest threshold is knowledge retention. A single production can run on a great coordinator. An organization that makes many productions cannot keep rebuilding that knowledge from zero and calling it a cost of doing business.

How to choose a developer for location and permit software

Ask them to model a jurisdiction on a whiteboard before you sign. Someone who has done this will separate the permit type, the triggering activity, the required riders, the lead time in business days and the approving authority, and will ask how you want to handle a rider that requires a booked safety officer as a precondition. Someone who draws locations and bookings has built a rental app.

Ask how they would evaluate whether a shoot day is clear. The correct answer involves a rules evaluation over permits, riders, agreements, certificates and notifications for a given date and entity, run on a schedule and surfaced before it is urgent. If the answer is a checklist a human ticks, you have bought a prettier spreadsheet.

Ask about offline behavior on mobile. Scouts photograph locations where there is no signal, and a build that assumes connectivity will be abandoned within a month by exactly the people it was meant to help.

Ask who owns the code and settle it in writing before kickoff. You should own the repository, the cloud accounts and the right to hire another firm at any point. At Digital Heroes the client owns the code from the first commit, and any developer who resists that is building a dependency rather than software.