Drafting and Structure

Transition and Flow Map

Diagnose missing reasoning and improve how sections, paragraphs, claims, examples, evidence, exceptions, and actions connect across a draft.

Free editable Markdown · Editors, writers, and writing coaches · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Document route

Draft title: [Working title]
Primary reader task: [What should the reader understand or do?]
Starting knowledge: [What can safely be assumed?]
Destination: [Desired conclusion or completed action]
Structural pattern: [Chronology, problem-solution, hierarchy, comparison, task sequence, or another]
Known branch: [Exception or alternate path]

Unit map

Unit ID: [Section or paragraph number]
Current heading or opening: [Text]
Function: [Claim / Evidence / Example / Definition / Instruction / Qualification / Handoff]
One-sentence content: [What this unit contributes]
Dependency: [What must be known first?]
Next relationship: [Cause, contrast, sequence, evidence, example, or another]
Problem: [Missing step, duplicate, misplaced, mixed purpose, or None]
Revision: [Move, combine, split, add, remove, or retain]

Boundary review

Boundary: [Unit A → Unit B]
Intended relationship: [Name it]
Reader question at boundary: [What may they ask?]
Current cue: [Heading, topic sentence, connective phrase, or none]
Logic supported: [Yes / No / Partly, with reason]
New cue or structural fix: [Write action]

Demonstrative words such as “this” have a clear referent.
Evidence appears beside the claim it supports.
Qualifications cannot be mistaken for optional detail.
Instructions respect prerequisites and dependencies.

Final test

Topic-sentence read: [What route appears?]
Reviewer summary: [How another reader described the flow]
Unexpected jump: [Location and fix]
Intentional repetition: [Why it remains]
Cross-link needed: [Destination and purpose]
Decision owner: [Writer or editor]

How to use this template

State the document’s reader task or central argument and summarize each section and paragraph by function.
Draw or list the dependency between claims, evidence, definitions, instructions, examples, and exceptions.
Name the relationship at every boundary and flag missing steps, duplication, false transitions, or misplaced material.
Reorder, combine, divide, add, or remove content before rewriting transition sentences.
Read the structural route aloud, test it with a reviewer, and complete a final reference and terminology check.

Reduce the draft to a logic outline

Write one sentence for the job of every section and one short label for each paragraph: claim, evidence, example, qualification, instruction, contrast, consequence, or handoff. Read only those labels. The reduced outline reveals repeated openings, unsupported conclusions, late definitions, and sections that perform several jobs. For task content, map prerequisites and actions in the order the reader encounters them. For an argument, map what each claim depends on. Do not preserve the current order merely because the prose already exists; moving one section may solve dozens of local transition problems.

Name the relationship at every boundary

Between adjacent units, state the intended relationship: continuation, cause, result, contrast, concession, example, evidence, chronology, hierarchy, return, or action. Then ask whether the content actually supports that relationship. A paragraph introduced as proof may only repeat the claim; an “however” may signal contrast where none exists. Missing context often appears when the writer knows an intermediate step and omits it. Add the step, qualify the claim, combine overlapping units, or remove the false link before choosing connective language. Headings and topic sentences should make the path visible without forcing readers to decode vague references.

Test the revised route

After restructuring, read the first sentence of each paragraph and the last sentence before every heading. Check pronouns, timeline, terminology, scope, and whether the reader knows why the next section arrives. Ask a reviewer to predict what should come next and summarize the relationship they understood. Variation in sentence rhythm can improve flow, but it is secondary to logic. Preserve necessary repetition where a reader may enter mid-page or complete steps over time. Record intentional jumps and cross-links rather than smoothing away an important branch or exception.

See the fields in context

Fictional example: equipment return guide

Cloudmill Workshop and its return process are invented.

Problem: The fictional guide explained packaging before telling readers which equipment qualified for return.
Dependency: Eligibility determines whether any packaging step is relevant.
Revision: Move eligibility and exceptions first, then preparation, booking, handoff, and confirmation.
Boundary cue: Add “If the item is eligible” before preparation rather than using the vague transition “Next.”
Test: A reviewer can now predict the decision point and explain the alternate repair route.

Frequently asked questions

Are transition words the main way to improve flow?

No. They signal relationships already present. Start with order, dependency, evidence, paragraph purpose, and headings. Add a connective only after the logic is true and the reader benefits from an explicit cue.

How can flow be checked in a long page?

Work at several scales: section route, paragraph function, sentence references, and entry points. A one-line reverse outline makes the large structure visible, while local boundary checks find missing links.

Is repetition always a flow problem?

No. Controlled repetition can reorient readers after a branch, support scanning, or restate an instruction where action occurs. Remove repetition that contributes no new function, but retain what reduces a real navigation burden.

When should a draft be split into several pages?

Split when readers have meaningfully different tasks, prerequisites, maintenance owners, or entry points and can navigate between them. Do not split solely to target minor keyword variations or hide a weak route.