Magazine production workflow:
who keeps the status?
· 8 min read

Andrey KovlyaginFounder of Chains. In print since 2004.
Story’s in copyedit. Story’s in layout. Story’s in proofreading.
At our weekly newspaper, people did the work, then reported it in chat so the production editor could update a spreadsheet. Each story took 10–12 messages like these. And after every one, the production editor went to a Google Sheet and copied the status over by hand, so everyone could see what was on fire.
It worked fine. Nothing ever blew up badly enough, so nobody fixed it. But I watched it for years and kept thinking: why do I have to write “done” when I’ve already done it?
Hi, I’m Andrey. I’ve worked in print since 2004. From 2011 to 2017 I was at a corporate newspaper, first as a layout designer, then as lead designer. The paper came out every two weeks at first, then weekly: 16 pages, plus specials and regional supplements, sometimes up to 40 pages a week. From 2013 to 2022 I laid out corporate magazines, in the office and remotely. I’ve produced books too. Now I’m a developer.
The stages of producing an issue
Here are the stages a story goes through:
- Writing
- Editing
- Copyediting
- Layout
- Proofreading
- Corrections
- Sign-off
- Prepress
- Printing
The list can be longer or shorter. It can be linear, or it can branch: the same text may go to print and to the website.
Where does the status of an issue live, and who pays for it?
Newspaper: Trello, a Google Sheet and a production editor
A weekly corporate newspaper, 16 pages, sometimes up to 40 because of specials running in parallel. In the office.
- Team
- 15 people
- Planning
- Weekly editorial meetings covering this week and the ones ahead.
- Tools
- Trello for content (copy, photos), a spreadsheet for status, Slack for communication, a file server.
- Status
- The production editor. Every story was reported in Slack, about 10–12 messages per story. On a busy day that could mean up to 60 messages about status alone.
- What worked
- One source for content, deadlines visible in the spreadsheet.
- The cost
- To keep everyone in the loop, one person checked Trello and Slack every day and copied the state into the spreadsheet.
- A detail
- The funny part is that we didn’t use Trello as a kanban board. Each column was an issue, and the leftmost column was the story backlog.
Fewer people, fewer messages. But the problem didn’t go away. It moved into one person’s head.
Magazine: one head
A corporate magazine, 10 issues a year, 64 pages each. Remote.
- Team
- 5 people
- Planning
- One person, who kept it all in his head.
- Tools
- Google Sheets, a chat, file sharing.
- Status
- The editor-in-chief’s head.
- What worked
- Everything. And it worked well.
- The cost
- He couldn’t afford to get sick.
- A detail
- How did I know it was time to start layout? A message from the editor would land in the group chat: “Look, it’s there now.” The downside was that I never knew what might arrive tomorrow, because the plan and the information weren’t shared.
And if the team is really small? Then you keep the status yourself.
Book: a spreadsheet and Zoom
A music theory textbook, 184 pages.
- Team
- Two authors and me.
- Planning
- The authors had the vision; they also supplied the manuscript and the ideas for the illustrations.
- Tools
- Google Sheets and Zoom calls.
- Status
- A spreadsheet. Chapter | illustration (version) | text (version).
- What worked
- I could check the spreadsheet and point out that one illustration had only been done once, so it was worth asking whether we’d forgotten about it.
- The cost
- I kept the status myself, alongside my actual job.
- A detail
- “There will be no final.” The higher the version number, the closer we were to the result.
The scale differs, the pattern doesn’t. People do the work, then report on it separately. One person holds the whole picture. The only thing that changes is where the status lives.
| Newspaper, ~15 | Magazine, 5 | Book, 3 | |
|---|---|---|---|
| How we tracked | Trello + spreadsheet + Slack | One head + spreadsheet + chat | Personal spreadsheet + Zoom |
| Where the status lived | In the production editor’s spreadsheet | In one person’s head | With me |
| What worked | Deadlines visible, content in one place | One source of truth | A living revision process |
| Where it broke | Heavy load on peak deadline days | He couldn’t get sick | Status was my second job |
The work nobody asked for
In all three stories there was a person who kept the status: the production editor, the editor-in-chief, me. None of us complained. It was just part of the job.
But this work doesn’t make the issue better. It doesn’t write the copy, lay out the page or catch the error. It only retells what has already happened. Work about work. And somehow it always falls to the person everything already depends on.
Why doesn’t a task tracker solve this?
Trello, Asana and Monday are good at showing status. But they don’t create it. Status appears when someone moves a card or changes a field. First a person does the work, then goes to the tracker and reports it. It’s the same work about work, in a different window.
Automations help, but someone has to write them and fix them when the process changes. That is another job for the team.
A tracker needs to be told. I wanted a tool that doesn’t.
What I took from this
- Files need one source of truth. At the magazine, nobody ever dropped a PDF into the chat, only a link to the folder. That’s why we never had two “final” versions.
- There is no final, only versions. Revisions aren’t a failure, they are the process. The higher the version number, the closer the result.
- Status should change from an action the person takes anyway. Hand off the page, and that is the status. No need to write about it separately.
The first two rules hold up fine on a Google Sheet and discipline. The third doesn’t hold up by hand: there’s always one person who ends up doing it for everyone. That’s why I built Chains.
Yes, in Chains you still have to click something. The difference is that it’s one action instead of three (message, card, spreadsheet), and it’s the handoff itself, not a report about it.
The same story, without the retelling
Remember the three messages from the beginning? Here are the same three handoffs in Chains.
- “Story’s in copyedit.” The writer handed in the text, and it showed up for the editor under On you now.
- “Story’s in layout.” The editor handed off the copyedit, and the story moved to the layout designer.
- “Story’s in proofreading.” The designer handed off the page, and it’s with the proofreader.
Three handoffs, zero messages. Handing off a stage is one action, and that action is the status.
Meanwhile, the production editor is looking at the issue as spreads. Every page has its own status, and nothing gets copied anywhere.
How it works for others
A four-person team at a monthly industry magazine has planned every issue in Chains since autumn 2024: 60 pages a month, and once a year a 140‑page special where every page is a separate story.
FAQ
How do you track the status of an issue in a small team?
I’ve worked with three ways. A chat and a spreadsheet: cheap, but someone copies statuses by hand. One person keeps everything in their head: fast, as long as they’re around. A tool where status changes with the handoff itself: that’s how Chains works.
Do we need a separate tool if there are three of us?
Not necessarily. There were three of us on the book, and a spreadsheet was enough. But I was the one keeping it, alongside my actual job. If you have someone like that and they’re fine with it, you don’t need a tool.
What is a flatplan, and does Chains have one?
A flatplan is a map of the issue as spreads: what goes on which page. Chains has a Flatplan view: the issue as spreads, built from the stories and their page counts, each page with its own status. You can’t drag pages around or place ads in it.
How much does Chains cost?
It’s free for teams of up to 5 people, with no trial period and no credit card. If there are more of you, write to me.
Try it
Chains doesn’t do layout and doesn’t sell ads. It answers one question: what stage is the story at, and who has it now.
You can test that on one issue of your own:
- Draw your process as a template: which stages, and who is responsible for each.
- Create a project for the issue.
- Add a job for each story and say how many pages it takes.
After that you see the issue as spreads, and statuses change when the work is handed off.
Chains is free for teams of up to 5 people, with no trial period and no credit card.
Want to ask first? Write to me: andrey@chains.design.
A person will still plan the issue. But they won’t have to retell what has already happened.