Indie production

Give every shoot decision a home.

Without a dedicated first AD, make the responsibilities and remaining day visible. Prepare current documents, nominate a clock owner and rehearse the tradeoffs before the set needs an answer.

An original diagram connecting a revised script, a running order and a shoot-day checkpoint

Write the responsibility.

A name, a revision and a specific next action beat a document everyone assumes somebody checked.

Count the real minutes.

Setups, moves, meals and wrap belong in the day. Completed items and remaining time tell different stories.

Keep the decision human.

A schedule can reveal pressure. It cannot decide staffing, safety or which performance the film needs.

Rehearse the day.
Keep the record.

Start with the fictional courtyard day from the guide: nine work items and eight production records. Change durations, nominate owners and see what a real checkpoint means.

Times use one calendar day in the entered local schedule. If the finish crosses midnight, plan a separate day. Elapsed minutes are entered by you; this is not an automatic stopwatch. All durations and priorities are editable planning assumptions.

JSON restores the complete project, setup ledger and register. CSV and Markdown preserve all source notes and dropped items. Exports are general planning records, not vendor-native files. Browser storage is optional: use Save; reset removes the saved example from this browser. Inputs are processed in this page; no AI inference or software integration is performed.

The bars show the active planned sequence; text cards below retain the full work. Completed work contributes to planned checkpoint progress; dropped work remains in the ledger but is excluded from remaining work. Essential breaks or wrap should remain Essential.

Running order

Document owners and checked revisions

Ready, checked revision and owner are entered notes, not verified permissions. A revision mismatch asks for review; a missing owner asks for responsibility. Change the current script revision to review dependent records.

What happens when a runtime or input is unavailable?

The editable source remains visible. If required D3 or Luxon cannot load, or dates and durations are invalid, derived results clear and save/export controls stay disabled. Correct inputs or reload after the required runtime returns. An invalid imported file is rejected while your current valid plan is retained. Keep a downloaded JSON if browser storage is unavailable.

How is the checkpoint arithmetic calculated?

Window = agreed finish minus start. Planned work excludes Dropped items. Completed planned minutes sum Done items. Behind/ahead compares entered elapsed minutes against those completed planned minutes. Remaining minutes sum Planned items. Projected finish = start + elapsed + remaining; finish slack = agreed finish minus projected finish. Durations are estimates and elapsed time is your observation; the result is not a prediction model.

Script revision flows into a reviewed running order and a human checkpoint

A current plan has a revision, an owner and a way to change. The useful question is what remains, who can decide, and what the next update must reach.

Pre-production without a first AD: make responsibility visible

An indie crew can share responsibilities, but a document cannot run a set. Build a current script breakdown, a feasible running order and a named owner for each production obligation. During filming, assign a person who can watch the clock while the director works with performers. Hire an experienced first assistant director when coordination, complexity or risk exceed what your crew can manage. A small crew count alone does not establish that a shoot is simple.

The central problem is competing attention. A director may also produce, secure locations and coordinate documents during preparation. On the day, those jobs collide: an actor needs direction while a location contact wants an answer and a department needs permission to change the plan. Advance decisions reduce that collision; they do not eliminate live judgment.

Use four responsibility columns rather than hoping the director will remember everything:

Responsibility Concrete output before filming Decision that remains live
Producer Scope limit, funded budget, agreements, contingency and decision authority Whether a proposed change is affordable and permitted
First AD / nominated floor lead Running order, realistic durations, cast availability and contingency discussion Safe sequencing, communication and an informed response to delay
Location lead Access agreement, applicable permissions, recce record, contact and verified logistics Changes to access, neighbours, conditions or location constraints
Coordinator / document owner Current contact list, version register, distribution list and acknowledgments Replacing obsolete documents and checking that the right people received changes

One person can hold several columns during preparation. Record who covers them during the shoot, including a backup when that person is performing, driving, recording sound or otherwise occupied. Asking the sound recordist to announce time may be possible between setups; it is unsuitable when it distracts them from recording or another duty. The arrangement must fit the actual crew.

The workbench above keeps that distinction explicit. Its document register tracks the revision each owner has checked. Its running order calculates planned times and remaining duration from your entries. It cannot confirm a permit, assess a location, negotiate a deal, discover a missing breakdown element or establish that a filming activity is safe.

