The whole workshop

Every part of a novel, on one desk.

Plot, characters, threads, and the manuscript itself — plus a docx export that’s already typeset, and a place to read every note your beta readers ever sent you.

Act II · Rising action

IncitingBeat 04
RisingBeats 05–08
MidpointBeat 09
CrisisBeat 11
ClimaxBeat 12
Plot

Acts, beats, and the bones underneath.

Lay out the architecture of your novel in a single, scrollable view. Mark beats as rising, midpoint, or climax. Pin a beat to a scene when you’re ready to write it — and watch the table of contents light up.

  • Reorder by drag, not by rewriting
  • Bind beats to scenes and POV characters
  • Custom beat types for the way you think

Threads

The missing keysetup · Ch. 03
The debt to the southpayoff · Ch. 14
The scar on Halvor’s handsetup · Ch. 06
Sera’s brotherpayoff · Ch. 22
Threads

Sanderson knew, all along

The novel is a series of promises, marching towards their payoff. As writers, we all know how difficult it is to keep track of them, especially if it’s stored somewhere in ‘james_has_the_key.txt’ on your desktop. Happened to us. Happens to you. Not in Storystruct.

  • Tag, classify, and link threads to scenes
  • See at a glance which promises are still open
  • Refactor a thread without losing its history

Docx export · The Salt-Crowned · Ch. 04

Page size15 × 22 cm
Margins1.5 cm
BodyCrimson 12pt / 1.35
HeadingsCrimson 18pt bold
Page numbersbottom-centre
Hyphenationen-US
Em-dashes
Docx export

A typeset manuscript, not a Word soup.

Export a chapter to .docx that’s already typeset — page size, margins, body and heading fonts, line spacing, page numbers, even language-aware hyphenation. Open it in Word, send it to an agent, print it. It looks like a book draft, not a dump.

  • Per-chapter or per-manuscript export
  • Honours your Story DNA: em-dashes, numerals, italics, scene breaks
  • Auto-hyphenation by language (EN, NL, DE, FR, ES, IT, PT)
Beta-reader feedback

The notes live where the prose lives.

Send a chapter to your beta readers. They send back a Word document full of track changes and comments — or a Markdown file, if that’s how they roll. Upload it against the chapter in Storystruct. We parse it in our backend, diff it against a snapshot of the prose, and show you the result: insertions, deletions, and emphasis added by the reviewer, with their comments anchored to the exact words they refer to.

The diff is stored as a review, so the same feedback can be read again, in the same place, long after you’ve rewritten the chapter underneath it.

  • .docx with track changes & Word comments, or .md
  • Insertions, deletions, and added emphasis — bold, italic, underline, strikethrough, highlight
  • Reviewer comments anchored to the text they comment on, with author & date
  • Replayed unchanged after the chapter is rewritten — the snapshot is preserved

It’s easier to see it than to read about it.

Open a story, lay out three beats, and feel the workspace. No setup, no template wizard.