Prepare an Alternative-Format Film Application Without Losing the Required Answers

You can change how your answers arrive. You can't usually change what they have to be.

That's the whole job in one line, and most of the difficulty lives in the gap between those two halves. Moving a written application into audio or video solves an access problem and creates a delivery problem: someone still has to find your answer to question three, still has to see the budget, still has to be able to assess the work. If the format makes the answers harder to locate or easier to lose, you've traded one barrier for another.

The method that works is unglamorous. Confirm what the recipient will actually accept, in writing. Map every required answer to a specific place in your submission. Speak the answers in your own words, in short labeled units. Add navigation only to the extent it was agreed. Then audit the assembled package against the form — not the script against your memory.

One thing to settle before any of it: a request is not an approval. Those are two different states, and confusing them is the most common way this goes wrong.

Confirm the route before recording an entire application

Before you press record, you need four facts from the recipient.

• Which questions may change format. All of them, or only the narrative ones? A budget table rarely becomes a voice memo.
• What kinds of files are allowed, and how long they may run. Audio, video, both? A per-file length cap? Any total cap?
• How and where the files are supplied. Same portal as the written form, a shared drive, an email to a named person? A specific upload area?
• What support has been agreed. A transcript? A labeled index? Someone who can read answers back to you? Nothing at all?

Notice that none of those questions require you to explain your body, your diagnosis, or your history. Ask about the concrete barrier and the concrete alternative: "I can't complete the 200-word summary as typed text. Could I submit that answer as a short audio file with a transcript?" That sentence gives the coordinator something to answer. A detailed account of why doesn't, and it asks the applicant to hand over more personal information than the process needs.

Then sort what comes back into two piles. Documented means a published instruction or a written reply naming your situation. Pending means you asked and haven't heard, or you were told to ask someone else. A pending request gets you nowhere near a finished submission.

Watch for the most tempting wrong inference here, which is reading a permission into a general accessibility page. The Sundance Institute's accessibility page, noted in September 2026, does exactly what such pages are designed to do: it offers a contact route for accessibility questions. It does not show that any named program accepts an alternative application format. A contact route is the door to the conversation, not the answer to it. Use it to start asking.

What a published route can look like

Some funders do publish this material. The BFI's guidance for its National Lottery Expanded Screen Funding, read in September 2026, describes audio and video upload options for some questions, with the eligible fields and suggested recording lengths shown in the form itself. Documents stay separately required. It also states that production polish is not assessed.

That last sentence is worth keeping. But notice what the guidance is not. It's UK-specific, for one named program, as the page read on one September day. It doesn't tell you which fields accept an upload today, whether you're eligible, what the deadlines are, or what any other funder does. The live form is the version that counts, and your recipient's written reply is what governs your submission.

Build the question map from the actual form

Open the form you were sent. Not a screenshot from last year, not the summary a friend gave you. The current one.

Then build a map: one line per required item, showing what it asks and where your answer will live. This is the single most useful document you'll make, because it's the artifact you'll use to catch losses later.

Here's a fictional teaching example, invented end to end, so you can see the shape of it. Riverbend Short Works Fund (invented) told an applicant, Nadia, in writing that she could answer the three narrative questions as audio files — one file per question, each labeled with the question number, each under four minutes, transcripts supplied as a separate PDF. Everything else stayed as documents. Her map looked like this:

Three things the map is doing that a script isn't.

It separates the questions the recipient actually asked. A project summary is not an artistic-practice statement, which is not a team description. These get scored as different things. If you answer the practice question with the same paragraph you used for the summary, you've written one answer twice and left a question unanswered — and it will read as though you didn't have anything to say about your own practice.

It reveals which items still need written fields or attached documents. A signature can't be spoken. A budget template arrives as a spreadsheet. A URL field wants a URL. Tapping those in the map early saves a scramble at the end.

It marks unanswered subquestions instead of letting them hide. A broad spoken story feels complete while you're telling it. Against a list of required prompts, it usually isn't. Nadia's logline, Q1a, is a separate line for exactly this reason.

One legitimate sharing note: a single line about the team might properly appear in both the summary and the team answer. That's fine as long as both are consistent and the shared line doesn't stand in for either full answer.

Outline spoken units in the maker's own language

Do not read the form aloud. It was written to be read silently, and it sounds like a form when spoken.

Instead, for each question, write a short answer followed by the explanation or example that supports it. Lead with the answer. A listener can't skim ahead to find out what you're getting at — they find out when you say it.

You may reorder sentences inside an answer for listenability. Keep the recipient's questions in the recipient's order, with the recipient's labels, so the reviewer can read your submission next to the form and check items off. Reordering the questions themselves makes that harder for no gain.

Here's one unit from the fictional example. Q3, team and roles, from Q3-team.mp3, 0:00–0:30:

"Two of us are on this project. I'm directing and editing. Priya Raman is producing — she's handling the schedule, the location permissions and the budget. We've both worked on short documentary before, mostly at this length. That's the whole team for this stage. Our community partner, the Eastside Print Room, has confirmed the workshop space for the shoot in June, and their letter is in the pack."

Answer first, then detail. Nothing is dressed up. The time references, the roles and the names are specific enough that a reviewer writing notes can keep up.

Now watch the last sentence. "Their letter is in the pack." That's an essential document being dispatched to a later moment that doesn't exist. The audio asserts something the package doesn't contain — and it's the kind of failure that feels like diligence while you're recording and reads as an omission to whoever opens the folder. Never send required evidence to an unspecified future, and never let a spoken claim about your own submission go unchecked.

