Does a Coincidence Start the Film—or Solve It for the Characters?
Does a Coincidence Start the Film—or Solve It for the Characters?
A synopsis is a compression machine, and compression has a favorite casualty: the middle. You keep the opening image, you keep the ending, and the connective tissue—the phone calls, the refusals, the changed plans—evaporates. When an accidental event sits near the start or the end, the loss creates a specific distortion. A traveler happens to pick up the wrong instrument case, and by the last line of the synopsis it's back with its owner, so the logline seems to say: luck gives, luck takes away, the end. The characters appear to have done nothing. Or the reverse: a synopsis credits a protagonist with a hard-won recovery that, in the actual scene, was handed to them by a stranger sitting in the right seat at the right gate. Same compression, opposite lie.
This matters because "coincidence" is not a verdict. It's a location. The useful question is not is coincidence allowed—no serious answer to that exists—but what does the accident change, and what do the characters still do with the change? That question can be answered from the pages in front of you, which is exactly why it belongs in the synopsis stage rather than the argument stage. What follows is an editorial demonstration built around two invented cases, not a report on any real film. The point is a method you can run on your own material.
Identify what the coincidence changes
Before judging the accident, name its function. In a working screenplay, an accidental event tends to do at least one of three jobs, and often two at once:
- It creates the problem. The wrong instrument case is now in the traveler's possession. Without the mix-up, there is no story.
- It redirects an ongoing pursuit. The protagonist was heading somewhere for their own reasons; the accident forces a detour.
- It delivers the outcome. The owner appears and the case is returned. The accident, not the search, resolves the situation.
These are consequences, not categories. A single accident can create the problem in act one and, through a different consequence, deliver the resolution in act three. Trace each consequence separately. "Coincidence starts this film" is not yet a judgment about whether the film works; it's a description of gear ratio.
The distinction matters most when you're deciding what your synopsis owes the reader. If chance creates the problem, you need to say so explicitly, because the reader will otherwise wonder why the protagonist is chasing an instrument case across a city for no stated reason. If chance delivers the outcome, you need to say that too, or the synopsis will read as though the search succeeded. The label is not the argument; it's the map.
Restore the actions between accident and result
Here is where a compressed synopsis most often falsifies. Take an invented scene pair.
Source scene (Example A): Mara, a traveler, picks up the wrong instrument case at a baggage claim. At home she opens it and finds a violin and a printed itinerary. She calls the number on the itinerary. No answer. She drives to the address on the itinerary—a music school—and learns the owner, Ilya, is on tour. The school gives her a venue. She takes a train she hadn't planned to take, misses a connection she'd paid for, and reaches the venue after the performance. Ilya is there. She returns the case.
Synopsis draft: "Mara accidentally takes the wrong case and manages to return it to its owner."
The synopsis is not false. It is thin in a way that misrepresents the people. "Manages to" compresses a phone call, a detour, an unplanned train, a missed connection, and a decision to keep going after the first route fails. Each of those is a choice. The accident gave her the case; she gave herself the detour. If the synopsis is meant to show what kind of film this is—a film about a person who takes on an inconvenience for a stranger—the compression has removed the evidence.
Now the harder version, because the point is not "restore all action, always."
Source scene (Example B): The owner, Ilya, is sitting in the departure lounge two seats from Mara. He sees the case, recognizes it, and says so. They swap. This case holds no itinerary or other identifying paperwork, and Mara has not opened it. Nothing else happens; the film continues into the story it was always going to be.
False synopsis: "After a determined search, Mara reunites the case with its owner."
There is no search. The reunion is an encounter. If you keep the false synopsis, you're not just compressing—you're inventing character traits. Mara didn't persist; she sat down. Ilya wasn't tracked; he appeared.
But note what follows. Restoring the truth—"Ilya happens to be at the same gate, recognizes the case, and they swap"—does not automatically mean the film is broken. It means the accident is doing the work of resolution. Example B may be deliberate: a film about two people who were always going to cross paths, in which the encounter is the point rather than a shortcut. The synopsis's job in that case is to make the encounter legible as design, not to smuggle in action that isn't there to make the ending feel earned in a conventional sense. Whether the design holds is a separate question. The synopsis must at least not lie about it.
Run the ending with and without the accident
Here's a diagnostic, not a rewrite. Take the accident out and ask two questions: What do the characters' actions still accomplish? What remains outside their control?
For Example A, remove the case mix-up. Mara never meets Ilya. Her choices—the phone call, the drive, the train—have no object. They accomplish nothing, because there is nothing to accomplish. The accident is load-bearing for the entire plot. But the choices are meaningful: they show what Mara does when a problem lands in her life. In this version, chance supplies the situation; Mara supplies the character. That is a coherent and common arrangement. A synopsis that honors it will say: the wrong case creates the problem, and what Mara does next is the film.
For Example B, remove the gate encounter. Mara has the case and no way to find Ilya; the reunion doesn't happen in that scene. Depending on the film, the case may never be returned, or it may return later if some other chance closes the gap. The accident is load-bearing for the outcome, not for the protagonist's behavior. The choice that matters—recognizing and returning the case—has been relocated from Mara to Ilya, and then to the seating chart.
These are different films, and neither is disqualified. But notice that the counterfactual has done a specific thing: it has told you which element the story depends on. That is the question the synopsis should be able to answer. A synopsis that credits Mara's persistence in Example B is not just imprecise; it has moved the load-bearing element from the seating chart to the protagonist. The synopsis now asserts an agency the scene does not contain.
One caution about this diagnostic: it can tempt you toward a rewrite. "What if Ilya doesn't sit there, and Mara searches instead?" That is a real story decision and belongs to the author, not the synopsis. Run the counterfactual to understand the mechanism you have, then describe that mechanism. Do not perform surgery on the beat sheet mid-synopsis.
Choose truthful compression or a development question
By now the synopsis has three honest options, and they depend on what the pages actually do.
If the synopsis omitted consequential action, repair it. Example A's "manages to return it" becomes: "Mara calls the number, drives to the school, takes an unplanned train, and reaches Ilya after the performance—returning the case at the cost of a connection she'd paid for." That's longer, and it earns the length by showing what kind of protagonist the film has. You can compress it back down to a clean line, but you should compress toward the actions, not away from them: "Mara tracks the case's owner across a tour schedule, missing a connection to complete the return." The protagonist's agency survives the compression.
If the screenplay deliberately gives chance decisive power, describe that role. Example B's honest synopsis might be: "Ilya happens to be at the same gate and recognizes the case—an encounter the film treats as the two strangers' preordained collision, not as a reward for any search." If the creator has said as much in an interview or commentary, cite that account as the creator's stated intention, not as proof that the ending succeeds. Without such an account, you can still describe what the pages do while flagging that the intent is inferred.
If the role of chance is unsupported or conflicts with the pitch's promise, ask a development question. Suppose the pitch promised a film about persistence, and the pages deliver Example B. The synopsis can't honestly say "Mara's determination pays off," and it shouldn't say "a coincidence saves her" as if that settles the film's quality. The useful sentence is a question: "Does the film intend the gate encounter as design—strangers destined to meet—or is the reunion expected to read as Mara's reward? These require different setups earlier, and the pages currently support the first." That's a real note, and it's more usable than "coincidences are lazy." It moves the conversation to the actual inconsistency instead of applying a rule the film may not owe.
What a synopsis can and cannot settle
There's a reason this method stays inside the synopsis rather than drifting into a general argument about coincidence in screenwriting. A synopsis can show you where the accident sits and what stands around it. It can show you whether the protagonist's choices touch the outcome or merely accompany it. It cannot show you whether audiences will accept the film's use of chance—that's a claim about reception, and nothing in the pages proves it in advance. It also cannot determine whether the accident was a wise choice. A film can be entirely built on a gate encounter and be coherent; a film can bury its protagonist in restored actions and still feel like luck wearing a costume, because none of those actions changed the result.
The most useful thing the synopsis can do is stop pretending. If the accident starts the difficulty and the characters work through it, write both halves. If the accident ends the difficulty, write that, and describe what the film uses the accident to reveal or arrange, if anything. If you can't tell which film you have, that's a development question, and asking it is the honest response. The line between "coincidence starts the film" and "coincidence solves the film" isn't a verdict about craft. It's a description of where the weight falls, and a synopsis that names the weight accurately gives its author something to work with.
What follows is the chain as it might appear at the bottom of a working document, annotated so the reader can see the decisions behind the prose.
- Accident: Wrong case picked up. (Creates the problem. State it plainly.)
- Response 1: Mara opens it, finds the itinerary, calls. (Choice. Shows initiative; keep.)
- Response 2: She drives to the address. (Choice; adds cost. Keep, possibly compressed.)
- Complication: Ilya is on tour. (Redirects pursuit; supplies the film's middle.)
- Response 3: She takes the unplanned train, misses a paid connection. (Choice with price. Keep—this is the character evidence.)
- Outcome: She reaches him after the performance. (Reunion. Note: reached by her route, not by luck.)
Run the same chain for Example B and the middle empties out, which is not a failure of the chain—it's the finding. The synopsis then says what fills the empty middle instead, or asks whether the absence is intended. Either way, the accident is no longer a fog over the whole story. It's a marked spot on a map you can actually navigate.
Frequently asked questions
Is coincidence automatically a flaw in a film synopsis?
No. The article treats coincidence as a location, not a verdict. The useful question is what the accident changes and what the characters still do with that change. An accidental event may create the problem, redirect an ongoing pursuit, deliver the outcome, or do more than one of those jobs, so each consequence should be traced separately.
How can I tell if my synopsis falsely credits the characters?
Compare the synopsis with the source scenes. In Example B, Ilya happens to be at the same gate, recognizes the case, and they swap; Mara has not opened it. A synopsis saying after a determined search she reunites the case with its owner invents persistence. The honest version either restores consequential action that was omitted or describes the accident's role plainly.
What diagnostic can show whether the accident is load-bearing?
Remove the accident and ask what the characters' actions still accomplish and what remains outside their control. In Example A, without the mix-up Mara's choices have no object, so the accident is load-bearing for the plot while her choices show character. In Example B, without the gate encounter the outcome may not happen, so the accident is load-bearing for resolution. Use this to understand the mechanism, not to rewrite the beat sheet mid-synopsis.
What if chance deliberately delivers the outcome?
Describe that role honestly instead of saying the search succeeded. If the creator has stated the intention in an interview or commentary, cite that as the creator's stated intention, not as proof the ending succeeds. If the pitch promised persistence but the pages do not support it, ask a development question about whether the encounter is design or meant to read as the protagonist's reward.
What can a synopsis not settle about coincidence?
It cannot show whether audiences will accept the film's use of chance, because that is a claim about reception. It also cannot determine whether the accident was a wise choice. It can show where the accident sits, what stands around it, and whether the protagonist's choices touch the outcome or merely accompany it.