--- title: "Creating a Printable Scene/Event Plan With Narrova" summary: "Turn a completed **Storyform Context** into a printable scene/event planning document with Signposts, Progressions, Events, Dramatic Scenarios, and space for discovery-writing notes." category: Story Planning difficulty: Guided estimated_time: 15-25 minutes start_in_app: Narrova start_url: /narrova best_for: - Dramatica users who miss plot sequence reports, tables of scenes, or older report-style planning. - Discovery writers who want structure without locking every scene too early. - Writers with a completed Storyform who need a printable development artifact. what_you_need: - A completed Storyform saved as Storyform Context. - A story idea, draft, or premise you are ready to illustrate. - A willingness to treat the plan as working material instead of final prose. starter_prompt: |- Using this Storyform Context, build me a printable scene/event plan. Organize it by Act, Throughline, Signpost, Progression, and Event. For each item, include: - the structural label - the underlying Dramatica meaning in plain language - the Area of Exploration - the Dramatic Function - the Area of Engagement - a one-sentence dramatic purpose - a discovery-writing prompt - space for my own illustration notes Do not write final prose. Give me a working plan I can print and fill in as I discover the story. steps: - title: Save the completed Storyform as context detail: Start from Storyform Builder and save or share the completed Storyform so Narrova can use it as Storyform Context. - title: Ask for a printable plan detail: Use Narrova to turn the Storyform into a working plan instead of a polished treatment. The goal is structural pressure plus note space. prompt: |- Using this Storyform Context, build me a printable scene/event plan. - title: Require the three Storybeat anchors detail: Ask Narrova to include Area of Exploration, Dramatic Function, and Area of Engagement so every beat has a clear structural what, how, and audience-facing mode. prompt: |- For every Storybeat, include the Area of Exploration, Dramatic Function, and Area of Engagement, then translate the combination into one practical scene-writing implication. - title: Narrow the output by Throughline detail: If the plan feels too large, focus on one Throughline at a time. Objective Story is usually the cleanest place to begin for event planning. prompt: |- Start with the Objective Story Throughline only. Break each Signpost into Progressions, then Events, and keep the output printable. - title: Convert Progressions into scene containers detail: Treat each Progression as a possible scene or sequence container, then use the child Events as the internal turns. prompt: |- For each Progression, suggest how its child Events could function as the moving parts of one scene or sequence. - title: Leave room for discovery detail: Ask Narrova to stop short of final prose so you can fill in the Illustrations yourself. prompt: |- Keep this as a planning worksheet. Leave space for my own Illustration notes and do not write final scene prose. what_you_get: - A printable Storyform-driven plan organized by Act, Throughline, Signpost, Progression, and Event. - A clean translation from PRCO/TKAD-style thinking into Dramatic Function and Area of Engagement. - A discovery-writing worksheet that keeps structure visible without replacing your imagination. workflow: Storyform Context -> Narrova -> Printable Plan output: Scene/event planning worksheet additional_prompts: - label: Make it more like a table of scenes prompt: |- Reformat this as a table of possible scenes. Use Progressions as the scene containers and list the child Events as internal turns. - label: Explain the old terminology prompt: |- Add a short legend translating PRCO into Dramatic Function and TKAD/KTAD into Area of Engagement. - label: Keep the plan writer-facing prompt: |- Reduce the theory language and make each entry read like a practical instruction for writing the scene. practical_tips: - Use Narrova for the printable map before you start writing scene prose. - Ask for one Throughline first if the full Storyform produces too much planning material. - Treat Events as scene turns unless the story rhythm calls for an Event to become its own scene. related_use_cases: - using-the-storyform-builder-to-spin-up-a-new-story - breaking-a-storyform-into-storybeats-and-moments-in-subtxt - using-existing-storyforms-to-build-a-brand-new-story related_links: - label: Scene and Event Plans From a Storyform url: /use/scene-event-plans - label: Narrova url: /narrova - label: Narrative Context Protocol url: /use/ncp date: 2026-04-21 --- *Want the spirit of the old plot sequence reports without freezing your story into a static document? Start with a complete Storyform Context, then ask Narrova to turn that structure into a printable planning worksheet.* ## Why this workflow works A completed Storyform already contains the larger argument of the story. The problem is not usually a lack of structure. The problem is translating that structure into something a writer can actually use while drafting. Narrova is useful here because it can read the Storyform Context and shape the answer around the exact Storyform in front of it. You are not asking for a generic beat sheet. You are asking for the Storyform's Signposts, Progressions, Events, and Dramatic Scenarios to become a working document you can mark up, print, and develop. ## Ask for structure before prose The starter prompt deliberately says **Do not write final prose**. That matters. If Narrova jumps straight to polished scenes, the structure can get buried under smooth language. Start with the planning layer instead: ```text Using this Storyform Context, build me a printable scene/event plan. ``` Then ask for each Storybeat to include three anchors: - **Area of Exploration**: what the beat is about structurally. - **Dramatic Function**: whether it operates as Potential, Resistance, Current, or Power. - **Area of Engagement**: whether the audience encounters it through Situations, Activities, Aspirations, or Contemplations. That combination gives you a useful writing question: ```text How do I dramatize this Area of Exploration, in this Dramatic Function, through this Area of Engagement, inside this Throughline and Signpost? ``` That is where the plan becomes playable. ## Translate the older Dramatica rabbit holes If you remember PRCO and TKAD, the current platform language is more writer-facing: - **PRCO** becomes **Dramatic Function**: Potential, Resistance, Current, Power. - **TKAD / KTAD** becomes **Area of Engagement**: - Knowledge -> Situations - Ability -> Activities - Desire -> Aspirations - Thought -> Contemplations - The item being explored, such as Hope, Theory, Trust, Test, Hunch, Learning, Understanding, or Obtaining, is the **Area of Exploration**. So a Storybeat is not merely "Hope." It can be read as something like: ```text Area of Exploration: Hope Dramatic Function: Potential Area of Engagement: Situations ``` In plain English: this beat explores Hope, sets it up as Potential in the circuit, and asks the audience to encounter it through states, conditions, or circumstances. ## Use Progressions as scene containers For many writers, the most practical move is to treat each **Progression** as a possible scene or sequence container. The child **Events** become internal turns within that scene. That means an Event does not have to become its own scene. It can, but it does not have to. The point is to use the structural material at the level that fits your pacing. If a Progression explores Hope, and its child Events move through Theory, Trust, Test, and Hunch, the scene is not simply about Hope. It is a scene where Hope is pressured, complicated, tested, acted upon, and reframed. ## Finish with a worksheet, not a verdict The best output from this workflow is a planning artifact: part map, part prompt sheet, part structural checklist. It should leave enough space for you to discover the actual Illustrations. When the plan is working, you can print it, move through it act by act, and fill in your own scene ideas without losing sight of the Storyform underneath.