THE FIELD GUIDE

A plan you can
take to set.

Shot Atlas is a production planner built by Sounak Bhandari. Start with the editable sample, or create a new production. The sample is illustrative, not a completed client film.

01 / Build the sequence

Name your production, set a shoot date and call time, and create scenes with their locations. Add shots, choose framing, lens, movement and lighting, then write direction, sound and continuity notes. Use Move earlier / Move later to change the shooting order.

02 / Keep the timing clear

Screen duration is the length of the finished shot. Setup + shoot time is how long you expect to spend making it. The schedule adds the second value to your call time in shot order. Include changeovers and breaks in your estimates. Crossing midnight is shown with a day offset.

03 / Save and return

Sign in with ChatGPT to save private productions. Save changes explicitly before leaving. My productions reopens your saved work. Each save checks a revision number; if another tab saved first, your changes remain open and you can export a backup before reloading.

04 / Add visual references

After saving a production, upload PNG, JPEG or WebP references up to 5 MB per image. References are private to your account. The image uploads immediately; save the production to attach it to the current shot. A production supports up to 100 shots, 30 scenes and 150 uploaded images, including replacements.

05 / Take it with you

• Export CSV: shot list, timing, technical details and notes.
• Print shot cards: print every shot or save to PDF using your browser.
• Export backup: a JSON package with production data and reference images, up to 25 MB of image data.
• Import backup: restore into a new production. Sign in first when the backup includes images. A partial upload failure keeps the restored text and any uploaded references available for recovery.
• Import old sequence: appears if this browser still has a sequence from the original Shot Atlas. The old browser record is preserved.

Engineering notes

The interface uses React and TypeScript. A Cloudflare Worker validates requests and enforces production ownership. D1 stores versioned production documents and image metadata; R2 stores image bytes. Parameterised queries, same-origin write checks and revision-based updates protect the save workflow.

The framing guide is a composition aid, not an optical simulation. There is no live multi-user editing or automatic film generation. This release focuses on a dependable planning workflow.