Screenwriters use two different kinds of tool: Search tools for finding the story and Build tools for assembling the script. Here is what working writers actually use for each, and why mixing them up causes the blank page.

Category
Screenwriting
Author

Justkay
Documentary Filmmaker & Founder at Storyflow
Topics
2026-07-26
•
23 min read
•
ScreenwritingTable of Contents
Screenwriters use two distinct sets of tools, and confusing them is the most common cause of a stalled script. For finding the story (research, character, structure, the thing the film is actually about) writers use index cards, corkboards, mind maps, and visual canvases such as Storyflow, Milanote, and Miro, plus notebooks and Scrivener. For building the script once the story is found, writers use dedicated screenwriting software: Final Draft, Fade In, Highland, WriterDuet, and Arc Studio. The planning half is where most writers are underserved, because they own a Build tool and keep trying to do Search work inside it. That distinction is the whole answer, and it is worth naming properly. Screenwriters do not have a writing problem. They have a Search problem that they keep trying to solve with Build tools. A screenwriting app is a magnificent instrument for laying track once you know where the train is going. It is a hostile place to figure out where the train is going, because every feature in it assumes you already decided. I have run development and pre-production on documentary and branded work for years, and the pattern is consistent enough to be boring: the writers who stall are almost never short on craft. They are sitting in Final Draft on page one, in a tool whose every affordance says "type the scene," trying to answer a question ("what is this actually about") that no scene-typing tool was built to hold.
Full disclosure: Storyflow is our own product, so weigh its placement here with the skepticism you would apply to any tool a company recommends on its own blog. We deliberately do not rank it first: index cards remain the most-used story planning tool in the profession, and Storyflow does not format screenplays at all, so it cannot be the tool a script is written in. Final Draft, Fade In, and Highland own that half outright, and this piece says so.
Screenwriting splits into two jobs. These are the tools writers actually reach for in each, and the one thing each is best at.
| Tool | Best For | AI Features | Price |
|---|---|---|---|
| Index cards | Search: beat order by hand | None | A few dollars |
| Storyflow | Search: one AI-readable board | Reads the whole board | $7.99 mo annual (free plan late 2026) |
| Scrivener | Search and Build in one project | None | One-time licence |
| Final Draft | Build: production formatting | Minimal | One-time licence |
Every screenwriter's process splits into two modes that feel similar and behave nothing alike.
The Search is the open phase. You are gathering research, testing premises, working out who the protagonist is and what they want, arguing with the structure, and throwing away four versions of act two. The work is nonlinear, spatial, and full of dead ends you need to keep visible in case they turn out to matter. Success in the Search looks like a decision: this is the story.
The Build is the closed phase. The story is decided. Now it becomes a formatted screenplay with sluglines, action, and dialogue, at industry-standard margins, with revision colors and locked pages if it is going into production. Success in the Build looks like a document.
The tools split along the same line, and they split hard.
| The Search | The Build | |
|---|---|---|
**The job** | Find what the story is | Assemble what the story will be |
**Shape of the work** | Nonlinear, spatial, revisable | Linear, sequential, formatted |
**What you need to see** | Everything at once | One page at a time |
**Failure mode** | Endless circling, no decision | Perfect formatting of a broken story |
**Typical tools** | Index cards, corkboard, mind maps, canvases, Scrivener, notebooks | Final Draft, Fade In, Highland, WriterDuet, Arc Studio |
**What AI is good for** | Gap-finding, pressure-testing, alternatives | Very little worth using |
The reason this framing earns its place is that it predicts the failure. A writer who owns only a Build tool will experience the Search as a personal failing (writer's block, lack of discipline) when it is mostly a tooling mismatch. A writer who owns only Search tools will produce beautiful boards and never finish a script.
Every tool a screenwriter uses sits on one side of that line or straddles it badly. This is the whole field in one table, with the property that actually decides the purchase: whether it formats a screenplay to industry standard.
| Tool | Half | Formats a screenplay | Real-time collaboration | Pricing shape |
|---|---|---|---|---|
**Index cards** | Search | No | In one room only | A few dollars |
**Storyflow** | Search | No | Yes, shared boards | Plus from $7.99/mo annual |
**Milanote** | Search | No | Yes | Free tier, paid above |
**Miro** | Search | No | Yes, strongest for rooms | Free 3 boards, Starter $8/user/mo |
**MindMeister / XMind** | Search, early | No | Varies | Free tiers, paid above |
**Scrivener** | Both, hybrid | Yes, via compile | No | One-time licence |
**Final Draft** | Build | Yes, the standard | Limited | One-time licence |
**Fade In** | Build | Yes | Limited | One-time licence, lower |
**Highland** | Build | Yes | No | Free tier, paid above |
**WriterDuet** | Build | Yes | Yes, built around it | Free tier, paid above |
**Arc Studio** | Build, leaning hybrid | Yes | Yes | Free tier, paid above |
Two things fall out of the table that are worth saying plainly. First, no tool is genuinely excellent at both halves, and the ones that try (Scrivener, Arc Studio) are hybrids that are strong on one side and adequate on the other. Second, the Build column is a solved problem: the differences between Final Draft, Fade In, and WriterDuet are real but small, and none of them will change whether you finish. The Search column is where the variance lives, and it is the column most writers have never deliberately chosen anything in.

A screenplay beat sheet on the Storyflow canvas, with act turns, character notes, and research sitting beside the beats
Put the research, the beats, and the structure on one canvas, and let the AI read the whole board when you ask what act two is missing. Then take the decided story into your screenwriting app and write it.

Still the most-used story planning tool in the profession, and it is not close. A scene or beat per card, laid out on a table or pinned to a wall, physically rearranged until the order feels right.
They persist because they get three things right that software struggles with: you see the whole story at once, you rearrange with your hands at the speed of thought, and the constraint of a small card forces you to state the beat in one line instead of hiding behind description. The costs are equally real. Cards do not travel, they do not back up, they cannot be shared with a collaborator in another city, and a cat or an open window can end your week.
The direct digital descendant, and the fastest-growing category in story planning. This includes Storyflow, Milanote, Miro, and the corkboard views inside Scrivener and Final Draft.
The pitch is straightforward: cards you can rearrange, on a surface big enough to hold the research beside the structure, that syncs and shares. A canvas suits story planning specifically because a story is a shape before it is a sequence. Act breaks, the midpoint, the gap where act two sags, a character who vanishes for forty pages: these are spatial facts about a story, and they are visible on a canvas and invisible in a document, where everything looks equally like a paragraph.
Where Storyflow fits in this category is narrow and worth stating precisely. It is a visual canvas whose AI reads the whole board you are working on, plus up to one Tactic and three Documents you `@`-mention, which means it can respond to the actual structure in front of you rather than to a prompt describing it. In practice that means asking what act two is missing while the beats, the character notes, and the research are all on the board being read, instead of pasting a summary into a chat window that cannot see any of it. Its Story blueprints library includes structural templates (Hero's Journey and AIDA among them) for writers who want a scaffold rather than a blank canvas.
Where Storyflow is the wrong tool: it does not format screenplays, so it cannot be the place the script is written. It is cloud-only, which rules it out if you need local-first files for confidentiality. Its blueprint library is broader than it is deep on niche genre convention, so a writer working inside a very specific format (a procedural teleplay structure, say) will find less prebuilt scaffolding than a screenwriting-specific tool offers. And a writer who genuinely thinks in prose, not in space, will find a canvas to be overhead rather than help.
Used mostly at the earliest stage, when the question is still "what is this about" rather than "what happens." Tools like MindMeister, XMind, and Coggle branch a central idea outward, which suits theme and character work better than plot, because plot eventually needs an order and a mind map resists order by design.
Plenty of writers use mind mapping for a single session at the start and never return to it, which is a legitimate use and not a failure of the tool.
The classic hybrid, and still the strongest single-application answer. Scrivener holds research documents, a corkboard, an outliner, and the draft in one project, and it can compile to screenplay format at the end. Writers who want everything in one place and are willing to climb a genuinely steep learning curve stay in Scrivener for decades.
Its weakness for screenwriting specifically is that its formatting and collaboration are not competitive with dedicated screenwriting software once a script goes into production, which is why many Scrivener users still hand off to Final Draft at the end.
Worth naming because the honest answer to "what do screenwriters use" includes paper. A large number of working writers do their earliest thinking longhand and only open a machine once there is something to type. No tool roundup should pretend otherwise.
The industry standard, and the reason is boring and decisive: it is what production expects. Revision colors, locked pages, production reports, and the file format assistants and line producers already know. Its Beat Board and Story Map are real planning features, and they are thin compared to a dedicated Search tool, which is a reasonable trade for a product whose actual job is formatting fidelity.
The most common answer for writers who want Final Draft's competence without Final Draft's price. Clean, fast, well-maintained, reads and writes the formats production needs.
Favored by writers who like a plain-text, distraction-free surface. Highland's outline mode and its sparse interface suit people who find Final Draft cluttered. It is a writing tool with light planning features, not a planning tool.
Both lead with real-time collaboration, which matters for writing partners and for rooms. Arc Studio in particular pushes further into structure and beat planning than most Build tools, which makes it the closest thing to a genuine hybrid in the Build category.
The handoff is the part most articles skip, and it is where the workflow succeeds or falls apart.
A working sequence looks roughly like this:
The discipline that matters is step 5. Writers who never leave the Search tool produce boards instead of scripts. Writers who skip to step 5 on day one produce perfectly formatted scripts with nothing underneath them.
A Search tool is a surface. What goes on it is a structure, and the structure you choose changes what the tool needs to do. Four are in common professional use, and they are not interchangeable.
Save the Cat, fifteen beats. Blake Snyder's beat sheet with named beats at named page numbers: opening image, catalyst around page twelve, break into two around twenty-five, midpoint at fifty-five, all is lost at seventy-five. Its reputation among writers is mixed and its usefulness is not really in dispute: it is the most teachable structure available and it will get a first-timer to a complete, functioning draft. The criticism, which is fair, is that fifteen fixed beats produce films that feel like each other. Use it as a diagnostic more than a blueprint: when act two sags, checking your midpoint against Snyder's will usually tell you why.
The sequence approach, eight sequences. The film as eight roughly fifteen-minute units, each with its own tension and its own small resolution. This is the structure that helps most with the problem writers actually have, because act two is not one problem, it is four sequences, and "act two sags" is nearly always "sequence four has no question of its own". Harder to teach and considerably better at diagnosing a specific broken stretch.
The Hero's Journey. Campbell by way of Vogler: ordinary world, call, refusal, mentor, threshold, trials, ordeal, reward, road back, resurrection, return. It is a character structure wearing a plot structure's clothes, and it works best when the story is genuinely about transformation and badly when it is not. Forcing a heist film or an ensemble drama through it produces a strained shape.
The story circle. Dan Harmon's eight-step compression of the same idea: you, need, go, search, find, take, return, change. Its advantage is that it is small enough to hold in your head and fast enough to run on a single scene, a subplot, or a whole season. Many television writers use it at multiple scales at once.
The practical point for tooling: a fixed-beat structure like Save the Cat wants a template with labelled slots, which is what Final Draft's Beat Board and most story blueprint libraries provide. The sequence approach and the story circle want an open surface, because the units are relational rather than positional and you are constantly asking what a sequence is doing relative to its neighbours. If you plan in sequences and your tool only offers a fifteen-slot template, the tool is fighting you.
Storyflow's blueprint library includes structural scaffolds (Hero's Journey and AIDA among the 200-plus on Plus, Pro, and Max) for writers who want a frame rather than a blank canvas, and the canvas itself suits the sequence approach for the reason above. It is worth being straight that a screenwriting-specific tool will have deeper genre-specific scaffolding than a general creative canvas does.
A writer has a premise and eleven weeks: a nurse in a rural hospital discovers her hospital has been quietly refusing a category of patient, and reporting it will end her career in the only town she can afford to live in.
Weeks one to three, gathering. Interviews with two nurses, three long articles on rural hospital economics, a documentary, and photographs of the actual region. All of it goes on one board, unordered. Three character notes appear early and are wrong. The premise sentence gets rewritten nine times, which is the real work of this stage and looks like nothing from the outside.
Week four, the decision. The story stops being about the hospital and becomes about the sister-in-law who runs the ward. That is the Search succeeding, and it happened because two things sat next to each other on the board: an interview quote about small-town loyalty and a note about who signs off on admissions. Neither meant anything alone.
Weeks five and six, beating it out. One line per card, forty-one cards. Laid out in eight sequences rather than three acts, because the sag was already visible in the draft outline and sequences locate a sag where acts only report one. Sequence five has two cards. That is the finding, and it is worth more than any note anyone gave.
Week seven, the pressure test. Everything is on the board, so the questions are answerable against the actual structure: which character disappears longest, which two beats make the same argument, where the protagonist stops driving the story. The answers were that the sister-in-law vanishes for thirty pages in the middle, and that beats nineteen and twenty-four are both "she realises she is alone in this". Both are structural facts about a shape, and both were invisible in the outline document the writer had been reading for six weeks.
Weeks eight to eleven, the Build. Final Draft, beats to scenes, ninety-eight pages. The board stays open on the second monitor, and gets opened properly twice: once around page fifty-five when the midpoint does not land, and once at page eighty when the ending needs the sister-in-law to have done something in act two that she has not done.
The honest accounting. Nothing here was generated. The AI was used twice, both times in week seven, both times to ask what was missing, and both times the useful output was a question rather than an answer. The premise, the sister-in-law, the eight-sequence choice, and every line of dialogue were the writer's. What the tooling did was make a structural problem visible in week seven instead of week ten, which is the difference between a fix and a rewrite.
AI's usefulness in screenwriting maps almost exactly onto the Search and the Build divide.
In the Search, it is genuinely useful, for a specific and unglamorous reason: it is good at noticing absences. Given a full set of beats, a model will reliably flag that your antagonist has no scene in act one, that two beats are making the same point, or that the midpoint is not actually a reversal. That is real work, and it is work a writer staring at their own outline for six weeks is badly positioned to do.
It is also useful for volume during divergence: twenty alternative versions of an inciting incident, of which nineteen are useless and one reframes the problem.
In the Build, it is mostly not worth using. AI dialogue is competent, generic, and unshootable, which is the worst combination because it is good enough to keep and bad enough to hurt. The reason is structural rather than a temporary limitation: dialogue carries character voice, and voice is precisely the thing a model trained on everyone's writing averages away.
The dividing line is that AI is good at questions about the story and bad at the story itself. Keep it in the Search. The judgment stays yours.
If you are starting out and want one tool: Scrivener. It covers both halves adequately and will not need replacing for years. Accept the learning curve.
If you already own screenwriting software and keep stalling: you are missing a Search tool, not a better Build tool. Add index cards or a visual canvas before you consider switching scriptwriting apps.
If you think spatially and your projects carry heavy research: a visual canvas for the Search, a dedicated screenwriting app for the Build. This is the two-tool setup most working writers converge on.
If you write with a partner or in a room: WriterDuet or Arc Studio for the Build, and any shared canvas for the Search.
If your script is going into production: Final Draft for the Build, whatever you like for the Search. This is not a quality judgment, it is a compatibility one.
Feature planning and television planning are different jobs, and a writer moving between them with the same setup will feel the friction immediately.
The unit is the season, not the script. A feature is one shape. A season is a shape made of shapes, with an arc per episode, an arc per character across the run, and a season arc that has to pay off at ten or eight or six hours. That is three overlapping structures, and it is the specific reason television rooms use walls rather than documents: you need all three visible simultaneously, and no document shows you two structures at once.
The board is literally a board. Most rooms still run on a physical wall with index cards in rows, one row per episode, columns for acts, plus a separate strand tracking each character's arc down the season. Digital equivalents exist and the good ones are the ones that preserve the grid, because the grid is doing the thinking: a character strand with a gap of four episodes is visible as white space and invisible in any other representation.
Beat counts are dictated by format. A network hour with commercial breaks has a fixed act structure with an act-out before every break, and those act-outs are not optional beats, they are contractual. Streaming has no breaks and correspondingly weaker act discipline, which is a freedom that regularly produces episodes with no shape. If you are writing streaming, imposing act breaks you do not technically need is usually the right call.
What to use. Arc Studio pushes furthest into structure among the Build tools and handles multi-episode planning better than Final Draft does. WriterDuet is the strongest choice when the room is remote, because it was built around simultaneous editing rather than having it added later. For the Search half, any canvas that holds a real grid works, and physical cards on a wall still beat all of it when everyone is in the same room, which is the honest reason writers' rooms kept meeting in person long after they technically had to.
The pattern from the feature process holds: decide the season shape in a spatial tool, then hand each episode to the Build tool. Writers who try to work out a season inside screenwriting software end up with eight well-formatted scripts that do not add up to a season.
Screenwriters use two kinds of tool because screenwriting is two kinds of work. The Search finds the story and runs on cards, canvases, mind maps, and notebooks. The Build assembles the script and runs on Final Draft, Fade In, Highland, WriterDuet, and Arc Studio. Almost every list that answers this question covers only the Build half, which is why a writer can own excellent software and still not get past page one.
Screenwriters do not have a writing problem. They have a Search problem that they keep trying to solve with Build tools. Fix the Search half and the Build half gets dramatically easier, because you are no longer asking a formatting tool to help you decide what the film is about.
For writing the script, the industry standard is Final Draft, with Fade In, Highland, WriterDuet, and Arc Studio as common alternatives. For planning the story before the script, most professionals use something entirely different: index cards, a corkboard, a visual canvas such as Storyflow or Milanote, or Scrivener. The planning tool and the writing tool are usually not the same product.
Yes, and they remain the single most common story planning tool in the profession. One beat per card, rearranged by hand until the order works. They persist because you can see the whole story at once and reorder it at the speed of thought. The limitations are that cards do not travel, back up, or share with a remote collaborator, which is why digital corkboards and canvases exist.
There is no single best tool, because planning and writing are different jobs. For planning specifically, the strongest options are index cards for pure simplicity, Scrivener for an all-in-one project, and a visual canvas such as Storyflow when you want research, beats, and structure on one surface with AI that can read the whole board. Choose based on whether you think in space or in prose.
You can. Final Draft includes a Beat Board and Story Map for exactly this. They are real features and they are deliberately light, because Final Draft's core job is formatting fidelity for production. Writers doing heavy development work usually find them thin and plan somewhere else, then bring the decided structure into Final Draft to write.
Scrivener is very good for the research and planning half and adequate for the writing half. It holds research, corkboard, outliner, and draft in one project and compiles to screenplay format. The trade-offs are a steep learning curve and formatting and collaboration that are not competitive with dedicated screenwriting software once a script reaches production, so many Scrivener users hand off to Final Draft at the end.
Fade In is the most common alternative, offering comparable competence at a lower price. Highland suits writers who prefer a plain-text, minimal surface. WriterDuet and Arc Studio lead on real-time collaboration for writing partners and rooms. Arc Studio also pushes furthest into beat and structure planning among the Build tools.
Most keep research separate from the script. Common approaches are a Scrivener project's research folder, a visual canvas where articles, images, and interview notes sit beside the developing structure, or a dedicated notes app such as Notion or Obsidian. The requirement that matters is being able to see research next to the story decisions it is supposed to inform, rather than in a folder you never reopen.
Most working screenwriters outline, and the ones who do not usually have a structure in their head that they simply have not written down. The practical argument is cost: restructuring a set of index cards takes an afternoon, and restructuring a finished draft takes weeks. Outlining is where structural mistakes are cheap to fix.
AI can produce screenplay-formatted text, and it is not usable as-is. Its dialogue is competent and generic, which is the worst combination, because it is good enough to keep and bad enough to weaken the script. AI is genuinely useful earlier, for pressure-testing structure, finding gaps in a beat sheet, and generating alternatives during the search phase. Keep it on the questions, not on the pages.
A beat sheet lists the story's essential turning points, usually one line each, in order, focused on structure. An outline is typically longer and more detailed, describing scenes and sometimes their content. Writers often build the beat sheet first to confirm the shape holds, then expand it into an outline before drafting.
There is no standard, and the useful test is not time but decidedness: you are ready to draft when you can state what the film is about in one sentence, name what the protagonist wants and what stands in the way, and lay out the turning points in order without arguing with yourself. Writers who draft before that point tend to discover the problem around page sixty.
Not necessarily. Scrivener covers both adequately, and it is the right answer for writers who want one application. Most working writers still end up with two, because the tool that is best at holding an unresolved story in view is rarely the tool that is best at producing a production-ready document. If your current setup is one Build tool and you keep stalling, adding a Search tool is usually the higher-leverage change.
Save the Cat's fifteen beats is the most teachable and will reliably get a first-timer to a complete draft, at the cost of a shape that can feel familiar. The eight-sequence approach is better at diagnosing a specific broken stretch, because it treats act two as four units with their own questions rather than as one long problem. The Hero's Journey suits stories genuinely about transformation and strains when forced onto stories that are not. Pick the one that matches your actual difficulty: use fifteen beats if you cannot finish, and sequences if you finish and act two sags.
On a grid, almost universally: one row per episode, columns for acts, and separate strands tracking each character's arc across the run. The reason is that a season is three overlapping structures (episode arc, character arc, season arc) and a grid is the only representation that shows more than one at a time. Arc Studio handles multi-episode structure better than Final Draft among the Build tools, WriterDuet is the strongest option for a remote room, and physical cards on a wall still win when everyone is in the same building.
No, and this is one of the few areas where the free options are genuinely competitive. Index cards cost a few dollars, Highland and WriterDuet both have usable free tiers for the Build half, and most visual canvases including Storyflow have a free plan that covers a single project comfortably. Spend money on the Build tool only when a production requires a specific file format, which in practice means Final Draft, and spend it on a Search tool only after you have confirmed with cards that you think spatially.
For a feature, somewhere between four and eight weeks of real work is typical for writers who plan deliberately, and the variance is mostly in how much research the story needs rather than in how fast anyone thinks. The signal that planning is finished is not a feeling of confidence, which never arrives. It is that you can state the story in one sentence, name what changes in the protagonist, and lay out the beats without hitting a stretch where you do not know what happens. If a run of cards is blank, planning is not done, and starting the draft will not fill them in.
It can produce something formatted like a screenplay, and that is a different claim. The failure is specific and structural rather than a temporary limitation: dialogue carries character voice, and a model trained on everyone's writing averages voice away, which produces lines that are competent, generic, and unshootable. That combination is the worst one, because it is good enough to keep and bad enough to damage the script. The genuinely useful application is upstream, asking what a structure is missing, and that is worth doing.
Start your next script, novel, or world from a ready-made Storyflow board instead of an empty page. The AI reads the whole canvas, so every suggestion is grounded in your story.
A visual AI workspace where every feature lives inside one canvas. No tab-switching, no context lost.
Build your entire board from a single message
Type what you need in the AI chat at the bottom of your canvas. The AI adds cards, headings, and structure directly onto your board.
Use expert frameworks as AI context
Type @ in the AI chat and choose any Tactic. The AI tailors every response to that framework instead of giving generic advice.
Turn your board into a mind map in seconds
Ask the AI to restructure your canvas as a mindmap. It connects your ideas into a visual hierarchy so you can see how everything relates.
Storyflow actually began as a personal tool while working on creative and research projects.
We kept running into the same problem: ideas were scattered everywhere: notes, documents, and whiteboards.
Nothing helped us see how everything connected.
So we started building a workspace designed around how ideas actually grow.
→ Read how Storyflow was created
Justkay
Documentary Filmmaker & Founder at Storyflow
Published: 2026-07-26
Transform your creative workflow with AI-powered tools. Generate ideas, create content, and boost your productivity in minutes instead of hours.