Who Has to Say Yes to This Film Screening?
Who Has to Say Yes to This Film Screening?
Before sending a screening proposal, identify the next decision the event needs and who can make it. The person who likes your film may not select the program, control the room, approve spending, or arrange the screening with the responsible film representative.
Those decisions sometimes belong to one person. Sometimes they do not. Your job is not to guess an institution's hierarchy. It is to make the proposed event specific enough that someone can tell you what they can decide—and what still belongs elsewhere.
A creative deck can explain the film beautifully and leave all of this unanswered.
Start with one possible event
“Libraries could be an audience for this” mixes together several things. Library patrons are possible viewers. A programmer may consider the film for an event. A library may provide space, staff, promotion, or none of those. Each possibility raises a different question.
Replace the category with a particular proposition, without presenting it as an agreement:
A proposed screening of The Last Repair, followed by a conversation about keeping, using, and passing on family possessions, with a neighborhood repair group and a library as prospective collaborators.
This is an invented example. The film follows two siblings clearing their late father's workshop. No library, repair group, filmmaker, or budget holder has agreed to this event. Naming the possibility gives the planning a shape; it does not supply the missing commitments.
The repair group might know people interested in the subject. That would not give it authority to reserve a library room. A librarian might welcome the idea without being able to commit the program budget. The filmmaker might be willing to participate without having established who handles the relevant screening arrangement.
Keep these statements separate from the beginning. Otherwise, a friendly conversation can turn into a chain of assumptions: the group likes the film, therefore the library wants it, therefore a date is available, therefore the screening can be announced.
The first useful question is smaller: does the library's current published process allow this kind of joint event proposal, and where should it be considered? This article does not name a real library or invent its policy. For an actual event, check that route before addressing someone as its decision-maker.
Map decisions, not job titles
Write down the unresolved decisions in ordinary language. “Who can tell us whether the film fits this program?” is more useful than a column headed “stakeholder.” You are trying to find what the next person can settle, not decorate a pitch with institutional names.
For the fictional library screening, an initial map might look like this:
| Decision needed | Person or role to establish | Material that could help | Current status |
|---|---|---|---|
| May a joint proposal enter the library's program process? | Contact identified by the library's published route | Brief event idea and prospective participants | Route not yet checked |
| Is this film suitable for the proposed program? | Whoever is responsible for selection | Accurate description and an authorized viewing route | No selection decision |
| Can the proposed event use the space and required support? | Library contact responsible for the room and event operation | Proposed format, timing, and access needs | No venue commitment |
| Who can confirm the film's availability and screening conditions? | Responsible filmmaker, producer, distributor, or other representative, as applicable | Specific event scope and proposed dates | Authority and conditions unconfirmed |
| Who may commit the event budget? | In this example, a separate program manager | Costs, responsibilities, and outstanding estimates | No spending approved |
| Does the repair group want to take a defined part? | Person the group authorizes to answer | Specific contribution being requested | No co-host or promotion agreement |
These are questions to verify, not six mandatory departments. One person could resolve several rows. An organization may use different terms or combine selection with budget approval. Update the map when the actual process becomes clear rather than making people conform to your diagram.
The distinction between roles has a documented release example. Sundance's historical 306 Hollywood case study describes Mia Bruno working on strategy and community-partner relationships, Michael Tuckman handling theatrical bookings, and local organizations co-hosting screenings.[^sundance] That is evidence of different work being assigned within one release, not a staffing template for every small event.
Put unknown ownership in the map. “To confirm” is a useful state when it prevents the team from addressing the wrong person as though the matter were settled. Do not fill an empty row with the most senior name you can find on a website.
Match the material to the decision
A screening proposal does not have to arrive as one large package for everyone. Begin with the information the published process requests. Where the process leaves room for a conversation, connect the material to the decision in front of that reader.
For selection, make the film legible. Explain what it is, what viewers will actually encounter, and why you are proposing it here. Offer a viewing route only when you are authorized to share it. A description of The Last Repair as a practical repair tutorial would mislead a selector; the film is about competing attachments to a workshop, not instruction in fixing objects.
For hosting, make the encounter legible. Is this only a screening, or a screening and conversation? Who is proposed to take part? What would the host be asked to provide? Keep the event idea provisional until the host's requirements are known. “We can bring a film and discuss an appropriate format” is different from promising a panel whose speakers have not agreed.
For the screening arrangement, make the request specific. Identify the proposed event rather than asking vaguely whether the film is “available.” Establish who can answer questions about that use and what they need in order to do so. Do not treat possession of a screener, an online viewing link, or the filmmaker's enthusiasm as confirmation of the event arrangement. This is a coordination step, not a determination of legal rights; any actual permissions or conditions need to be confirmed with the responsible party.
Video Project's published community-screening process makes one such distinction explicit. It separates choosing a film and submitting a request from receiving pricing options and confirming a booking.[^videoproject] Its sequence is useful because a request and a confirmation are visibly different states. It is one provider's process, not a universal rule for every film, institution, or screening.
For the budget decision, make the commitments legible. Name the proposed costs and who is expected to meet them. Separate an estimate from a quoted amount and both from an approved commitment. Include staff work and other contributions that someone must agree to provide, even when no invoice is involved. “Free event” tells a viewer about admission; it does not tell an organizer who will do the work.
In the fictional map, the program manager needs a bounded proposal, not an uncosted promise to “support independent film.” The repair group likewise needs to know whether you are requesting subject knowledge, a speaker, help reaching potential viewers, or responsibility for the event. Those are not interchangeable favors.
Give access requirements the same clarity. If the event depends on captions or a particular access arrangement, record who will confirm its availability and suitability. Do not promise that a file or venue meets an attendee's needs before the relevant people have checked. A good proposal exposes a dependency while there is still time to address it.
Keep interest from turning into an invented agreement
Use status language that says exactly what a response established. The useful question is not simply “Did they say yes?” but “Yes to what?”
An invitation to submit materials means the recipient will receive them through the indicated route. It is not film selection. Interest in a conversation is not a co-host commitment. A possible date is not necessarily a room reservation. A room reservation alone does not confirm every condition of the screening.
For the invented example, imagine that the library's published route has now been checked and a contact has invited an event proposal. That hypothetical change would update only the first row of the map. The next action would be to submit the proposal through that route. It would not authorize an announcement reading “The Last Repair at the Library.”
Record the substance of the reply and its limits beside the status. Preserve the original message internally rather than relying only on a label such as “warm lead.” A useful note would say: “Invited a proposal for consideration; no film selection, date, or budget agreed.” The wording is less flattering and considerably more useful to the next person handling the project.
When a recipient cannot make the next decision, ask for a bounded handoff:
Who or which published process can confirm whether this proposal may be considered for the program? We have not agreed a date or screening arrangement.
That is not a request to bypass the recipient or find a more powerful person. It allows them to identify the appropriate route, including telling you that there is no route for the proposal as currently framed.
Do not put a prospective organization's logo on a deck merely because someone forwarded your message. Do not say “partnered with” when the recorded action is “agreed to read.” Describe the actual relationship and check any proposed public use of the organization's identity with it. Your internal decision map is not a permission slip for promotional claims.
Replace “support the film” with the next ask
An undifferentiated message sent at once to the library, the repair group, the filmmaker, and the program manager holding the budget—the four parties in our example—might say:
We would love your support in bringing this important film to the community. Please let us know how we can work together.
The recipients must now invent the event, decide what “support” means, and work out which of them is being asked to do what. Enthusiasm does not repair that ambiguity.
A better first inquiry, made through the library's verified public route, would say:
We are exploring a screening of The Last Repair with a neighborhood repair group as a prospective collaborator. The proposed discussion concerns how families decide what to keep, use, or pass on. Does your current program process allow joint proposals of this kind, and what material would you need to consider one? No date, venue, budget, or screening arrangement has been agreed.
This is sample wording for the fictional situation, not an inquiry that has been sent. It asks for a decision the recipient may be able to make now. It also leaves them free to say that the program is unsuitable, the submission route is different, or a necessary condition is missing.
Once that answer arrives, update the map and prepare the material for the next unresolved decision. The result should be one accountable next step—not an impressive list of people who might someday like the film.
<!-- ARTICLE BODY END -->Sources
[^sundance]: Jess Fuselier, “Distribution Case Study: 306 Hollywood”, Sundance Institute. See “Assembling a Team” and the supported-theatrical discussion. Historical 2018–2019 release context; inspected September 19, 2026. Used for distinct roles, not outcomes or a universal process. [^videoproject]: Video Project, “Community Screening Events”, “Here's how it works,” steps 1–6. Inspected September 19, 2026. Provider-specific request and confirmation sequence; no price, legal threshold, or actual screening permission is asserted here.
Frequently asked questions
Why isn’t it enough to find someone who likes the film?
The person who likes your film may not select the program, control the room, approve spending, or arrange the screening with the responsible film representative. Those decisions sometimes belong to one person and sometimes do not. Make the proposed event specific enough that someone can tell you what they can decide and what still belongs elsewhere.
How should you begin shaping a screening proposal?
Replace a broad category with a particular proposition, such as a proposed screening followed by a conversation, with prospective collaborators named as possibilities rather than agreements. Naming the possibility gives planning a shape; it does not supply missing commitments. For an actual event, check the institution’s published process before addressing someone as its decision-maker.
What decisions should be mapped, and what should the map show?
Write unresolved decisions in ordinary language, not job titles. Rows might cover whether a joint proposal may enter the program process, film suitability, use of space and support, confirmation of the film’s availability and screening conditions, budget commitment, and whether a partner wants a defined part. These are questions to verify, not mandatory departments; one person could resolve several, and unknown ownership should stay marked as unconfirmed.
What material should be matched to each decision?
For selection, explain what the film is and what viewers will encounter, offering a viewing route only when authorized. For hosting, make clear whether it is a screening or a screening and conversation, who might take part, and what the host would provide. For the screening arrangement, make the request specific and identify who can answer questions about that use. For budget, name proposed costs and distinguish estimates from quoted amounts and approved commitments, including staff work and access requirements.
How do you keep interest from becoming an invented agreement?
Use status language that says exactly what a response established. An invitation to submit materials is not film selection; interest in a conversation is not a co-host commitment; a possible date is not necessarily a room reservation; and a reservation alone does not confirm every condition. Record the substance and limits of the reply, and ask for a bounded handoff when the recipient cannot make the next decision. Do not use an organization’s logo or say “partnered with” unless that relationship and public use are actually confirmed.