Production & Call-Sheet Manager
And call_sheet.html comes back out with the crew table, the scene schedule and the sunrise time already in it.
Move a 06:00 call to 07:30 in one config file, run it.
And call_sheet.html comes back out with the crew table, the scene schedule and the sunrise time already in it.
$35/mo for as many productions as you shoot, or $29 for a single production. Both give you the HTML sheet, the crew table and the budget report. Cancel any day and keep every sheet you generated.
The sheet went out at six. The location changed at midnight.
Call is 06:00. At 11:40pm the location moves, and the sheet you sent at six is now wrong in four places: the address, the map link, three of the call times, and the sunrise you built the whole first setup around.
So you open last week’s sheet and save-as. The crew list goes in again. The schedule goes in again. You paste the new address and the table formatting detonates. At 12:40 you send version three into a group thread and hope nobody reads version two.
Next morning somebody shows up at the old location. There’s always somebody.
How does the sheet get rebuilt in seconds?
The shoot lives in a text file, so changing it is changing one line.
- Write the shoot once as JSON:
title,date,callTime,location,address, and aschedulearray of{time, scene, desc}. Addsunrise,sunsetandnotesif you want them on the page. - Point
CREW_CSVat a crew list ofname, role, callTime, phone, email. PointBUDGET_CSVatcategory, budgeted, actualif you’re tracking the money. Both optional. - Run it.
call_sheet.htmllands in your output folder and opens straight in a browser. When the location moves, edit one field, run it again, send version three.
What ends up on the sheet
Four outputs, and the one that matters is the file you attach to the email.
- Renders
call_sheet.htmlwith no external CSS, JavaScript or CDN inside it, so the file a crew member opens on a phone at 5:40am on one bar of signal is exactly the file you sent. - Mirrors the same sheet to
CALL_SHEET.mdfor the people who’d rather have it pasted into the thread than opened as an attachment. - Puts sunrise and sunset on the page, so the argument about whether there’s still light for scene 2B happens the night before instead of on the day.
- Builds
BUDGET.mdfrom the budget CSV with per-category variance and a running total, and it reads(120.00)as negative 120, the way the person who typed it meant it. - Validates the shoot config instead of crashing on it. A missing
callTimecomes back as a plain list of errors, not a stack trace at 12:40 in the morning. - Escapes every value that goes into the HTML, so an apostrophe in a location name or a crew member’s surname doesn’t quietly break the table.
- Writes
production.jsonwith the shoot, the crew and the budget summary, which is the file your producer wants when they ask what the day cost.
Who this is wrong for
Built for the shoot with no production office. A creator, a small crew, one to five days, one person writing the call sheets in between doing everything else. Wrong for you if you have a coordinator whose actual job is distribution, because it won’t send the sheet and it won’t tell you who opened it. And it does one day per config today. A three-day shoot means three configs, and that’s how it works until multi-day lands.
Against a Google Docs template, and against StudioBinder
StudioBinder is the better tool if you can afford it and staff it. It sends the sheet, it tracks who opened it, and it carries the whole production behind the sheet, shot lists and scheduling and stripboards. That’s a real advantage and it’s worth the money on a real production. What it isn’t is fast at midnight, when the thing you need is to change one address and re-send. The Google Docs template you’ve been duplicating is fast to start and gets slower every week, because you retype the crew every time. Editing one line of a text file and re-running takes seconds, and it produces a page nobody has to log in to read.
The crew’s phone numbers
A crew CSV holds names, phone numbers and email addresses, and none of it leaves your machine. Nothing is uploaded and nothing phones home. The HTML sheet is self-contained on purpose: no CDN, no tracker, no font fetched from a server, so nobody on the outside learns anything from the fact that your gaffer opened the file at 5:12am. Output is written under OUTPUT_FOLDER only, at 0600 permissions. The sheets are just files. Attach them to an email or don’t.
Two prices, and what shows up
$35 a month covers as many productions as you shoot. $29 covers one, if one is all you have this year. Either way you get call_sheet.html, CALL_SHEET.md, BUDGET.md and production.json. Setup is writing the shoot config once, which takes about as long as filling in the header of your old template did. After that the first sheet is one run away, and version three is another run away.
Security and privacy
Handles production data: crew contact details (phone/email), shoot locations, and budget figures. Security is designed in.
Principles
– Local-first. SHOOT_CONFIG, CREW_CSV, and BUDGET_CSV are read from disk and never transmitted anywhere; nothing in this tool touches the network. Nothing is uploaded, no telemetry, no cloud dependency.
– Non-destructive. Source files (shoot config, crew CSV, budget CSV) are only read, never modified or deleted.
– Least privilege. Reads SHOOT_CONFIG/CREW_CSV/BUDGET_CSV, writes only under OUTPUT_FOLDER.
Protections implemented (v0.1.0)
– Path-traversal defense — every output filename is sanitized (safeSegment) and every write is checked with assertWithinRoot(), so the call sheet can’t be written outside OUTPUT_FOLDER.
– Fail-fast config validation — clear errors for missing SHOOT_CONFIG/OUTPUT_FOLDER before any file is touched; parseShootConfig additionally validates the shoot JSON’s shape (required fields, schedule array) and never throws, returning a list of errors instead.
– Restrictive permissions — the generated call_sheet.html, CALL_SHEET.md, BUDGET.md, and production.json are written 0600.
– HTML-escaping — every value that flows into call_sheet.html (title, location, address, notes, crew names/roles/contact info, scene descriptions) is HTML-escaped, so a stray <script> in a crew list or shoot config renders inert rather than executing.
– Defensive parsing — the CSV parser and currency parser never throw on malformed input (missing fields default to empty string, unparseable budget amounts default to 0); a malformed SHOOT_CONFIG produces a clear error list rather than crashing the run.
– Secrets discipline — .env and generated CallSheets/ output are git-ignored; no secrets or production data in the repo. Crew phone numbers and emails are only ever written to the local OUTPUT_FOLDER, never transmitted.
Distribution / AV trust
Known limitations / roadmap
– v0.1.0 generates one call sheet per run; multi-day shoots need one SHOOT_CONFIG/run per day.
– No PDF export yet — call_sheet.html prints cleanly from a browser in the meantime.
– Weather/sun times are pass-through fields (sunrise/sunset in SHOOT_CONFIG); there is no live weather lookup.
Reporting
Report suspected vulnerabilities privately to the maintainer before public disclosure.
Frequently asked questions about Production & Call-Sheet Manager
What is a production & call-sheet manager and what does it do?
A production & call-sheet manager is the tool a small production team uses to plan a shoot and keep everyone on the same page. Instead of building call sheets by hand in a document and emailing crew schedules around, you enter your shoot details, crew, and locations once, and the tool generates the call sheets and the schedule from that. The Production & Call-Sheet Manager is built for very small productions and creators, the shoots that do not need a studio-scale system but still need everyone to know where to be, when, and with what.
The output of any shoot is a finished work, a film, a video, a set of images, and that work is copyrighted the moment it is fixed in a tangible form, a point the U.S. Copyright Office makes in its overview, What is Copyright. Running the production in an organized way is part of protecting the value of what you are making. When the call sheets, the schedule, and the budget all trace back to one plan, the record of how the work came together is clear, which matters if questions about the production ever arise later.
The three jobs the tool handles are tightly linked. AI-assisted call sheets pull from the shoot details you entered, crew scheduling arranges who is needed when, and a live budget tracks costs as the production runs. Because all three come from the same plan, a change to the schedule shows up on the call sheet and against the budget rather than living in three files that slowly disagree. That single source is the difference between a plan and a pile of documents.
Here is the honest scope. This is not a studio operations platform, and it is not trying to be. StudioBinder and Yamdu own the mid-market, and the production & call-sheet manager plays deliberately at the very small end, the solo creator and the tiny crew who find those tools heavier and pricier than their shoots justify. If you are running large productions with big departments, you will outgrow it. If you are not, that is the point.
Pricing follows the same logic. You can pay monthly or per production, whichever matches how often you shoot, so an occasional creator is not locked into a subscription between jobs. For a small team, that flexibility is part of the fit. You can see how the tool is aimed at small productions and creators on the creators and agencies industry page, and judge whether a right-sized call-sheet and scheduling tool beats the document-and-email approach you use now. Setup stays simple on purpose. You put in the shoot once, the tool builds the call sheet and the schedule from it, and the budget starts tracking against the plan from day one. There is nothing to configure that a one-person or five-person crew would not use. That restraint is deliberate, because a small production loses time to tools that assume a structure it does not have. The value is in doing the few things a small shoot genuinely needs, cleanly, rather than offering fifty features a solo creator would spend more time switching off than using on an ordinary day.
Does the production & call-sheet manager help when my crew are independent contractors?
On most small productions the crew are not employees. They are independent contractors hired for the shoot, the camera operator, the gaffer, the sound person, brought on for a day or a week and then gone. That arrangement carries obligations, both for them and for you as the person paying them. The IRS lays out the filing and self-employment tax rules that apply to independent workers in its self-employed individuals tax center, and keeping clean records of who worked which day is the groundwork those obligations rest on.
The production & call-sheet manager helps by making the crew record a natural part of scheduling. When you schedule crew for a shoot, you are also building a record of who was called, for which days, on which production. That record is exactly what you need later when it is time to account for what each contractor was paid and to hand a preparer a clear picture of the labor on a given job. The scheduling and the recordkeeping are the same act.
This matters because the alternative is reconstruction. Without a scheduling record, working out who worked how many days on a shoot that wrapped months ago means digging through texts and memory, which is exactly when contractor records get sloppy. A production & call-sheet manager that keeps the crew schedule tied to each production means the answer is already written down, day by day, from the call sheets you already made.
It is worth stating the limit plainly. The tool does not calculate self-employment tax, issue tax forms, or decide whether a given worker is a contractor or an employee. Those are questions for you and your preparer, guided by the IRS rules. What the tool does is keep an organized record of the crew you scheduled and the days they worked, so the inputs to those decisions are accurate and easy to find rather than pieced together after the fact.
For a small production that hires a rotating crew shoot after shoot, that running record is quietly valuable. Each production carries its own crew schedule, and together they form a clear history of the contract labor your work depended on across the year. When the crew record is a byproduct of the scheduling you did anyway, the contractor side of running a production stops being a year-end scramble. You can see how scheduling and the records it produces fit small productions on the Production & Call-Sheet Manager product page. There is also a coordination benefit that feeds the same record. When a contractor knows their call time from a call sheet the tool generated, and you know from the same schedule that they were booked, both sides are working from one version of the arrangement. That reduces the small disputes that crop up when a crew member remembers a different call time or a different day than you do. The schedule is the shared truth, and because it doubles as your record of who worked when, the coordination you do to run the shoot is also the documentation you keep for later.
Call sheets hold crew contact details, so is that data kept safe?
A call sheet is, by design, a sheet full of personal information. Names, phone numbers, home or hotel addresses, emergency contacts, sometimes more, all gathered so a crew can be reached and coordinated. That makes every call sheet a small pile of personal data, and it deserves the same care any business owes the personal information it collects. The FTC’s guide, Protecting Personal Information: A Guide for Business, frames the job as five steps, take stock, scale down, lock it, pitch it, and plan ahead, and a call sheet touches every one of them.
The production & call-sheet manager helps with take stock and scale down first. When call sheets are generated from one place, you know where your crew’s contact details are, instead of having them copied into a dozen emailed PDFs scattered across everyone’s inboxes. Each of those loose copies is a place the data could leak from, and the more call sheets that go out as attachments, the harder the information is to account for. Keeping the source in one tool shrinks that scatter.
Lock it and pitch it are about access and disposal. A crew’s contact details do not need to live forever in a hundred old email threads after a shoot wraps. Having the call sheets organized in one place means you can actually manage that information rather than losing track of every copy the moment you hit send. The tool keeps the crew data with the production it belongs to, which is a far cleaner arrangement than a trail of forwarded files.
The honest limit is the same one that applies to any working tool. The production & call-sheet manager is not a security product, and it will not claim to be one. What it offers is organization, one source for the call sheets rather than an uncontrolled spray of attachments, which is the practical starting point the FTC describes. Guarding your own accounts and being careful who you share a call sheet with is still on you.
For a small production, the realistic gain is fewer copies of your crew’s personal details floating around where you cannot see them. When call sheets come from one organized source, the take-stock-and-lock-it advice becomes something you can act on rather than an abstraction, and your crew’s information gets treated with the care they would expect. You can read how the tool keeps call sheets and crew details organized on the Production & Call-Sheet Manager product page. It also helps to think about what happens after a production wraps. Old call sheets have a way of living forever in inboxes, long after the crew has moved on to other jobs. Keeping them organized in one place means you can decide, deliberately, what to hold and for how long, instead of leaving stray copies of your crew’s home addresses and phone numbers in email threads you have forgotten about. For a producer who cares about treating a crew well, that kind of tidy handling of their personal details is part of the respect the working relationship deserves, not an afterthought.
How is this different from StudioBinder or Yamdu, and does it help track what I pay?
The difference is scale and price. StudioBinder and Yamdu are built for the mid-market, productions with real departments and budgets to match. The Production & Call-Sheet Manager is aimed at the opposite end, the very small production and the solo creator who find those platforms heavier and more expensive than a small shoot warrants. It is not trying to out-feature them. It is trying to be the right size for a team that a studio-scale tool would overwhelm.
Part of being right-sized is handling the money side without becoming an accounting suite. Small productions still pay crew and vendors, and those payments matter at year end. When payments run through cards or third-party payment networks, they can be reported on a Form 1099-K, which the IRS explains in its overview, Understanding your Form 1099-K. The live budget in the tool tracks what a production spends as it happens, so the record of what you paid out is building itself rather than waiting to be reconstructed against a form months later.
That budget tracking is where a production & call-sheet manager earns its keep beyond the call sheets. Because the budget updates as the shoot runs, you can see costs against plan in real time, and you finish a production with a clear record of what went where. When a 1099-K or a vendor statement arrives, checking it against your own budget record is a lookup rather than a guessing game across receipts and memory.
It is fair to be clear about the boundary. The tool tracks a production budget, it does not do your bookkeeping or file your taxes, and the 1099-K reference above is background for why a clean spending record helps, not a claim that the software handles the form. What it gives you is an accurate, live picture of production costs, which is one solid input to the accounting you or your preparer do afterward.
So the plain comparison is this. If you run large productions, a mid-market platform earns its price. If you run small ones, a production & call-sheet manager that keeps call sheets, crew, and a live budget in one right-sized tool fits better and costs less, with the option to pay per production when you shoot only now and then. You can see where it sits against the bigger tools on the creators and agencies industry page and decide which scale actually matches your work. The pay-per-production option reinforces the point. A creator who shoots a handful of times a year should not carry a subscription through the quiet months, and being able to pay only when a production is actually running keeps the tool honestly matched to a small operation’s cash flow. Combined with the live budget, that pricing means the cost of the tool itself is easy to see against the cost of the shoot. For a small team watching every dollar on a production, a tool that is transparent about its own price fits the same discipline you apply to everything else on set, and it means the manager pays for itself the first time it catches a budget overrun before it happens rather than after.
Does the tool help with branded productions and disclosure obligations?
A lot of small-production work today is branded content, a shoot commissioned by a company to promote a product. That kind of work carries a disclosure duty, because when there is a material connection between a creator and a brand, the audience has to be told clearly. The FTC spells out what counts and how obvious the disclosure has to be in its guide, Disclosures 101 for Social Media Influencers. For a producer taking on branded shoots, keeping the details of each such production organized is part of handling that duty responsibly.
The production & call-sheet manager does not post anything or police captions, and it will not decide whether a finished piece was disclosed correctly. What it does is keep each production organized as its own record, with the shoot details, the crew, and the budget in one place. When a shoot is a branded job, having the production documented, who worked on it, what it cost, what it was for, means the paper trail around that commission is clear rather than scattered, which is exactly what you want if a client or the brand later has questions about the work.
This organization is quietly useful because branded-content questions tend to arrive after delivery. If a brand asks what was produced under a given agreement, a production & call-sheet manager that kept the shoot as a single record lets you answer from documentation instead of memory. The call sheets and the budget for that production are attached to it, so the facts about the job are where you can find them.
The limit is worth stating clearly. Compliance with the FTC guidance is the creator’s and the brand’s responsibility, not the software’s, and the tool cannot make a disclosure clear and conspicuous on a platform it never touches. What it can do is keep the production behind a branded piece well documented, so the business side of the commission is organized even though the disclosure itself happens elsewhere, on the post.
For a creator whose work mixes personal projects and branded commissions, keeping each production as its own clean record is simply good practice. The branded jobs carry extra scrutiny, and being able to show exactly how a commissioned shoot was planned and run is part of being a professional counterpart to the brands you work with. You can see how the tool organizes each production end to end on the Production & Call-Sheet Manager product page, and consider how a documented shoot record would serve you when a branded client comes back with questions. In the end the tool draws a clean line. The creative and legal duty to disclose sits with you, and the tool sits behind it, keeping the production that produced a branded piece documented and easy to account for. That separation is the right one. You would not want software pretending to sign off on your disclosures, and you do want software that keeps the shoot behind them organized. For a producer building a reputation with brands, the ability to show a well-run, well-documented production for every commission is worth more over time than any single clever feature.
| Attributes | Value |
|---|---|
| Deployment |
Cloud |
| Platform |
Web |
| License Type |
Subscription |
| Billing Period |
Monthly |
| Target Customer |
Creators & Agencies |
| Free Trial |
Yes |
Frequently bought together
-
AI Grant / Proposal Writer (local RAG)
$39.00 -
AI QA / Citation Layer for AI outputs
$39.00 -
AI Receptionist That Acts
$95.00 -
AI Support Inbox for Microteams
$39.00 -
Batch Image / Brand Asset Generator
$65.00 -
Batch Video/Photo Culler for Creators
$119.00 -
Bulk Document AI Processor / Batch PDF Splitter+Binder
$249.00 -
Client Portal + AI Concierge / Micro Portal Builder
$39.00







