> For the complete documentation index, see [llms.txt](https://info.picturesup.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.picturesup.app/shoot-day.md).

# Shoot day

Shoot day is the on-set view: the call time, the location, who to call, camera rolls, the shot list, the gear check and talent releases, on a phone, with big type and a high-contrast mode for direct sun. Once it is open it keeps working without signal and syncs when you are back.

![Shoot day on a laptop](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2F2fRIYiW1NxXYXwZOsOE6%2Fshoot-day.d9e8067e.png?alt=media) *The Day tab, with the crew call, the location and the sun.*

### Opening it

* The "Shoot day" button in a production's header. It turns red in the week of a shoot.
* The Shoot day tab on a phone, which opens the next shoot in your productions.
* "Open Shoot day" in Search.

Pick the day at the top when a shoot has more than one. The sun icon switches to the high-contrast light theme and back, and the choice is remembered on that device. The line under the day says "Synced" with the time, or how many changes are waiting to go up.

![Shoot day on a phone](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FK5sBHLnQOUj1FMBxO1bb%2Fphone-shoot-day.e05d8f51.png?alt=media) *The same day on a phone.*

### Day

The crew call, large, with how long until it. The location with its address and parking notes, and "Open in Maps". Sunrise and sunset from the location's coordinates, and the weather as entered in Plan. Key contacts with a "Call" button each: the producer and director first, then the location contact, and the nearest hospital with 911.

Two more lists, when the production uses them: timed reminders for the day, and a packing checklist that is ticked off on set and "Reset for new day" the next morning.

### Camera

A card for each camera with the roll it is on. "+1 roll card" starts the next one, so A003 becomes A004, with Undo. "Add a camera" adds the next letter.

When camera reports are on, log takes as you go: scene, take, notes, "Log take" or "Log as circled". The last takes list below, with the roll each is on. Admins and editors can switch reports on or off here for the production.

### Shots

The shot list from Plan for this day. Tap a shot to mark it Shot, and the count at the top follows. Shots without a day sit in their own list underneath.

### Gear

![The Gear check on a phone](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2Fv0RyJnlMG4SJoq4O72Ef%2Fphone-shoot-gear.805c804a.png?alt=media) *Drag right to verify, left for missing, hold to set aside.*

The day's gear list from the Gear tab, as packages, cases, crew kit and rentals. Check each item: drag right to verify, drag left to mark it missing, or press and hold to set it aside. Tap an item for the same choices as buttons. "Scan QR" finds an item or a whole case by the code printed under its label: type it in, and the case's items verify together. The dock at the bottom keeps the count: verified, missing, set aside, to check, and when the rental is due back.

"Check-out list" opens the production's Gear tab, where the list is built and moved through its stages.

### Releases

![Releases on a phone](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2Fi7dvajPHsgxMYjfeI1AT%2Fphone-shoot-releases.16f1d731.png?alt=media) *Who has signed and who has not.*

Everyone on camera, unsigned first. "Sign a release" opens the studio's release form on the phone: hand it over, they read, fill in their name, sign in the box and save. Admins and editors can send a signing link by email instead. Signed releases file themselves in [Paperwork](/paperwork.md).

### Working offline

Every change on Shoot day is saved on the phone first and sent in order when there is signal: roll cards, gear checks, shots, takes, reminders, packing and signatures. The banner says "Offline, saved on this phone" with the count, then "Back online" with how many changes synced. Tap the sync line to try now.

The page has to be open before the signal goes. It cannot be loaded from scratch with no connection yet.

### Good to know

* Crew, editors and admins all make changes here. Viewers can follow the day but not change it. Archived productions are read-only.
* Which tabs show is set per production in its Settings under Shoot day tools: shot list, camera rolls, camera reports, packing checklist, reminders and releases.
* Scanning with the phone's camera comes with the iPhone app. In the browser, type the code.
* Signatures made on set wait in the phone's browser until they sync.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://info.picturesup.app/shoot-day.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
