Prepare a submission-ready manuscript
Join the waitlist to test SagaScope and secure coherence before export.
Quick answer (if you only read this)
Before submitting a manuscript, you want three things:
- A readable document (clean layout, identifiable chapters and titles).
- A coherent text (fixed facts, timeline/chronology, social coherence).
- A reliable export (DOCX for iteration, EPUB/PDF for final presentation).
This guide gives you a full migration + export workflow with checklists and frequent mistakes.
The goal isn’t to turn your novel into a product.
The goal is to protect your work from “end of process” mistakes: broken headings, timeline inconsistencies, relationships that evolve without proof, or scenes that stop paying arc promises.
Why export errors usually appear at the end
Halfway through, your manuscript is alive. You correct continuously.
Then comes “I need to send it”:
- you lock the formatting;
- you convert to a final type of file;
- you reread faster;
- you use different tools;
- you take fewer margins and less time.
That’s where mistakes show up:
- a chapter isn’t separated correctly;
- time references no longer match the latest version;
- names are “almost identical” (nickname variants, spelling differences);
- social continuity feels broken (“they already know each other” without paying proof).
Export is a lock, not just a rendering.
Migration: what you really gain (beyond storage)
Migrating to a modern writing workflow isn’t a luxury.
You gain the ability to control coherence earlier.
Instead of discovering incoherence at the final PDF stage, you can:
- verify chronology and timeline;
- verify narrative promises;
- verify relational anchors.
That’s how coherence becomes stable on long novels.
For the underlying memory challenge, see:
Migration workflow (Word / Scrivener / Docs) in 7 steps
Step 1 — Make your manuscript “importable”
Before import:
- keep distinct chapter titles;
- avoid random line breaks inside headings;
- keep a readable hierarchy even while drafting.
You reduce the risk of a badly reconstructed structure.
Step 2 — Lock your anchors (names + time markers)
Do a quick pass:
- proper name spelling;
- nickname variants (if you use them, decide and stabilize);
- relative time markers (day/night, seasons, “two months later”).
These are facts that must remain stable across the novel.
Step 3 — Import and keep your narrative base aligned
After import, your narrative base should reflect your manuscript up to date.
Your priority isn’t “enter everything manually.”
Your priority is to be able to request reliable verification when a key scene arrives.
Step 4 — Use chronology to fight “I forgot”
One of the best uses during migration: timeline validation.
When chronology holds, incoherences reveal themselves immediately (ages, seasons, travel durations).
See:
Step 5 — Verify relationships like a network (not like a list)
On choral/political novels, relationships aren’t boxes.
They evolve.
That’s why the graph becomes a powerful revision tool:
- bridges,
- holes,
- and credible progression.
See:
Step 6 — Fix before locking the format
Best rule: don't lock formatting until coherence is validated.
If you export and then correct a chapter, you must rerun the same checklists.
Step 7 — Prepare final export by format
DOCX, EPUB and PDF each have their mission.
Then you apply a “format” checklist (below).
Coherence checklist before export (do it every time you lock)
Run a quick pass (20–40 minutes) before converting:
- Fixed facts: appearance, identifiers, major rules.
- Chronology: ages, dates, durations, flashbacks.
- Social coherence: who knows what, and how links evolve.
- Arc promises: what you make the reader believe must be paid off (proofs, costs, consequences).
Then export.
For deeper coherence methods, connect to:
DOCX: the working format (and common mistakes)
DOCX is for:
- reading;
- annotating;
- correcting;
- iterating.
Common mistakes:
- headings not separated;
- inconsistent styles (table of contents breaks);
- pagination “visual” mismatch with the narrative structure.
Before DOCX final export:
- validate chapter structure;
- check the table of contents if you generate it automatically.
EPUB: digital publication (and fewer surprises on reflow)
EPUB is often appreciated because it:
- adapts better on mobile;
- reflows smoothly.
What to verify:
- structure (chapters/sections);
- clear separation;
- compatibility of headings and anchors.
Tip: if you still expect editorial feedback, keep DOCX as your master file and export EPUB snapshots only when ready.
PDF: “frozen” submission (preview, navigation)
PDF is useful for:
- sending to editors;
- previewing the final look;
- producing a version that won’t shift.
Common mistakes:
- incorrect table of contents;
- weird word breaks;
- odd pagination on small screens.
Before generating your final PDF:
- preview on mobile-like sizes;
- check readability (margins, title sizes).
Examples of what editors really expect
Requirements vary, but the foundation stays:
- readable and clean text without conversion artifacts;
- clear structure (title/chapters/anchors);
- reasonable Internal coherence (names, time references);
- a navigable document (you can understand where you are).
They don’t need perfect design.
They need reliability and clarity.
Genre matters: romance, SF, fantasy and coherence ROI
- In romance, believable relationship step progression depends on time coherence and social knowledge (“who knows what, when, and why”).
- In SF, system coherence (logistics, deadlines, rules) turns a cool idea into a believable book.
- In fantasy, rule coherence (magic constraints) protects tension and prevents “arbitrary” solutions.
So no matter the genre, a coherence checklist is a profitable investment.
Common mistakes (and how to avoid them right after migration)
- Correcting style but not facts: prose improves while incoherence remains.
- Exporting too early: you lock an inconsistent state.
- Changing a magic rule without ripple effects: the scene becomes a “free exception.”
- Ignoring timeline with flashbacks: romance pacing may feel off, magic may become too convenient.
- Letting name variants drift: spelling/nickname changes become bombs.
Workshop: a submission-ready pass in 60 minutes
If you need to submit this week, here’s a realistic pass without perfectionism.
1) Structure (15 minutes)
- Does every chapter have a unique title/anchor?
- Are separations obvious (page breaks/sections)?
- Are “bonus” parts clearly marked (prologue/epilogue)?
2) Coherence (25 minutes)
Do three micro-passes:
- Fixed facts: names, spelling, appearance anchors, major rules.
- Time: relative markers, travel durations, ages, seasons.
- Social: who knows what at each reveal—and how information travels.
3) Export & preview (20 minutes)
- Export DOCX (master) + PDF (preview).
- Preview PDF on a narrow/mobile-like width.
- Check: headings, breaks, table of contents (if present), margins.
Result: you eliminate most end-of-process mistakes.
Editor checklist: what makes reading faster (or slower)
Editors don’t only read prose.
They also read:
- navigability (where am I? which chapter?);
- anchor stability (names, time, relationship progression);
- lack of artifacts (broken headings, empty pages, inconsistent styles).
Checklist:
- Clear main title + consistent chapter headings.
- No scene “jumps” without a visible break.
- Stable proper names (same spelling everywhere).
- Understandable time jumps (even if implicit).
Typical case: EPUB looks fine, PDF looks weird
Why:
- EPUB reflow can hide structure problems;
- PDF exposes breaks, whitespace, and style inconsistencies.
Fix:
- fix structure first (headings/sections);
- re-export;
- re-check PDF (it’s the most unforgiving format).
Workshop: stabilize proper names (and remove “time bombs”)
On long novels, the most frequent variants:
- accents (Élise/Elise),
- apostrophes/spaces (d’Argent/d Argent),
- nicknames (Alex/Alec),
- transliterations (Khaël/Duncan).
Fast method:
- pick one canonical spelling.
- list 10 high-risk names (characters + places).
- normalize those 10 everywhere (this fixes most issues).
Workshop: export without losing structure (chapters/scenes)
Before exporting, verify three things:
- every chapter starts clearly (heading + visible separation),
- scenes are separated consistently,
- non-novel parts (acknowledgements, notes) are isolated.
If you do only one thing: make the structure navigable.
Per-format checklist (tickbox style)
DOCX (revision / feedback)
- consistent heading styles
- page breaks at chapters (or visible separation)
- no broken line breaks/double spaces
- table of contents (if used) correct
EPUB (reflow reading)
- headings recognized as headings (navigation)
- no accidental merged scenes
- no footnotes that break flow
PDF (submission)
- stable pagination
- readable headings
- margins ok (desktop + mobile)
- no blank pages / orphan headings
Case study: your manuscript “works” in Word but breaks in export
This happens all the time.
Scenario
- In Word/Docs, you used manual formatting (bold + font size) instead of heading styles.
- You separated chapters with multiple blank lines instead of a consistent page break or heading.
- You pasted scenes from multiple sources (Google Docs, Scrivener compile, email notes).
Result:
- EPUB navigation is broken (no chapters in the TOC),
- PDF shows weird spacing and orphan headings,
- the editor can’t quote passages reliably (“which chapter is this?”).
Clean fix (minimal effort)
- Convert chapter titles to real headings (consistent hierarchy).
- Insert a visible chapter separation rule (page break or consistent divider).
- Remove “double blank line” hacks and replace with structure.
If you do this once, every export becomes easier.
“Submission-ready” checklist (what editors notice first)
Editors will forgive a lot.
They won’t forgive friction.
They notice:
- can I navigate?
- are anchors stable?
- does the document look like it was converted cleanly?
Checklist:
- Chapter titles are consistent and easy to spot.
- No accidental duplicate chapter numbers/titles.
- Names are stable (same spelling every time).
- Time jumps are readable (even if subtle).
- No scene is “floating” without a clear break.
Genre lens: how export mistakes hurt you differently
Romance
The most damaging “export” mistake is often coherence, not layout:
- relationship steps look inconsistent because the timeline anchor got lost,
- chapter breaks remove the rhythm of emotional progression.
SF
The most damaging mistake:
- technical terms / names drift across versions (spelling variants),
- time/distance references become contradictory after edits.
Fantasy
The most damaging mistake:
- proper nouns drift (places, titles),
- magic rules feel inconsistent because a key proof scene got moved without re-anchoring.
Extra appendix: what to do when requirements are unclear
Some publishers say “send a PDF.” Others say “send DOCX.”
If the requirements are unclear, your safest workflow is:
- keep a clean DOCX master (for edits and comments),
- produce a PDF snapshot (for stable preview),
- optionally produce an EPUB snapshot (for mobile reading).
Then ask one clarifying question (if you can): “DOCX or PDF preferred for annotation?”
“Last mile” sanity checks (5 minutes each)
Quick scan 1: headings and separation
- Do chapters start on clean boundaries?
- Any orphan title at the bottom of a page?
- Any merged chapters?
Quick scan 2: names and typography
- Proper nouns consistent (spelling, accents)?
- Quotes consistent (“ ” vs " ")?
- Any repeated double spaces or broken paragraphs?
Quick scan 3: timeline anchors
- “Two days later” still matches the current draft?
- Any age references that conflict with earlier anchors?
These scans catch most submission-breaking mistakes.
Troubleshooting: the 8 most common export artifacts
1) Broken chapter hierarchy (no TOC entries)
Cause: manual formatting instead of real headings.
Fix:
- convert chapter titles to real heading levels;
- keep a single hierarchy (H1 for title, H2 for chapter, H3 for scene if needed).
2) “Merged scenes” in EPUB
Cause: separators are visual only (blank lines) and get reflowed.
Fix:
- use a consistent divider or heading;
- ensure each chapter is its own section.
3) Orphan headings in PDF
Cause: page breaks happen automatically and push a title to the bottom.
Fix:
- insert page breaks before chapters;
- adjust spacing rules (avoid huge “before heading” spacing).
4) Smart quotes, apostrophes and encoding weirdness
Cause: copy/paste from multiple sources, mixed locales.
Fix:
- normalize quotes and apostrophes once;
- do a fast scan on a PDF snapshot.
5) Line breaks that turn into “staircase paragraphs”
Cause: hard line breaks inside paragraphs (from email, PDFs, some exports).
Fix:
- remove hard breaks and keep real paragraphs;
- re-export and re-check.
6) Footnotes/endnotes that destroy flow
Cause: notes are used as story content rather than references.
Fix:
- move essential information into the text;
- keep notes as truly optional.
7) Inconsistent scene markers
Cause: three different separators used across the manuscript.
Fix:
- pick one marker (blank line + symbol, or heading) and standardize it.
8) Name variants that slip back in
Cause: edits across versions (DOCX vs PDF) without canonical list.
Fix:
- maintain a canonical list (10–20 key terms);
- normalize before your final export.
Mini-plan: what to do if you only have 30 minutes left
If the deadline is brutal:
- Export a PDF snapshot.
- Scan headings/separation (2 minutes).
- Scan first 3 chapters + last 2 chapters for name variants (10 minutes).
- Scan for orphan headings and weird spacing (5 minutes).
- If anything looks broken, fix structure first, then re-export.
This is not perfect—but it prevents avoidable rejections.
FAQ
What’s the best format before submitting?
Typically DOCX for revision and iteration. Then EPUB/PDF depending on the request.
How do I avoid export breaking coherence?
Run a coherence pass before export: fixed facts, chronology and social coherence.
Why do chapters have to be clear?
Because editorial navigation depends on structure. Both editor and reader need to know where they are and how to connect anchors.
Do I need to migrate if I’m already in Word?
Not strictly. But for long novels, a narrative base approach can make coherence checks more reliable.
Keep this framework handy
Get SagaScope early access + writer templates — one email, no account required.
Ready to structure your novel?
Join the SagaScope waitlist. Founder perk: locked pricing + AI credits at launch.
Frequently asked questions
- What’s the best format to revise before sending?
- DOCX is usually the most practical for revision and annotations. EPUB/PDF are for final presentation, depending on what’s requested.
- How do I prevent export from breaking coherence?
- Do a final « coherence » pass before exporting: fixed facts, timeline/chronology, social coherence and arc promises. A narrative base aligned with your manuscript reduces omissions.
- What if my titles/chapters are poorly structured?
- Before submission, make structure readable: consistent headings, clear chapter separation, stable numbering/anchors. Editors need to navigate quickly.
- Do I need to migrate if I’m already writing in Word?
- Not necessarily. But migrating to an approach with a narrative base can make long-novel coherence checks more reliable.
SagaScope Team
The team behind SagaScope, passionate about writing and technology.
Similar articles
Export DOCX, EPUB, PDF: how to prepare your manuscript for editors
Method and checklist to export your novel as DOCX, EPUB and PDF: internal coherence, formatting, chapter structure and what editors typically expect.
Prepare your manuscript for Amazon KDP: pre-publish checklist
Narrative coherence, KDP metadata, EPUB/DOCX export, SagaScope → Vellum/Atticus workflow and common post-upload errors.
Migrating from Google Docs/Word to a dedicated writing tool
Migration guide from Google Docs or Word to a dedicated writing tool: preserve chapters, rebuild a narrative base, and keep coherence with Auto-Codex.