Five AD functions, with an owner for the live decisions

Build the schedule. Begin with actual availability and restrictions, then group compatible work by location, lighting conditions, cast and setup. Script order is usually a poor starting point because it can repeat moves and lighting work. It may still be useful for a particular performance, changing continuity or an unusual production; treat it as a creative choice whose cost is visible. Record travel, load-in, setup, meals, resets and wrap instead of counting only camera time.

Prepare the running order. Give each setup a stable identifier, scene reference, purpose, owner, estimated minutes and contingency note. A drawing or floor plan can be more useful than polished boards for a controlled dialogue scene. A complex move or unfamiliar space may justify fuller previs. Put a printed or downloaded current order in the hands of the floor lead, with the revision and date visible.

Monitor progress during the day. Choose checkpoints while useful adjustments remain possible. A third and two thirds through the working period are reasonable illustrative positions, not an industry rule. Compare actual completed work against the planned cumulative duration; counting setups alone treats a five-minute insert and a ninety-minute lighting setup as equivalent. Recalculate remaining time and include any breaks or moves still ahead.

Coordinate safety communication. Preparation includes identifying hazards, arranging competent people, agreeing controls and briefing the crew. Conditions must still be reviewed on the day. The UK HSE explicitly requires responsibilities, risk management and ongoing review, including unpaid work; its guidance also says legal duties cannot simply be transferred to another person. Other jurisdictions and production activities have their own requirements. Vehicles, water, height, weapons, fire and public access require appropriate planning and expertise rather than a checkbox in a schedule. HSE film and television guidance.

Keep the room moving. Decide who calls changes, who communicates them to departments and who can stop work. Remove avoidable choices before the day, but keep a mechanism for new information. Quiet, explicit communication is more useful than asking every department to infer urgency from the director's mood.

Write a conditional adjustment menu in advance. A possible sequence is to remove redundant protective coverage, reduce unnecessary repeats on material already captured, coordinate compatible preparation without double-booking people, simplify a costly setup, and discuss a revised finish only if availability, agreements and safe working conditions allow it. This is a creative negotiation, not an automatic instruction. Do not sacrifice essential story information, sound, safety controls, agreed breaks or somebody's other obligation to make a chart turn green.

The tool deliberately distinguishes Essential, Protective and Optional work. A filter identifies candidate savings, but does not delete them. Mark a setup Dropped only after a human decision, with the reason retained in its notes. Already completed work remains in the record; removing it would erase the history needed to understand the day.

The documents that make an indie shoot legible

There is no universal eight-document threshold that authorizes a shoot. The following is a practical baseline to adapt to the project, location, employment arrangements and distribution needs. More than one item can live in a production binder; each still needs an owner and a current version.

Document Useful minimum content Check before release
Locked scene-numbered script Revision label, stable scene IDs, current pages and change notes Removed scenes are reflected downstream; added scenes can use a suffix rather than silently renumbering everything
Scene breakdown Cast, background, props, wardrobe, effects, vehicles, special equipment and restrictions per scene A second person reviews the physical requirements, not only the story
Shooting schedule Location/time grouping, availability, moves, breaks, estimated work and contingency Current script revision and real access windows match the schedule
Contact and availability list Names, roles, reachable numbers, calls and relevant availability Confirm the current details privately; avoid broadly publishing personal contacts
Location file Agreement, applicable permit/insurance evidence, access, parking, recce, contact and emergency logistics Verify the entrance, access period and conditions with the responsible contact
Performer and other necessary agreements Relevant permissions and agreed terms for the people and material involved Use documents appropriate to the jurisdiction and intended use; record who checks them
Call sheet and change record Date/revision, individual calls, address/access, work, contacts, logistics and distribution Send with enough time for confirmation; track delivery separately from acknowledgment
Shot list and spatial plan Story purpose, setup order, camera/blocking information and contingencies Departments understand the feasible setup and the alternatives

Add a Day Out of Days when cast or other element availability needs a cross-day view. Its value depends on conflicts, not a magic minimum actor count. Build a real budget even when self-funding: cash costs, unpaid obligations, insurance, meals, transport, post and contingency still exist. Funding partners may require a particular template and accounting detail.

