Before-draft questions

• □ What is the book about?
• □ Who is it for?
• □ What does the reader need before they open it?
• □ What should the reader understand, feel, decide, practice, or build after finishing it?
• □ What makes this book different from a generic AI-generated draft?
• □ Is this book meant to entertain, teach, guide, warn, inspire, document, or prepare the reader for something else?
• □ Does the book stand alone, or does it connect to a larger creator system?

Reader promise checklist

• □ The book has one clear primary promise.
• □ The promise can be explained in one or two sentences.
• □ The promise matches the intended reader.
• □ The promise is not exaggerated.
• □ The promise does not guarantee legal, financial, health, platform, professional, spiritual, sales, or business results.
• □ The promise matches the title, subtitle, introduction, back cover copy, and product page direction.

Target reader check

• □ Reader’s current situation is clear.
• □ Reader’s problem, desire, question, or curiosity is clear.
• □ Reader’s experience level is defined.
• □ Reader’s likely objections are listed.
• □ Reader’s next step after the book is understood.
• □ Language is appropriate for the reader’s level.
• □ The reader profile is specific enough to guide writing choices.

Book type options

• □ Fiction novel.
• □ Short story collection.
• □ Devotional or faith-based reflection guide.
• □ Nonfiction teaching book.
• □ Practical how-to guide.
• □ Workbook or guided journal.
• □ Training manual.
• □ Memoir or personal story.
• □ Framework book based on your method or system.
• □ Companion book connected to a product, training path, or creator brand.

Chapter path check

• □ Opening chapter gives the reader a reason to continue.
• □ Each chapter has a clear job.
• □ Chapters build in a logical order.
• □ Repeated sections are intentional, not accidental.
• □ The middle does not drift away from the reader promise.
• □ The ending gives the reader a clear sense of completion or next step.
• □ The table of contents reflects the reader journey, not just topic storage.

AI drafting check

• □ AI is being used for support, not as the final authority.
• □ Draft sections are reviewed before moving forward.
• □ Examples are made specific.
• □ Repeated wording is removed.
• □ Claims are checked.
• □ The tone fits the reader.
• □ The author’s point of view is present.
• □ The draft does not sound like a generic article stretched into a book.
• □ Human edits are strong enough that you would stand behind the final wording.

Fiction development check

• □ Main conflict is clear.
• □ Protagonist has a real desire and internal pressure.
• □ Antagonistic force is understandable.
• □ Stakes increase over time.
• □ Character decisions affect the plot.
• □ Scenes are not just events; they change something.
• □ Ending resolves the story’s main pressure.
• □ The story carries a human emotional center, not just plot mechanics.

Nonfiction development check

• □ Book problem is clear.
• □ Reader starting point is clear.
• □ Reader ending point is clear.
• □ Chapters are ordered by learning path, not random topic order.
• □ Key terms are explained simply.
• □ Examples are relevant to the reader.
• □ Practical tools, prompts, checklists, or reflections are included where useful.
• □ The book does not overpromise outcomes.
• □ The author’s experience, framework, or point of view is clear.

Human review check

• □ Reader promise still matches the manuscript.
• □ Chapter order still makes sense.
• □ Repeated AI phrasing has been reduced.
• □ Weak examples have been replaced or removed.
• □ Unsupported claims have been checked or softened.
• □ Sensitive topics are handled carefully.
• □ The author’s voice is present.
• □ The book feels useful, not just complete.
• □ The manuscript is ready for file preparation, not just another rewrite pass.

Documentation check

• □ AI tools used are listed.
• □ AI-generated sections are identified in your private notes.
• □ Human edits and rewrites are documented.
• □ Image sources are listed.
• □ Cover art source is documented.
• □ Quotes are reviewed and sourced.
• □ Scripture or faith-based references are checked where used.
• □ Public-domain material is reviewed carefully.
• □ Contributor permissions are saved where relevant.
• □ Client, student, patient, or private information has been removed unless there is clear written permission and lawful use.
• □ Final AI disclosure notes are prepared before KDP upload.

Human authorship record

• □ Original idea notes saved.
• □ Reader promise saved.
• □ Chapter outline saved.
• □ Draft versions saved.
• □ Major rewrite decisions saved.
• □ Source list saved.
• □ AI-use notes saved.
• □ Final manuscript approval date saved.
• □ Final publishing package folder started.

Reader next-step check

• □ Book has a clear ending.
• □ Back matter includes a helpful next step.
• □ Website or Shopify page is included where appropriate.
• □ Newsletter or community invite is relevant.
• □ Free download supports the book topic.
• □ Paid upgrade is useful, not random.
• □ Next step does not overpromise results.
• □ The next step matches the reader’s stage after finishing the book.

• □ Asking AI to write too soon: direction should come before drafting.
• □ Confusing length with value: a longer draft is not automatically a stronger book.
• □ Skipping the reader promise: the book needs a clear reason to exist.
• □ Letting AI flatten the voice: clean wording can still feel generic.
• □ Formatting before review: structure should be stable before file prep.
• □ Ignoring documentation: AI use, sources, rights, and changes should be tracked.
• □ Using private client or student material carelessly: professional and confidential material needs extra caution.
• □ Publishing with no next step: readers should know where to go after the book.

• □ First-time authors using ChatGPT or other AI writing tools.
• □ Fiction writers building story structure, characters, or worlds.
• □ Nonfiction creators turning ideas into practical guides.
• □ Coaches turning frameworks into books or workbooks.
• □ Educators creating training books or student resources.
• □ Faith-based writers preparing devotional or teaching content.
• □ Practitioners turning original methods into educational products.
• □ Creators using books as part of a larger Shopify or platform path.

• How to Format and Publish Your AI-Assisted Book Without Breaking the Upload — use this after your draft is ready for file preparation.
• How to Publish Your Book on Amazon KDP Without Getting Lost — use this as the main KDP readiness checklist before upload.
• Self-Publishing on KDP, Then Building the Real Business on Shopify — use this when the book needs to connect to an owned platform.
• AI Writing & Publishing Resource Hub — use this to find the right writing, editing, KDP, Shopify, and publishing resource for your current stage.
• AI Copyright for Authors — use this to strengthen your human authorship, source-tracking, AI-use, and rights documentation habits.
• Build and Market AI-Assisted Products From Your Existing Framework — use this if your book comes from a teaching system, method, course, or original framework.
• AI Creator Roadmap — use this to see where writing, publishing, branding, and monetization fit inside the wider creator system.
• The Righteous Beat — use this to stay connected to Jack Righteous updates, systems, and creator strategy.