Why distribute production documents as PDF instead of editable files?

Because on a shoot everyone must be looking at the same thing, and a PDF guarantees that. A script or storyboard exported to PDF renders identically on the director’s laptop, the AD’s tablet, and a runner’s phone — same page breaks, same scene numbers, same frame order — with no risk of someone accidentally editing the master or seeing a reflowed layout. Editable formats are for authoring; the PDF is the locked, distributable version of record. When the camera assistant says "we’re on page 14," page 14 is the same page for everyone, which is exactly what a fast-moving set needs.

How do I assemble a production bundle for the crew?

Merge the documents the crew needs into one ordered PDF and add bookmarks so people can jump between sections. A typical bundle might be the script, then the storyboard, then the shot list and any reference material, with a call sheet issued separately per day because it changes daily. One navigable file beats a folder of loose attachments that someone inevitably opens the wrong version of. Keep the individual documents as masters and rebuild the bundle when something changes, so the packet is always an assembly of current parts.

How should I handle script and storyboard revisions?

Treat each revision as a dated, immutable version and never overwrite the last. Film convention uses colored revision pages and revision dates for exactly this reason — so the crew can tell at a glance which version they are holding. For PDFs, encode the revision and date in the filename and ideally on the page (a revision stamp), keep prior versions archived rather than deleted, and reissue a complete file rather than patching. The goal is that anyone on set can confirm they have the current pages, and that you can reconstruct exactly what was distributed when, which matters when a scene changes the night before a shoot.

What is the best way to share unreleased scripts and boards securely?

Unreleased creative material can be confidential (embargoes, NDAs, competitive sensitivity), so control both the file and the channel. Encrypt sensitive PDFs with an open password and send the password separately; for wider crew distribution, use a sharing method that lets you limit and, ideally, log access rather than blasting an attachment to a large list. Watermarking copies with the recipient’s name deters leaks of pre-release material. Match the protection to the sensitivity — a public-facing shoot needs little; an embargoed production needs encryption, controlled sharing, and watermarks.

How do I keep production PDFs small enough to share fast on set?

Compress the heavy parts — usually storyboard frames and reference images — to a screen-appropriate resolution, since crew are viewing on phones and tablets over patchy on-location connections, not printing gallery prints. Keep text documents (script, shot list) as native text so they stay crisp and tiny. A bundle that downloads instantly on a weak signal is one people actually open; a 60 MB packet that times out gets ignored. Test the download on a phone over cellular before you send it to the unit.

Is it safe to assemble production documents with an online tool?

For unreleased scripts, boards, and anything under embargo or NDA, prefer client-side tools. Server-side tools upload your files to a third party where they may be cached; client-side (in-browser) tools merge, compress, and secure locally so the file never leaves your device — ScoutMyTool’s PDF tools work this way. Creative material leaking early is a real risk in production, so confirm a tool processes client-side before uploading anything you would not want seen ahead of release.

6 min read

PDF for video producers — storyboards + scripts

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

On my first shoot as a producer, the morning was lost to a version problem: half the crew had yesterday’s script, the storyboard was three separate files, and someone was working off a call sheet for the wrong day. The work itself was ready; the documents were chaos. The fix was unglamorous — lock everything to PDF, assemble one navigable bundle, and version revisions properly — and it made every subsequent production calmer. This guide covers packaging scripts, storyboards, shot lists, and call sheets as PDFs the whole crew can open identically, keeping revisions straight, and sharing sensitive material without it leaking.

The production document toolkit

Document	Tool	Why it matters on set
Script	PDF (locked)	Page-faithful; everyone references the same pages
Storyboard	Merge-PDF	Frames in sequence as one shareable file
Shot list	Add page numbers	Numbered, scannable on set
Call sheet	PDF (per day)	Identical on every crew phone
Production bundle	Merge + bookmarks	Script + boards + lists in one navigable packet
Share with crew	Compress / secure	Fast download; protect unreleased material

Step by step — package a production for the crew