A call-sheet deadline such as 8pm the previous evening is an agreement you can adopt, not a universal promise that every shoot can meet. Stagger calls only when preparation and dependencies allow it. A recipient opening an email is different from confirming their call. Keep an escalation route for missing acknowledgment and a clearly communicated procedure for revised sheets.

In the register, use the current script revision as the common reference. Every row records its owner, checked revision, state, due date, link and full notes. A checked revision mismatch is a reminder to review, not proof that the document is incorrect. A status such as Ready is an entered planning note, not independently verified compliance. After a script change, review all dependent documents; do not just edit the filename.

Be your own producer without approving every idea

Count locations, access windows, company moves, cast combinations and technical requirements alongside pages. A short script with many locations can require more coordination than a longer one in a controlled space. Page count still matters for dialogue, performance and camera time; no single count describes the whole production.

Set explicit constraints before committing to the script. For example: two shoot days, three accessible spaces, four speaking roles and no scene requiring a moving vehicle. These are fictional project choices, not limits every filmmaker should adopt. When an idea exceeds them, record the extra obligation and decide whether to revise the scene or revise the resources.

Invite somebody with less attachment to the story to read the breakdown. Ask: Which requirement is still a guess? What depends on another person's answer? What would prevent the day from starting? A working car, a child performer or an exterior after dark should trigger a specific planning conversation rather than an optimistic duration estimate.

Keep a change record with the reason, decision owner and affected artifacts. If scene 14 is cut, check cast days, location access, costume continuity, equipment, shot list, schedule and call sheet. A spreadsheet is a perfectly reasonable starting point when the ownership and review process work. A more elaborate system is justified when linked updates, recipient tracking, shared permissions or complex reports solve a real coordination problem.

A worked five-day block, and a checkpoint you can actually rehearse

Consider a fictional micro-budget feature block with seven crew, four locations and three principal actors. The locked script has 44 scenes. The director-producer records the script revision as R3, groups the work by access and cast, and makes a five-day availability table. This is an illustration of planning mechanics, not a report of a production we tested.

Day Date Location / work Cast availability Update to make
1 9 November 2026 Archive room, scenes 3–11 Ada and Ben Check the narrow entrance and equipment load-in
2 10 November 2026 Kitchen, scenes 12–20 Ada, Ben and Cora R3 removes scenes 17 and 19: rebuild the day, props and cast notes
3 11 November 2026 Courtyard, scenes 21–29 Ada and Cora Access and usable light constrain the finish; nominate an available clock owner
4 12 November 2026 Workshop, scenes 30–37 Ben and Cora Review remaining essential story information before adding coverage
5 13 November 2026 Archive pickups, scenes 38–44 plus agreed returns Ada and Ben Preserve a conditional pickup window rather than promising it will cover every delay

The 44 scene identifiers describe the earlier scope; once two scenes are removed, the active scene count is 42. Preserve their cut status in the change record instead of pretending they are still active. If the R2 schedule still contains those setups, it should be reviewed before it is distributed. Do not call a document current merely because it was exported recently.

Rehearse the failure as well. Suppose day two loses 40 minutes preparing a setup for the now-cut scene 17 because departments received R2. A coordinator's pre-distribution review could have caught the mismatch. Allow 20 minutes in this fictional workflow to check the script change against the board, props, actor calls and sheet; actual review time depends on the change. The comparison is not proof that every revision takes twenty minutes or causes a forty-minute delay.

At a later courtyard checkpoint, suppose usable light is limited to 120 minutes and three remaining setups are estimated at 80, 60 and 25 minutes. Their total is 165 minutes, exceeding that window by 45. Identify the indispensable story material and discuss the alternatives before the light disappears. Simply saying there are three setups obscures the unequal work. A nominated available producer can announce remaining time every 30 minutes, with the floor lead updating the order; do not assign that interruption to a recordist who is actively recording. If one optional item moves to a pickup day, confirm access, cast and crew commitments instead of treating the new date as free capacity.

For day three, suppose the crew has agreed a working period of 08:00–17:00. The example below allocates 400 minutes of work, including setup, a move, a meal and wrap. That leaves 140 minutes of unallocated time inside a 540-minute window. Slack is a planning allowance, not permission to skip breaks or treat an end time as flexible.

