How to read a stripboard for hidden company moves

August 31, 2026 · updated August 31, 2026

A schedule can look clean and still be hiding a company move nobody flagged. A stripboard shows scenes in order, one strip per scene – it doesn’t announce, on its own, that scene fourteen sits at one address and scene fifteen sits forty minutes away. Reading past that gap is a separate skill from just reading the board, and it’s the one that keeps a shoot day from losing an hour it never budgeted for.

A company move is exactly what it sounds like: the whole unit – cast, crew, equipment, trucks – relocating mid-day from one set-up to another. It costs real time on top of the drive itself: strike, travel, and reset. One hidden move can cost a day an hour before a single new scene gets shot, and a schedule that reads fine strip by strip can still bury two or three.

Before reading a single scene, check the day’s primary location on its banner. If a day is built around one address, most strips should share it. A day with more than one address in the header is telling you, before you’ve read a single strip, that at least one move is coming.

Check Set against Location on every strip, not just the ones that look different

This is the step most people skip, because Set and Location aren’t the same field and a stripboard doesn’t always make the difference obvious at a glance. Set is the in-story place from the slugline – WALT’S HOUSE, KITCHEN. Location is the real-world filming address that Set is linked to. Two different Sets can share one Location – a house standing in for both the kitchen and the garden – with no move between them. Two scenes that read as the “same place” in the script can still sit at two different real addresses if they were shot on different stages or different days at different houses. Reading Set alone tells you the story. Reading Location tells you the move.

Watch for banners between strips

A company move is one of the standard reasons a banner – a non-scene event – gets inserted directly on the board, sitting between the strips it separates. If banners are visible on your board, a move is usually marked exactly where it happens, not left for you to infer from the Location field alone. If your team doesn’t use banners for moves yet, that’s worth starting: it turns an inference into something everyone sees without cross-checking two fields themselves.

Treat “nearby” as still a move

A move across the street costs less than a move across the city, but it isn’t free. Strike and reset happen regardless of drive time, and a short move that gets waved through as “basically the same location” is exactly the one that eats fifteen minutes nobody accounted for. Count it.

Count moves per day, not just their presence

One move is a planning line. Two or three in a single day is a different conversation – about whether the day’s page count is realistic at all, not just about where the transport truck needs to be. Read the whole day before deciding a move is manageable; two “manageable” moves back to back rarely are.

Flag early, to the department with the longest lead time

Locations and transport need the most notice – permits, parking, drive routes. An AD catching a move on the stripboard during prep is useful. An AD catching it the morning of is a scramble. The earlier a move surfaces, the more it’s a planning decision instead of a recovery.

Common pitfalls

The most common mistake is reading the stripboard the way you’d read a call sheet – scene by scene, in order, trusting that if nothing looks obviously wrong, nothing is. A stripboard rewards a second pass specifically for location, done separately from the pass that checks cast and page counts, because the two kinds of error hide in different places.

The second is assuming a shared neighbourhood means no move. It doesn’t. Two addresses ten minutes apart still cost the strike-travel-reset sequence in full.

The third is trusting the Set field. It describes the story, not the shoot. A stripboard that only shows Set will hide moves that a stripboard showing Location would catch immediately.

Conflict detection catches a real slice of scheduling problems automatically – but a company move buried between two similarly-named sets is exactly the kind of thing that needs a human eye checking Location against Location, not just a rule checking for double-bookings. Reading the board well is still the job.