Creative references
The script, shot plans and visual references describe the intended work. Keep them connected to the current production decisions and the people making them.
A current reference needs an owner, a version and a route to the people using it. Organize the binder around those handoffs, from the creative brief through wrap.
A production binder organizes the current creative, planning and production records so that the people who need them can find the right reference. It can be a physical binder, a permission-controlled digital workspace or a combination. The organizing task is not finished when files have been uploaded: someone must maintain ownership, versions, access and delivery.
For a small video project, the producer may coordinate the register. On a larger production, the production office works with departmental owners. The exact roles vary. ScreenSkills’ production-coordinator checklist describes maintaining documentation, coordinating call-sheet changes and ensuring delivery materials reach the appropriate people. Those responsibilities matter even when a small team does not use the coordinator title.
The script, shot plans and visual references describe the intended work. Keep them connected to the current production decisions and the people making them.
Schedules, location information and daily instructions help people carry out the plan. Changes must reach the people whose work depends on them.
Continuity, media and sound records explain what was captured and what remains open. They support the next team rather than staying buried in the production office.
The fourteen document categories below form a practical starting inventory, not a universal compliance checklist. A documentary interview, a scripted short and a multi-location drama may need different records. Add project-specific requirements and obtain authoritative forms or instructions from the people responsible for contracts, permits, insurance and delivery.
Identify the version that production is working from. For a scripted project, retain scene references that departmental plans can use consistently. For an interview or corporate video, the equivalent may be an approved outline, questions and deliverable brief. The owner is usually the person responsible for the creative reference, working with the producer.
When content changes, explain which references change with it. Replacing a script without telling the schedule or props owner can leave departments planning different work. Preserve prior references and the reason for the revision. Use the production’s agreed revision conventions rather than inventing a numbering scheme after everyone has started.
A breakdown identifies what the planned work requires: people, locations, props, wardrobe, equipment and special activities. Departmental owners supply or confirm the details they understand. A producer or assistant director can coordinate the consolidated record. It connects creative intent to practical requirements.
For a fictional interview shoot, a breakdown might identify three speakers, a product demonstration, a quiet recording room and a second location for supporting footage. A specialist requirement should become a visible planning item, with an owner and an unresolved question where necessary. A checkbox does not establish that the resource has been booked.
The schedule arranges the planned work into production days or blocks. It should reflect actual availability, location access, setup needs and dependencies. The person coordinating the shoot maintains it with input from departments. A schedule can group work efficiently, but the order should remain understandable to everyone carrying it out.
State whether a version is provisional or issued. If a location becomes unavailable, identify the affected work and circulate a revised plan. The register should point to the current reference, not merely retain a file named “final” among several incompatible alternatives.
For projects with cast working across multiple days, a Day Out of Days record summarizes their production-day involvement. It helps the production team discuss availability, holds and working periods alongside the schedule. The exact codes and obligations belong to the production’s agreed system.
A simple interview project may use an availability table instead. Record what is confirmed and what is pending, and keep commercial or personal information with the authorized owners. Do not interpret an availability label as a booking contract or a determination of pay.
A budget describes the agreed financial plan; actual costs and commitments need their own maintained records. The producer or accounts team controls the relevant references and who can access them. The crew may need an authorized purchasing process without needing to see every negotiated rate.
Separate estimates from committed expenditure, and record changes through the production’s approval process. A binder index can point to the controlled budget location. It should not distribute restricted financial information merely because the rest of the binder is shared broadly.
A shot list identifies planned coverage and its purpose. The director and camera team can develop it with input from the assistant director or producer. Useful entries distinguish a shot reference, scene or activity, framing, movement and relevant production notes. The appropriate detail depends on the work.
For a product demonstration, identify the action that must remain visible rather than relying on “close-up” alone. For an interview, note intended coverage without pretending a documentary participant’s behavior can be scripted. Keep the list connected to the actual schedule and current creative reference.
Storyboards help communicate visual sequences, while floor plans can explain positions, movement and equipment relationships within a space. Choose the reference that answers the team’s question. A carefully chosen plan may be more useful than a large collection of decorative images.
The director and relevant departments own the creative and practical decisions. Mark speculative elements and confirm what can be carried out. These references are not substitutes for location checks or responsible assessment of production activities.
Maintain the production contacts people actually need: role, agreed communication route and relevant availability. A coordinator or producer can own updates. Distinguish a working contact list from personal records or emergency-contact information that requires more limited handling.
Give the day’s recipients a usable route to the right person without distributing every private detail. Check the copy used on location and revise it when roles or numbers change. A document register can reference the controlled list without embedding personal data in a publicly shared package.
A location file brings together the current location reference, access arrangements, responsible contact, relevant agreements and practical instructions. The location owner or producer coordinates it with affected departments. Parking, entry points and loading arrangements can matter as much as the address when people arrive with equipment.
Permits, insurance, risk arrangements and restrictions vary by location and production. Obtain the required instructions from the responsible parties and identify unresolved items. This guide and its local register do not issue permits, evaluate insurance or determine whether a location is safe to use.
Keep the appropriate documents with the responsible production owner and distinguish unsigned drafts from executed records. The required forms depend on the engagement, jurisdiction, contract and intended use. Avoid applying an anonymous online template as though it automatically establishes the rights your project needs.
For union productions, consult the applicable official process. SAG-AFTRA’s production-center guidance, for example, identifies production contracts and time-report submissions for that contract route. Confirm the current applicable agreement with the representative rather than treating this page’s fourteen-category inventory as the required paperwork.
A call sheet communicates the issued plan for a specific production day: relevant calls, location instructions, planned work and the information recipients need to prepare. The coordinating owner gathers details from departments and checks the issued version. A daily sheet should be a clear operational reference, not an unfiltered dump of the entire binder.
Agree distribution timing around the real production process. When a material detail changes, issue a clear revision and contact affected people through the agreed route. Record who received the relevant information where your process requires it. A sent file is not proof that everyone read or understood it.
Continuity notes connect what was filmed with the intended sequence and coverage. They can record relevant action, dialogue changes, preferred takes, wardrobe or prop state and other observations needed for the edit. ScreenSkills’ script-supervisor checklist describes continuity, coverage and the link between set and editorial.
On a smaller project, identify who can responsibly retain useful notes when there is no dedicated script supervisor. Explain the limits of that arrangement. A photograph can help explain the position of a prop; it cannot automatically establish that every shot will cut together. Keep scene and take references with the observation.
Camera and media records identify the material captured and the technical context the next team needs. Useful references may include the camera, card or reel label, clip references, recording settings and relevant issues. The camera or data team maintains the records in the project’s agreed format.
Keep an offload record alongside them. Identify the source media, destinations, operator and verification result from the actual transfer process. A label saying “backed up” is insufficient when nobody can identify which source was copied where. The binder tool below can record a reference to that evidence; it does not inspect media or verify copies.
Sound notes help editorial understand the recording layout and relevant problems. Identify the recording reference, tracks or microphones, synchronization information and take-specific issues where applicable. The sound team owns the technical details and the delivery requirements for post sound.
A note such as “intermittent handling noise during answer three” is useful when it names the corresponding recording. Without that reference, an editor may have to rediscover the issue. Retain information about separate recordings or alternative takes instead of assuming the camera track contains everything needed.
Use an appropriate offload process with the data owner and retain its evidence. Blackmagic Design’s current Clone Tool demonstration describes separate-drive copies and checksum verification. A verified copy addresses transfer integrity; it does not by itself establish a complete disaster-recovery or retention plan.
Do not format or reuse source media based on an unverified binder checkbox. Follow the production’s agreed release process for media, and distinguish completed transfers from pending ones. The handoff should explain what is available, where it is and what remains unresolved.
Organize by project and document purpose. A practical structure can separate creative references, scheduling, contacts, locations, agreements, daily instructions, reports, media logs and archive material. Restricted financial or personal records should have the appropriate access rather than inheriting the broadest shared folder’s permissions.
Record the document title, responsible owner, version or date, source location, intended audience and current state. A note should explain what changed or what remains open. The register supports navigation; the underlying source remains the document or system the production has designated authoritative.
When issuing a new reference, preserve the prior one and update the current pointer. Avoid accumulating “final,” “final new” and “final approved” without a way to identify the applicable version. Choose a consistent naming convention appropriate to the production, and include an unambiguous date when a document belongs to a particular day.
A maintained digital source supports updates and history. An offline or printed snapshot can help people work where connectivity is unreliable. Prepare the specific material the day requires, check that it is readable and identify the version on the snapshot. Do not assume a link will load at the location simply because it works in the office.
Explain how an issued revision reaches people using offline copies. A printed call sheet does not update itself. If a person has an old copy, name the changed information and provide the new reference rather than hoping they notice a newer file in a shared folder.
A binder can contain contact details, negotiated rates and legal records alongside broadly useful creative material. Review who can view, edit, download and share each class of document. Do not confuse a hidden link or a filtered database view with an access boundary.
Google Drive’s current sharing guidance distinguishes viewer, commenter and editor access and discusses inherited folder permissions. Notion’s permissions guide similarly notes that the broadest access granted to a user applies. Test the recipient’s actual access rather than relying solely on a page label.
The local register’s inclusion checkbox controls which entered records go into its ZIP. It is not an authentication or permissions system. Full source JSON contains all entered rows, including excluded rows. Save that complete source only where it belongs, and inspect a selected package before sharing.
Consider an eight-person team recording four interviews and a workshop demonstration at two locations. This is an invented example, not a report of a customer production or a suggested universal schedule. The producer coordinates documents while camera, sound and creative owners maintain their specific references.
| Moment | Document decision | Useful handoff |
|---|---|---|
| Planning | The approved outline specifies which interview topics and demonstration actions are needed. | The breakdown identifies the demonstration equipment and a quiet interview space. The producer resolves access questions before issuing the day plan. |
| Preparing days | The schedule groups interviews at the first location and demonstration coverage at the second. | Each departmental owner checks their requirement. The location reference includes the agreed entrance and loading instructions. |
| Issuing day one | A current call sheet identifies the relevant calls and instructions. | The coordinator distributes the issued reference through the agreed route and handles any important late revision explicitly. |
| During capture | Camera and sound teams record media references and take-specific issues. | The creative owner notes preferred answers and missing coverage. The data owner retains actual offload and verification evidence. |
| Wrap and edit | The receiving editor gets the current outline, selected creative references, media map and reports. | The handoff identifies an interview pickup still needed. That open item is preserved rather than hidden behind a “complete” status. |
This project may not need a scripted cast Day Out of Days chart, but it still needs confirmed interview availability. It may use a simple floor plan instead of a fully illustrated storyboard. The responsible owner should decide how each requirement is met, including records that are not applicable, instead of dropping a category without discussion.
If a day-two location changes, update the location reference, schedule and daily instructions together. Explain the effect on departments and the approved creative plan. The binder register can flag the revised references; it cannot decide whether the replacement location, activity or agreement is suitable.
These six options are compared using current public primary documentation. They are not ranked by tested reliability, industry trust or measured speed. A production platform can generate specialized records; a document workspace can organize references. Either still needs owners and a maintained process.
| Platform | Useful role | Question to test |
|---|---|---|
| Storyflow | Its visual workspace brings creative references and planning material together. | Where will authoritative production and restricted records live? Its pricing distinguishes paid early access and invited collaboration from a forthcoming standalone Free plan. |
| StudioBinder | Its production-document resources cover breakdowns, schedules, call sheets and reports. | Which records does your account actually generate, and how will arbitrary documents and the wrap package be retained? |
| Notion | Pages and structured records can organize a document index, with configurable sharing. | Can recipients find the current reference and see only the intended information? Do not assume a view filter creates security. |
| Google Drive | File and folder storage with sharing controls can hold source documents and issued exports. | Who maintains the register and current version pointer? Check inherited access and how offline snapshots are prepared. |
| Yamdu | Its call-sheet workflow connects script elements, scheduling, distribution and confirmation tracking. | Does the chosen entitlement and recipient workflow fit your production? Test how important revisions reach people. |
| Celtx | Its pre-production offering connects script work, breakdown and scheduling. | Which downstream records and file exports does the project need beyond the generated plans? |
A small crew may already have a suitable document system. Add specialist software when it solves a defined need, such as schedule generation, distribution tracking or interconnected breakdowns. Compare seats, guest access, storage, exports and ongoing administration using current terms for your actual account. Do not use an old price or a “free” label as a substitute for checking the workflow.
At wrap, agree what the receiving team needs and what the production must retain. A useful handoff can include the current creative reference, coverage notes, media and sound maps, appropriate clearance references and an open-items list. The exact delivery requirements follow the contract and receiving organization’s instructions.
Distinguish delivered, received and accepted. A successful upload does not prove that the recipient can open the package or that all required materials are present. Record the actual handoff response, resolve missing records with their owners and retain the exact issued package reference.
Rights documentation should connect the intended material to the appropriate agreements or clearances. A folder label reading “chain of title” does not establish ownership or permission. Ask the responsible producer and advisers to confirm the requirements for the project, and preserve authoritative evidence with appropriate access.
Retention varies with agreements, organizational policy and applicable obligations. Do not apply a universal “keep forever” or fixed-year instruction to all records. Identify the owner of the retention plan, including personal data, contract documents and media, and keep source exports where that plan requires them.
No. Treat the categories as an inventory to adapt. Record why something is not applicable and how the production meets the underlying need. Confirm project-specific requirements with the responsible owners.
Name a coordinating person, often the producer, and retain departmental owners for the details they understand. A central index works best when changes have a clear route to the people using them.
The material people need for their work on the day, in a readable current snapshot. Determine that with the team and preserve restricted access. Explain how revisions will reach people holding old copies.
Coverage and take notes can still help editorial. Identify the actual needs of the edit and who records them; do not pretend that a reduced arrangement provides every function of a dedicated script supervisor.
A report records information about the media or transfer. Actual verification comes from the transfer process and its evidence. The local register does not inspect footage, hashes or storage destinations.
No. It organizes entered references and notes. Obtain the appropriate authoritative documents and keep them with the responsible production owner.
No. ZIP and selected CSV contain included rows only. Complete source JSON contains every entered row so you can restore your work. Inspect exports and choose the appropriate destination.
No. It contains your selected entered text and a register. References are labels, not fetched attachments. Package the actual authoritative files separately where required.
Name who maintains the document and who answers an unresolved question.
Connect the issued reference to the decision and preserve prior versions as history.
Give recipients the information they need through the appropriate access.
A binder connects the current reference to the people who need it.
Start with fourteen editable categories or add your own. Enter references and complete notes, then choose which rows belong in a selected package. This tool packages entered text with JSZip; it does not fetch documents, verify signatures, inspect media or determine production readiness.
Only checked rows appear in selected ZIP and CSV. Complete source JSON and text preserve all rows, including excluded information. The package note is included in both selected and complete exports; keep it appropriate for the package audience.
The ZIP contains a selected register JSON, spreadsheet-safe CSV, README and one text note per selected row. Referenced files are not attachments. CSV formula-like cells receive a protective apostrophe; complete source JSON retains the original strings. Changing inputs clears the review, and a pending ZIP is discarded if the inputs change. Invalid restore leaves current work intact. Save source before reload: this page has no automatic storage or access-control system.