Template

A nonfiction book outline template you can adapt to your idea

The complete framework is below: book-level foundation, part and chapter fields, trackers for evidence, objections and open questions, a filled example, and a final structure check. Nothing to download, nothing to sign up for. Copy what is useful into wherever you actually work and delete the rest.

How to use it

Work top-down and expect to loop. Fill the book-level foundation first, even roughly — almost every later field is decided against it. Then sketch parts, then chapters, then come back and fix the foundation once the chapters have taught you what the book is.

Answer in your own shorthand. This is a thinking instrument, not a document anyone will read. A field you cannot answer is the most valuable thing on the page — write “don’t know yet” and leave it visible rather than filling it with something plausible.

Nothing here is stored, sent or submitted. There are no input boxes on this page by design.

Before you outline

Three things are worth having in front of you first: your raw material in one place, a rough sense of who this is for, and permission to write a structure you will later change. If you have none of the three, the outline will be a guess wearing a suit.

1. Book-level foundation

The layer everything else is judged against. Fill this in before you name a single chapter.

Foundation fields

Working title: A placeholder is fine. Its only job is to stop you calling the file “book”.
Target reader: One specific person, not a demographic. What do they already know, and what will they refuse to sit through?
Reader’s current problem: What is wrong or unclear from their side — in their words, not yours.
Reader promise: What they will understand or be able to do by the end. One sentence. This is the field everything else answers to.
Central question: The single question the book answers. If you have three, decide which two are chapters.
Working thesis or main argument: Your current best answer, stated as a claim someone could disagree with. “Working” means you expect it to change.
Why this matters now: What makes this the moment for the book. If the honest answer is “it doesn’t”, the book may be timeless rather than topical — say so.
Scope: The territory the book covers: period, place, discipline, kind of reader, level of depth.
What the book will not attempt to cover: Written down explicitly. This field prevents more scope creep than any other, and it answers the reviewer who wants a different book.
Desired change in the reader: What they think, feel or do differently at the end. If nothing changes, the book is a report.
Author perspective or credibility: Why you are the one writing this — experience, research, access, or a vantage point. Also where your authority runs out.
Evidence standards: What counts as support in this book: studies, interviews, archival record, practice, reasoning. Decide once so chapters don’t apply different rules.
Voice and tone: How it sounds and how close it stands to the reader. Useful later, when revision starts sanding your voice off.
Approximate structure: The organising pattern — problem to solution, chronological, concept by concept, argument and objections — and roughly how many parts.
Known research gaps: What you are currently missing. Keep this list alive; it is the difference between a gap and an accident.

2. Part-level template

Repeat for each part. If your book has no parts, skip this and treat chapters as the top tier.

Part fields

Part title: Working title. Parts are often named last, once you can see what they turned out to do.
Reader’s starting point: What the reader believes and understands as this part opens. Different for part three than part one.
Purpose of the part: One line: what this part does for the argument as a whole.
Main question: The question this part answers on the way to the book’s central question.
Chapters included: Titles or working labels, in order.
What must be understood before moving on: The thing the reader has to accept or grasp before the next part can work. If you cannot name it, the part may not be doing anything.
Transition into the next part: The move from here to there. A part that ends without a reason to continue is where readers stop.

3. Chapter-level template

One card per chapter. This is the layer that does the most work — and the one worth filling in only two or three chapters ahead of where you are writing.

Chapter fields

Chapter title: Working title. Expect to change it once the chapter exists.
Chapter purpose: One line on what this chapter does for the book. Not its subject — its job.
Reader question: The question in the reader’s head when they arrive here. If you cannot name it, they may not have one.
Main claim or lesson: The one thing they should be able to state afterwards.
Supporting points: The two to five steps the claim stands on, in the order they become believable.
Evidence or sources needed: What each point rests on — and whether you have it yet. Unhad evidence goes to the tracker below.
Example, story, analogy or case: The concrete material that makes the abstraction land. Note what it is doing, so you notice if two chapters use examples that do the same job.
Counterargument or complication: The objection a sceptical reader raises here, at full strength. A chapter with none is either uncontroversial or unexamined.
Definition that must remain consistent: Any term this chapter defines or relies on. This field is how you avoid redefining your key concept in chapter nine.
Reader takeaway: What they carry forward. Different from the main claim: this is what survives to the next chapter.
Link to previous chapter: Why this follows that. If the answer is “it just does”, the order may be arbitrary.
Transition to next chapter: The question or tension you leave open.
Open questions: What you have not resolved about this chapter. Keep them attached to the chapter rather than in your head.
Draft status: Not started, notes only, drafted, revised, or settled. The only field here that is purely administrative — and the one that stops you rewriting chapter one for a fourth time.

