Explain Why Your Film Fits a Particular Program

A programming-fit statement is a claim about a relation. This film does something specific; this program says it is looking for something; here is what happens when the two are put in the same room. Everything else in the note — the admiration, the award list, the fact that your earlier short played somewhere similar — is either context around that claim or a substitute for it.

Fit and selection are different questions, and keeping them apart is most of the work. Fit is something you can argue, and something a programmer can answer. Selection depends on budget, print condition, how the strand already balances, which filmmakers can travel, and a dozen things nobody publishes. A note that treats the first as a prediction of the second produces the two most common bad paragraphs: one that flatters the institution, and one that repeats the institution's own sentences back to it.

What follows is a working method, not a studied one. It comes down to reading the program's current words, finding the actual thing in your film that answers them, being honest where it doesn't, and asking only the question the process permits.

Read the current program, not its reputation

Before you write anything, get three things from the source: what this edition or strand says it is for, what stage of work it accepts, and how it says it wants to be approached. Then get the eligibility rules — premiere status, length, format, territory — and keep them in a separate mental drawer. Eligibility decides whether the film can be considered. The artistic argument decides whether it belongs. Mixing them produces notes that explain your runtime as if it were an aesthetic position, or apologize for a premiere status as if it were a weakness in the film.

Reputations lag. A festival known for one kind of cinema opens new strands; a venue associated with retrospectives starts a first-feature prize; a strand's stated purpose changes between editions while its name stays the same. Answer the page in front of you, not the summary you absorbed five years ago. If a strand's description this year is about comedy, the fact that it once programmed three-hour landscape films tells you nothing.

Previous selections are context, not evidence. The useful thing you can learn is that a film roughly like yours has shown there — which is mild encouragement and no information about this year's rules. What you cannot learn from a lineup is the remit or the programmer's private preferences. "They like slow work" is a summary of the past, not a promise about your film, and a public interview in which a programmer describes an interest is a bounded account of taste, not a route into the decision.

Here is an invented brief, written for this article. The festival, the strand, the address, the film, and the crew that follows are all fictional. No real program's policy, inquiry process, or selection outcome is represented here, and the permissive contact policy in this brief belongs to this invented strand alone.

Fairweather Documentary Week — Long Watch

Long Watch programs films that hold a place long enough for routine to become legible. We are drawn to work where duration is doing the thinking: films that stay with a location past the point where it becomes informative, and where the viewer's own attention becomes part of the subject. We are also drawn to labor that stays invisible on purpose.

Long Watch screens in a single 94-seat room. One screening per film. No parallel programming runs during the strand.

We consider completed films only. Works in progress are not eligible for this strand.

If you are unsure whether your film suits the strand, you may send one inquiry of up to 150 words to [inquiry address] before submitting. We answer by email, usually within two weeks. This is not a submission and does not affect the selection process.

Three facts here do most of the work: the strand's purpose is stated in three sentences, two about form and one about subject; it accepts finished films only; and it publishes a route for one narrow question while explicitly saying that route does not affect the selection process.

Now the film. Nightwater runs 74 minutes and follows four maintenance workers through three consecutive nights at a municipal reservoir. It has no dialogue, no narration, no music, and no archival material. The sound is the site: pumps, water moving through pipes, footsteps on wet concrete, tools, radio static. Shots hold between ninety seconds and eleven minutes, and the camera moves only when the crew moves. Of the four workers, three appear throughout; Aldo, who works the far end of the site, barely shares the frame with anyone until the third night.

Find the concrete relationship between film and program

Four kinds of material in a program description are worth answering: a subject, a form, a viewing context, or a question the strand says it is asking. The Long Watch brief offers form, a subject, and a viewing context. That is enough to build an argument from.

The shape of the argument is almost always the same three moves. What the program says it does. What your film actually does, named specifically. What the pairing would let viewers encounter. The third move is the one people skip, and it is the one that turns a compliment into a reason.

Compare three paragraphs written for this brief.