Lock each document to PDF. Export the script, storyboard, and shot list to PDF so they render identically for everyone and cannot be accidentally edited — the distributable version of record.
Assemble a navigable bundle. Merge script, boards, and lists into one ordered PDF, add page numbers, and add bookmarks so the crew can jump between sections quickly.
Version revisions, do not overwrite. Stamp the revision and date on the file (and ideally the page), archive prior versions, and reissue a complete file so everyone can confirm they have the current pages.
Compress for fast on-set download. Shrink storyboard frames and reference images to a screen-appropriate resolution so the bundle opens instantly on a phone over a weak connection.
Protect unreleased material. Encrypt sensitive PDFs and control the sharing channel; watermark copies with the recipient’s name to deter leaks of embargoed scripts and boards.
Issue call sheets separately, per day. Because they change daily, distribute the day’s call sheet as its own current PDF rather than burying it in a static bundle.

Versioning is the difference between a calm set and a chaotic one

The film industry’s colored-revision-page convention exists because a production is a stream of changes and the expensive failure is people acting on the wrong version. You do not need the full colored-pages system for a small shoot, but you do need its principle: every distributed document carries a visible revision and date, old versions are kept rather than overwritten, and changes go out as a fresh complete file. Encode that in your PDF filenames and on the pages themselves, and a crew member can always answer "is this current?" without asking. It is the same append-only discipline that keeps any document set sane, and on a set — where a wrong page can mean a wasted setup — it pays for itself the first time a scene changes overnight.

FAQ

Why distribute production documents as PDF instead of editable files?: Because on a shoot everyone must be looking at the same thing, and a PDF guarantees that. A script or storyboard exported to PDF renders identically on the director’s laptop, the AD’s tablet, and a runner’s phone — same page breaks, same scene numbers, same frame order — with no risk of someone accidentally editing the master or seeing a reflowed layout. Editable formats are for authoring; the PDF is the locked, distributable version of record. When the camera assistant says "we’re on page 14," page 14 is the same page for everyone, which is exactly what a fast-moving set needs.
How do I assemble a production bundle for the crew?: Merge the documents the crew needs into one ordered PDF and add bookmarks so people can jump between sections. A typical bundle might be the script, then the storyboard, then the shot list and any reference material, with a call sheet issued separately per day because it changes daily. One navigable file beats a folder of loose attachments that someone inevitably opens the wrong version of. Keep the individual documents as masters and rebuild the bundle when something changes, so the packet is always an assembly of current parts.
How should I handle script and storyboard revisions?: Treat each revision as a dated, immutable version and never overwrite the last. Film convention uses colored revision pages and revision dates for exactly this reason — so the crew can tell at a glance which version they are holding. For PDFs, encode the revision and date in the filename and ideally on the page (a revision stamp), keep prior versions archived rather than deleted, and reissue a complete file rather than patching. The goal is that anyone on set can confirm they have the current pages, and that you can reconstruct exactly what was distributed when, which matters when a scene changes the night before a shoot.
What is the best way to share unreleased scripts and boards securely?: Unreleased creative material can be confidential (embargoes, NDAs, competitive sensitivity), so control both the file and the channel. Encrypt sensitive PDFs with an open password and send the password separately; for wider crew distribution, use a sharing method that lets you limit and, ideally, log access rather than blasting an attachment to a large list. Watermarking copies with the recipient’s name deters leaks of pre-release material. Match the protection to the sensitivity — a public-facing shoot needs little; an embargoed production needs encryption, controlled sharing, and watermarks.
How do I keep production PDFs small enough to share fast on set?: Compress the heavy parts — usually storyboard frames and reference images — to a screen-appropriate resolution, since crew are viewing on phones and tablets over patchy on-location connections, not printing gallery prints. Keep text documents (script, shot list) as native text so they stay crisp and tiny. A bundle that downloads instantly on a weak signal is one people actually open; a 60 MB packet that times out gets ignored. Test the download on a phone over cellular before you send it to the unit.
Is it safe to assemble production documents with an online tool?: For unreleased scripts, boards, and anything under embargo or NDA, prefer client-side tools. Server-side tools upload your files to a third party where they may be cached; client-side (in-browser) tools merge, compress, and secure locally so the file never leaves your device — ScoutMyTool’s PDF tools work this way. Creative material leaking early is a real risk in production, so confirm a tool processes client-side before uploading anything you would not want seen ahead of release.

Citations

Build your production bundle in the browser

ScoutMyTool Merge PDF combines script, storyboard, and shot list into one navigable packet — entirely client-side, so unreleased material never leaves your device. Then bookmark, compress, and version for the crew.

Open Merge-PDF tool →