What is a canonical manuscript?
- The single file treated as the current, authoritative version.
- All edits land on it; all other copies are snapshots or drafts.
- Prevents version confusion when multiple people touch a book.
- Usually marked clearly and stored in one agreed location.
- The opposite of "final_v3_REAL_final_USE_THIS.docx".
A canonical manuscript is the single file treated as the current source of truth for a book — the one version everyone edits and the one that ultimately ships. Every other copy is a snapshot, an export, or an old draft. Naming one file canonical is how teams avoid two people editing different versions and merging conflicting changes later.
Chapter i·Why it matters
The most common and costly book-production error is version confusion: an editor marks up one copy while the author rewrites another, and changes get lost merging them back. Designating a canonical manuscript — one agreed file, one location — removes the ambiguity. Everyone knows which file is live, so edits accumulate in one place instead of forking.
Chapter ii·What to include
- One file explicitly marked as canonical.
- A single agreed storage location.
- A rule that edits land only on the canonical copy.
- Dated snapshots for history, never edited directly.
- A clear handoff process when control passes between people.
- Exports (PDF, EPUB) treated as outputs, not the source.
Chapter iii·Example
A co-author duo names one cloud file the canonical manuscript. Each writes in tracked changes on that file rather than passing copies back and forth. When their editor takes over, she works on the same file — so nobody ever has to reconcile two diverging versions.
Chapter iv·Related questions
WriteLoom holds one canonical manuscript per project, so everyone edits the same source — no merge conflicts.
See the Write studio