Plan around golden hour
The sun does not wait for a lighting tweak. Golden hour shots are scheduled backwards from the moment the light dies.
What this is about
Golden hour — the stretch after sunrise and before sunset when sunlight comes in low and warm — is the cheapest premium look in filmmaking and the least forgiving window in a schedule. Its length depends on latitude and season: generous in a northern summer, brutal in winter. The failure pattern repeats on every unprepared set: the team arrives with daylight to spare, burns it on blocking and small fixes, and the actual window opens with two shots still unrehearsed. The fix is arithmetic, not talent — know the sun's time and direction for your date and place, and build the afternoon backwards from it.
The order matters more than the tools. Skip a step and you usually notice two steps later — by which point the fix costs several times as much.
What runs differently here
In planning terms, that means:
- Sun position is knowable in advance: ephemeris apps show time and direction for any date and location — direction decides the framing, not just the hour.
- The window length changes with season and latitude; the same shot list can fit a June evening and overwhelm a December one.
- Shots inside the window are rehearsed outside it — blocking, focus marks, dialogue passes all happen in flat light.
- Every golden-hour plan needs an overcast answer, because the forecast owes you nothing.
Step by step
This order gets you there fastest:
- Identify which shots genuinely need golden light — usually fewer than the treatment implies — and rank them, because the window will not hold them all.
- Look up sun time and direction for the exact date and location, and check on the scout where the light actually falls: a hill or a building can shorten your window.
- Build the schedule backwards from the light's end: last shot, the one before it, rig time, rehearsal — the afternoon's clock runs in reverse.
- Rehearse everything before the window opens: blocking, camera moves, focus marks, a full pass with stand-ins. Inside the window you only execute.
- Pre-rig the following setup where possible, so switching shots costs a walk, not a build.
- Define the overcast plan in advance — an alternative scene, a lighting solution, or a calm decision to move the shot to the next morning.
- Put the sun times on the call sheet and name the cutoff moment: after this minute, the priority list decides, not the discussion.
Common pitfalls
What most often goes wrong in practice:
- Planning golden hour by feel instead of by ephemeris — the sun sets behind the wrong building.
- Scheduling four setups into a window that holds two, so the best light is spent moving the camera.
- No overcast plan, which turns a grey forecast into an on-set crisis meeting.
With TillyGen
TillyGen anchors sun-dependent shots in the schedule and warns when the plan collides with the window, so the golden hour is protected on paper before it matters in the field.
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
How long does golden hour actually last?
It depends on latitude and season — long in high-latitude summers, short in winter. Check an ephemeris for your date and place instead of assuming a fixed hour.
How many setups fit into one golden hour window?
Fewer than hoped. With rehearsal done and the next setup pre-rigged, a small number of prioritized shots is realistic; a list of six is a list of three.
Morning or evening golden hour — does it matter?
The light is comparable, the logistics are not: mornings give you a rested crew and light that improves as you rig; evenings give you rehearsal time but a hard cutoff.
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.