What Is a Chapter Brief?
A chapter brief is the operational contract for a single chapter. It defines what the chapter must accomplish, what it must set up, what it must pay off, and what it must not repeat. Here is why it matters.
What is a chapter brief?
A chapter brief is the operational contract for a single chapter. It defines the chapter's purpose, objective, summary, required setup, required payoff, concepts introduced, what must not be repeated, how it connects to the previous chapter, and what it prepares for the next.
It is not a summary. A summary describes what the chapter is about. A brief prescribes what the chapter must do. This distinction matters: a brief is binding on the draft, not just suggestive.
Why chapter briefs matter
Without a brief, a chapter is just a topic. You know you need to write about X, but not what X must accomplish, what it must set up for the next chapter, or what it must not repeat from earlier chapters.
This leads to chapters that wander. You write 3,000 words about X, but they do not serve the book's promise, they do not set up what comes next, and they repeat a concept already covered in chapter 4. The book becomes a collection of chapters instead of a coherent work.
A brief prevents this. It gives you a contract: this chapter must do A, set up B, pay off C, and avoid repeating D. When you draft, you draft against the brief. When you review, you check the draft against the brief.
What goes in a chapter brief
A complete chapter brief includes the following fields:
- Purpose: Why this chapter exists in the book. What role it plays in the overall structure.
- Objective: What the reader should achieve or understand after reading this chapter.
- Summary: A one-sentence description of what happens in the chapter.
- Required setup: What needs to be established before this chapter for it to make sense.
- Required payoff: What this chapter must deliver or resolve.
- Concepts introduced: New concepts, terms, or characters this chapter introduces.
- Do not repeat: Material from earlier chapters that must not be repeated.
- Previous connection: How this chapter connects to the previous one.
- Next preparation: What this chapter sets up for the next one.
First chapter awareness
A good chapter brief system knows which chapter is first. The first chapter's brief should set previous connection and required setup to None, instead of referencing a non-existent previous chapter. This seems obvious, but many tools generate briefs that reference a previous chapter even for chapter 1.
The concepts introduced field should list only concepts this chapter actually introduces, not concepts a later chapter will define. This prevents the model from front-loading definitions that belong in later chapters.