Guides/Feature Workflows

Reading Analyze

The two measured groups, the Copy Editor's Read, and where each finding leads

Two Groups of Measured Findings ↓How a Finding Works ↓Record Gaps and Beats ↓Copy Editor's Read: One Reader's Opinion ↓Character Presence Has Moved ↓

Two Groups of Measured Findings

Analyze organizes into two labeled groups of findings, plus a separately labeled subjective read at the bottom of the list. There's no overview screen to open first and no numbered sequence to work through — each is a flat list of facets, and clicking Analyze takes you straight to the first one.

Every facet row shows how much of your manuscript it examined and, when it has something to say, how many findings are open. Those two numbers already tell you where to look — there's no dashboard to open first.

Line-Level Analysis: Repetition, Sentence openers, Filter words, and Adverb overuse — deterministic scanners over your prose. Each one flags the same pattern on every run, so a clean read is real news.
Structural Analysis: Scene weight, Dialogue balance, Chapter length, Tension flatness, and Pacing uniformity — located, reproducible patterns over your scenes and chapters.

How a Finding Works

Each facet keeps two things apart: coverage — what it looked at — and findings — what it surfaced. A facet that reads "reviewed" is telling you it examined your manuscript and found nothing to flag, not that your manuscript is good. A facet that hasn't run yet says so outright, rather than showing a bare zero that could be mistaken for a clean pass.

A finding itself has a plain claim on the card face — no hedging, no drill-down required to understand it — and a "See details" link to the fuller reasoning and evidence behind it. Nothing in Analyze changes your manuscript or writes anything to your project on its own.

For each finding you decide: Agree adds it to My Actions, your own revision checklist; Set aside clears it for now without grading it, so a later read won't force you to re-triage it; and, from the finding's own detail view, Disagree records that the read was wrong. None of the three touches your prose — the edit that follows is yours.

Record Gaps and Beats

Below the two measured groups sit two more destinations. Record Gaps compares the characters, places, and connections your prose contains against your own roster and reports the difference — the only place in Analyze that writes to your project, and only when you say so. Beats gives you a read-only, top-down account of the structure you built: a per-chapter read of pacing, the beats analysis detected in your scenes, and peak tension — with a one-click way to bring any of them into Outline, Beat Cards, or Thread Health.

Copy Editor's Read: One Reader's Opinion

At the very bottom of Analyze's list, behind a visible divider, sits the Copy Editor's Read — the model's own developmental take on how your book is built and how it moves, written in prose rather than as a list of findings. It never shares a screen with the measured facets above it, and it's never presented as a finding: hand the same manuscript to two human editors, or two AI platforms, and you'll get two different reads back.

Weigh it the way you'd weigh notes from a copy editor you hired — worth considering, never a verdict to act on. At the foot of the read, "This resonates" and "I disagree" let you say whether it was useful; your answer persists across sessions. If you'd rather see only measured, denominatored findings, turn it off in Settings › AI features — it disappears from Analyze's list entirely and everything else keeps working exactly as before.

← All guides Documentation FAQ

Tension & Pacing

Reading Pacing Uniformity

Chapter Balance & Scene Length