Work item Planned minutes Priority Reason / contingency
Briefing and load-in 35 Essential Location access, departments and changes discussed
Courtyard master, scene 23 80 Essential Establish the departure and spatial relationship
Close dialogue, scene 23 60 Essential Preserve the turning point in the conversation
Protective reverse 35 Protective Candidate to simplify if existing coverage works
Meal 45 Essential Agreed break; it is not a coverage saving
Move and reset 30 Essential Carrying equipment and resetting are real time
Gate insert 25 Optional Alternative: use the readable action in the master
Workshop pickup 60 Essential Confirm access and cast before retaining this work
Wrap and location check 30 Essential Return the space and equipment as agreed

This is the workbench's populated day. At 12:00, mark the first three items Done and enter 240 elapsed minutes. Their planned duration totals 175 minutes, so the recorded checkpoint is 65 minutes behind that planned cumulative point. Remaining planned work is 225 minutes; projected completion is 15:45, still 75 minutes before the entered finish. These two statements are compatible: a day can be behind its sequence yet still have slack before the hard end.

If the courtyard master takes longer, or the workshop access shifts, edit the actual assumptions. The tool does not infer duration from the screenplay. If the gate insert is explicitly dropped, remaining duration falls by 25 minutes and the reason stays in the ledger. If you add forty minutes to an essential setup, the projected finish moves forty minutes later. That immediate arithmetic makes the conversation concrete without pretending to make the creative decision.

The starter includes eight document-register rows. One has an earlier checked revision and one lacks an owner, so the demo shows what needs a conversation. Update the revision and owner to see those reminders clear. Export its full JSON to carry the exact demo into another browser, or use the JSON restore control after editing. CSV and Markdown include every setup and register record, including dropped items and full notes; neither is a vendor-native schedule file.

The original scope can also be budgeted as an illustrative 70 hours of preparation for a five-day block: 12 script/breakdown, 16 locations/casting, 10 crewing, 10 schedule/availability, 12 shots/spatial plans and 10 paperwork/distribution. Those entries total 70; they are a proposed allocation to change, not a measured standard or a guarantee that preparation will fit that time.

A recce records operating conditions, not just attractive photographs

Visit at a relevant time and observe the conditions your shoot will encounter. If a second visit is impossible, ask precise questions and record which answers remain unverified. A photograph of an empty room does not establish access, sound, power or permission.

Power: record accessible sockets, proposed loads and who can verify the electrical arrangement. Do not infer circuit capacity from the number of sockets or improvise distribution from a webpage.

Sound: listen and record representative ambient conditions: traffic, ventilation, neighbouring work, aircraft and intermittent equipment. A quiet weekend visit does not establish weekday sound. Include the time and the sound recordist's questions.

Sun and lighting: note window direction, shooting hours, natural light changes and practical fixtures. A compass, location photograph or sun-path app can support a discussion; weather and the actual location still matter.

Entrance and parking: record the actual loading door, stairs, lift dimensions, van access and restrictions. Separate a map pin from the entrance the crew must use.

Welfare: establish usable toilets, water, meals, seating, shelter and any relevant accessibility requirements. These are production needs, not optional rewards for finishing quickly.

Other occupants: identify neighbours, tenants, staff and the person authorized to agree the arrangement. Confirm what happens if their needs or opening hours change.

Put photographs and observations in the location file with dates and owner notes. Mark entrance and light direction clearly, and write what the photograph cannot prove. Record agreement, insurance/permit questions and emergency logistics separately. Applicable permissions, releases and insurance depend on the jurisdiction, activity, owner and intended use; obtain the appropriate advice rather than treating a sample binder as a legal clearance. The UK HSE's production guidance is a useful jurisdiction-specific starting point for managing risks and review. HSE.

Choose tools by the production job they really perform

Capabilities and public plan information were checked against the linked official pages on 6 October 2026. These are documentation-based decisions, not authenticated product trials, delivery benchmarks or brand reliability ratings. A product appearing earlier below is not ranked higher.

