When a guide becomes a casebook, revise its metadata to explain the cases, the analysis readers will perform, and the support the book provides. Remove promises of a complete sequential method unless that instruction remains. Check the title, description, and audience language against the final reading experience.
Identify what changed in the reader’s task
A guide may originally teach a process from beginning to end. During revision, the author might replace that sequence with several situations showing different decisions and outcomes. The subject remains similar, but the reader's work changes from following a method to examining cases.
Write the new task explicitly. For example, a book about community projects might now ask readers to compare how different groups organized their work. That is a useful purpose, but it is not the same promise as a complete instruction manual for running a project from the first meeting onward.
Check whether the instructional promise still holds
Review the final contents for the steps implied by the old title or subtitle. Determine which steps are actually taught and which readers must already understand. An introductory explanation and several case discussions may not supply the sequence a beginner expects from a complete practical guide.
If the book retains a method section, describe its role accurately. It may provide a framework for analyzing the cases rather than an exhaustive procedure. The distinction helps readers decide whether the book fits their current need without requiring the author to diminish the value of the case-based approach.
Explain what kind of cases readers will encounter
Identify whether the cases are documented accounts, fictional teaching scenarios, or a clearly described mixture. Keep this distinction consistent with the manuscript's own framing. Do not let a broad marketing phrase imply that invented situations are direct reports of real events.
Describe the selection boundaries that matter to the audience. Cases may focus on small organizations, one region, or a particular stage of a project. The description should not imply comprehensive coverage of a wider field merely because the underlying subject has a broad name.
Make the support around the cases visible
Check what the reader receives besides the narratives. The book might include discussion questions, comparison tables, commentary, or suggested ways to analyze tradeoffs. Describe the features that are actually present and explain their function rather than listing impressive-sounding educational terms.
Avoid promising model answers when the book offers open discussion. Conversely, if it does supply worked analysis, do not describe the collection as nothing more than stories. The useful metadata explains how the supporting material helps readers engage with the cases and what remains for them to interpret.
Reconsider the intended starting knowledge
A sequential beginner's guide often teaches concepts before asking readers to apply them. A casebook may assume that readers already recognize those concepts. Review the manuscript's explanations and identify the knowledge needed to make sense of the cases without outside instruction.
Update audience language accordingly, while avoiding claims about formal qualifications the book cannot establish. If the book is designed for discussion with a facilitator, say so where it affects expectations. If independent readers can use it, verify that the necessary navigation and explanations are actually included.
Reconcile every visible promise before release
Compare the title, subtitle, description, cover wording, and introductory explanation as one set. Use current KDP metadata guidance when entering the publication details. A corrected description cannot fully resolve a cover that still advertises a different kind of book.
Save the approved metadata with the final contents and a short account of the change in purpose. If a later revision restores a substantial instructional sequence, revisit the positioning using the new evidence. The goal is to keep the reader promise attached to the current book instead of allowing the original proposal to dictate how every later edition is described.
Frequently asked questions
Clear answers for this publishing decision.
Can a casebook still teach practical skills?
Yes. The question is how it teaches them and what support it supplies. Describe the actual analysis, discussion, or worked explanation rather than assuming that a case collection provides a complete sequential method.
Must I remove every reference to a guide?
Review the overall promise in context. If the term implies instruction the book no longer supplies, revise it. The final wording should help readers understand the actual structure and task.
Should fictional cases be identified in the description?
Make their nature clear wherever it materially affects the reader’s understanding. Keep the description consistent with the manuscript and avoid suggesting that invented scenarios document actual events.
What should the title, subtitle, description, and keywords look like before I upload?
Check the mechanical limits first, then make sure title, subtitle, categories, and description describe the same book for the same reader; a keyword is useful when it matches how that reader searches, not because it is popular.
Draft the listing fields in a book project