Location scouting software, connected to your breakdown

Scouting reads as fieldwork, and it is. But the hours rarely disappear in the car. They disappear rebuilding the list of locations from the script, patching it after a rewrite, digging through an inbox for the quote a venue sent three weeks ago, and answering “how many days are we there?” for the tenth time. Location scouting software therefore has nothing to prove about photos or maps. It is judged on whether it keeps that list correct on its own, and whether a decision, once made, actually travels to the people who need it.

A breakdown is already a read of the script location by location: Soldum's AI extracts, scene by scene, the set, INT or EXT, DAY or NIGHT, the background actors and the technical needs. Spelling variants are merged — “EXT. BAKERY”, “BAKERY (day)” and a typo all point at one real place, so they count as one line to scout. What you end up with is not a list of scenes but a list of places to find, each carrying what gets shot there. That is exactly the document most productions rebuild by hand, and that goes stale on the next draft.

Locations do not carry equal weight. A place holding twenty scenes across three shoot days deserves an early visit and a backup; a half-page walk-through can wait until late in prep. Ranking by scene count and by shoot days falls out of the breakdown automatically, and it settles the order without an argument. It also exposes the false alarms: a location everyone worries about because it looks spectacular, but that amounts to a single shot, should not eat a week of searching.

Once the list exists, each location becomes a need to cover: a venue to rent, a scouting agency to brief, a permit to request, sometimes a set to build. In Soldum those needs go out to a search contextualized by the project — the town, the dates in the shooting schedule, the nature of the need — and come back as proposals, alongside your own vendor book, which grows from one project to the next. Quote requests are drafted from the project context, but nothing leaves without you reading it first. Each proposal then moves along visible statuses — proposed, contacted, negotiating, locked — so at any moment you know which locations are covered and which are not.

A recce ends in a number: what the place costs, per day or as a flat fee. More often than not, that number decides. Proposals coming back from the search arrive marked price to confirm — a private house or a scouting agency does not publish a rate — and the amount is entered after the call, with its unit. It then lands on the matching line of the budget, where it sits against the original estimate. “Can we afford this location?” stops being a conversation and becomes a line item.

Scouting only matters if it moves the schedule. Soldum's shooting schedule groups scenes by location and accounts for travel time, so choosing between two places immediately shows how many company moves you avoid and how many days the project gains or loses. The cheaper day rate is not always the cheaper location — it can cost you two extra moves. Downstream, the address and contact of the place you locked are picked up on the call sheet for the day concerned and in the contact list you export for the crew, so a late location change means one new version to re-share rather than three documents to rewrite.

Three ways of running a scout coexist, and what separates them is not photo quality — all three let you share a folder — but what happens when the script or the schedule moves. A spreadsheet and a shared drive are free and flexible, but the list of locations is maintained by hand and a venue's quote lives somewhere else entirely. A dedicated scouting tool structures location files and visits, without necessarily knowing the scenes, the budget and the schedule of the project. A connected chain ties the ends together: the list comes from the script, the price joins the budget, the place joins the schedule. Disclosure: Soldum publishes one of the solutions described here.

Worth saying plainly, because finding out late is what disappoints. No software visits a place, judges the light, pulls a filming permit or talks a reluctant owner round. Soldum is not a scouting photo library either: images and floor plans stay in the tools where you make them. And nothing changes in the project without your approval — AI proposals go through a validation queue that shows their impact before anything is applied. What the software does is hold the list, tie it to the budget and the schedule, and move the decision along. The rest is craft, and it stays craft.

Scouting is one link in a chain that starts at the script. Soldum reads the screenplay, extracts the breakdown with AI, derives the list of locations from it, builds an optimized shooting schedule around them, prices the budget off the same data and produces the call sheets day by day. Everything stays in one tool, which is why locking a location ripples all the way through instead of being copied by hand into four documents. Productions shooting in France get one extra thing: the budget follows the categories and pay rates the French industry works with — nothing about scouting itself is country-specific.