4. Evidence and research tracker

One row per claim that needs support. Nonfiction rarely fails because a claim was wrong; it fails because nobody wrote down that the claim was still unsupported.

Evidence tracker fields

Claim: The assertion, stated as it appears in the draft.
Evidence needed: What would actually support it — not what you hope exists.
Source: Where the support comes from, specifically enough to find again.
Verified?: Have you read the source itself, rather than a summary of it? Yes or no. No third option.
Citation recorded?: Is the full reference captured somewhere you will find it in a year?
Limits or uncertainty: What the evidence does not show. This field is what keeps the draft’s wording honest during revision.
Where used: Every chapter that leans on it — so that if the evidence weakens, you know what else moves.

5. Objections and open questions

Two short trackers that stop the book quietly becoming a case for the prosecution.

Counterargument tracker

One per serious objection.

Objection: Stated in its strongest form, not the version that is easy to answer.
Who holds it: A real constituency — a school of thought, a profession, a reader you know.
Where it is addressed: Which chapter takes it on. An objection with no address will find your reviewers instead.
My response: The answer, in a sentence.
Does it change my claim?: Sometimes it should. A qualification recorded here is worth more than a rebuttal you do not believe.

Open-question list

One per unresolved decision.

Question: What you have not settled — structural, factual or ethical.
Why it matters: What depends on the answer.
What would answer it: A source, an interview, a decision you can simply make, or writing the chapter.
Blocking which chapters: So you know whether it is urgent or merely open.
Decide by: A point in the project, not a date — “before drafting part three”.

6. Transition and sequence check

Run this against the outline as a whole, reading only the purpose lines in order.

Sequence check

Every chapter has a stated reason for following the one before it.
Nothing is used before it is defined or explained.
No chapter asks the reader to accept something the previous chapters have not made believable.
Each part ends with a reason to continue rather than a full stop.
The reader's starting point at each part matches what the previous part left them with.
No two consecutive chapters make the same move.
The book's hardest claim arrives after its support, not before.

7. A filled example

The Neighborhood Garden is a fictional book invented to demonstrate the fields. It is an instructional example only — nothing in it is a factual claim about the world.

Book-level foundation — filled

Working title: The Neighborhood Garden
Target reader: Someone who walks past a fenced empty lot most days and has started wondering who owns it. No organising experience. Willing to spend a year, not a decade.
Reader’s current problem: They can picture the garden. They have no idea what happens between wanting it and having it, and every account they have read skips that part.
Reader promise: Help residents turn an unused neighbourhood lot into a sustainable community garden without underestimating the organisation, the maintenance, or the conflict.
Central question: What actually makes a community garden last past its second summer?
Working thesis: Gardens fail for social reasons far more often than horticultural ones — so the decisions that matter most are made before anything is planted.
Why this matters now: Enthusiasm for these projects is easy to find; honest accounts of the ones that collapsed are not.
Scope: Small urban lots, volunteer-run, temperate climate, no paid staff.
What the book will not cover: Horticultural instruction, rural land, municipal farms, anything with a budget large enough to hire someone.
Desired change in the reader: They start with the agreement and the maintenance plan instead of the seed order — and they know what to do when two neighbours want incompatible things.
Author perspective: Ran one garden for six years and watched two others fail. Not a horticulturalist and not a lawyer; says so.
Evidence standards: Named interviews and documents the author has seen. Personal experience labelled as such. No statistics unless traceable to a source the reader can check.
Voice and tone: Practical, candid about failure, not inspirational.
Approximate structure: Three parts: before planting, the first season, the years after.
Known research gaps: Liability and insurance — currently one conversation and an assumption. See the evidence tracker.

The three parts

Part one — Before anything is planted: permission, people and the agreement. Purpose: establish that the unglamorous decisions are the load-bearing ones.
Part two — The first season: the work, the early conflicts, and the point where the initial enthusiasm runs out. Purpose: show what the first year actually costs.
Part three — Staying alive: succession, maintenance and handing it on. Purpose: answer the central question — this is where lasting is decided.

Chapter card — filled (Part one, chapter three)