Tool Specific useful mechanism Decision / limit to check
Storyflow References, writing and visual planning share a canvas; AI can use selected board/document context Useful for treatment and look development. The retrieved pages do not establish a linked production stripboard, Day Out of Days, delivered call sheets or a live floor clock
StudioBinder Scene breakdown, stripboard, reports and call sheets; recipient states distinguish delivery, opening and confirmation Trial a representative production chain. Its current free tier is limited and sends sample call sheets only to yourself
Celtx Script-centered production records, breakdown, schedule, budget, cast/crew and call-sheet refresh Useful when writing and production planning need a shared project. Production tools are paid inclusions/add-ons; free writing access is different
Shot Lister Shot-by-shot/minute-by-minute schedules and Live Mode; optional Pro crew sync and script import Useful for the day and setup-level changes. It is not merely a clock, and Pro features have separate subscription terms
Yamdu Imported script/tagging, production schedules, call sheets and recipient confirmation Shared production structure may help complex responsibility and change management; small crew size alone does not rule it in or out
Movie Magic Scheduling 10 Breakdown sheets, boards, sub-boards, element conflicts, calendars, DOOD and report export Useful when an experienced AD, financier or multi-unit/episode workflow needs its actual format. Budgeting remains a separate integrated product
Previs Pro Spatial camera/blocking work, script import, animatics and documented exports Useful for feasibility and communication; a digital scene does not verify real clearance, access or safety. Current authoring spans Mac, iPad and iPhone
Spreadsheet / shared binder Explicit scene table, availability grid, revision register and PDF distribution Low financial cost, but change review, permissions, acknowledgments and version ownership remain manual

Storyflow: the treatment and look, with a deliberate production handoff

Use a canvas when the work is comparing references and developing a treatment, spatial relationships or shot intentions. Keep the selected look and its reason alongside the material. The practical handoff is a current treatment, stable scene/shot IDs, and the decisions departments need—not an assumption that a creative board becomes a delivered call sheet. The current pricing page distinguishes paid standalone early access from free invited collaboration and an upcoming standalone Free plan. Annual-equivalent Plus is $7.99, Pro $14 and Max $39 per month on the retrieved page; verify actual availability and billing before buying. Storyflow pricing, creative workspace.

StudioBinder: linked production records, with meaningful free limits

Official tutorials connect tagging, script-version updates, stripboards and reports including Day Out of Days. The current plan help also includes screenwriting, so calling StudioBinder a product with no screenwriting is outdated. Free access permits one project but only ten tagged elements, ten shots, ten scheduled scenes or 50% of a screenplay import, and sample call sheets sent to yourself. That can test a workflow; it does not establish a complete free crewed-shoot system. Use a representative script and actual required recipient count to check a paid plan. Breakdown and scheduling tutorials, free-plan limits.

Recipient analytics distinguishes bounced/dropped messages, opened emails and confirmed calls. Opening alone is insufficient confirmation; a status page does not independently prove future delivery reliability. Recipients can view/confirm without creating an account according to the official call-sheet guide. Check missing acknowledgments, maintain a direct-contact route and bring an appropriate offline copy for the day. The retrieved pricing URL redirected to an application shell without usable prices, so no exact paid subscription figure is asserted here. Status definitions, recipient workflow.

Celtx: keep script, availability and production context together

Celtx's production offering covers budgets, call sheets and reports; its Cast & Crew library connects availability and contacts with breakdown, schedule and budget. In its documented call-sheet workflow, Refresh pulls current script, breakdown, catalog, calendar and cast/crew data. That is a useful specific handoff mechanism, but it still needs a coordinator to check the sheet after edits. Distribution sends a PDF by email without a recipient login. The documented status view preserves the version actually distributed even after the working sheet is refreshed; Google Sheets export is available for manual customization. These mechanisms make version review concrete rather than assuming every recipient sees a later edit. The retrieved documentation does not establish the same recipient analytics as StudioBinder; treat that as a comparison question, not proof that Celtx can never track anything. Production tools, Cast & Crew, Call Sheets.

The current pricing matrix separates Free, Writer, Writer Pro and Team, with production tools as paid inclusions or optional add-ons. It describes a seven-day paid-feature trial, a one-project Free tier, and annual-only Student/Education arrangements. Student access requires eligibility and lists a discount for Writer Pro plus production tools; do not assume every person or a free account receives them. Dollar prices were not present in the retrieved matrix, so confirm the package and seat count in the actual quote or checkout. Celtx plans.

Shot Lister: setup-level scheduling and a live day

