Turn a Documentary Deck Into a Grant Proposal Without Copying It Into Every Answer
Turn a Documentary Deck Into a Grant Proposal Without Copying It Into Every Answer
The deck works. Fourteen slides, the logline lands in the room, the images hold, the room goes quiet at the right moment. Then the application opens, and it is nine fields — one of them four hundred characters, one of them asking for a whole-project budget, one of them a button for a visual sample — and the deck suddenly has nothing to say.
This is the ordinary collision between two documents that look similar and do different jobs. A pitch deck is a persuasive sequence designed to be spoken over. A grant proposal is a set of answers to one recipient's questions, under that recipient's limits, with the evidence that recipient requires. You can carry truthful material from one to the other. You cannot carry the deck itself.
Fix the application and the cycle you are answering
Before you decide what you have, decide what you are answering. Name the recipient out loud. Save the instructions you are working from, with the date you read them, because grants change their questions between cycles and a document you downloaded last year is not authority for this year.
The worked example in this article is the Sundance Institute Documentary Fund. Its published FAQ, as read at the time of writing, sorts three things that a deck tends to blur together: a written explanation of the project, a whole-project budget, and visual material that depends on the production phase the film is in. The same page routes applicants by stage — the section is literally titled "Production Phases: When to Apply." That single fact already tells you something a deck cannot: the question set you answer depends on where the film currently stands, not on how good the trailer looks.
Read the current instructions for four things before writing a word:
- The exact wording of each question. "Describe your approach" and "describe your visual style" are not the same prompt.
- Limits. Character counts, word counts, page counts, and whether the limit is enforced by the form or just requested.
- What is permitted as an attachment. Decks are sometimes allowed as supporting material and sometimes not. Find out. Do not assume.
- Stage and sample rules. Whether a sample is required at all, and what it has to be from.
If the checklist and the portal disagree — one says the sample is optional, the other makes it mandatory — write down the discrepancy and ask. Choose the harder requirement in the meantime. Silently choosing the friendlier reading is how applications get disqualified for a reason that has nothing to do with the film.
One more caution: this fund's published route is one recipient's route, not a general law of documentary applications. Different funds ask different things, and a habit you build from one form will mislead you on the next.
A deck, a treatment, and a proposal do different jobs
It helps to keep three documents separate in your head, even though they share sentences.
A deck is a sequence of slides for a live room. The slides carry images and fragments; you carry the argument. Its unit of persuasion is the whole presentation.
A treatment is continuous prose describing the film: who and what is in it, how it will look and unfold, what it is about. Its unit is the read.
A proposal is someone else's question list, answered. Its unit is the individual field. A proposal can be built from deck material and treatment prose, but its success is judged field by field.
Here is the test that catches most of the problem. Read one of your answers with the question covered. If it would sit comfortably under three or four other prompts in the same form, it is not an answer. It is the synopsis again, wearing a different heading.
Map useful material, then mark the actual gaps
The mapping is mechanical, and that is what makes it honest. Three columns: the question, the material you already have that truthfully speaks to it, and what the question still needs that the material does not establish.
To make this concrete, here is a fictional project. Nothing in it has been submitted, evaluated, or filmed beyond what is stated, and no applicant's portal or budget has been inspected.
The project. The Tuesday Room is a documentary about the Hollis Street Band, a volunteer brass ensemble of 22 players that has rehearsed in the basement of a union hall every Tuesday for forty-one years. The building has been sold. The band's lease ends in the spring. Whether the band finds an affordable room, relocates, or stops playing is unknown — the season is still running, and the search is still going.
What the team has. A fourteen-slide pitch deck. One eight-minute visual sample, shot at a single Tuesday rehearsal, showing the band working through a march, the room, the sound, and how the players talk to each other between takes. A plan for future filming: rehearsals through the coming season, the room search and its negotiations, and the band's standing spring concert, wherever it ends up happening.
What the team does not have. A written account of the filmmaker's own practice. A confirmed work plan with dates. A whole-project budget.
| The question asks for | The material supplies | The gap |
|---|---|---|
| What the film is about | Deck logline and a synopsis paragraph; the band, the hall, the deadline | Roughly nothing — this one is nearly ready |
| Subject and context | Deck's "why now" slide; the sale, the lease, the neighborhood | Confirmation of specific dates and figures from the band's own records |
| Artistic approach | Sample shows how the room sounds and how people behave in it | How the film will be shot across a season, and what changes when the room does |
| Filmmaker practice and access | Deck's biography slide in outline | A full account of prior work, working method, and the actual relationship to the band — the applicant must supply this from their own record |
| Work plan and stage | Deck timeline graphic, undated | Confirmed schedule tied to the phase the film is genuinely in |
| Budget and financing | Deck's one-line "we need X to complete" | A whole-project budget, plus a clear separation of what is requested, committed, and merely anticipated |
| Visual sample and its explanation | One eight-minute rehearsal sample | Whether this stage permits a sample from material already shot, what the sample is meant to demonstrate, and the technical requirements for the file itself |
Look at the last two rows. They are where decks fail, because they are the fields a deck was never built to answer.
Rewrite without turning inquiry into an outcome
The most common failure in this translation is not laziness. It is that a pitch deck trained you to state the film as a finished thing, because that is what gets a room interested.
Here is a fictional synopsis, as it might sit on slide three:
The Tuesday Room follows the Hollis Street Band, a volunteer brass band that has rehearsed in the basement of the old union hall every Tuesday for forty-one years, as the new owner prepares to convert the building into apartments. With the lease ending in the spring, the band's twenty-two members must decide whether to find a new home, fold, or fight.
Paste that into the synopsis field: fine. Paste it into the approach field: it says nothing about how the film will be made. Paste it into the filmmaker-practice field: it says nothing about the filmmaker. Paste it into the work plan: it says nothing about what happens next week. Four fields, one paragraph, zero answers.
The rewrite is not harder prose. It is a different job for each field, and the discipline of keeping tenses honest.
The synopsis can stay roughly as above, with one correction. "Must decide whether to find a new home, fold, or fight" describes a decision that has not been made. That is fine in a synopsis if the framing is right — the film is about a decision in progress. It is not fine if the next sentence implies the band fights and wins.
The approach describes intention. The film will be shot primarily in rehearsal, in long takes, with the room held as a constant frame so that a change of room reads as a change in the film's body. A second camera will cover the band's spring concert, wherever it is held. Sound is recorded so the arrangements carry the film rather than comment on it. Every sentence is a plan. None of it claims a scene exists.
The filmmaker statement is about the maker, not the plot. It is also the field where invention is most tempting and most destructive, because the material is your own life and nobody in the form will stop you. It belongs to you to write from your actual record — the films you have made, how you work, why this band, and what access you genuinely have. If you have not worked with this kind of subject before, say so and explain how you are preparing. That is an answer. A fabricated prior project is not.
The work plan is where the fictional project's gaps live. The deck has a timeline graphic with no dates. The real plan needs the phase the film is in, what has already been shot (one rehearsal, one Tuesday), what remains, and what depends on events the team does not control — the room search, the negotiations.
One habit worth building: scan every answer for sentences that assert an outcome the film has not reached. When the band finds a new home is a promise. If the band finds a new home is the truth. The band searches for a new home is also the truth, and usually the better sentence.
Check the work prose cannot replace
Some of what an application requires is not writing at all, and no amount of good prose substitutes for it. The fund's published material treats the written explanation, the budget, and the visual sample as separate obligations; a complete-looking form does not repair an absent sample or an unsupported budget line.
The sample. The FAQ's guidance on visual material is stage-specific, which means the sample rule changes depending on where your film is. Check three things: whether a sample is required or optional, whether the stage permits material from another project or requires material from this one, and what the technical requirements are for the file — length, format, captions, hosting. The eight-minute sample in this scenario is described, not an actual file. In your own case, the file has to be viewed and technically checked before it counts as a sample rather than an intention.
Watch for a quieter trap: a required sample is not the same as an optional deck. If your deck is permitted as supporting material, it supplements; it never stands in for a required answer or a required file.
The budget. If the fund asks for a whole-project budget and your deck has one line reading "we need X to complete," you have a wish, not a budget basis. The numbers have to come from project records — crew rates, days, gear, post, contingency — and somebody has to be able to defend them. The fictional team in this example does not have that yet, and the honest column in the map says so.
Financing status. Never describe a proposed source as secured. Three categories, kept visibly distinct: money committed, money requested, money anticipated. Rounded optimism here is the kind of error a reviewer can check, and it corrodes everything else you wrote.
Process and disclosure questions. Some applications ask how the work will be made — who shoots, how footage is stored, whether synthetic media or AI tools are involved. If your form asks, answer from your records, not from memory, and do not assume a question exists or doesn't. Read the form.
The general shape of this section: prose can address gaps in explanation. It cannot address a missing file, an unconfirmed schedule, an unsourced budget, or a biography you do not have.
Review the submission as a set of connected answers
Read the finished draft as a reviewer would, which is to say, as a stranger reading nine fields in sequence without your deck in front of them.
Cut repetitive synopsis passages, but keep the context each prompt genuinely needs. A reviewer reading only the budget field should still understand what project it belongs to. Over-correction — stripping all context to avoid repetition — creates a set of answers that don't cohere.
Then check consistency across everything, written and attached: names, spellings, dates, running time, the phase the film is in, the amount requested, the number of people on the crew. Two answers that disagree about how far along the film is are worse than one vague answer, because they raise a question about the other eight.
Then check the mechanical layer: the actual limits, the actual file specifications, the actual naming conventions. These are the least interesting checks and the most common cause of a submission that never gets read.
The answer map you end with
End the process with a single annotated list, sorted by four verbs. This is what the writer has when the drafting session is over — not a completed application, not an eligibility verdict, and not a recommendation to submit.
- Reuse. Material that already answers the question. In the fictional example, the synopsis and most of the subject context.
- Rewrite. Material that exists but is doing the wrong job. The approach field, drawn out of what the sample implies rather than out of the plot. The work plan, with the dates that are actually settled written in and the rest left as visible gaps.
- Obtain. Material that does not exist and cannot be written into existence. The filmmaker's own practice account. The whole-project budget. The schedule dates the work plan still lacks — the phase the film is genuinely in, and the shoot days that depend on the room search. Confirmation of the sale date and the lease terms from the band's records.
- Resolve. Questions that only the recipient can answer. Whether this stage allows a sample from already-shot material. Whether the deck is permitted as an attachment. What to do if the checklist and the portal disagree.
For The Tuesday Room, the honest status after mapping is something like this: the synopsis and subject context can be drafted today; the approach can be drafted today, in intention, clearly marked; the work plan can be drafted only up to the dates that are settled, and the budget cannot be drafted at all until the numbers exist; the sample exists but needs to be checked against requirements nobody has read closely yet.
That is a useful place to stop. It tells you what you can write before lunch and what has to happen in the world first — a conversation with the band about dates, a budget built from real quotes, a decision about how the season gets shot if the room is lost. A deck can start all of that. It cannot finish any of it.
And one plain limitation, since it affects how you should use everything above: the fund observations here come from one published FAQ page as it read at the time of writing. The fictional project has not been run through a real form by a real applicant, no portal was opened, no budget was assessed, and no sample was viewed. Read your own instructions, from your own cycle, before you trust any mapping — including this one.
Frequently asked questions
Why can't a strong pitch deck simply be pasted into a grant application?
A deck is a persuasive sequence designed to be spoken over; a grant proposal is a set of answers to one recipient's questions under that recipient's limits and evidence requirements. The proposal is judged field by field, not as a whole presentation.
What should you confirm in the current application instructions before drafting?
Read the exact wording of each question, the character or page limits, what attachments are permitted, and the rules for stage and sample. Save the instructions with the date you read them, because grants change between cycles. If the checklist and portal disagree, choose the harder requirement and ask.
How can you tell whether an answer is actually answering its prompt?
Cover the question and read the answer. If it would sit comfortably under three or four other prompts in the same form, it is not an answer; it is the synopsis again wearing a different heading.
Which application gaps cannot be repaired by better prose?
A missing sample, a budget without project records, an unconfirmed schedule, and a filmmaker biography you do not have cannot be written into existence. Financing status must also separate money committed, requested, and anticipated, and a proposed source must never be described as secured.
What does the final answer map look like?
End with a list sorted by four verbs: Reuse, Rewrite, Obtain, and Resolve. It shows what already answers a question, what exists but is doing the wrong job, what must be built or confirmed in the world, and what only the recipient can answer. The fund observations are limited to one published FAQ page as read at the time, and the fictional project was not run through a real form.