The Programmer’s Point of View
Imagine you’re a programmer for a festival like Tribeca. You have thousands of films to sift through. Each one arrives as a digital file, a thumbnail, and a small packet of information. You’re not just looking for a good movie; you’re looking for a voice,
a vision, a reason to champion one film over a hundred others that are also technically proficient and narratively sound. You’re looking for a spark. You click open the director’s statement, hoping for a key to unlock the film’s soul. And what do you find? A plot summary.
The Mistake: The Statement as Book Report
This is it. The single most common and debilitating mistake a director can make. They treat the director’s statement as a factual summary of what happens in the movie. They write things like, “The film opens on Sarah, a lonely accountant who discovers a mysterious box. She then embarks on a journey to find its owner, meeting a cast of quirky characters along the way.” It’s not wrong, but it’s utterly useless. The programmer has a synopsis for that. They are about to watch the movie, or have just watched it. Reciting the plot back to them is like telling a chef the ingredients of a dish they just cooked. It’s redundant and, frankly, a little insulting. It suggests the filmmaker thinks the programmer needs their hand held to understand the story, or worse, that the filmmaker has nothing more to say beyond what’s literally on screen. It’s a massive, wasted opportunity.
Why This Kills Your Campaign
A book-report statement fails because it answers “what” instead of “why.” A festival campaign isn't just about getting your film accepted; it's about building a narrative around your film that programmers, and later the press and audiences, can latch onto. A programmer reads your statement looking for answers to crucial questions: - Why did *you* have to be the one to tell this story? - What personal connection, obsession, or unique perspective do you bring? - What are you trying to explore beyond the plot? What’s the film *about*, not just what happens in it? - What’s your artistic intent? Why did you make specific choices in tone, style, or performance? A plot summary provides zero insight into any of this. It renders the director—the supposed visionary—invisible. In a sea of thousands of submissions, invisibility is death. The film becomes just another competent but generic entry, lacking the compelling human story behind it that makes a programmer sit up and fight for it in selection meetings.
The Fix: Answer the 'Why' Question
A powerful director’s statement is a manifesto, a confession, and a mission statement rolled into one. It’s the soul of the project, not its skeleton. It should be written in the first person and burn with your specific voice. Instead of summarizing the plot, use the statement to connect the film's themes to your own life or worldview. Did a childhood memory inspire the protagonist’s journey? Is the film an attempt to grapple with a question that keeps you up at night? Say that. Talk about your artistic approach. Why did you choose a handheld camera to create a sense of unease? Why did you cast non-actors to capture a specific authenticity? This isn't technical jargon; it's a window into your creative mind. It shows you are an author with intent, not just an operator who filmed a script. The goal is to make the programmer feel like they know you and understand what drives you. You want them to read it and think, “I get it. I see the passion. I have to see this film.”
