How does a small press build an editorial calendar?
- An editorial calendar schedules the whole slate, not one book.
- Build it backward from release dates through each production stage.
- Space releases so titles do not compete for the same attention.
- Capacity — staff and budget — caps how many books fit a window.
- The calendar is the press's core planning document.
Build an editorial calendar by setting realistic release dates for each title, then working backward through the production stages — editing, design, proofing, printing, marketing lead time — to place every milestone on a shared timeline. Space releases so two titles never compete for the same launch attention, and check the whole slate against your capacity: the number of books you can actually edit, produce, and market in a window is the real limit.
Chapter i·Why it matters
A small press lives or dies on coordination, and the editorial calendar is where that coordination happens. Without one, releases bunch up, production stages collide, and the team discovers too late that three books need covers the same month. Building the calendar backward from release dates and against honest capacity turns an overwhelming slate into a sequenced plan everyone can work from.
Chapter ii·What to include
- A realistic release date per title.
- Backward-planned milestones through every production stage.
- Spacing so launches do not cannibalize each other.
- A capacity check against staff and budget.
- Marketing lead time built in before each release.
- A shared, single source of truth the whole team uses.
Chapter iii·Example
A four-person press plans six titles for the year. Working backward from each release date, they slot editing, design, and proofing onto one calendar, space the launches at least six weeks apart, and realize two fall books would overload design — so they shift one to winter. The slate becomes a plan instead of a pile-up.
WriteLoom puts your whole slate on one editorial calendar, so releases stay spaced and every title's stages are visible at once.
See WriteLoom for teams