If you're writing two or more books at the same time, you already know the real threat isn't inspiration running dry. It's the practical task that evaporates between projects: proof copies you meant to order three weeks ago, the email to your cover designer sitting in drafts, the KDP categories you said you'd fix before launch. A single cross-book to-do list, kept in one place instead of scattered across notebooks and apps, stops these from becoming recurring launch disasters.
Why separate to-do lists fail multi-project authors
Most multi-book authors start organized: one notebook for Book A, a separate document for Book B, maybe a sticky-note wall for the side project. It works until you're juggling three books in different stages: one in final edits, one with beta readers, one queued for a KDP relaunch. Then the system breaks in a specific, predictable way.
Tasks don't vanish because you forgot they exist. They vanish because you forgot where they live. “Order proof copies” for Book B gets buried in notes for Book C, and by the time you remember it, your launch window has narrowed without the physical books in hand.
Separate lists also hide your real workload. Book A's list looks manageable with four tasks. Book C's list looks manageable with four tasks. Together, they may represent ten open tasks, including two that depend on a designer's response. You only see the total when you open several lists, often after you have already promised too much for the week.
The practical fix is simple: one list for every active project. You do not need a complicated system to get the main benefit. You need one reliable place to add tasks, see what remains open, and mark work complete.
What a cross-book to-do list actually solves
A shared to-do list does three things that per-book lists struggle to do:
- It surfaces bottlenecks across projects. If “email cover designer” for two books remains open for a week, you can see the pattern. Separate lists make that same bottleneck look like two unrelated loose ends.
- It protects launch-critical tasks from getting buried. Ordering proof copies, checking a paperback interior, updating KDP keywords, and following up with beta readers are easy to postpone because they are not drafting. Keeping them beside your other work makes them harder to ignore.
- It gives you an honest picture of your week. Seeing every open task in one view is the quickest way to notice that you have committed to more than you can realistically finish.
This does not replace project planning. A to-do list is not a launch calendar, production schedule, or Gantt chart. It is the working list that answers a narrower question: what still needs doing?
That distinction matters. If a task has a fixed date, such as a preorder deadline or a printer cutoff, put the date in your calendar as well. Use the shared task list to make sure the work itself remains visible between calendar reminders.
How to structure a cross-book to-do list that scales
Put the book name in the task itself
You do not need project tags to keep one list readable. Write enough context into each task that you can understand it at a glance. A simple prefix works well: “Novel A: revise chapter 9,” “Novella B: email cover designer,” or “Novel A: order proof copies.”
This is especially useful when several books are in similar stages. “Check cover” is vague when you have three covers in progress. “Thriller: check paperback wrap against final page count” tells you exactly what to do without opening another project first.
Keep task wording action-based. “KDP” is not a task. “Fantasy novel: paste approved description into KDP” is. “Beta feedback” is not a task. “Mystery: review Dana's comments on chapters 1–5” is.
Separate creative work from operational follow-ups in your wording
“Revise the ending” is a creative task. It needs protected writing time and may take several sessions. “Order proof copies” is operational. It involves a platform, a purchase, or another person, and it can be completed in a short block once you sit down to do it.
Both belong on one list, but clear wording helps you choose what to tackle. Start operational tasks with a direct verb: email, order, upload, check, send, confirm, update, or follow up. Creative tasks should name the scene, chapter, or revision problem so they do not become vague promises to “work on the manuscript.”
If something has an external deadline, add it to your calendar and write the next physical action in the list. For example, instead of “Launch paperback by 15 May,” write “Romance paperback: upload corrected interior” and “Romance paperback: order final proof.” The calendar holds the date; the list holds the work.
Keep completed tasks out of your way
A good task list should show progress without becoming a record of everything you have ever done. Mark tasks complete as soon as they are actually finished. That small habit matters because an open task list is useful only when it reflects reality.
Do not leave completed items unchecked “just in case.” If you may need to revisit something, create a new task that describes the follow-up. “Ask designer for revised spine text” is clearer than treating “email designer” as permanently half-finished.
Review your list weekly, not when you remember
A cross-book list only works if you actually look at it. Set one fixed weekly review: Sunday night, Monday morning, or whenever suits your schedule. Scan every open item across every project.
This is when you catch the task that has been sitting for three weeks. Proof copies and designer emails are classic offenders because they feel like someone else's move. They slip from “waiting on” to “forgotten” without a deliberate check-in.
During the review, either complete, delete, or rewrite unclear tasks. If an item still says “Marketing,” make it specific before the week starts. If it no longer matters, remove it. A short, accurate list is more useful than a long list that makes you feel busy.
Where cross-book tracking fits into your workflow
If you're using Pendrilo, the To-do drawer gives you one cross-book task list no matter which book you are working in. The To-do button is available across authenticated pages, so you can open the same running list while drafting, rearranging chapters, checking book details, or working in Workshop.
Add an item in the input at the top of the drawer. Each task can hold up to 500 characters, which is enough room to include the book name and the next action. When you check an item off, Pendrilo strikes it through and places it below the open tasks. If a task no longer belongs on the list, use the trash can and confirm its deletion.
The same list is per-user and stored server-side, so it follows you across devices. That is useful if you draft on a laptop, check launch details on a desktop, and make notes from your phone. It is still your one list, not a separate list attached to each book.
Each book's Workshop dashboard also shows the open cross-book tasks as its first card. You can tick off completed items directly on that card, and clicking the card opens the full To-do drawer. The dashboard card is not a separate per-book list; it is another way to reach the same shared list while you are already reviewing a specific book's publishing work.
That placement is useful because publishing tasks often arise while you are doing something else. You notice a missing cover file while checking Workshop, add “Cozy mystery: upload final ebook cover” immediately, and return to the task later without relying on memory.
You can pair this with concrete launch preparation. If proof-copy orders keep slipping because you're unsure of trim size or printing costs until the last moment, use Pendrilo's free KDP cover-size calculator or royalty calculator to pin down those numbers early. Knowing the specs before you need them removes one reason a task sits untouched for weeks.
A simple weekly rhythm
If you want structure rather than building one from scratch, try this rhythm:
- Monday morning: Open the list and scan every open task across every book. Rewrite vague items so each one names the next action. Put any fixed-date commitments into your calendar if they are not there already.
- Daily: Pick two or three tasks to move forward. Mix creative and operational work so a designer follow-up or KDP update does not sit untouched for a full week. Mark completed work off immediately.
- Friday afternoon: Do a quick check for external dependencies. Is there anything you need to send, order, upload, or confirm before the weekend?
If you receive beta-reader feedback, you can also turn a useful comment into a linked task from Pendrilo's Revision inbox when that feature is available. The task points back to the original feedback rather than copying it, which helps you keep the reader's note and your action item connected without cluttering the manuscript.
The system does not need to be clever. It needs to be one place, checked consistently, that does not let a launch-critical task hide behind a more interesting creative one.
Getting started without overengineering
You can start with a simple spreadsheet, a note app, or even a paper list if that suits your style. The format matters less than the habit: one list, clear task wording, and a weekly review.
As you add books, resist the urge to turn task management into another project. You do not need elaborate categories, color systems, or a perfect schedule before you can benefit. Start by moving every open task from your separate notes into one list. Then make the next action clear enough that you could do it without rereading an old email thread.
If you're juggling multiple manuscripts and want your task list alongside your drafts and publishing work, Pendrilo keeps the shared To-do drawer one click away throughout the studio. New accounts include a seven-day trial with one book and 3,000 cumulative manuscript words; multi-book workflows require paid access. You can start the trial without a credit card or automatic conversion to a paid plan.
