You have a finished screenplay. Now comes the part nobody puts in the montage: finding suitable readers, preparing what they ask for and keeping track of where the script goes. A sensible submission process gives you concrete actions. It cannot promise a sale.
1. Make sure the draft is actually finished
Before sending the draft, read it through, fix distracting errors and address the story problems you already know about. You want the reader responding to the work, not struggling to follow it.
Get feedback before you query. Trusted peers, a writers’ group, a mentor, or a paid reader can all work, but the useful note is specific: a scene that drags, a character whose choice doesn’t track, a reveal that arrives too early. “I liked it” is pleasant. “I stopped believing her at the midpoint” is useful.
If formatting is the thing making readers twitch, fix that first. Our screenplay format cheatsheet covers what goes where without turning the page into a design project.
2. Write the logline, then the synopsis the recipient actually asked for
A logline is the one-or-two-sentence version: protagonist, problem, stakes, and a reason to care. Keep it concrete. If you need three semicolons and a family tree, it is not a logline yet. Our guide to writing a logline goes deeper on the craft.
A full synopsis is a different tool. It summarises the main story, including the major turns and the ending, when a full synopsis is requested. Do not treat it as a teaser. The Sundance Feature Film Program asks applicants for a synopsis that includes major story points and the ending; its Screenwriters Lab supports first or second fiction features. Check the current programme page for eligibility and requested materials, and follow that programme’s word limits rather than assuming one universal length.
Fictional example:
Logline: When an audit threatens to erase evidence of falsified patient records, a hospital cleaner must get her recordings to an investigator, even though they implicate the surgeon who saved her mother.
3. Know the difference between a query, a requested script, and an application
- An initial query is a short introduction asking whether the recipient wants to read more. It usually includes a logline, a few lines of relevant context, and a clear request. Do not attach the full script unless the recipient asks for it.
- A requested full script is what you send after someone says yes. That is when the PDF goes out, formatted, proofread, and named clearly.
- A programme application is a specific form with its own questions, synopsis, bio, sample pages, deadline, and eligibility rules. Follow the programme’s brief, not your query template.
Here is a fictional query for that project. Replace the bracketed details with accurate research and use it only where queries are accepted:
Subject: Query — The Cleaner’s File (feature, contained thriller)
Dear [Name],
I’m querying because [Company] produced [specific film or type of film], and this project sits in that territory.
The Cleaner’s File is a contained thriller. When an audit threatens to erase evidence of falsified patient records, a hospital cleaner must get her recordings to an investigator, even though they implicate the surgeon who saved her mother.
The script is complete at 104 pages. I can send the first ten pages or the full script, whichever you prefer. Thank you for your time.
[Name]
[Contact]
4. Target recipients who actually accept submissions
Look for recipients who handle your genre and format, then read their submission policies. Some accept queries; others require a referral or a particular application route. Researching their work helps you explain the fit without inventing a personal connection.
The WGA East signatory agency list is a starting point for researching agency identity, not proof that an agency wants unsolicited scripts. Check each agency’s own policy and relevant clients before approaching.
For competitions and labs, use the official route. The Nicholl official partners page lists public-submission routes; check that page for current details rather than assuming a direct application or deadline. For a wider map of competitions and what they are for, see our guide to screenwriting competitions. For associations and resources, our review of screenwriters’ associations is a useful starting point.
5. Build writing relationships without treating them as transactions
Join a writing group, attend a local reading or collaborate on a short film. Repeated participation gives you something to discuss beyond asking someone to read your screenplay.
Be useful. Give notes when asked. Attend readings and table reads, and pay attention to how dialogue plays out loud; our guide to table reads and dialogue is a good primer. When someone asks what you are working on, have the logline ready. When they ask to read it, ask whether they prefer a query, ten pages, or the full script. Do not assume.
6. Keep a submission log and keep writing
A simple tracking system stops you from sending the same script twice to the same person, missing a requested revision, or forgetting which programme asked for a synopsis with the ending.
| Item | What to record |
|---|---|
| Recipient | Name, company or programme, genre focus |
| Route | Query, requested full, application, competition |
| Date sent | And method (email, form, portal) |
| Materials sent | Logline, synopsis, pages, full script |
| Response | No, request for more, pass, no response yet |
| Next action | Follow-up date, revision, or close the file |
Start the next project while submissions are out. Keep any follow-up within the recipient’s stated policy, record the response and move on when the answer is no. A request to read more is useful progress; it is not yet an offer.
If an offer arrives, get qualified professional advice before agreeing to terms. For now, choose one appropriate recipient, check the instructions and prepare that submission.