Two planning constraints, both easy to miss:

The word limit and the time limit can pull against each other. Suppose two subquestions in one file are each capped at 300 words — 600 words total — while the file itself is capped at four minutes. Speaking at a relaxed pace, call it 130 to 150 words a minute, 600 words runs from about four minutes to four and a half. Write to the word limit, then time the read, and honor whichever cap is tighter. In the fictional example, Nadia's 3:48 was under both, but only just.

Access is not an invitation to perform. You don't need music, a second camera, professional lighting, or four takes. The BFI's published guidance says production polish is not assessed, which is a useful thing for any applicant to hear. A quiet room, a phone, and a plain-spoken answer are sufficient. Treating the alternative format as a production brief turns an access route into extra labor for the person it was meant to help.

Add the navigation and support the route allows

Navigation is whatever the recipient agreed to and can actually use. Nothing more.

Labeled files are the baseline. Name them so a reviewer can match file to question without opening anything. If the route allows a transcript, a one-page index, or time references, add them as agreed — and check the format of what you send. A photographed page is not a usable transcript; it can't be searched, copied, or read aloud by software. Real, selectable text is worth more than a scan, and a plain text or text-based PDF file is usually the least fussy way to provide it.

But be careful with the word "agreed." A transcript is not automatically required. If your recipient didn't ask for one and doesn't need one, you're not obliged to produce it, and this article isn't a reason to give yourself another week of work. If it was agreed, it's part of the submission, so it gets checked like everything else.

Two small confirmations that prevent avoidable failures: that the upload area accepts the file types you're sending, and which time zone the deadline is in. "6 p.m. local time" is ambiguous when local means the fund's city and you're in another one.

Audit the assembled submission, not just the script

Check the actual package against the actual requirements, item by item, with the files open. Not the plan, not the script, not your memory of recording it.

Here's the fictional audit of Nadia's folder, run against the map above.

Two failures, both findable only by comparing the recording to the form. The logline was never recorded; the letter was discussed but never filed. Neither would have shown up in a read-through of the script, because the script wasn't the submission.

The audit should also listen for differences introduced during recording — a team member named differently than in the budget lines, a month that contradicts the schedule, a qualification that got dropped because it was awkward in speech. Spoken answers drift more than typed ones. That's normal, and it's why you check.

Now the honest limits of this example. The Riverbend rules were invented to teach the method, not to describe any real funder. In the real case, the fixes depend on the recipient's rules. Adding the missing logline means re-recording the Q1 file, since the route said one file per question — or asking the coordinator whether a separate short file is acceptable. Don't assume the workaround; ask. If you re-record Q1, the summary's time reference shifts, and the transcript has to be updated to match. The partner letter simply needs to be attached as a file, which then may change the index. Those dependencies are exactly what the map exists to catch.

An excellent set of answers sitting in a channel nobody accepted is still not a completed submission. Format approval, upload method, and the deadline all have to hold at once.

What the map should say when you're done

When you finish, the map should read as a set of closed items: every required answer located, every required document attached and named, every agreed support file present, every length and channel limit met.

Keep a second list beside it, and split it in two. The first part is what is still yours to close: the unanswered subquestion, the missing attachment, the fix you know you have to make. Those are not an acceptable open state. They mean the submission is not ready to send, and they stay on the list until they're done. The second part is what you cannot close yourself: the coordinator's reply you're waiting on, the permission you asked about and haven't heard back on. That part is not a failure. It's the honest state of a submission that is otherwise ready, and writing it down is how you keep the difference between a request and an approval from dissolving at the end of a long week.

Keep your own language in the answers, keep the recipient's questions intact, and change only the part you actually needed to change.

Frequently asked questions

What should be confirmed with the recipient before recording an alternative-format application?

Confirm four facts in writing: which questions may change format, what file types and length caps are allowed, how and where files are supplied, and what support such as a transcript or index has been agreed. Ask about the concrete barrier and alternative rather than giving a detailed personal history. A request is not an approval.

How can you tell whether an alternative format has actually been approved?

Documented means a published instruction or a written reply naming your situation. Pending means you asked and have not heard, or were told to ask someone else. A general accessibility page or contact route is not approval; it is the door to the conversation. A pending request gets you nowhere near a finished submission.

What is the purpose of the question map?

Open the current form and make one line per required item showing what it asks and where your answer will live. The map separates questions the recipient asked, reveals items that still need written fields or attachments, and marks unanswered subquestions. It is the artifact used to catch losses when auditing the assembled package.

If a word limit and a time limit pull against each other, which do you honor?

Write to the word limit, then time the read, and honor whichever cap is tighter. At 130 to 150 words a minute, 600 words runs about four to four and a half minutes. If a file is capped at four minutes, that cap is tighter. In the invented Riverbend example, 3:48 was under both but only just.

Does a published alternative-format route, such as BFI guidance, establish what another funder will accept?

No. The BFI guidance for National Lottery Expanded Screen Funding, read in September 2026, describes audio and video upload options for some questions, with eligible fields and suggested recording lengths shown in the form, and it states that production polish is not assessed. It is UK-specific, for one named program, as the page read on one day, and does not tell which fields accept uploads today, eligibility, deadlines, or what other funders do. The live form and written reply govern.

Further reading

• Add Captions to a Film Pitch Clip and Deliver the Right Version — Read this to decide which delivery version a recipient can actually open and to test it in the receiving route before sending.
• Write a Documentary Filmmaker Statement That Explains Your Practice — Read this when the practice question is on the form, so your answer explains how you work rather than restating the project summary.