Why Your Brain Cannot Evaluate a Script and What to Do About It

Every development executive, producer and script consultant in the business has experienced this. You read a script, form a strong opinion, write your notes, and then a colleague reads the same script and reaches the opposite conclusion. Both of you are experienced. Both of you are thoughtful. Both of you are wrong about each other being wrong.

The reason is not taste. It is biology.

How memory actually works

Memory is not a recording. It is a reconstruction.

When you read a script, your brain is not storing a faithful copy of what you encountered. It is filtering, compressing and reorganising information in real time, and then reconstructing a version of it when you try to recall it later.

This process is governed by a few principles that have significant implications for how scripts get evaluated.

Working memory and the 4 to 7 item limit

Working memory, the part of your brain that holds what you are currently processing, has a capacity of roughly 4 to 7 items at any one time. This is not a personal limitation. It is a universal feature of human cognition.

What this means in practice: you cannot hold a 120 page script in your head simultaneously. Nobody can. You are always reading in fragments, processing in chunks, and building a picture piece by piece.

This is why script notes tend to focus on specific scenes, specific moments, specific lines of dialogue. The brain can hold and articulate a handful of things at once. Everything else gets compressed or lost.

It also explains why development conversations involve so much back and forth. Each pass surfaces a different 4 to 7 things. The full picture never gets seen by anyone in the room at the same time.

Event segmentation and how stories get stored

Cognitive science has established through Event Segmentation Theory that the brain does not store continuous experiences as a timeline. It breaks them into events, meaningful chunks, and stores those chunks rather than the stream itself.

When you read a script, your brain is constantly making decisions about where one event ends and another begins. Those segmentation decisions are shaped by your existing schema, your experience, your expectations of the genre, your personal history with similar stories.

Two readers segment the same script differently. They store different chunks. They reconstruct different stories when asked to recall what they read.

This is not a flaw in the reader. It is how human memory works.

The forgetting curve and what survives a read

Within hours of reading a script, significant detail is lost. Within days, mostly gist remains.

What survives is not a representative sample of the script. Research on recall consistently shows that people retain gist and overall meaning, key events and emotional moments, and the beginning and end of an experience more reliably than the middle.

The middle of a script, often where the most important structural work happens, is the most vulnerable to forgetting.

The Peak End Rule and what executives actually remember

Daniel Kahneman's Peak End Rule describes a consistent pattern in how people evaluate experiences. Memory of an experience is dominated by two moments: the peak, the most emotionally intense moment, and the end.

The average of the experience has surprisingly little influence on how it is remembered and evaluated.

For script evaluation this has a direct implication. An executive who reads a script with a powerful Act 2 climax and a strong ending will likely remember it favourably regardless of what the first half looked like. An executive who reads a script with a weak ending will likely remember it unfavourably regardless of what came before.

The coverage that emerges from that read is not an evaluation of the whole script. It is an evaluation of the peaks and the ending, reconstructed through the reader's existing schema.

Reconstruction and the coverage problem

When a reader writes coverage, they are not reporting what they read. They are reconstructing it.

The reconstruction process works like this. The brain retrieves fragments. It fills gaps using logic, expectations and existing patterns. It produces a coherent story that feels like memory but is partly fabrication.

This is why two experienced readers can recommend opposite decisions on the same script. They are not evaluating the same thing. They are each evaluating their own reconstruction of it.

Coverage is opinion. But it is opinion shaped by cognitive processes that neither the reader nor the executive receiving the notes is typically aware of.

Two objections worth taking seriously

Objection 1: If audiences only remember what lingers, isn't evaluating what lingers the right approach?

This is a good faith argument and it deserves a good faith answer.

The emotional impact that lingers is real and it matters. A film that leaves a lasting impression on an audience is doing something right. But the problem is that what lingers in a development read is not the same as what will linger for an audience watching the finished film.

A development executive reading a script is not the audience. They are reading a technical document that requires significant imaginative work to translate into a cinematic experience. What lingers for them is shaped by their industry experience, their schema, their knowledge of similar films. That is a different reconstruction than what a general audience will experience watching the finished product.

Evaluating what lingers in a script read is effectively evaluating the executive's reconstruction of their imagination of the film. That is several steps removed from the actual audience experience.

There is also the Peak End Rule to consider. What lingers in any experience is heavily weighted toward the peak and the ending. A structurally weak first half with a powerful climax will be remembered positively. A structurally strong film with a weak ending will be remembered negatively. If greenlight decisions are made on the basis of what lingers in a read, they are being made on a sample that is systematically biased toward peaks and endings and away from everything in between.

Structural data gives you a view of everything in between. Not instead of emotional response. Alongside it.

Objection 2: Reading a script is not the same as watching the film. How does one translate to the other?

Honestly and imperfectly. The gap between page and screen is real and significant. Direction, performance, score, cinematography, pacing in the edit. These elements transform a script in ways that are genuinely difficult to predict from the page alone.

But here is what holds across that translation: structure.

The structural signature of a script, the arc, the act distribution, the scene pacing, is one of the most stable elements in the journey from page to screen. A script with 349 scenes becomes a film with 349 scenes. The intensity curve of a script tends to predict the intensity curve of the finished film more reliably than any other single measurable element.

The elements that transform unpredictably in production are execution elements: performance, direction, score. The elements that remain relatively stable are structural. That is precisely what structural analysis measures.

The argument is not that script structure predicts everything about the finished film. It is that script structure is the most stable and measurable predictor available at the development stage. Everything else at that stage is a bet on execution. Structure is a bet on the blueprint. And betting on a blueprint you can see is better than betting on one you cannot.

