Tracking Chapter Deadlines in a Scanlation Group

Readers notice a scanlation group's schedule before they notice its quality. A weekly release that slips to "whenever" loses readers faster than a typo does. Yet most groups track deadlines with a single date per chapter — and that date tells you almost nothing until it is already missed.

Put deadlines on steps, not only on chapters

"Chapter 42 is due Friday" is a promise nobody in particular owns. The translator thinks there is time because typesetting is the long step; the typesetter cannot start until both tracks are done. By Thursday everyone is waiting on everyone.

Work backwards from the release date instead:

Step	Typical share of a chapter's time
RAW sourcing	short, but blocks everything
Translation + proofreading	runs in parallel with the art track
Cleaning + redraw	runs in parallel with the text track
Typesetting	starts only when both tracks finish
QC	short, but needs a free slot

Give each step its own date, and make the date the end of that day in your group's time zone. "Due Wednesday" should mean Wednesday 23:59 for everyone, not "Wednesday somewhere".

Measure waiting, not just lateness

A deadline tells you when something is late. It does not tell you that a chapter has been sitting on a step for six days with nobody touching it. Waiting time is the early warning; lateness is the post-mortem.

Two numbers are worth watching for every chapter:

1. Which step it is on — the obvious one.
2. How long it has been there — the useful one.

If cleaning normally takes two days and a chapter has been in cleaning for five, you know before the deadline that something is wrong: the cleaner is busy, stuck on a hard redraw, or gone.

Remind the right person, once

Nagging the whole Discord channel trains people to mute it. A reminder should go to one person — whoever holds the step — and only when there is a reason: the previous step just finished ("it is your turn"), the deadline is close, or the chapter has stalled.

A simple rhythm that volunteer teams tolerate:

• When a step finishes: notify the next person directly.
• Three days and one day before a deadline: a quiet personal reminder.
• When a chapter has not moved for two weeks: escalate to the person who assigned it, because at that point it is a staffing problem, not a memory problem.

Plan for the person who disappears

Every group eventually has a member who stops answering. The fix is not a stricter deadline; it is making reassignment cheap. If a step can be handed to someone else in a minute, with the files already attached, a disappearance costs a day instead of a chapter.

Doing this without a spreadsheet

You can run all of the above in a spreadsheet with a "last moved" column and a lot of discipline. The usual failure is that the discipline lives in one person.

In FansubPanel, deadlines are stored as end-of-day dates in one time zone, every member sees their own queue with deadlines in "My Tasks", the next person is notified automatically when a step finishes, and a chapter that has stayed on the same step for 14 days triggers a reminder to whoever holds it. The workflow guide explains the steps those dates attach to.