Plan a self-publishing project in stages

Define the edition you are making

A self-publishing plan begins with a particular product, not a list of platforms. Decide what the reader will receive: a paperback, hardback, ebook or some combination. Describe the intended audience, approximate extent, use of colour or illustrations, and any special requirements such as an index or workbook space. These choices shape the work and the budget.

Separate the first release from possible later formats. Planning a paperback and ebook together may be sensible, but an audiobook or illustrated edition need not enter the same schedule simply because it might eventually exist. Each additional format brings its own files, checking tasks and distribution decisions. A bounded first project is easier to manage accurately.

Record the current state of the manuscript. A complete draft, an edited manuscript and an approved proof are different starting points. If structural questions remain, leave room to resolve them before paying for layout that may need substantial reworking. The plan should reflect the actual book, including unfinished research and permissions, rather than an idealised version ready for upload.

Put decisions before dependent work

Arrange stages by what they need from earlier stages. A cover designer needs a brief and format information. A print cover's spine depends on the final production specification, including page count and paper. An index needs stable pagination. An ebook needs its own inspection rather than automatic approval because the print pages look right.

Some work can proceed together. You can research production options while editing, or prepare a cover concept before the final page count exists. Mark provisional elements clearly so nobody treats them as approved specifications. Parallel work saves time only when later changes are anticipated and responsibilities remain clear.

Include decision points rather than just delivery dates. After structural editing, approve the shape of the text. After layout, inspect a proof. After corrections, verify the changes. These points make it possible to stop a faulty file moving downstream. A schedule that contains no time for decisions assumes that every first delivery will be final.

Assign the work and define the handovers

For each task, record who does it, what they receive and what they return. If you commission help, describe the scope and the number or form of revision rounds. “Design the book” can mean very different things to different people. Specify whether the work includes print files, ebook files, editable source files, cover variations and later corrections.

You may undertake some tasks yourself, but allow time to learn the tools and verify the results. Familiarity with writing software does not automatically cover print-file preparation or ebook behaviour. Test a small representative sample before committing the entire manuscript to a process you have not used before.

Keep one authoritative file at each stage and archive milestones. A simple project record should identify the approved text, current layout, cover version and unresolved questions. If a change affects more than one format, record every place that needs updating. Otherwise the ebook can retain an old correction while the paperback moves ahead.

Budget for completion and correction

Obtain quotations based on the actual scope. Include editorial work, design, production, proofs, shipping and any specialist tasks. Distinguish costs incurred once from costs attached to each copy sold. Leave a defined allowance for corrections and unexpected work instead of assuming the first quoted total is the final cash requirement.

Plan how copies will reach readers. Print-on-demand, a stock order and direct sales each create different operational tasks. Consider who handles orders, storage, fulfilment and enquiries where those apply. Availability through a channel does not remove the need to tell suitable readers that the book exists.

Choose a publication date only after the dependent work is visible. Build in time to inspect the final files and physical proofs, resolve defects and confirm listings. If the project is tied to an event, work backwards from the date copies must actually be available, not merely the day you hope to press a publish button.

Leave a record for the next edition

At release, save the approved files, specifications, metadata and account records in an organised archive. Record the exact version used for each format. Keep a separate correction log for later discoveries rather than editing archived release files silently.

The project is easier to maintain when publication is treated as a documented milestone. You can then assess an update, reorder or new format using the decisions already made, instead of reconstructing the production process from old attachments.