Chapter title: The Agreement Nobody Wants to Write
Chapter purpose: Convince the reader to write down decision-making rules before there is any disagreement to resolve.
Reader question: “We all get along — isn’t a written agreement a bit much?”
Main claim: Agreements are worth writing precisely while everyone still agrees; afterwards they are impossible to write and desperately needed.
Supporting points: 1. Early conflicts are about small things and go badly anyway. 2. Undocumented founder authority becomes resentment by year two. 3. Groups without an exit rule cannot remove anyone. 4. Writing it takes an evening.
Evidence or sources needed: Interview with the Bell Street group (have it). Their written agreement, with permission to quote (have it). One group that had none (have it, anonymised).
Example or story: The dispute over whether a plot could be reassigned after a member stopped attending. Doing the job of showing that the trivial trigger is not the real problem.
Counterargument: Formal structure deters volunteers, and some good groups run for years on trust alone. Answered rather than dismissed: the chapter argues for one page, not a constitution.
Definition to keep consistent: “Member” — used throughout the book to mean someone with a plot and a vote, not any volunteer. Defined here.
Reader takeaway: Write four things down this month: who decides, how someone joins, how someone leaves, and who holds the keys.
Link to previous chapter: Chapter two ended with permission secured — the moment a loose group becomes an entity with obligations.
Transition to next chapter: Leaves open the question the agreement cannot solve: what if the people who signed it stop turning up?
Open questions: Whether the sample agreement belongs here or in an appendix.
Draft status: Drafted, not revised.

An evidence gap, recorded

Claim: volunteer-run gardens on borrowed land usually need their own liability cover. Evidence needed: what arrangements comparable groups actually hold, and what a landowner typically requires. Source: one conversation, second-hand. Verified? No. Citation recorded? No. Limits: the author is not qualified to advise on this and the requirements vary by jurisdiction. Where used: part one, chapter two — currently written as though it were established. It is not, and the gap stays visible until it is.

An unresolved structural decision

Question: does the story of the garden that failed open the book or close part two? Why it matters: as an opening it sets a candid tone and risks deterring the reader on page three; in part two it lands harder but the first part is more conventional. What would answer it: drafting both and giving them to three readers who have never run a garden. Blocking: chapter one only. Decide by: before drafting part three.

8. Final outline review

Run this once the outline is filled in, before you commit to drafting from it.

Final review checklist

Does every chapter serve the reader promise?
Is each major claim supported, or clearly labelled as interpretation?
Are definitions consistent across chapters?
Is important background introduced before it is needed?
Are examples doing distinct work, rather than repeating each other?
Are counterarguments addressed fairly, in their strongest form?
Are any chapters repeating the same function?
Does each part create a clear transition into the next?
Are research gaps visible rather than hidden inside confident prose?
Could a reader explain the argument after seeing only the outline?

Moving the outline into Writva

If you want the outline and the manuscript to be the same object rather than two documents that drift apart, the Binder takes the same shape as this template: you name the tiers, so parts and chapters become the hierarchy, and each chapter is a writing unit linked to its own draft. Reordering a chapter carries its draft with it.

The fields that are not structure — evidence needs, objections, open questions — can live as ideas attached to the project and associated with the section they belong to, so they surface when you reach the chapter rather than in a notebook you have stopped opening.

There is no automatic conversion: moving an outline in is something you do, chapter by chapter, and it is usually worth the hour because you re-examine every decision while you do it.

How to Organize a Nonfiction BookGetting from scattered material to an argument in order.
How to Outline a BookA flexible outlining method for planners and discovery writers.
How to Edit a BookEditing a whole manuscript in passes, from structure to sentences.
For Nonfiction WritersArguments, claims, evidence and chapter structure for nonfiction.

Questions about this template

Is there a file to download?

No, and that is deliberate. The whole template is on this page — copy the parts you want into whatever you already write in. A download would mostly be a reason to ask for your email address.

Do I have to fill in every field?

No. Some fields will not apply to your book, and deleting them is a real decision rather than a failure. The fields that are hard to answer are the useful ones: difficulty usually marks the part of the book you have not thought through.

Can I use this for a memoir or a business book?

Largely, yes. The book-level and chapter-level fields work for most argument-driven or explanatory nonfiction. A narrative memoir will get less from the evidence tracker and more from the transition checks; take what fits.

Do I need Writva to use it?

No. This is a framework, not a product feature, and it works on paper or in any document. Writva is one place to keep it — the Binder holds the same parts and chapters as a live structure — but the template stands on its own.

Start with the promise and one chapter card

The reader promise, then a single chapter filled in properly. You will learn more from one complete card than from fifteen half-finished ones.

Try Writva free See pricing

How to Organize a Nonfiction BookGetting from scattered material to an argument in order.
How to Outline a BookA flexible outlining method for planners and discovery writers.
For Nonfiction WritersArguments, claims, evidence and chapter structure for nonfiction.