Show What the Next Round of Film Funding Will Finish
Show What the Next Round of Film Funding Will Finish
This funding will help us move the edit forward. It's true of nearly every unfinished film, and a funder can't do much with it. The sentence describes motion. A budget needs a destination.
The usable version names one output — the thing that will exist when this money is spent — places it inside the whole-film budget you already have, and is honest about which resources you can count on. Most of the difficulty sits in that last part. A partial funding plan tends to present itself as a single financed number, when it's really several kinds of money with different rules attached.
Everything below assumes you have a current, priced cost basis for the film. Without one, the honest first task is to build it, and this article can't help you skip that step.
Start with the whole film, then isolate this request
One budget. The stage request is a route across it, not a separate document with its own arithmetic.
That means the whole-project figure stays visible in the request: the finish line you're aiming at, the cost basis you're using, and where this chunk of work sits between the stages already done and the stages still ahead. If you build a smaller, friendlier budget for the pitch and it disagrees with the one your producer is carrying, a reviewer has no way to tell whether you're sloppy or hiding something. Both readings cost you.
Two properties of that budget matter more than the rest.
Its date. Costs move. A basis priced before your last shoot block is a different document from one priced after it, and the differences — a rate you negotiated later, a location you lost, an archival quote that came in higher — are exactly the lines a reviewer will ask about. Say when the basis was prepared and what it assumes. If you're working from an older version, say that too, and say what has changed. "Current" is a claim you should be able to date.
Its finish line. "Finished film" is a decision, not a default. A festival premiere, a broadcast delivery, a distributor's list of required materials — each one implies a different amount and kind of remaining work. The finish line determines what's still outstanding after your stage, which is the thing your request is really being measured against.
It's worth knowing that some recipients ask for the whole-project picture and the current-stage material at the same time. The Sundance Documentary Fund's application guidance asks applicants for budget information and for visual samples — a bounded example of a funder wanting both the full cost basis and evidence of where the work actually stands. That's one fund's requirement, not a general rule, and it doesn't tell you how much your film needs or whether your requested amount would finish your stage. Check the cycle you're applying to; requirements change.
The useful habit is to name the stage before this one and the stage after it out loud. "Development and production are complete. This request covers editorial. Finishing is not funded here." That one sentence prevents most of the confusion that follows.
Separate available resources from money that might arrive
Four buckets, and they are not interchangeable.
Committed cash is signed or in the bank, with terms you've read. Conditional support exists only if something else happens — a match is raised, an approval clears, a date is met. Pending applications are submitted and undecided; when the decision lands matters as much as what it says. In-kind support is work, space, equipment, or services given rather than paid for.
Here's a hypothetical to work with. A two-person documentary team has finished principal photography. Interviews and verité footage sit on backed-up drives. They want to request editorial support. Their resources look like this:
- A small grant already committed, restricted to rights clearance and archival licensing.
- A loaned edit workstation, calibrated monitor, and storage from a post facility, secured for a set window, returnable when the window closes, not transferable and not convertible to cash.
- A consulting editor who has agreed to give notes on the cut if the stage gets funded. The fee is part of the stage cost.
- A regional arts grant, applied for, with a decision date that falls after the edit would need to begin.
- A finishing award they intend to apply for in a later cycle, which would pay for color, mix, and delivery materials. Not secured.
Two questions belong to every resource before it goes anywhere near the stage. What is it allowed to pay for? When is it actually available?
The restricted grant answers the first question sharply: it can pay licensors and nothing else. It is real money and it cannot pay an editor. If you assign it to rights clearance in one place and let it quietly cover editorial labor in another, you've funded the same dollars twice.
The facility loan answers both questions. It replaces a rental line — the room, the monitor, the storage — so your budget shouldn't ask a funder to buy them. But equipment isn't a wage. A loaned suite does not pay the person who sits in it, and a funder reading "we have secured a post facility" may reasonably assume the editing is covered unless you say otherwise.
The pending application is the most tempting one to smooth into the total, because a submitted application feels like progress. Keep it separate until the decision actually arrives. If the decision lands after your stage has to start, the money isn't available for this stage no matter how likely it is.
And the finishing award is a different stage. It belongs in the whole-project picture and in the paragraph about what comes next. It does not belong in the ledger for this request.
Define an output someone can actually use
Work backward from the endpoint. "A reviewable rough cut" is three words hiding a job.
Start with what the recipient will do with it. A reviewable rough cut at this stage means someone can open the file, watch it end to end without you in the room, and give you notes that attach to a specific version. That definition implies temp sound, no graphics or titles yet, a slate or label identifying the cut, and a way to send it. It also implies the export itself — rendering and delivering a playable file is work, and it's the last thing on the list, which is how it gets left out of budgets that stop at "assembly."
Then list what has to happen between here and there:
- Logging and transcription of the interviews, so the editor isn't hunting through raw footage.
- A paper edit or selects pass, deciding what the film is arguing.
- Assembly, building the first full-length structure.
- A review round with someone who isn't the editor — the consulting editor's notes, in this example — and the editor's time to act on them.
- The export and delivery of review copies.
Each of those lines needs a person and a duration. That's how a stage becomes costable: not "editing," but assistant-editor time for logging, editor time for assembly, a notes pass, editor time for revisions, and the export. If a line has no person attached, it hasn't been priced yet.
This is where the distinction between activity and completion does its work. Paying for a block of editor time is an activity. The stage is finished when the export exists. Those are different claims, and only one of them belongs in a request. Write the endpoint first, then buy the tasks that reach it.
Say plainly what the output is not. Not picture lock. Not mixed sound. Not color. Not delivery materials, E&O, or distribution readiness. A reviewer who sees a rough-cut stage described without those exclusions will assume you've included them, and asking later for more money to do what they thought they'd already funded is a bad conversation.
Reconcile the stage and disclose the next dependency
Now match every task to a resource, in writing, and leave the unfilled portion visible.
| What the stage requires | What it actually takes | Resource assigned | Status |
|---|---|---|---|
| Logging, transcription, paper edit | Assistant-editor time | None yet — part of the request | Unfilled |
| Assembly — the first full-length structure | Editor time for assembly | None yet — part of the request | Unfilled |
| Somewhere to cut | Workstation, monitor, storage | Loaned post suite | Secured in-kind; time-limited; not cash |
| Review round | Notes from the consulting editor, plus editor time to revise the cut once | Notes pass conditional on the stage being funded; editor time in the request | Conditional |
| Reviewable export | Editor and assistant time, render, delivery link | None yet — part of the request | Unfilled |
| Rights clearance and licensing | Cash to licensors | Restricted grant | Secured, restricted to this line |
| Color, mix, deliverables | Finishing facility, mixer, delivery | Finishing award, later cycle | Not secured; later stage |
One resource stays out of the table, because it isn't a requirement of the stage. The regional arts grant is applied for, and its decision lands after the edit would need to begin. It's a resource considered and excluded — it belongs in the whole-project picture, not in this request.
Read the unfilled rows together, because they're the request. The loan covers row three; it does not cover row two, even though row two happens inside row three's room. The restricted grant is cash sitting closest to the thing that can't use it. The pending application might arrive, and the timing makes it useless here. Three separate truths that a single "financed to date" number would flatten into one.
When the amount you can raise doesn't finish the stated output, you have two honest moves.
Shrink the stage to something coherent. If the money buys assembly but not the export, stop promising a rough cut and define a smaller endpoint that the money genuinely reaches — an internal assembly screening for the team and two invited readers, held in the loaned suite, with written notes collected afterward. It's a real output with a real purpose. It isn't a rough cut, and the request should say so.
Make the request conditional and name the trigger. "This amount completes assembly. The review round and export follow once the second installment is confirmed, and we would provide the assembly for review in the meantime." The dependency is disclosed, the reviewer knows what they're buying, and nobody is surprised in a report.
What you can't do is remove the completion work from the description while keeping the endpoint claim. Consider the failure version: the team asks for an amount that covers assembly editor time, and the narrative describes the stage as delivering "the completed rough cut." The money runs out at the end of assembly. The review round and the export have no funding. Either the rough cut never becomes reviewable, or the team does the work unpaid and late, and the report to the funder can't be reconciled against the budget that promised it. The request was honest about the arithmetic and dishonest about the destination, which is the harder problem to fix later.
Here is a before, drawn from the hypothetical team's first draft:
We have completed filming and are now in the edit. We are requesting support to complete post-production and prepare the film for festival submission. Editing is the largest remaining cost, and this funding will let us finish the edit and put the film in front of audiences.
It's not false, exactly. It's also three endpoints in one paragraph — post-production, festival submission, audiences — none of which this request pays for, and no statement of what will exist when the money is gone.
After:
This request funds the editorial stage that ends with a playable rough cut. It covers three things: assistant-editor time to log, transcribe, and build a paper edit from the interviews; editor time to assemble the cut and revise it once; and the export and review copies that let a reader watch the film end to end. A consulting editor has agreed to a notes pass once the stage is funded; that fee is included here.
The edit room is covered. [Facility] has loaned a workstation, calibrated monitor, and storage for the duration of the stage, so there is no equipment rental in this request. The loan carries no cash value to the film and cannot be applied to an editor's fee.
Rights clearance is funded separately by [grant], restricted to licensing costs. It cannot be moved to editorial labor.
What will exist at the end: a rough cut at its current working length, with temporary sound and no graphics, exported with a slate identifying the version, watchable without us in the room. What will not: picture lock, mixed sound, color, titles, or delivery materials. Those sit in the finishing stage, where we will apply to [finishing fund] in a later cycle. Nothing in this request depends on that award; if it doesn't come, the rough cut still exists.
The revision is longer than the first draft, and the added length is where the claim lives. The draft describes motion. The revision says where the money stops.
The stage statement at the end of the second version — the paragraph beginning "What will exist at the end" — is the sentence to test your own request against: this support completes this output, under these conditions, with these obligations remaining. If you can't fill all three blanks using the same line items that appear in your cost basis, the request isn't finished yet — and better to discover that now, while you can still change the scope, than after the money arrives and the work is standing exactly where the budget left it.
Frequently asked questions
What makes a stage funding request useful to a reviewer?
It names one output that will exist when the money is spent, places that request inside the whole-film budget already in use, and is honest about which resources can be counted on. A sentence like 'This funding will help us move the edit forward' describes motion, not a destination.
Why does the budget's date matter in a funding request?
Costs move, so a basis priced before the last shoot block is a different document from one priced after it. The differences, such as a later-negotiated rate, a lost location, or a higher archival quote, are exactly the lines a reviewer will ask about. State when the basis was prepared and what it assumes; if working from an older version, say what has changed. 'Current' should be a claim you can date.
How should committed cash, conditional support, pending applications, and in-kind support be treated?
They are not interchangeable. Committed cash is signed or in the bank, with terms read. Conditional support exists only if something else happens, such as a match being raised or an approval clearing. Pending applications are submitted and undecided, and when the decision lands matters as much as what it says. In-kind support is work, space, equipment, or services given rather than paid for. Each resource must be asked two questions: what is it allowed to pay for, and when is it actually available?
What are honest moves if the amount raised does not finish the stated output?
One move is to shrink the stage to something coherent that the money genuinely reaches, such as an internal assembly screening for the team and two invited readers in the loaned suite, with written notes collected afterward, and to say plainly that it is not a rough cut. The other is to make the request conditional and name the trigger, for example: this amount completes assembly; the review round and export follow once the second installment is confirmed. What you cannot do is remove the completion work from the description while keeping the endpoint claim.
What should the stage statement at the end of the request be able to say?
It should be able to say: this support completes this output, under these conditions, with these obligations remaining. If you cannot fill all three blanks using the same line items that appear in your cost basis, the request is not finished yet.