Its official site describes a minute-by-minute shooting schedule and Live Mode, allowing reorganization during shooting. Pro adds script importing, storyboards, Scriptation sync, unlimited projects beyond the base limit and Crew Sync for up to ten crew. Therefore “no scheduling or collaboration” is not a current description. Use it alongside your actual breakdown, agreements and distribution process rather than treating it as all production administration. Shot Lister.

The retrieved site advertises a free download and optional Pro at $15.99 monthly or $99.99 yearly. App-store region, current base limits and required features should be checked before purchase. Two months at the listed monthly price are $31.98; six are $95.94 and seven are $111.93. Compare the actual period of use against the annual commitment, without assuming that subscription savings outweigh staffing needs.

Yamdu: shared structure when coordination earns it

Current official material describes imports from Final Draft, Fountain, Celtx and PDF, AI-assisted element suggestions, stripboard organization and generated call sheets. Distribution can track confirmations and reminders. External contacts can receive material without becoming normal system users. AI tagging still needs scene-by-scene human review; do not interpret a suggested element as a verified production requirement. Yamdu call sheets, external contacts, creating and distributing sheets.

If departments, units or changing recipient groups need shared context, the structure can justify its setup. If your working problem is a simple day with stable records, learning another system may be unnecessary. No documented 25-person threshold establishes the right choice. The retrieved public pricing page exposed an iframe rather than a usable price table; obtain actual project/user/module terms instead of assuming it always costs more than a particular competitor. Yamdu pricing.

Movie Magic Scheduling 10: formats, conflicts and experienced handoff

The current version manages breakdown sheets and element categories rather than being limited to imported breakdowns. It supports multiple episodes/units via sub-boards, conflicts, calendars and an on-screen DOOD. Official support documents native Final Draft .fdx and tagged .sex imports, opening legacy MMS6 .msd files and saving the current .mmsx format. Reports include PDF/Excel, and scheduling elements can transfer to the separate Movie Magic Budgeting product. Check the receiving AD's version and the actual export they need before committing. Current features, support and file formats.

The official annual store listing showed a limited introductory $199.88/year alongside $279.88/year, with a 12-month commitment. These are retrieved public terms, not a permanent discount. Current Windows/macOS support and academic eligibility are documented separately. Familiarity, report requirements and conflict management can justify it for a short; “feature films only” is too absolute. It does not by itself replace a call-sheet distribution system or an AD. Annual subscription.

Previs Pro: test spatial ideas, then check the actual location

Camera positions, lenses, actors and sets can make a feasibility conversation concrete. Use a measured space and real proposed equipment as the reference; a proxy scene cannot establish that a camera, crew or rig physically clears the location. The current official pricing includes Mac, iPad and iPhone, script import, animatics, 2D/3D/MP4/NLE exports and AI features with separate use-based charges. A statement that it is iPad-only is outdated. Previs Pro pricing and features, platform/subscription guidance.

The retrieved plans list Free with watermarked exports and one animatic per project; paid monthly is $39.99, annual $119.99 ($9.99 monthly equivalent), and lifetime $359.99. AI use can add costs. Three monthly payments are $119.97—two cents less than the listed annual price—while four total $159.96. Choose for duration and required capabilities, not a headline monthly equivalent. The lifetime figure equals three listed annual payments before future price or product changes; that arithmetic does not guarantee lifetime value.

Put money against the constraint, then put preparation on a calendar

Before a software subscription or equipment upgrade, identify the thing that could stop the shoot: competent floor coordination, appropriate insurance/permissions, agreed meals and welfare, reliable sound, available cast or location access. An AD can free the director's attention; sound can preserve intelligible performances; food and an agreed finish support the crew. Their importance does not establish a universal purchase ranking or that three AD days always cost less than a lens rental.

Make an explicit budget with local quotes and agreed rates. Insurance costs and requirements vary; equipment and public-liability coverage are different questions. Crew participation, payment and working conditions must follow the applicable arrangements and laws. Avoid budgeting on a hope that everyone will keep extending an expenses-only commitment. Software should earn its place by solving the identified coordination problem.

For a fictional 15-page short filming on 5–6 December 2026, the following nine-week preparation outline gives concrete handoffs. The ranges deliberately overlap because availability and approvals depend on other people. They are a plan to adapt, not universal lead times.

