Re-export After Edits Checklist

Late edits are normal. The safe pattern is simple: treat each export as a release candidate, validate high-risk pages first, fix at source, then upload only one latest verified file.

Treat every post-edit export as a new release candidate

After meaningful manuscript edits, generate a new export instead of reusing older files.

Use versioned names like `book-v18-rc1.pdf` and `book-v18-rc1.epub` so your release notes, checks, and upload candidates stay in sync.

A versioned candidate log prevents stale-file uploads near launch day.

Review high-risk pages before full-document scrolling

Start with chapter openings, scene transitions, and page-before-chapter boundaries.

After structural edits, verify front matter and back matter order plus TOC destinations before deep visual review.

This risk-first pass catches most late-edit regressions quickly.

Run validation checks by output type

For print-ready PDF updates, run KDP Print Previewer and clear warning-level blockers first.

For EPUB updates, run validation checks and click each TOC entry to confirm navigation targets.

Do not consider a candidate final until both format-specific checks pass.

Fix source content, not final artifacts

When defects appear, edit manuscript source structure or style settings and re-export.

Avoid patching final PDF/EPUB files as a normal workflow. Those patches are easy to lose on the next export.

Source-first fixes keep future revision cycles stable.

Lock setup near publish and record the exact passed file

Avoid trim-size, margin, and typography changes late unless required.

If setup changes are unavoidable, run one full re-export plus validation pass before upload.

Record the exact file version that passed checks and upload only that artifact.

Numbers and Reference Tables

Late-edit re-export risk matrix

Change type Highest-risk breakage First validation pass Final sign-off proof
Text edits inside existing chapters Page-flow drift near chapter transitions Preview chapter-open pages and page-before-chapter pages One screenshot set from affected chapter boundaries
Front/back matter reordering TOC target mismatch and pagination shifts TOC click-through plus section-order check TOC pass screenshot and final order note
Image or bleed changes Trim/bleed warnings and edge cut-off risk Run print Previewer bleed checks first Before/after warning panel screenshots
Typeface or style changes Font substitution and line-wrap movement Font embedding check + chapter-open spot check Font-properties screenshot for final candidate

Publish Checklist

  1. Edit source manuscript and record change scope in release notes.
  2. Export fresh PDF/EPUB/DOCX with a new release-candidate version name.
  3. Run print Previewer checks for PDF candidates.
  4. Run EPUB validation and TOC click-through checks for EPUB candidates.
  5. Inspect chapter-open and transition pages before full-manuscript scrolling.
  6. Inspect front/back matter order after structural edits.
  7. Fix source content/settings only; do not patch final artifacts.
  8. Re-export and rerun checks on the newest candidate.
  9. Confirm warning counts and high-risk pages are clean.
  10. Upload only the latest verified release-candidate files.

Warning-to-Fix Map

Warning pattern: issue appears fixed but still shows in checks

Fix: Confirm you are validating the newest release-candidate file, not an older similarly named artifact.

Verify: Latest version name appears in validation tool and warning count reflects recent fixes.

Warning pattern: TOC targets changed after small edits

Fix: Normalize heading structure and regenerate TOC from corrected source content.

Verify: Each TOC entry lands on the intended section in order.

Warning pattern: chapter starts moved unexpectedly

Fix: Lock trim/margins/type settings and remove hidden page-break artifacts before re-export.

Verify: Chapter-start sequence matches release notes in final candidate.

Warning pattern: repeated regressions after each revision

Fix: Use one source-of-truth manuscript and one candidate naming convention across team/editor workflow.

Verify: Regression count drops and each fix references one canonical candidate version.

Proof Checks

Release-candidate evidence packet

  • Store warning-panel screenshots with page numbers for each resolved blocker.
  • Store one TOC click-through screenshot set for EPUB candidate.
  • Store one final clean-check screenshot per output type before upload.

The Senswriter way (faster)

Use the same workflow in one workspace: draft, export, run checks, fix source, and publish one clean release-candidate file.

Open the Senswriter Workspace and see export examples.

Frequently Asked Questions

Do I need to re-export after every manuscript edit?

Re-export after any meaningful edit that could affect structure, pagination, TOC targets, or typography. Small typo edits can often be batched into one candidate pass.

Can I patch the final PDF and skip source fixes?

You can patch files in emergencies, but source-first fixes are safer and prevent repeat defects on the next export.

What is the minimum safe validation pass before upload?

At minimum: preview high-risk chapter transitions, clear warning blockers, and confirm TOC/navigation behavior for the latest candidate file.

Sources and Claim Checks