Count Shoot Days From Setups, Not Shot Lists
A shot list with thirty items is not thirty setups, and a location move costs another one. Multiply shots by setups, divide by the setups you can light in a day, and round up to whole days.
1 · scene group | shots | setups per shot
FIRST-LOAD
Research prototype — checkout unavailable. Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Data note: Everything runs in this browser tab on the shoot day card: your scene group | shots | setups per shot stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: Every new framing needs at least one setup. After: the shoot day card shows the working beside each named row so the reader can change the assumption and inspect the consequence.
2 · Read the shoot day card
This is scheduling arithmetic from your own count and rate and is not a production, safety or permit plan. Confirm locations, permits, crew hours, rest requirements and risk assessments with the people responsible before shooting.
Paid layer: shoot day card print and history
one-time step · the free reading above stays complete
Free tier
- one complete shoot day card run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the shoot day card with its row workings
- CSV of shoot days and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the shoot day card, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
This is scheduling arithmetic from your own count and rate and is not a production, safety or permit plan. Confirm locations, permits, crew hours, rest requirements and risk assessments with the people responsible before shooting.
- Method: Ten kitchen shots at two setups each is twenty setups, which needs three days at eight per day. The whole sample list needs five days, and a group that leaves a part day is flagged.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Mechanism: competence-autonomy-loop
Optional AI formatting, not calculation
For this shoot day card, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a shoot day card. Return plain rows only: scene group | shots | setups per shot. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: scene group | shots | setups per shot. No AI response is executed as code.