Assistant editors
Keep all production paperwork organized and accessible. No more hunting through email for yesterday's camera report or continuity notes.
Digital file cabinet for post-production
Organize lined scripts, facing pages, and set documents
Developing Tank's Editor's Binder keeps lined scripts and facing pages in a 2-up book view, and stores call sheets, camera reports, sound reports, and notes in one project space.
DocumentType
Episode 103: Lined ScriptLined script
Episode 103: Facing PagesFacing pages
Day 12: Camera ReportCamera report
Day 12: Sound ReportSound report
A secure binder for scripts and set docs, tied to scenes and shoot days.
Physical binder vs. digital editor's binder
Without Developing Tank
- Physical 3-ring binder with loose documents
- Flipping between multiple documents by hand
- Documents scattered across email and shared drives
- No searchable index or metadata
- Risk of losing or misplacing critical paperwork
Result: Inefficient workflows, lost time hunting for documents, no audit trail.
With Developing Tank
- Digital binder with 2-up book view for scripts
- Paired facing pages and lined scripts side-by-side
- All documents organized by scene, shoot day, and type
- Searchable, tagged, and indexed automatically
- Secure access with project-level permissions
Result: Fast retrieval, organized workflows, complete audit trail.
Editors
Reference scripts, facing pages, and notes without leaving the edit bay. 2-up view pairs everything you need in one place.
Script supervisors
Store lined scripts and facing pages as they're created. Editorial teams access the latest version after upload instead of waiting for handoff.
How it works
Three steps to an organized digital binder
Upload production documents and organize them by scene, shoot day, and document type.
1
Upload documents
Add PDFs and images: lined scripts, facing pages, camera reports, sound reports, call sheets, or notes.
2
Tag by context
Assign documents to scenes or shoot days so editors can find them during review.
3
Access documents by scene or shoot day
View documents in 2-up book view, search by type, or browse by scene.
Inputs
PDFs + images (scripts, lined scripts, reports)
Process
Organize by scene/shoot day, create 2-up view, build index
Outputs
Searchable binder + 2-up book view + check views
Faster lookupsFind any document in seconds, not minutes of hunting.
Cleaner workflowsScripts and facing pages always paired; no context switching.
Better organizationScene and shoot-day tagging keeps everything discoverable.
What you store
Lined scripts, facing pages, call sheets, camera and sound reports, continuity notes, and any PDF or image file your team produces during post-production.
How it organizes
Automatic scene detection pairs scripts with facing pages. Shoot-date tagging groups all day-of reports. Custom labels let your team organize by episode or department.
Who accesses it
All project members can view and reference binder documents. Access is controlled by project membership. Binder data stays inside your project.
Binder features
Common document organization patterns
Script and facing page pairing
Pair a lined script with its facing pages in a 2-up book view. Turn pages together without switching between documents.
Scene-based organization
Organize documents by scene number. Scripts, facing pages, and notes for Scene 12 stay grouped together.
Shoot-day grouping
Tag documents with the shoot day. Camera reports, sound reports, and call sheets for Day 5 stay together for production reference.
Searchable index
Search by scene number, document type, episode, or custom tag.
Document storage
Supported document types and storage
Scripts and facing pages
Pair lined scripts with facing pages. Multi-page PDFs are supported, and the 2-up view lets you reference both at the same time.
Production reports
Camera reports, sound reports, continuity notes, and miscellaneous PDFs from production. All tied to the scene or shoot day.
Image files
JPG, PNG, TIFF, and other image formats. Useful for hand-written notes, camera settings, or any visual reference from set.
Security and access
Documents are stored securely on Developing Tank servers. Access is controlled by project membership. You own your data and can delete it anytime.
Frequently asked questions
Can I view a lined script alongside facing pages?
Yes. The 2-up book view pairs a lined script on the left with facing pages on the right. Page counter drives both panes, so you stay in sync across documents.
Does it work with camera reports and sound reports?
Yes. Upload camera and sound reports as CSV or TXT. We parse and link entries to the Codebook, and they're searchable within the binder.
Can I search documents by content or metadata?
You can browse by scene or shoot day. Full-text search is in development. For now, use your browser's find feature within a document.
Can I import script supervisor logs as CSV?
Yes. Upload script supervisor camera logs as CSV or TXT files. Developing Tank parses the entries and links them to clips and scenes.
Who can access my binder documents?
Only project members with the appropriate role (Viewer, Editor, Admin). Access is controlled by project permissions. You can delete documents anytime.
Is my data secure?
Yes. Documents are stored securely with encryption. Access is verified per-request via Firebase authentication + RLS policies. See our Trust page for details.