Breaking a Storyform Into Storybeats and Moments in Subtxt

Open a completed Storyform in Subtxt, illustrate Signposts, break them into Progressions and Events, then weave the resulting Storybeats into Moments that can function like scenes or sequences.

Want to turn a completed Storyform into something closer to a scene or sequence board? Use Subtxt to break the Storyform into Storybeats, then weave those Storybeats into Moments.

Why this workflow is separate from the Narrova plan

Narrova is excellent for a printable working map. Subtxt is better when you want to actually build the structure in the platform.

The difference matters. A Narrova plan can tell you what the Storyform suggests. Subtxt lets you make those Storybeats real, revise them, break them down, and then place them into Moments that behave like scenes, sequences, chapters, set pieces, or any other storytelling unit you use.

Work Throughline by Throughline

Start in Illustrating and choose one Throughline:

Then open the Storybeats tab. Stay with one Throughline long enough to understand its movement before trying to weave everything together.

Break broad movement into usable turns

The sequence is simple:

  1. Illustrate the Signpost.
  2. Break the Signpost into Progressions.
  3. Break selected Progressions into Events.

Do not assume more detail is always better. Some stories need all the Events. Others only need the Signposts and a few Progressions. The goal is not maximum granularity. The goal is enough structural pressure to make the story writable.

Read the Dramatic Scenario before writing the scene

Every Storybeat carries a Dramatic Scenario:

For older Dramatica users, this is where PRCO and TKAD reappear in modern language. PRCO becomes Dramatic Function: Potential, Resistance, Current, Power. TKAD/KTAD becomes Area of Engagement: Situations, Activities, Aspirations, Contemplations.

That gives you a clear bridge into Storytelling:

What is being explored?
How does this beat function in the circuit?
How should the audience encounter it?

If you can answer those three questions, you can usually find the scene.

Use Progressions as scene or sequence containers

A practical rule: treat a Progression as a possible scene or sequence container, then use the child Events as internal turns.

For example, if the Progression explores Hope, and the Events move through Theory, Trust, Test, and Hunch, the scene is not merely "a Hope scene." It is a scene where Hope is pressured by ideas, trust, testing, and intuition. That gives you shape, escalation, and a reason for the scene to turn.

Weave into Moments

After the Storybeats exist, move to Plotting and begin attaching them to Moments. A Moment is the storytelling container: a scene, sequence, chapter, set piece, or any other unit that makes sense for your draft.

Moments can hold Storybeats from multiple Throughlines. That is the point. A scene may carry Objective Story pressure, reveal something personal in the Main Character, let the Influence Character challenge the current worldview, and move the Relationship Story at the same time.

The discipline is to know which Storybeats you are weaving and why. Once that is clear, the Writing workspace can help you read the Storytelling flow, generate Synopses, and export more usable writing material.

The payoff

At the end of this workflow, you do not just have a list of scenes. You have a Storybeat-to-Moment plan: each Moment carries visible structural pressure, and each Storybeat still knows which Throughline, Signpost, Progression, or Event it belongs to.

That is the real upgrade from a static report. You can still print, review, and revise, but the plan stays connected to the living Storyform.

Read the raw Markdown