Overview
An editorial workflow tracker helps a managing editor keep content moving from request to draft, review, approval, publication, and refresh. This playbook installs a structured tracker and a workflow runbook so the team can see what is ready, what is blocked, and what needs a decision before the next editorial review.
It is built for content teams that are running the workflow from a Trello board, Asana project, or spreadsheet that has become just messy enough to hide the real state of production. Juno keeps the useful layer: stages, owners, reviewers, dates, links, blockers, next actions, and refresh status.
Why you should make editorial work easier to review
Editorial production rarely fails because nobody has ideas. It fails in the quieter places: a draft has no reviewer, an approval is implied but not given, a published asset needs refresh, or a request sits in the wrong column long enough to become invisible.
Content Marketing Institute's research hub keeps returning to the value of documented content strategy and operations, not just more output (Content Marketing Institute). Google also frames useful content around serving real people clearly, which is hard to protect when production status and review context are scattered (Google Search Central).
This playbook treats the workflow board as an editorial decision surface. A title in "review" is not enough. The managing editor needs to know who is reviewing it, what they are checking, what could block publication, and what should happen next.
Run it before weekly editorial standups, campaign content reviews, publication planning, or any moment when the board looks full but the next move is fuzzy.
Step-by-step
- 1Confirm the brand or publication, content types, workflow stages, review rules, refresh rules, and the team's expectation for aging work.
- 2Install or reuse the editorial workflow tracker with fields for content item, stage, owner, reviewer, approver, dates, priority, links, blocker, next action, and refresh status.
- 3Add active requests, briefs, drafts, review items, scheduled pieces, published assets, and refresh candidates so backlog work does not look the same as committed production.
- 4Review the tracker for missing owners, stale stages, overdue drafts, absent briefs, unclear reviewers, unresolved approvals, missing links, and publication dates without readiness.
- 5Update the workflow runbook when stage definitions, approval expectations, owner rules, or refresh standards change, keeping the operating guidance short enough to use again.
- 6Use future manual, weekday, or weekly runs to refresh the same workspace, so resolved blockers, aging work, and recurring approval gaps stay visible over time.
Frequently asked questions
Does this replace a full project management system?
No. It replaces the minimum useful editorial workflow board: tracking content status, ownership, review, approval, publication readiness, blockers, and refresh needs. Detailed task dependencies, workload planning, and team-wide project management can stay elsewhere.
How is this different from a content calendar?
A content calendar focuses on what should publish and when. This tracker focuses on how each content item moves through production, review, approval, publication, and refresh. The two can work together, but they answer different editorial questions.
Do we need an existing board or spreadsheet?
No. Existing rows, draft links, or board exports make the first pass faster, but Juno can start from the confirmed requirements and create a clean operating tracker with assumptions marked clearly.
How often should we run it?
Weekly works well for most active editorial teams. Weekday reviews are useful when content moves quickly, approvals are frequent, or campaign publishing dates are close.