The prestige-led version: "It would be an honor to be considered for Fairweather Documentary Week. My previous short screened at [a festival] in 2023, and I have long admired the strand's commitment to bold, patient cinema. Nightwater is a meditative, immersive work in the tradition of [a well-known director], and I believe it would sit beautifully alongside the films you have programmed in previous years."

This is polite, and it says nothing. Every sentence could be sent to a different program with one word changed.

The keyword-matching version: "Nightwater is a work of sustained observation in which the viewer's attention becomes part of the subject. It holds a place long enough for routine to become legible, and it is drawn to labor that stays invisible on purpose. It is patient, observational, and durational, and I think it exemplifies exactly the kind of programming Long Watch has become known for."

Better organized than the first, and no more informative. Every claim is the brief's own language reassembled. Cover the program's sentences, as a test, and see what a reader would still know about the film: nothing. A fit statement that collapses when you remove the program is a mirror.

The concrete version:

Nightwater runs 74 minutes and follows four maintenance workers through three consecutive nights at a municipal reservoir. Nothing is narrated and nothing is explained. The film's first eleven minutes are a single fixed shot of a pump house interior while two workers change a valve seal; the camera does not move until they leave. The relationship the strand might use is between Ruben, twenty-two years at the site, and Dita, in her first month: the handover between them happens on camera, without a word. In a single room with no parallel programming, an audience can stay inside the film's own clock. I would like to know one thing: does the strand ever program a film with no spoken language at all?

About 125 words, against the brief's 150-word ceiling, and it asks a single question at the end. It names the runtime because the runtime is doing work in the argument. It names one organizing choice — the eleven-minute opening shot — rather than listing themes. It gives the handover as the relationship the strand might use, because the brief asks for routine becoming legible and a handover is a routine that becomes legible on screen. And it uses the viewing context the brief supplied: one room, one screening, no parallel programming, which is exactly the condition under which an audience submits to a film's clock rather than checking what else is on.

Notice what it does not do. It does not claim the film is important. It does not pretend 74 minutes is short or long. It does not say the strand will love it. It hands over two facts about the film and one inference about the room, and lets the programmer make the judgment.

Name the difference that matters

Now take the same brief and change one thing — not the program, the film.

Suppose the version of Nightwater you have is 74 minutes built almost entirely from interviews. The same four workers, seated in a borrowed office, recall one bad night when a valve failed and they kept the system online for eleven hours. Nine minutes of present-tense footage are cut through it: the pump house at three in the morning, a corridor, a hand on a valve. No archival material, no narration. The crew speaks for themselves.

What survives? The subject does. This is still a film about labor nobody sees, and the brief's final sentence names exactly that. What does not survive is the duration argument. A 74-minute runtime is a property; a film that holds one place for 74 minutes is a method. The brief's first sentence is about holding a place, and the interview film does not do that. It describes the place, at length, in retrospect.

So the argument gets shorter and more honest. Name the final sentence's connection — invisible labor, told by the people who do it. Say plainly that the film is testimony-led rather than durational. Then ask the question that is actually open: is the strand's first sentence a requirement or an interest? If Long Watch only programs work that holds a place, this film is for somewhere else, and the filmmaker would rather learn that from a two-line email than from a rejection.

Two failure modes follow from this variant, and both are common.

The first is relabeling. Seventy-four minutes is not a synonym for durational. Cutting to interviews does not make a film observational. If the only link between your film and the brief is a word both of you use, you have found a shared vocabulary, not a fit.

The second is editing the brief to suit the film. If your argument only works once you have quietly rewritten the strand's purpose — treating its final sentence as the whole remit, or assuming that any film about invisible labor must be welcome — then you are describing a program you invented. The brief did not move. The film changed, and the argument has to change with it.

Sometimes this analysis produces the most useful answer of all: the film belongs somewhere else. A strand, a venue, a series, or a commissioning context with a stated purpose closer to what the film actually does. Finding that is not failure. It is the same labor, pointed at a better target.

Write for the next permitted decision

