Planning a comic localization pipeline is deceptively hard. On paper it looks like any other project: a list of chapters, a delivery date, a team. In practice, a single slip anywhere upstream cascades through everyone downstream. If translation runs a day late, the proofreader starts late, the letterer sits idle, and the whole chapter derails. The schedule that looked comfortable on Monday is quietly on fire by Thursday.

This guide walks through why comic pipelines behave differently from generic projects, why the usual project tools mislead you, and a concrete method for planning one that actually holds up.

Why comics are not a normal project

The most important difference is the unit of work. In a generic project the unit is a task. In comic localization the unit is the page. Pages flow, one by one, through an ordered set of stages: translation, proofreading, cleaning, lettering, QA, and delivery. A chapter is not "done at 100 percent" as a single lump. It is a stream of pages, each at a different point along the line.

Three properties make this genuinely different to schedule:

Stages depend on each other. Lettering cannot start on a page before cleaning has finished it. Proofreading cannot start before translation. Downstream can never overtake upstream.
Throughput is per person and per language pair. A translator might comfortably clear a certain number of pages a day for Japanese to English, and a very different number for Japanese to French. A letterer's daily rate has nothing to do with the translator's. Every person has their own real, sustainable pace.
The work is tied to art files. Pages are images with their own properties. The schedule and the files are the same thing, not two systems you reconcile by hand.

Why generic project tools break

Gantt charts and Kanban boards are built to track tasks, and that is exactly where they fall short here.

They track tasks, not pages, so they cannot reason about a chapter as a flowing stream.
They have no concept of a person's real daily capacity, let alone one that changes by language pair.
They cannot gate a stage by actual completion of the stage before it. A card can be dragged into "lettering" while cleaning is only half done.
They know nothing about the art files, so the plan and the work drift apart.

You can force a comic pipeline into a board, but you end up maintaining the illusion of a schedule by hand, and the illusion is what breaks on the day it matters.

The method

Here is the core, and it works whether you do it on a whiteboard or in software.

Estimate each worker's capacity. For every person, record pages per day, per language pair. This is the single most important input, and it is the one generic tools throw away.
Set the calendar. Define your company working days and holidays. Capture each person's leave. For freelancers, capture their outside commitments too, since their available hours are not yours to assume.
Auto-fit pages to available capacity. Distribute the chapter's pages across each person's real daily capacity, stage by stage, instead of assuming everyone is infinitely available.
Gate the stages. Ensure no stage starts before the one before it finishes, and keep a deliberate buffer between translation and lettering so a small slip early does not starve the back half of the line.
Work backward from delivery. Derive per-stage deadlines from the delivery date, then look for any stage whose fitted schedule would miss it. That is your early warning, weeks ahead instead of days.
Watch overallocation across everything. A person is not free just because one project has room for them. Check load across all projects at once, and for freelancers, across all the companies they work with.
Plan tentatively, then commit. Draft the whole plan without booking anyone. Only once it holds together do you commit it, which books the work and sends freelancer offers. Planning and committing should be two separate, deliberate acts.

Done in this order, the plan tells you the truth early: it is either feasible with the people and days you have, or it is not, and you learn that while you can still fix it.

Where Zfuro fits

This is precisely what Zfuro's capacity planning is built to do. It models each worker's throughput by language pair, respects working days and leave, auto-fits pages across gated stages, derives deadlines backward from delivery, and surfaces overallocation across every project and, for freelancers, across every company. Because it is a full planning and full production system in one place, the plan and the actual page work never drift apart. If you want the mechanics in detail, see how planning works, along with the production workflow and team roles and freelancers.

The takeaway

A comic pipeline is a dependency chain of pages moving through people who each work at their own real pace. Plan it as a task list and the misses stay hidden until they cascade. Plan it around per-worker capacity, gated stages, and deadlines derived backward from delivery, and the schedule tells you the truth while you can still act on it.