# Check ebook coherence and facts before publishing

Use project-level coherence review and factual checks to catch contradictions, repetition, and unsupported claims before export.

Canonical: https://www.scribora.ai/docs/workflow/coherence-and-fact-checking
Category: Workflow
Last reviewed: 2026-09-29

## Chapter quality is not book quality

Ten individually readable chapters can still make a poor book if they repeat the same lesson, contradict each other, change terminology, or introduce prerequisites after they are needed. Pro-quality projects can use coherence-oriented review across the manuscript rather than judging each chapter in isolation.

## Fact checking still needs judgment

Automated factual review can identify and correct many risky claims, but it should not be treated as a guarantee. Before publication, manually inspect claims with legal, medical, financial, scientific, reputational, or rapidly changing consequences.

- Check numbers and dates against the underlying source.
- Keep opinion and evidence clearly separated.
- Verify named people, companies, studies, and quoted claims.
- Re-check facts that were current when the source was collected but may have changed since.

## Fact checking and plagiarism checking are different systems

Pro fact checking is part of the generation pipeline: it compares factual claims against source excerpts available to the chapter and can run an automatic correction pass when problems are found.

The plagiarism scan is a separate review/publishing tool. It measures similarity against the project's internal source material and, when the web check is available, external web matches. Its result can be Original, Checked, or Needs review; it does not certify factual truth.

## Know the limit of source-grounded fact checking

The automated fact-check step only has evidence when source excerpts are available. A claim outside that evidence can still require manual verification even when the Pro pipeline completed successfully.