Turnaround Time
Turnaround time is the break between the end of one working day and the start of the next for each individual crew or cast member.
What this is about
The number is checked before a call sheet goes out, and it is checked person by person, because the grip who stayed to derig did not wrap when the actors did. If a day runs long, the next call moves later automatically, and that shift cascades: a late start means a late wrap, which pushes the day after. Travel time counts in many agreements, which matters as soon as the unit base is far from the hotel. Producers who ignore it end up paying penalties and losing shooting hours at the same time.
A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.
What runs differently here
Where this differs from the general case:
- Turnaround is the scheduling measurement; the rest period is the entitlement behind it, set by law and by collective agreements.
- It is counted from individual wrap to individual call, so different departments can have different call times the next morning.
- A forced turnaround, where someone is called back early, is normally compensated and should be a decision, not an accident.
With TillyGen
TillyGen checks the gap between wrap and the next call while the schedule is still a draft, not after the call sheet is out.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
Does travel time count towards turnaround?
In many agreements it does, at least between unit base and accommodation. Check the contract before planning a distant location with an early call.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.