Window Dates Output and dependency
Nine to seven weeks out 3–23 October Lock the working script, number scenes and draft the physical breakdown; review scope
Eight to five weeks out 10 October–6 November Casting and locations in parallel; record access, recce and permission/insurance questions
Six to four weeks out 24 October–13 November Approach DP, required camera/lighting support, sound and other actual roles with precise commitments
Five to three weeks out 31 October–20 November Build schedule and availability/DOOD from confirmed constraints; review after changes
Four to two weeks out 7–27 November Shot intentions, floor plans and any necessary boards/previs; validate location feasibility
Two weeks out 21–27 November Agreement, insurance, release and risk-management sweep; unresolved items get an owner
Final week 28 November–4 December Confirm calls, current sheets, contacts, transport and backups; deliberate controlled changes

“Freeze” means controlled revisions, not refusing material new information. If access or cast availability changes in the final week, update the relevant records, communicate the revision and reconfirm the affected people. A permit may take longer than this example allows; establish actual lead times with the responsible authority before selecting dates.

Recruit with an answerable ask, and deliver what you promised

Use specific dates, roles, hours, rate and scope. For example: “We are shooting a fictional archive-room short on 5–6 December, with proposed calls at 08:00 and planned wrap at 17:00. We need a sound recordist for both days. The offered rate is [actual amount], with [actual expenses] and meals. Here is the treatment and breakdown; can we discuss availability and the terms?” Replace brackets before sending. The real ask must disclose payment and cancellation terms rather than hide them until the fourth conversation.

Send a short treatment with reference images and a clear creative purpose. Do not imply that enthusiasm or reel material replaces required pay or a fair agreement. Give a precise commitment people can accept, decline or negotiate. Record what “two days” includes: prep, travel, equipment, overtime, pickup dates and cancellation are separate questions.

Use a deal memo appropriate to the arrangement, including dates, role, hours, rate/expenses, equipment, cancellation, credit and promised deliverables. Friends benefit from the same clarity. Agree how changes are approved and avoid silently converting a two-day favour into a third shooting day.

Plan crew delivery as real post-production work: who supplies an approved graded copy or permitted reel extract, what usage is allowed, and by what agreed date. A fictional arrangement might promise a private viewing link by 15 January and permitted extracts after release. Record those obligations rather than assuming the editor will remember months later. Finish according to the agreement, feed people properly and communicate delays honestly.

When judging brands, separate documentation from trust. A long company history, marketing testimonial or visible confirmation feature is not a measured uptime or delivery guarantee. Check a representative script, collaborator access, real report, cancellation terms and a usable export. The underrated low-cost improvement may be a reviewed breakdown and current PDF, a person available to watch the clock, or spatial previs for one genuinely uncertain setup. Choose the missing capability rather than a universal winner.

Questions about running an indie shoot

What is the best pre-production tool for an indie filmmaker?

Choose the missing job. StudioBinder and Celtx offer linked production records; Shot Lister is useful for setup-level scheduling and live progress; a spreadsheet can work when version review and distribution are manageable. Test a representative chain before buying. StudioBinder's current Free tier is a limited trial, including self-only sample call sheets, rather than a promise to run an entire crewed shoot free.

Which responsibilities disappear when there is no dedicated crew role?

None of the work disappears. Producer decisions, floor coordination, location arrangements and document ownership still need explicit owners. A person may prepare several outputs, but their availability during filming must be realistic. Written preparation reduces conflicting decisions without replacing live judgment.

Do I need a first AD for a short film?

Consider scene complexity, coordination, experience, access and hazards rather than a universal crew or location threshold. Hire competent floor coordination when the director and crew cannot manage it while performing their other duties. The workbench is a planning aid and cannot establish that a shoot is adequately staffed.

How can we monitor the day without a dedicated AD?

Nominate an available person, agree checkpoints and compare elapsed time with the planned duration of completed work. Recalculate remaining tasks, breaks, moves and wrap. Use a pre-agreed adjustment discussion; do not automatically remove safety controls, essential story information or agreed breaks to recover time.

Which documents should exist before filming?

Begin with a current scene-numbered script, reviewed breakdown, schedule, reachable contacts, location file, appropriate agreements, call sheet/change record and shot/spatial plan. Add availability reports, budget detail and specialized documentation when the production requires them. Every record needs ownership and a visible revision.

What is Shot Lister for, and does it schedule shoots?