Whatever the film is, the note has three parts and no more: the strand's purpose, in a clause; the film-specific connection, in the concrete form above; and the practical context the program asked for. Runtime, available cut, language and subtitle status, stage of completion, and anything else the form requests. Facts you can confirm with the people who own them — not estimates, not a future cut you hope to finish, not a runtime that will be settled in the mix.

Follow the requested format exactly. If the form asks for 200 words, write 200 words. If it asks for a synopsis and a link, send a synopsis and a link rather than an essay attached to a shorter answer. The format is not the interesting part of the decision, which is precisely why getting it wrong costs you.

If the program publishes an inquiry route, that route has a purpose and a limit. Long Watch permits one question of up to 150 words, which means the budget should be spent on something the recipient can answer in a sentence. "Does the strand ever program a film with no spoken language at all?" has an answer. "Would you select this film?" does not — nobody can honestly answer it before a lineup exists, and asking it puts the programmer in the position of managing your hopes. "Who decides?" is answered by the published process, so it wastes the question.

Where no inquiry route exists, there is no inquiry. The published process is the route, and a programmer's public remarks at a Q&A are not a channel. Reading a stated remit carefully and then following the formal path is not passive; it is the thing that keeps your film in the pile that gets read.

The same discipline covers the spoken version. In an invited conversation, a panel, or the introduction before a screening, you have about two sentences, and they should do the same work: what the film does, and where it sits in relation to what this strand says it is for. The awards recitation is not a fit argument in writing, and it is worse out loud.

One practical consequence of all this: a fit statement does not travel whole. The film half of it — the 74 minutes, the eleven-minute shot, the wordless handover — travels with the film and stays true. The program half has to be rebuilt for each context, from that context's current words. If you find yourself pasting the same second paragraph into a note to a different strand, that paragraph was not doing anything.

What the ending has to survive

Here is the compact version, assembled from what the invented film and the invented brief actually support:

Nightwater, 74 minutes. No dialogue, no narration, no archival material. Three consecutive nights with four maintenance workers at a municipal reservoir; shots hold from ninety seconds to eleven minutes. The handover between Ruben, twenty-two years at the site, and Dita, in her first month, happens on camera without a word. Long Watch screens once, in a single room with no parallel programming — an audience can stay inside the film's own clock. Route: the inquiry address in the current edition's published guidance, one question, under the word limit.

Four claims, four sources. The runtime, the dialogue status, the shot lengths, and the handover are properties of the film, confirmed with the people who made it. The single room and the one screening are the strand's published conditions. The route is the strand's published process, checked for this edition rather than remembered from the last one.

That is the test to run before you send anything. Not "does this sound flattering?" but whether each claimed connection can be traced back to something the film does and something the program currently says. If a sentence can't be traced, cut it. If the whole statement can be sent unchanged to the next program on your list, it isn't a fit argument yet — it's a compliment with a runtime attached.

Frequently asked questions

What is the difference between programming fit and selection?

Fit is a claim about the relation between what a film does and what a program says it is looking for; it can be argued and answered by a programmer. Selection depends on budget, print condition, strand balance, travel, and unpublished factors. Treating fit as a prediction of selection produces flattery or recycled program language.

How should I use a program's previous lineups when writing a fit statement?

They are context, not evidence. They may show a roughly similar film has screened there, which is mild encouragement and says nothing about this year's rules or remit. A lineup cannot reveal the stated purpose or a programmer's private preferences; answer the current published page.

What four things in a program description are worth answering?

Subject, form, viewing context, or a question the strand says it is asking. The example brief offers form, a subject, and a viewing context. Build the argument from those, not from reputation.

What does relabeling look like, and why is it a failure?

Relabeling is using a shared word as if it were a fit. For example, 74 minutes is not a synonym for durational, and cutting to interviews does not make a film observational. If the only link is a word both use, it is shared vocabulary, not a fit.

If a program publishes an inquiry route, what kind of question belongs there?

Spend it on something the recipient can answer in a sentence, such as whether the strand ever programs a film with no spoken language. Do not ask whether they would select the film or who decides, if the process already answers that. In the invented brief, the route is one question up to 150 words and does not affect selection.