A screenplay is not a document. It is a database of scenes.


I lost a forty-page outline once. Forty pages. Two weeks of work. Gone because I had been writing in the wrong unit.
I had been writing a screenplay in pages. Industry-standard format, scene headings, action lines, dialogue, all of it. Forty pages that I thought were the work. They were not the work. They were what the work looked like when I printed it.
A scene is the unit. A card is the unit. A page is what you get when you print a unit onto paper. I had confused the artifact for the thing.
Why we measure the wrong thing
We measure screenplays in pages because that is what the camera sees: a page equals about a minute of screen time. So pages feel like progress.
Pages are a coincidence. They are a unit of measurement that happens to be useful for production scheduling, not for writing. A page is what a scene looks like after you have one and you print it.
When you write in pages, you think in pages. "I wrote eight pages today" sounds like work. It is not work. It is layout.
The scene is the constraint
A scene is one thing that happens. The confrontation. The reveal. The lie that unravels. It has a beginning and an end that are not negotiable.
Once you commit to writing in scenes, the constraint tightens. You cannot smuggle two scenes into one and call it one page. You cannot pretend a transition is a scene. You cannot hide weak writing behind page count.
The constraint is the gift. Every writing problem I ever had dissolved when I asked: what is the scene doing? Not "how many pages does this run" — what is the scene doing?
One scene, one card, one decision
A screenplay organized around scenes rather than pages is not a technical choice. It is a storytelling choice.
When every scene is its own block — discrete, movable, alive with its own metadata — the tool aligns with how stories are actually made. You can see the shape of your entire film at a glance. You can drag a card from act three into act one and the structure holds. You can drop in the scene you know clearly first and write the connective tissue later.
Click a card, you are inside that scene. Change the synopsis on the card, the scene reflects it. There is no syncing, no exporting your outline into your screenplay, no managing two documents.
Pages are the byproduct, not the goal
When scenes are the unit, the screenplay builds its own memory as you write it. Which characters are in this scene. Which act it belongs to. Whether it is draft or revised. None of this lives separately from the screenplay. It lives inside each scene.
Page count still exists. It is still useful for production scheduling and budget conversations. But the primary measure of progress is scenes, not pages, because scenes are what you are actually building.
When you finish writing a scene, you have finished a scene. Not a fraction of a page. Not a chunk of text. A scene.
Why this works better than a document
A document gives you everything or nothing. A database of scenes gives you exactly what you ask for.
Export every scene a specific character appears in. Pull a complete dialogue report. Generate a scene matrix showing which characters appear in which scenes across your entire screenplay. None of this is possible when your screenplay is just a document.
For writers who think non-linearly — and that is most writers, even the ones who pretend otherwise — this is not a small convenience. It is a fundamentally different relationship with the work.
The shuffle is the point
Rearranging is where scene-centric writing earns its keep. In a document, moving scenes means cutting and pasting text and hoping the formatting survives. In a scene-based tool, you drag an index card. The scene moves. Everything stays intact — characters, synopsis, notes, metadata.
For writers who discover their structure through the act of writing rather than before it, this is not a small convenience either. The structure holds regardless of the order you wrote it in.
Try it with NoteDex
If you have ever lost a screenplay — or a project, or a course, or a quarter — to the wrong unit, the fix is the same. The page is not the work. The card is not the page. The card is the constraint.
NoteDex treats every idea the same way: one card, one scene, one decision. The card carries its metadata, its characters, its notes, its place in the structure. You can shuffle the cards. You can see the shape. You can find any one of them with one tap.
That is the entire pitch. Not "unlock your potential." Not "revolutionize your workflow." The card is the constraint. The constraint is the tool.
What to do this week
Take one project you have been writing in pages. Break it into scenes. Give every scene a one-line headline that names what the scene does, not what happens in it. "She finds out he lied" — not "She reads the letter."
Put each headline on a card. Spread them on a table. Look at the shape. That shape is your screenplay. The pages were never the screenplay. The cards were.



