Final Draft for a planning-to-script workflow. Milanote for research and character context. Miro for collaborative cards. Storyflow for an evolving development canvas. Choose the place your thinking belongs, then inspect the order of your own beats.
There is no single planning method every screenwriter uses. This guide compares official feature documentation reviewed October 5, 2026, rather than claiming to have tested these products on a production. Separate the work of finding a story from formatting and delivering its screenplay.
Final Draft
Choose desktop Final Draft 13 when the outline should feed the script.
The documented workflow runs from Beat Board to Outline Editor to script pages. Arrange beats, place them in timeline lanes, refine their positions, and send the outline into the script. Outline paragraphs can then become screenplay elements or be hidden while you draft.
The product edition matters. Final Draft's January 2026 support article explicitly says Final Draft Writer does not include Beat Board or Outline Editor; those features require desktop Final Draft 13. Do not choose a browser writing product on the assumption that the desktop planning workspace comes with it.
Ask first: do you need the plan inside the screenplay editor, and are you using the edition that actually has the planning tools?
Choose it when research, characters and references shape the outline.
Milanote's writing page describes combining text, images and video, mapping character connections, collecting research with a source-saving web clipper, and rearranging story structure with movable cards. It presents the workspace as a companion to your writing software.
That separation can be useful: the research board stays spacious while the draft becomes linear. Give each sequence a clear purpose and keep the reference beside the reason you collected it. Before committing, check how you will move the useful outline into the editor where you actually write; a visual board is not evidence of screenplay pagination or revision management.
Ask first: is your problem finding and organizing material, or delivering formatted screenplay pages?
Miro's sticky-note documentation supports adding and arranging notes, bulk entry, pasting spreadsheet cells as stickies, tags and connections. Text can be exported to CSV. Commenters can leave comments but cannot add sticky notes; contributors who need to move or create cards need the appropriate editing access.
For a writing room, this means the board can hold alternatives and relationships without forcing a particular beat-sheet template. Establish what a card represents: a scene, a revelation or a turning point. Mixed units quickly make a board harder to discuss. Plan the handoff to the screenplay document separately instead of treating whiteboard positions as screenplay pages.
Ask first: will your collaborators edit cards, or review a plan someone else owns?
Choose it to keep the changing story beside its supporting material.
Storyflow's beat-board page describes one card per beat, movable and rewritable on an infinite canvas with research, characters and references nearby. It explicitly distinguishes this planning workspace from screenplay software: it does not format or paginate scripts, handle revision colors, or export a Final Draft FDX file.
That is a useful boundary for choosing a workflow. Develop the story on the board, then write in a screenplay editor while the plan remains available. Do not expect the planning board to become a formatted script automatically.
Access: current pricing states paid-only early access, free invited collaboration today, and standalone Free planned before the end of 2026. Broad free-start marketing conflicts with that explicit availability. This distinction was checked October 5, 2026; signup was not tested.
Try moving an event before its setup. The scene may still make sense in the story world, but the audience may not have the information you intended them to have. A planning board is useful when the cards carry both the event and the reason for its position.
Separate event order from reveal order
A flashback is an intentional difference between chronology and presentation. The tool below checks only the earlier-reveal rules you enter. It does not assume the order of events in the story world or impose a screenplay formula.
Name the dependency
If a later choice relies on the audience knowing a promise, record that earlier beat's ID. A connection without a reason is easy to preserve after it stops being useful.
Keep room for revision
A conflict is a question for the writer, not a quality score. You can revise the rule, move the beat, or deliberately keep the uncertainty while you explore another version.
A mystery reveal
The discovery should follow the clue only if you want the audience to recognize the connection immediately. Enter that rule explicitly instead of asking a tool to invent it.
Keep five planning records connected to the draft.
A screenplay plan gives a writer somewhere to inspect the story before committing to pages. It can include a beat sheet, movable scene cards, character and relationship notes, a prose treatment, and a rewrite record. Those documents describe different levels of the same work; maintaining their connection matters more than choosing an elaborate template.
A beat sheet names major changes in the story. A scene card identifies a more specific dramatic unit: who acts, what pressure they face, and what changes. Character notes explain choices rather than only supplying biography. A treatment tests whether the story reads as a connected sequence in prose. A rewrite record identifies how the actual draft differs from the intended plan and which changes remain open.
The screenplay editor carries formatted pages and the production-facing file. A planning board may carry research, alternate paths, and a structural overview beside it. Some products connect those views directly; others require a deliberate export or maintained link. Neither arrangement is universally better. The useful question is what happens when a card or scene changes.
If the draft introduces a different midpoint while the board retains the old one, a later structural review can diagnose the wrong story. Keep the source draft revision explicit. Update the plan from the pages the reader actually received, retaining the earlier baseline when it helps explain the change.
Separate story chronology from audience reveal order. A flashback, withheld identity, or delayed explanation can intentionally place information out of chronological sequence. The local tool checks only your explicit earlier-reveal rules. It cannot infer narrative meaning, emotional credibility, or what a reader should know.
Six starting points, with different handoffs.
Tool
Documented planning route
Trial question
Final Draft
Desktop Beat Board through Outline Editor to screenplay pages.
Are you using the edition with these features, and does the outline-to-page workflow fit your writing process?
Milanote
Movable story material, research, visual references, and character context alongside writing software.
How will the chosen outline reach the actual script, and who keeps it current after changes?
Miro
Collaborative sticky notes and connections, with current contextual Sidekicks creation in supported formats.
Can the real collaborators create or move cards, and what source material governs generated content?
Storyflow
A visual beat board beside supporting story material, separate from screenplay formatting.
Can the current draft, structure, character decisions, and review notes remain identifiable without implying FDX export?
Notion
Maintained pages and databases, with current Agent assistance for creating and editing those records.
Does your story bible need structured retrieval, and how is the episode plan connected to it?
Arc Studio
An integrated Plot Board, outline, and script workflow with documented outline export routes.
How do beats connect to the actual scenes, and which account features support your collaborators and revisions?
Final Draft’s current support article explicitly distinguishes its Writer product from desktop planning: Writer does not include Beat Board or Outline Editor. Its outline guidance describes the desktop bridge to pages. Check the actual edition before buying a workflow that the browser product does not provide. Writer limitation and desktop outline guidance.
Current Notion Agent can help create and edit pages and databases; a story bible need not be described as necessarily built entirely by hand. Current Miro assistance also goes beyond an older summary-only description. Generated structure still requires a writer to review invented or unsupported choices. Notion Agent, Miro Sidekicks, and Arc Studio Plot Board.
This is a documentation-based comparison, not a ranking of story quality or writing speed. Keep product capability, editorial preference, and actual tested handoff distinct.
Compare five rounds using your actual story.
Round
Useful test
What can break
Beat sheet
Name the major changes and uncertainty under the structure you intend to use.
A filled template disguises an unclear causal sequence.
Scene cards
Move an actual scene and inspect what its new position requires the audience to know.
The board’s order changes while the script or reveal logic remains stale.
Characters
Connect desire, conflict, refusal, and change to specific story decisions.
Biographical detail never affects the plot or its relationships.
Treatment
Read the selected story as connected prose rather than isolated card labels.
A transition that seemed clear in the grid becomes vague on the page.
Rewrite
Compare the actual received draft with the baseline plan and proposed changes.
Notes refer to another revision or the board represents only the writer’s original intention.
Include a deliberate change during the trial. Move the discovery before the clue, or replace a character’s reason for refusing help. Inspect affected records and ask your reader which version they are reviewing. A card interface can make movement easy without making the resulting story coherent.
The relationship checker below offers a narrow test: whether your chosen order satisfies the supplied prerequisite IDs and whether those rules contain a cycle. A compatible graph order is a mathematical possibility. It is not a recommendation for where the most dramatic reveal belongs.
Choose a useful structure without letting it write the story.
Three acts provide a broad way to discuss setup, developing pressure, and resolution. Save the Cat uses a named fifteen-beat framework. The Story Circle offers an eight-part lens on character movement. The Hero’s Journey uses a different stage-based perspective, while sequence approaches group the story into larger dramatic units. These are ways to inspect work rather than universal proof that a screenplay succeeds.
Pick a lens that makes the current problem easier to see and explain it to the reader. You can revise the framework when it ceases to help. A template’s empty slot is a question, not an obligation to invent an event. Page targets and a predetermined scene count should not override the particular story’s action, rhythm, or intended form. The framework owner’s overview of Save the Cat beat sheets.
Scrivener, WriterDuet, Plottr, and paper
Scrivener’s corkboard associates synopsis cards with project sections, and moving them can rearrange the manuscript. WriterDuet’s card documentation similarly says card order changes the corresponding document content. Those are meaningful handoff mechanics, distinct from rearranging independent whiteboard notes. Inspect the actual file and mode before assuming the same behavior in every product.
Plottr’s timeline organizes chapters, plotlines, and scene cards as a visual planning hub. Check the export or connection to the software where you deliver the screenplay. Physical index cards can make a room’s story discussion immediate; preserve a recoverable record and label which arrangement is current before moving cards between versions.
A fictional thriller, from premise through a structural rewrite.
Night Crossing is a fictional contained feature about a ferry pilot who finds evidence of an unauthorized passenger during a night crossing. A demand to conceal the discovery conflicts with the pilot’s responsibility to protect the people aboard. One writer develops the project while a producer reads the plan. The initial intended scope is a feature-length thriller; exact page length remains a draft result, not a software prediction.
Premise and structure
Write the central want, obstacle, and cost before selecting software. Here the pilot wants to complete the crossing and expose what is happening, but each disclosure can put another passenger at risk. The plan uses a three-act lens to inspect how the pilot’s choices escalate that conflict. Research about vessel operation and plausible constraints remains separate from invented story details.
Create twelve provisional major beats and mark unresolved ones. Break them into fifty-two candidate scene cards only when that level of detail helps the story. These are example planning quantities, not a quota for every feature. Each card explains the action, relevant person, and what changes.
Characters and treatment
Develop four principal character records around wants, conflicts, refusals, and relationships. The pilot’s hesitation must affect actual choices; a detailed childhood biography is not a substitute. Link the passenger’s information and the opposing character’s pressure to the beats where they matter.
Write a prose treatment from the selected cards and check the transitions. A six-page working treatment can be appropriate for this fictional review, but agree the length and purpose with the recipient. The producer asks why the pilot trusts a passenger before seeing the evidence. Capture that question against the current plan and decide whether the scene, the earlier clue, or the intended ambiguity needs revision.
Stage
Owned record
Handoff check
Outline
Premise, provisional twelve beats, fifty-two candidate cards, character choices, and open questions.
The producer can identify the requested structural decision and the actual version.
Treatment review
Connected prose and the recorded trust-before-evidence question.
The proposed answer is reflected in the relevant cards and character decisions.
First draft
The screenplay in the selected editor and its source revision.
Formatted delivery is inspected separately from the board’s appearance.
Structural rewrite
The actual draft outline beside the previous baseline and proposed changes.
New scene order, reveal assumptions, and page revisions identify the same draft.
Bring the actual pages back
The written draft introduces the evidence later than intended and expands another sequence. Re-outline what exists instead of pretending the original plan still describes the screenplay. Preserve the previous board, identify the actual draft received, and link the proposed earlier-reveal rule to the specific clue and trust decision.
Use the chosen script application’s actual revision tools for pages. Use the board for the structural discussion. If assistance summarizes an attached draft, verify the extracted scene facts and whether the format is genuinely supported. Reading an FDX attachment and exporting a finished FDX screenplay are separate capabilities.
Final Draft or Arc Studio may connect outline and script through documented integrated workflows. Milanote or Miro can preserve visual story discussion with a deliberate page handoff. Storyflow can keep the developing plan and context together while the screenplay stays in its editor. These are illustrative routes, not a measured assertion that one product writes or reviews the story fastest.
Eight steps before and after page one.
State the premise. Identify who acts, what they want, what opposes them, and why the choice matters. Keep uncertainty visible.
Choose a working structural lens. Name the framework or custom approach so collaborators understand the level you are discussing.
Draft the major beats. Describe changes and consequences in your own words. Mark provisional answers.
Develop useful scene cards. Explain the action and change; avoid a fixed card-count target or breaking material into detail too early.
Connect characters to decisions. Check how desire, conflict, refusal, and relationships drive specific story turns.
Write connected treatment prose. Use it to inspect missing links and communicate the intended story at the recipient’s required level.
Review the identifiable plan. Ask a trusted reader a specific question and maintain notes against the current version.
Write, then reconcile. Draft in the appropriate application and bring the actual pages back into the structural record.
Planning is iterative. A writer may discover the premise through pages or research rather than finishing every step in order. Use the records to clarify the next decision, then update them as the story changes. A completed template is not a gate that proves the draft is ready.
Cost the actual writing team and choose by stage.
A solo writer may need one integrated application or a planning board beside a script editor. A four-person writing team should identify who creates cards, who edits pages, and who only reviews. An invitation can have different permissions and allowances from a paid editing account. Count the actual roles and current features rather than multiplying the entry price by four.
Compare one-time purchases, subscriptions, included collaboration, paid seat types, AI usage, and the billing period. Current edition details matter as much as nominal cost. Desktop Final Draft planning is not implied by a Writer subscription. A planning board’s price does not include every screenplay-editor feature the production may require.
Inspect free access and its limits through the actual account. Storyflow’s current pricing FAQ describes paid early access, a forthcoming standalone Free plan, and free invited collaboration today. Broader free-start marketing is not proof that a standalone account has launched. Current pricing FAQ.
For a feature writer developing a spec, emphasize the structural overview and a clean path to pages. For a pilot writer, distinguish episode structure from a searchable season bible. For a live writing room, trial actual multi-person editing and the room’s existing habits. For delivery to producers, confirm the requested format and revision requirements rather than assuming every recipient wants the same file.
At idea stage, loose research and alternatives may help. During structure, the beat-level view becomes useful. During scene development, inspect sequence and reveal order. During treatment or pitch work, the prose and presentation need to read clearly. During drafting, formatting and actual page behavior matter. During rewriting, use both the real page revision and the structural diagnosis.
Retain a specialist when the job requires exact screenplay formatting, a particular deliverable format, tracked page revisions, large structured story-bible retrieval, native-device work, or the room’s preferred live workflow. A planning canvas can be valuable without replacing every responsibility in the writer’s stack.
Eight pitfalls, and a reusable story board.
A script-only view can hide the larger structure; a separate board can become stale. An unexplained framework makes notes difficult to interpret. Too many detailed cards obscure an unsettled premise. Character biography can replace dramatic choices. Missing treatment prose leaves transitions untested. AI beats can imply answers the writer has not defended. Paying for unused collaboration adds overhead. Resolve those actual problems instead of treating any one interface as the cause.
Maintain the current draft and source revision. State what a card represents. Use enough detail to inspect the present decision. Read the story as prose when disconnected labels conceal a gap. Keep uncertainty and alternatives rather than accepting a generated outline as authoritative.
A board that survives the next draft
Premise, theme, intended ending, and questions that could change them.
Acts or sequences with provisional major beats and related scene cards.
Character choices and relationship context connected to the relevant turns.
Research and references with the reason for collecting them.
The treatment and any agreed pitch presentation.
A named source draft, reader notes, and proposed structural changes.
Earlier baselines kept distinct from the current plan.
Before sharing, test the actual reader route and distinguish viewing from commenting. Before exporting, inspect what the format carries. The local SVG keeps labels compact while JSON and Markdown retain full summaries, reasons, and notes. An unresolved order conflict can remain in a draft record; missing or duplicate beat IDs must be repaired so the graph represents the intended rules.
Questions before choosing a place for the story.
Which tool should a screenwriter use to plan?
Choose against the current decision and handoff: research, beats, scenes, character choices, treatment, pages, or rewrite. The actual collaborators and deliverable format matter more than a universal score.
Is Final Draft good for planning?
Its documented desktop Beat Board-to-Outline Editor-to-pages workflow can connect planning to the script. The current Writer product does not include those planning features; check the edition.
Can Miro or Milanote hold a story plan?
They can support visual story material through their documented workflows. Establish card meaning, collaborator access, and how the selected plan reaches the screenplay.
How does Arc Studio differ?
Its current guide connects Plot Board, outline, and script views. Trial that actual connection and account features against the way you work.
Is Notion useful for a story bible?
Structured pages and databases can support maintained records. Current Agent assistance can help create or edit them, but the writer still verifies facts, relationships, and ownership.
How many cards should a feature contain?
Use the level of detail that reveals the story’s present problem. A provisional beat, scene, or sequence is a different unit; a fixed card quota does not establish dramatic completeness.
Should I write a treatment?
Connected prose can expose transitions hidden by the card view and support reader discussion. Choose its purpose and length with the recipient.
Can a board replace a screenplay editor?
Only if its actual capabilities meet the required formatting, revision, and delivery needs. A story-planning canvas does not automatically produce paginated screenplay or FDX output.
Can AI plan the screenplay for me?
It can propose structure or summarize supported source material. The writer remains responsible for facts, causal logic, choices, originality, and the actual dramatic result.
Can the producer read without signing in?
Read-only viewing, commenting, and editing can require different access. Test the real sharing mode and account entitlement before making it the sole review route.
Does the local checker impose three acts or chronology?
No. It evaluates your explicit earlier-reveal IDs against the chosen order. It does not infer event chronology or apply a screenplay formula.
Can I retain a circular rule while exploring?
Yes, draft exports retain it as an unresolved finding. The cycle is a contradiction in the supplied rules, not a verdict on the story’s quality.
Your beats. Your reveal rules.
Arrange the cards in reading order. Give each a unique ID and optional IDs that must appear earlier. Graphlib builds the directed relationship graph, detects circular rules and computes one compatible order when possible. The checker compares that graph with your chosen order. It reads identifiers and rules, not the meaning or quality of your story.
Add a story title and at least one beat.
Draft exports retain circular rules and order conflicts as unresolved findings. Missing IDs, duplicate IDs or incomplete beats block export until repaired. SVG labels are compact; full summaries, reasons and notes survive in JSON and Markdown. No FDX or screenplay pagination is produced. Files remain in page memory; save JSON before leaving.
Questions worth settling.
Does Final Draft Writer include desktop planning tools?
Its current support article says Beat Board and Outline Editor are unavailable in Final Draft Writer and require desktop Final Draft 13. Check your edition before choosing it for that workflow.
Can a relationship checker improve a story automatically?
This tool can identify contradictions in the ordering rules you supplied. It cannot determine whether a beat is dramatic, original or emotionally convincing. The compatible order is one mathematical possibility, not an editorial recommendation.
Can I keep unresolved conflicts in a draft?
Yes. The export marks them as unresolved so your writing partner can see the same question. Invalid references are different: repair missing or duplicate beat IDs first so the graph actually represents your intended rules.