Structuring Any Document

The beginning of a document does three things: establishes context (what is this about and why does it matter?), states the purpose (what will the reader know or be able to do after reading?), and sets expectations (roughly how long is this and what will it cover?).

A good beginning tells readers exactly what they're getting into — no false promises and no buried leads. If the reader can't tell what the document is about after the first paragraph, the beginning isn't working.

Keep the beginning proportionate. A beginning that takes three paragraphs to reach its point is usually too long. Get to the purpose fast.

The middle is where the document does its work — presenting evidence, developing arguments, explaining concepts, building the case for the conclusion. Every section of the middle should advance the document's central purpose.

The most common problem in the middle is structure that follows the writer's research process rather than the reader's comprehension needs. You learned things in a particular order while writing. The reader doesn't need to follow that same path.

Write the middle in the order that makes sense for the reader, not the order you discovered the information. Getting there often requires rearranging after a first draft.

Use the pattern that matches what the reader needs to do with the document. Common patterns for the middle of a document:

• Chronological (events in time order) — suits instructions and histories, but often buries the conclusion.
• Problem–solution — suits proposals.
• Cause and effect — suits explanations and incident reports.
• Comparison (option A versus option B) — suits decisions.
• General to specific — suits overviews and reference material.

You can combine patterns — a proposal might use problem–solution overall and a comparison within the solution section — but each section should have one clear logic.

End by telling the reader what to do with what they've just read — not by summarizing it. "In conclusion, this document has covered X, Y, and Z." This is a table of contents written after the fact. The reader just read the document — they don't need a summary of what they know.

The end should answer: what should the reader do with what they've just read? Implications, next steps, open questions, or a call to action are all appropriate endings. Summary is not.

A strong ending makes the reader feel the document was worth their time. A weak ending makes them wonder why they read to the end.

Outline your document after you've written it — not before. Does the outline match what you intended to argue? If the outline of what you wrote differs significantly from the outline you planned, your draft has wandered.

Read only your headings and topic sentences in sequence. Do they tell a coherent story on their own? If not, the structure is the problem — not the prose quality within each section.

Give someone only the first and last paragraphs. Do they have an accurate sense of what the document argued? If not, your beginning and ending aren't doing their jobs.

A draft report on a failed product launch follows the order events happened: the planning, the build, the launch, the problems, and finally, on the last page, the recommendation to change the release process.

Restructured for the reader: open with the main finding and recommendation — "the launch failed because testing was cut to meet the date; we recommend a fixed testing window before any release." The middle presents the evidence in order of importance. The end covers next steps and open questions.

The content barely changes, but the reader now knows the point in the first paragraph and can read everything after it as support for that point.

Headings, topic sentences, and brief transitions tell readers where they are and where they are going. In a longer document, a short roadmap sentence at the start — "This report covers the cause, the impact, and the fix" — helps readers navigate.

Signposting should be light. One sentence that orients the reader is helpful; a paragraph explaining what each section will contain is usually a sign the structure isn't clear enough on its own.

Balance matters as much as order. A document whose background runs for three pages and whose recommendation takes one paragraph signals the wrong priorities. As a rough check, compare how much space each section takes with how important it is to the reader. The sections that matter most to the reader's decision or understanding should get the most careful development, not necessarily the most words.