A book proposal is a decision document
A book proposal helps a publishing partner understand the book, the reader, the reason this author should write it, and the shape of the finished project. It is not a second copy of the manuscript and it is not a string of promises about how important the subject might become. The proposal gives a reader enough context to decide whether the project fits a list, an audience, or a working relationship.
Requirements vary by agent, publisher, category, and stage of the project. Start with the requested guidelines and use their headings, order, length, and file requirements when they are provided. If you are preparing an internal proposal for an editor, collaborator, or client, agree on the questions it must answer before you spend time polishing the layout.
Begin with a one-sentence book promise
Write a sentence that identifies the reader, the problem or desire, and the result the book will provide. A broad topic is not a promise. The history of home cooking names a subject; a guide that helps busy first-time cooks plan seven reliable dinners from a small pantry gives the reader a reason to care. The sentence should describe what the book actually teaches or delivers, not the largest possible claim about the market.
Use the promise as a test for every section of the proposal. The overview should explain it, the chapter summaries should develop it, the sample pages should demonstrate it, and the author section should establish why you can address it. If the promise changes during revision, update the proposal and metadata together. A proposal that describes one book while the sample pages deliver another creates avoidable doubt.
Define the reader before the market section
Describe the primary reader in terms of a real situation: what they are trying to do, what keeps getting in the way, and what they already know. You can name secondary readers when they matter, but a proposal aimed at everyone usually gives no one a clear reason to choose the book. Reader detail also helps you set the right level of explanation, examples, tone, and scope.
Then explain how the book meets that reader at the moment they need it. A practical book may be useful during a decision, a transition, a project, or a recurring task. A narrative nonfiction book may organize a question that readers have encountered but not yet understood. Keep this section grounded in the manuscript. Do not invent a community, need, or audience response that you cannot support.
Write an overview without overselling
The overview should give the proposal reader a quick, coherent account of the book. Introduce the situation or question, explain the author's angle, describe the path through the material, and state what the reader will understand or do by the end. Lead with the real tension in the project. If the book exists because a common approach leaves readers stuck, explain exactly where it fails and what your manuscript does differently.
Avoid inflated claims that the chapters do not support. Words such as revolutionary, definitive, or unprecedented ask the reader to accept a conclusion before seeing the evidence. A clear description of the problem, method, examples, and boundaries is more persuasive. The overview should make the project feel specific enough to evaluate and complete enough to imagine as a finished book.
Create chapter summaries that prove the structure
A chapter summary should do more than repeat the table of contents. Explain the chapter's question or purpose, the main material it covers, the change it creates for the reader, and the way it leads to the next section. For narrative nonfiction, include the story, investigation, or scene that carries the idea. For a practical book, show the decision, method, example, or exercise that makes the chapter useful.
Write summaries at a consistent level of detail, then check the sequence as a whole. The early chapters should establish the problem and vocabulary the later chapters need. The middle should develop the method or argument rather than circle the introduction. The final chapters should deliver the promise and give the reader a sensible next step. If two summaries perform the same job, revise the structure before hiding the repetition in smoother prose.
Explain comparable books with care
Comparable titles help a proposal reader understand the shelf, conversation, or reader expectation around your book. Choose comparisons for a reason: they may share the audience, subject, format, tone, or problem your book addresses. Explain what each title shows about the market and where your project differs. A useful comparison is specific enough to position the manuscript without pretending the books are identical.
Do not turn the section into a list of famous authors or unsupported sales claims. If you have not verified a number, leave it out. The point is not to guarantee that the proposal will perform like another book. The point is to show that you understand the reader's existing choices and can explain why this manuscript belongs beside them while offering its own angle.
Describe your author platform with evidence
The author section should answer a practical question: why are you positioned to write this book and help it reach the intended reader? Include relevant experience, professional access, previous work, teaching or speaking, research, community connection, or demonstrated audience relationships. Choose evidence that relates to the book. A long biography can still leave the proposal reader unsure why this project belongs with you.
Be direct about what is established and what is growing. Do not inflate follower counts, imply endorsements you do not have, or describe a possible audience as a guaranteed one. A credible platform section can include a plan for building reach, but it should separate current evidence from future work. Specificity makes a developing platform easier to trust than a collection of broad credentials.
Set scope, format, and completion status
State the practical shape of the project: estimated word count, number of chapters, intended format, illustrations or other assets, appendices, references, and the current status of the manuscript. If the book is complete, say which version is complete. If it is in progress, describe what remains and how you will finish it. A proposal reader needs a realistic sense of the work still in front of everyone involved.
Scope also protects the reader promise. A book that promises a full course but has room for a short guide needs a narrower claim or a larger plan. A project with interviews, permissions, charts, or source notes needs those dependencies visible before the sample pages are judged in isolation. Keep estimates honest and update them when structural revisions change the manuscript.
Select sample chapters strategically
Choose sample pages that show the book doing the work described in the proposal. The opening may be the right choice when it establishes the promise clearly, but a later chapter can be stronger when the book's method or voice takes time to arrive. Follow the recipient's instructions about which chapters and how many pages to include. Never make the reader guess why the sample represents the project.
Prepare the sample as a clean review copy. Check the title, chapter heading, paragraph breaks, citations or links, names, and any notes that belong only to the working project. If the sample begins in the middle, add the context the requested format allows, but do not bury the pages under a long explanation. The sample should be easy to open and should deliver the same reader experience the proposal promises.
Keep proposal, manuscript, and metadata consistent
Before you send a proposal, compare its title, subtitle, audience, word count, chapter names, claims, and completion status with the current manuscript. Structural edits can leave an old chapter order in the proposal. A new positioning decision can make the comparison section sound unrelated. A revised word count can conflict with the scope section. These errors are small to fix when you treat the proposal as part of the project, but they are easy to miss when each file lives alone.
Preserve a snapshot of the version used for the submission. If a recipient asks for a revision, you can see what they read before you change the source. Keep alternate titles, private notes, source material, and unsent drafts separate from the final proposal package. Clear version names reduce the chance that an older attachment travels with a newer email.
Organize the proposal workflow in Awtter
Awtter can keep the proposal decisions connected to the working manuscript. Use the Binder for the chapter order, Notepad or section notes for the overview and platform details, Research for comparable-title and source notes, and tags or saved views to gather sections that still need verification. This gives the proposal a visible relationship to the book instead of making it a separate document assembled from memory.
Create a snapshot before you prepare the submission copy, then export the proposal and sample chapters in the requested formats. Generate a PDF when the recipient needs a fixed review copy and a DOCX or Markdown file when they need editable source, but always check the actual exported files. Keep private production notes outside the included Binder sections so they do not slip into the package.
Run a submission-ready review
Read the proposal as someone deciding whether to spend more time on the project. Is the reader clear? Does the overview make a specific promise? Do the chapter summaries show progression? Are the comparisons and author evidence relevant? Does the sample chapter support the claims? Is the completion status honest? Check the requested file names, attachments, word counts, links, and order before sending anything.
Then read the manuscript and proposal side by side one last time. Remove placeholders, comments meant for collaborators, contradictory numbers, and language that promises a book the current draft does not contain. A strong book proposal does not need to sound grand. It needs to make the project easy to understand, the work easy to evaluate, and the next step easy to agree on.