The movement order is the last document nobody automated
Four levels of nesting, rebuilt by hand for every shoot day, then retyped when a single pickup shifts. Transport is the most reconciled document on a production and the least supported by software.
Every production department has a document that defines it. Camera has the equipment list. Locations has the recce report. Transport has the movement order, and it is the only one that has to be right before anyone is awake to check it.
It is also the document that most resists being templated, because it is not a list. It is four levels of nesting. A day holds vehicles. A vehicle holds movements. A movement holds passengers. Change anything at any level and the levels below it are wrong.
Why a template never survives contact
Open any production company's drive and you will find a movement order template, and you will find that nobody uses it after day two. The reason is that the template captures the shape of the document but not the shape of the work.
The work is: pull the crew list. Cross it against who is actually called that day. Group them by where they are staying. Check that against the hotel list, which changed on Tuesday. Assign vehicles by capacity, which means knowing that the van seats eleven and one of the eleven is a camera assistant travelling with a case that takes a seat. Set departure times by working backwards from the first call. Then do it again tomorrow, because tomorrow is a different location.
A template gives you an empty grid to type all of that into. It does not know any of it. So every shoot day, someone rebuilds the same reconciliation from the same four sources, by hand, at night.
What one wrong pickup time costs
The cost of an error here does not scale with the size of the error. It scales with the size of the unit.
A pickup time that is twenty minutes wrong is not twenty minutes of damage. It is a driver at the wrong hotel, a client standing alone in a lobby, and a unit that starts the day behind and never recovers it. On a shoot day, time lost in the morning is the most expensive time there is, because everything downstream was scheduled against it. And unlike most production errors, this one is invisible until it has already happened — the sheet looked fine, because the sheet always looks fine.
That is what makes transport different from most paperwork. A wrong number on a catering order costs you lunch. A wrong number on a movement order costs you the morning.
Days are not copies of each other, but they are close
The most useful thing a transport tool can do is not the document. It is copy to days. Most productions run the same vehicle configuration across a block of shoot days with small variations — the same four vans, the same drivers, one location change, two crew swaps. Rebuilding that from scratch each day is where the errors enter, because a person retyping the same information for the fifth time stops reading it.
Copy the day, then edit the differences. The copies have to be genuinely independent afterwards — a change to Tuesday must not silently alter Wednesday — but the starting point should be yesterday, not a blank grid.
Over capacity is a signal, not a validation error
One small thing worth designing loudly: when a vehicle has more passengers assigned than seats, that is not a form error to be corrected before saving. It is an operational fact that a coordinator often creates deliberately at 11pm, knowing they will resolve it in the morning when they find out whether the second camera assistant is actually travelling.
Software that refuses to save an over-capacity van forces people back into the spreadsheet, where nothing is checked at all. Software that flags it clearly and lets it stand keeps the work inside the system and keeps the flag visible until someone deals with it. The distinction matters more than it sounds — it is the difference between a tool that reflects the production and one that argues with it.
The links have to survive the PDF
Finally, the thing that is always lost in export. A movement order is read on a phone, in a van, in the dark, by a driver who needs the map to open when they touch the address. If the pickup location is a live link on screen and dead text in the PDF, the document has failed at the exact moment it is being used.
Map deep links, intra-document jumps, phone numbers that dial — these have to survive rasterisation. It is a small technical detail and it is most of what makes the difference between a document that gets used and a document that gets screenshotted and then ignored.
None of this is complicated. It is just work that nobody automated, because the people who could automate it have mostly never had to produce one at midnight for a call at five.