How to Prepare Your Nonfiction Manuscript for Structural Editing
Most nonfiction manuscripts reach an editor in decent shape at sentence level. The prose is clean, the paragraphs behave themselves, and there is a voice on the page. What is far less certain is whether the book works as a whole: whether chapter four earns its place, whether the evidence on page ninety supports the claim on page twelve, and whether a reader who finishes the last page could say what they gained. That is the work of structural editing — and the more thinking you do beforehand, the sharper your editor's feedback will be.
Structural editing goes by several names — developmental editing, substantive editing, sometimes just "big-picture editing" — but the job is always the same. It examines the architecture of the book: the order of the argument, the weight given to each part, the logic that carries a reader from one chapter to the next without asking them to hold too much in their head at once. It is not line editing, which polishes sentences, and it is not copy-editing, which catches errors. A structural editor may well tell you to delete your favourite chapter and write a new one in its place, and they will usually be right to.
The catch is that structural problems are the hardest kind to see from inside the manuscript. You know what you meant, so the gaps fill themselves in. You remember the caveat you made in chapter two, so the bald claim in chapter seven feels less bald than it reads. Preparing a manuscript for structural editing is largely an exercise in forgetting what you know and reading what is actually on the page. Doing that work before you hand the file over means your editor's time goes on diagnosing the book rather than excavating it.
Begin with the promise your book makes
Every nonfiction book makes a promise to its reader, whether or not the author has ever written it down. Before anything else, write yours in a single sentence. Present tense, no hedging, as specific as you can manage.
This book shows a first-time team leader how to run a weekly meeting people do not dread.
A good promise has three parts. It names the reader — here, a first-time team leader, not "anyone who works in an office". It names what they want — meetings that are not dreaded. And it names what the book will do about it — show them how to run one. If any of those three parts is vague, the manuscript will be vague in exactly the same place, because you will have been writing towards nothing in particular.
That sentence is your test. Any chapter that does not serve it is either doing work you have not noticed yet, or it belongs in a different book. Two failure modes show up again and again. The first is the missing promise: the writer has a subject (leadership, habits, gardening) rather than a promise, and the chapters read like a tour of a topic rather than a path towards something. The second is the promise so broad that nothing could fail it — "This book helps people live better" — which sounds generous and gives you no way to make a single decision.
If you cannot write the sentence at all, structural editing will open with a long conversation about what the book is. Better to have that conversation with yourself first.
Stress-test your central argument
Your argument is the spine of the manuscript, and it should be something a reasonable person could disagree with. "Meetings waste time" is an observation. "Most weekly team meetings should be replaced by a written update" is an argument, and it can be defended.
Four checks are worth running:
- The load-bearing claim. Which ideas, if removed, would cause the book to fall over? Those need your strongest evidence, the most careful phrasing, and the most space. The claim that written updates beat meetings for routine coordination is load-bearing; the aside about calendar hygiene is not.
- The objection. Where would a sceptical reader push back? A manuscript that never acknowledges the counter-case reads as either naive or evasive, and it loses the reader who was halfway convinced. Name the strongest objection in your own words — that some work is genuinely synchronous and creative — then answer it, or say honestly where the evidence runs out.
- The through-line. Can you describe how one claim leads to the next in a single paragraph? If you need a diagram to explain the sequence, the reader will need one too, and they will not get it.
- The proof. For each major claim, can you point to the page where it is supported? Not the page where it is asserted — the page where it is supported.
Map the manuscript at chapter level
Prose expands to fill the space it is given, and a chapter that began as a paragraph can reach six thousand words without anyone deciding it should. The antidote is a chapter map: one line per chapter, answering three questions.
- What question does this chapter answer? Not what topic it covers — what question it answers for the reader.
- What does the reader know or believe after it that they did not before?
- Why does it come here, rather than earlier or later?
If a chapter cannot answer the second question, it is probably a chapter you enjoyed writing rather than one the reader needs. If it cannot answer the third, you may have a sequencing problem: two chapters that each work alone but fight each other when placed in order. Read the map back to yourself out loud. It should sound like an argument, not a list of subjects. "Why meetings fail, how written updates work, when to keep the meeting, how to run the ones you keep" is an argument. "Meetings, communication, culture, tools, remote work" is a table of contents pretending to be a book.
Trace the evidence back to the claims
Once you have the map, check the distance between each claim and its support. Readers do not hold evidence in their heads across long stretches. If your strongest study sits in chapter two and your strongest claim in chapter eight, either move the evidence forward or restate the case where the claim actually lives.
Watch for the opposite problem as well: a mountain of evidence piled under a modest point. This usually means the writer is more interested in the research than in the argument, and it slows the book down in exactly the places where it should be gaining momentum. Ask of every piece of evidence whether it changes what the reader thinks. If it does not, it is decoration.
Then check degree. Does the wording of your claim match the strength of what supports it? "This suggests" and "this proves" are different promises, and a book that makes confident claims on cautious evidence will be caught — by a reviewer, by a practitioner in the field, or simply by a reader who stops trusting you somewhere around chapter six. Structural editing is where you catch it first.
Write a structural edit brief
Hand your editor more than a manuscript. A short brief, one or two pages, saves weeks of back-and-forth and produces a far more useful set of notes.
- The promise sentence. Yours, in your words, even if it is wrong. Your editor can argue with a sentence. They cannot argue with a shrug.
- The chapter map. One line each, in your own language.
- Who the reader is. What they already know, what they are afraid of, what they have already tried.
- The parts you are unsure about. Point at them directly. Editors find it much easier to be honest about a chapter you have already flagged as shaky.
- Your questions. If you suspect the book starts too late, say so and ask. Otherwise you may get a detailed report on punctuation and nothing on the beginning.
- What you are willing to change. If chapter three is non-negotiable because it is the reason you wrote the book, say so. Editors are not mind readers, and they will happily spend their time proposing a fix you will never accept.
Polish what you can, leave the structure alone
There is a strong temptation, once a structural edit is booked, to spend the waiting weeks line-editing. Resist most of it. Time spent perfecting sentences in a chapter that may be cut is time you will not get back, and worse, it makes you attached to prose you may need to lose. The more beautiful the sentence, the harder it is to hear that the paragraph should go.
What is worth doing is smaller and duller. Fix typos and obvious errors so they do not distract. Standardise names, terms and capitalisation so your editor is not reading variation as significance. Make headings and lists consistent. Keep one file, cleanly formatted, with a visible chapter structure. These are courtesies, but they are also diagnostics: a manuscript with three spellings of the same key term usually has three slightly different ideas behind it.
What a good structural edit looks like on the page is rarely a list of small corrections. It reads more like this:
Chapters 4 and 5 are doing the same job. Chapter 4 explains why synchronous work is expensive; chapter 5 explains why asynchronous work is cheaper. That is one argument, split across two chapters, with the same examples appearing in both. Consider merging them and using the freed space for the trust material you mention on page 140 but never develop — that is where the real objection to your argument lives, and right now it gets two paragraphs.
You cannot write that note for yourself. But you can arrive at the meeting having already asked the questions it answers, which is the whole point of preparing. Write the promise, test the argument, map the chapters, trace the evidence, and tell your editor everything you already suspect. The structural edit will still find things you missed. It will just find the interesting ones.