Kurt Vonnegut theorized in 1946 that stories have universal shapes that could be plotted on a simple axis. Decades later researchers used natural language processing to analyse nearly 2,000 works of fiction and confirmed he was right. The neuroscience is clear: drawing or visualizing the shape of a story creates stronger neural pathways than reading alone. Seeing the whole is a fundamentally different cognitive act from reading through it.

What visualization changes

If memory is reconstruction, and reconstruction is shaped by what the brain can hold at once, then the most powerful intervention is to give the brain something it cannot generate on its own: a view of the whole.

A structural visualization of a screenplay shows the entire arc as a single image. Every scene. Every act. The intensity curve across the full runtime. The character presence from first page to last.

This is information the brain cannot reconstruct from reading alone. It requires the whole to be present simultaneously, which is precisely what working memory cannot provide during a linear read.

When a development executive can see the full arc of a script at once, they are working on a different cognitive level. Not scene by scene. Not notes on 4 to 7 things. The whole picture, held in a single view.

This does not replace the read. It complements it. The gist, the emotional response, the sense of whether a story resonates, those come from the read. The structural picture, the one the brain cannot hold simultaneously during a linear experience, comes from the visualization.

Together they give the development executive something no single read can provide: a complete picture.

What this means for writers

The same principle applies on the writing side. A writer revising a script is working scene by scene, often losing sight of the larger structural shape. Notes come in fragments. Rewrites address fragments. The arc drifts without anyone noticing because nobody is holding the whole thing at once.

Working at arc level rather than scene level is a fundamentally different cognitive task. It requires seeing the whole before deciding what to change. Visualization makes that possible.

The brain remembers compressed, meaning driven summaries with a few strong moments and reconstructs the rest when needed. A structural visualization is the antidote to that compression. It gives back what the brain had to throw away.

arc.quanten.co

Further Reading

Working Memory Miller, G.A. (1956). The magical number seven, plus or minus two: Some limits on our capacity for processing information. Psychological Review, 63(2), 81–97. scholar.google.com/scholar?q=miller+magical+number+seven

Baddeley, A. (2000). The episodic buffer: A new component of working memory? Trends in Cognitive Sciences, 4(11), 417–423. scholar.google.com/scholar?q=baddeley+episodic+buffer+working+memory

Event Segmentation Theory Zacks, J.M., Speer, N.K., Swallow, K.M., Braver, T.S., & Reynolds, J.R. (2007). Event perception: A mind-brain perspective. Psychological Bulletin, 133(2), 273–293. scholar.google.com/scholar?q=zacks+event+segmentation+theory

The Forgetting Curve Ebbinghaus, H. (1885). Memory: A contribution to experimental psychology. psychclassics.yorku.ca/Ebbinghaus/memory.htm

Peak End Rule Kahneman, D., Fredrickson, B.L., Schreiber, C.A., & Redelmeier, D.A. (1993). When more pain is preferred to less: Adding a better end. Psychological Science, 4(6), 401–405. scholar.google.com/scholar?q=kahneman+peak+end+rule

Memory as Reconstruction Bartlett, F.C. (1932). Remembering: A study in experimental and social psychology. Cambridge University Press. scholar.google.com/scholar?q=bartlett+remembering+reconstruction

Chunking Chase, W.G., & Simon, H.A. (1973). Perception in chess. Cognitive Psychology, 4(1), 55–81. scholar.google.com/scholar?q=chase+simon+chunking+chess

Schema Theory Bartlett, F.C. (1932). Remembering: A study in experimental and social psychology. Cambridge University Press. Anderson, R.C., & Pearson, P.D. (1984). A schema-theoretic view of basic processes in reading comprehension. scholar.google.com/scholar?q=schema+theory+memory+anderson

Primacy and Recency Effects Murdock, B.B. (1962). The serial position effect of free recall. Journal of Experimental Psychology, 64(5), 482–488. scholar.google.com/scholar?q=murdock+serial+position+effect+free+recall

Peak End Rule applied to evaluation and judgment Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux. amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555

Script to screen translation and structural stability McKee, R. (1997). Story: Substance, Structure, Style and the Principles of Screenwriting. HarperCollins. scholar.google.com/scholar?q=mckee+story+structure+screenwriting

Field, S. (1979). Screenplay: The Foundations of Screenwriting. Dell Publishing. scholar.google.com/scholar?q=syd+field+screenplay+structure

Multimodal processing and film comprehension Magliano, J.P., & Zacks, J.M. (2011). The impact of continuity editing in narrative film on event segmentation. Cognitive Science, 35(8), 1489–1517. scholar.google.com/scholar?q=magliano+zacks+continuity+editing+event+segmentation

Audience memory for film versus text Zwaan, R.A. (1994). Effect of genre expectations on text comprehension. Journal of Experimental Psychology: Learning, Memory, and Cognition, 20(4), 920–933. scholar.google.com/scholar?q=zwaan+genre+expectations+text+comprehension

Vonnegut's Story Shapes storytellingedge.substack.com/p/the-simple-shapes-of-great-stories

The original research paper confirming Vonnegut's theory arxiv.org/pdf/1606.07772.pdf

Multimodal encoding and drawing Referenced in the Storytelling Edge piece above. For deeper reading: scholar.google.com/scholar?q=multimodal+encoding+motor+cortex+memory

Kurt Vonnegut's original Shapes of Stories lecture youtube.com/watch?v=oP3c1h8v2ZQ