What is a publishing workflow?
- An ordered sequence from finished manuscript to live retailer listing.
- Canonical sequence: 10 stages from developmental edit through launch.
- The order matters — running steps backwards forces redo work.
- Total workflow length: typically 6-12 months for a traditionally-edited indie book.
- Most workflow failures happen at handoff points between stages.
A publishing workflow is the ordered sequence of tasks that takes a finished manuscript to a published book on retailer dashboards. The canonical sequence is: developmental edit → line edit → copy edit → proofread → cover design → interior layout → metadata setup → retailer upload → ARC distribution → launch. Skipping a step or running steps in the wrong order produces avoidable launch failures.
Chapter i·Why it matters
Authors who treat publishing as one task miss the dependencies between stages. The interior layout cannot start until the manuscript is final; metadata cannot go to ONIX until the ISBN is assigned; ARCs cannot ship until the cover is final. A workflow names the dependencies so you can plan the calendar realistically — and identify the actual critical path.
Chapter ii·What to include
- Developmental edit (4-8 weeks).
- Line edit (4-6 weeks).
- Copy edit (3-5 weeks).
- Proofread (1-2 weeks).
- Cover design (4-8 weeks, can run parallel with edits).
- Interior layout (2-4 weeks, after copy edit).
- Metadata setup (1-2 weeks, before launch).
- Retailer upload (1 week, T-30 from launch).
- ARC distribution (T-60 to T-30).
- Launch week and 30-day post-launch QA.
Chapter iii·Example
A self-publishing author maps her 80,000-word thriller’s workflow before drafting begins. She knows her August launch requires copy edit complete by April, line edit by February, developmental complete by December. Drafting back-plans from there to a January start the year before. The book ships on schedule because the workflow named the deadlines a year in advance.
WriteLoom’s Sell studio holds the publishing workflow — every stage with its dependencies and deadlines — so handoffs don’t get dropped.
See the Sell studio