Shot Lister provides shot-by-shot, minute-by-minute schedules and Live Mode for tracking and changing the day. Optional Pro adds features including script import and crew sync for up to ten crew. It complements the rest of production administration; calling it a tool with no scheduling or collaboration is outdated.

Are Yamdu or Movie Magic Scheduling useful on a short?

They can be when shared structure, conflicts, reports, an experienced AD's preferred files or financier handoff justify them. They may add unnecessary setup for a simple project. Match the required workflow and current terms rather than excluding them solely by format, budget or an arbitrary crew threshold.

When does Previs Pro help?

Use it to discuss uncertain spatial staging, camera positions and a location that is difficult to revisit. Current authoring is available on Mac, iPad and iPhone, with free and paid limits. Digital previs supports feasibility review but does not prove actual equipment clearance, permission or safe rigging.

Where should the first production money go?

Fund the constraint and obligations: appropriate staffing, permissions/insurance, sound, meals, transport and agreed terms may be more urgent than software or upgraded equipment. Obtain local quotes and assess the specific plan. There is no universal price comparison between an AD and a lens rental.

How long does indie pre-production take?

It depends on scope, access, cast, approvals and available time. The dated nine-week outline is an adaptable fictional plan for a 15-page short, not a benchmark. Work that depends on other people should start early enough for actual lead times and revisions.

Why can a shoot run late despite having a schedule?

The schedule may omit setup, moves, breaks or wrap; assume unconfirmed availability; or reflect an obsolete script. Durations can also change legitimately during filming. Review physical constraints before the day and compare actual progress against current work instead of treating the original export as immutable.

Is insurance required for a short film?

Requirements depend on jurisdiction, activities, location agreements, equipment providers and other contracts. Confirm the actual coverage and evidence needed with appropriate parties before filming. A sample schedule or register cannot provide legal clearance or verify that a policy covers the intended work.

Should we shoot in script order?

Usually build the order around access, lighting, cast and setup constraints so that moves and resets are visible. A performance or continuity reason may justify script order for some work. Compare the concrete cost and creative need; a universal rule misses useful exceptions.

What is the biggest pre-production mistake?

One common failure is committing to a tool or schedule before understanding the physical work, then failing to update dependent records after changes. A reviewed breakdown, responsibility register and revision process address that failure. More software alone does not.

Can we run the shoot from spreadsheets and PDFs?

Yes, when the actual record volume, change review, permissions and distribution are manageable. A small crew can still have difficult access or many revisions. Add linked software when it removes a real manual burden, and maintain current offline artifacts rather than relying on a particular crew-count cutoff.

How should we approach crew when the budget is limited?

State the role, dates, hours, actual rate, expenses and cancellation terms at the outset, with a treatment and realistic scope. Negotiate a clear lawful arrangement, keep agreed conditions and record any promised credit or permitted material. Do not substitute vague future exposure for agreed obligations.

What makes a recce different from a casual visit?

A recce records relevant operating conditions: power questions, ambient sound, light direction, actual entry/parking, welfare and other occupants. Visit or investigate at the relevant shooting time, retain dated observations and flag unverified answers. Attractive photographs alone do not establish readiness.

How can the director also act as producer?

Set resources and scope explicitly, compare changes against them, and ask an independent person to review the breakdown for unconfirmed requirements. Record decisions and affected documents before emotional attachment makes revision harder. Arrange realistic live coverage for responsibilities that collide with directing.

Should production constraints influence the script?

Yes, when they reflect actual resources and obligations. A chosen limit on days, locations or roles can focus the work, but it does not guarantee a better script. If a story requires more resources, decide deliberately whether to secure them or rewrite rather than quietly assume they will appear.

How should I evaluate trustworthy software and fair pricing?

Check current documentation, required limits, recipient access, support, a representative export and full billing/cancellation terms. A brand's age or testimonial is not a measured reliability comparison. Separate a free trial, invited access, annual equivalent and extra seats or AI charges before comparing cost.

Which practical improvements are easy to overlook?

A second reader of the breakdown, a current availability report, explicit entrance notes, an available clock owner and a reviewed contingency menu can all help. Previs may be valuable for one uncertain space; a spreadsheet may be adequate for stable records. Their usefulness comes from the specific missing job rather than a universal brand ranking.

Keep your shoot, crew and production decisions connected with Super