How to Structure a Long Read So Readers Finish It

A long read asks a lot of the person on the other side of the screen. They are giving you twenty minutes, maybe more, at a time when almost everything else they could open would take less. The good news is that length itself is rarely why readers leave. They leave when they lose the sense of where they are, why they are still there and how far there is to go. Structure is how you answer those three questions without ever stating them out loud.

This is how we think about building a long piece so that it holds together from the first paragraph to the last. None of it is a formula. It is a set of habits that make the reader’s route easier to walk.

Start with the promise, not the background

Many long drafts open with context: the history of the subject, how the writer came to it, the wider debate. All of that may belong in the piece. It rarely belongs at the top. The opening has one job, which is to tell the reader what they will get if they stay. Call it the promise.

A promise can be a question you intend to answer, a scene that raises one, or a plain statement of what the piece will show. What matters is that a reader could finish your first two or three paragraphs and say, in a sentence, what the piece is about and why it might be worth their time. If they cannot, they will start skimming to find out, and skimming readers rarely come back to the careful version.

A useful test: write the promise as a single sentence on a separate note before you start revising. Then check that your opening delivers it, and that your ending keeps it.

Build a route, not a pile

Once you know the promise, the body of the piece becomes a route towards it. The mistake to avoid is the pile: a heap of interesting material in roughly the order you found it. Piles feel generous to the writer and exhausting to the reader, because nothing tells them why this section comes after that one.

One way to turn a pile into a route is to list the questions a curious reader would ask, in the order they would ask them. What happened? Why does it matter? How does it work? What goes wrong? What should I do with this? Each question becomes a section, and the order of the questions becomes the order of the piece. If two sections answer the same question, merge them. If a section answers a question nobody would ask, cut it or move it to a note.

Headings are the visible signposts of the route, so write them with care. On FullySky, longer pieces get a table of contents built from their main headings (see features), which means your headings are also read together as a list before anyone reads a word of the body. Read your headings in sequence on their own. If they tell the story of the piece in miniature, the structure is probably sound. If they read like a list of vague labels, such as Background, Discussion and Thoughts, the reader will not know what they are walking towards.

Give every section a job

Inside the route, each section should do one clear thing: explain, show, compare, complicate or resolve. When you reread a section, try to name its job in a few words. If you need a paragraph to describe what a section does, it is probably doing several things at once and would be stronger split in two.

Pay special attention to the last paragraph of each section. That is where readers decide whether to continue. A good section ending does not summarise what was just said. It hands the reader forward: it raises the question the next section answers, or names the tension the next part will deal with. These hand-offs are small, often a single sentence, but they are what makes a long piece feel like one piece instead of a collection of short ones.

Vary the distance

Think of a long piece as a camera that moves. Sometimes it is close: a single moment, a person, a detail, a line of dialogue. Sometimes it pulls back: an explanation, a pattern, an argument. Most flat long reads stay at one distance the whole way through, either all close-up anecdote or all overview.

A rhythm that tends to work is close, then wide, then close again. Open a section with something concrete, step back to say what it means, then return to a specific example that tests the idea. Readers rest when the distance changes. They also remember the close-ups far longer than the explanations, so put your most important points next to your most vivid material.

The same principle applies to the texture of the page. A run of dense explanatory paragraphs can be broken by a short list, a quotation you can properly attribute, or a single-sentence paragraph that lands a point. We write more about this in Pacing and White Space.

Land the ending

The ending is where the promise is kept. It does not need to repeat every point. A reader who has come this far remembers them. What they want is a sense of arrival: the question answered, the scene resolved, or the idea carried one step further than they expected.

Three endings that tend to work: return to the opening image and show how it looks different now; state the one thing you most want the reader to take away, plainly; or point forward, to what the reader can do or watch for next. Three endings that tend not to work: a list of everything already said, a sudden new topic, and a closing line that apologises for the length.

A quick test before you publish

Before a long piece goes out, it is worth running through a short check. These are the questions we ask of our own drafts:

• The promise. Can you state what the piece offers in one sentence, and is that sentence visible in the first few paragraphs?
• The headings. Read alone, in order, do they tell the story of the piece?
• The jobs. Can you name what each section does in a few words?
• The hand-offs. Does each section end by pulling the reader into the next one?
• The distance. Is there a concrete example within every few screens of explanation?
• The ending. Does it keep the promise without repeating the whole piece?

If a draft passes all six, it is ready for a reader. If it fails one, that is usually the place to spend your next hour. Structure will not make a weak idea strong, but it will make sure a good idea reaches the people who chose to give it their time.