For Art Director (Agency / In-House)s ·
What you'll accomplish
The shoot brief says one thing, the call sheet says another, and a producer's question in chat gets a third answer from memory. Put the approved script, shot list, schedule and printer's spec sheet into one ChatGPT Project for the campaign. Then the shoot brief, the call sheet draft and the answers to team questions all come from the same files, with the file named each time.
What you'll need
Check before you upload. An unreleased script, a schedule with a launch date and a shoot plan are all confidential until launch. Replace the client and product with a code name such as "Project Lantern." Remove talent names, crew names, phone numbers and addresses before you build the files, since those are not needed for a brief. Then look at your workspace's data settings. On a personal plan, find the setting that controls whether chats are used to improve models, and on a business workspace ask the admin what the retention rules are. If your AI policy does not list ChatGPT, stop and ask.
Make clean copies of the four documents. Do not upload the originals.
What you should see: Four files, each with a code name and a date.
In ChatGPT, look in the sidebar for Projects and start a new project. Name it after the campaign code name, such as "Project Lantern Production."
What you should see: A project page with a place for files and for instructions. Troubleshooting: If you cannot find Projects, your plan or workspace may not include it. Ask your workspace admin.
Add the four files at the project level, not inside a single chat. OpenAI's help page says project-level files stay available in every conversation in that project, while files added in one conversation stay in that conversation only.
What you should see: The four files listed in the project.
Open the project's settings (look for a three-dot menu near the project name, then project settings or instructions) and paste this.
Use only the files in this project. Name the file for every fact you use.
If the files do not say, write "missing from the files" and list what you would need. Never fill a gap from general knowledge.
Do not invent dates, sizes, quantities or names. Do not add product claims.
Use code names only.
Format dates as they appear in the schedule file.
What you should see: The instructions saved.
In a new chat inside the project, ask for the shoot brief first, then the call sheet.
What you should see: Drafts that name the source file for dates, setups and sizes. Troubleshooting: If the draft contains a time or size without a file name, ask "Which file says that?" and delete anything it cannot source.
Open the schedule, shot list and spec sheet. Check every date, call time, setup and size in the draft one by one. The project drafts, and the schedule and spec sheet decide.
What you should see: Every figure in the draft matches a line in a file.
Draft the shoot brief for the Project Lantern hero shoot from the script and shot list. Use sections for purpose, setups, props and wardrobe, must-haves and open questions.
A crew member asks whether the print version needs extra bleed. Answer from the printer's spec sheet only and name the page. If it is not there, say so.
List every difference between the shot list and the schedule: setups listed in one but not the other.
Turn the open questions from the last chat into a short email to the producer, one question per line.