Audit the operating system before adding dates

A calendar is ready only when it can explain how work becomes complete, how much unfinished work the system can hold, and what happens when reality differs from the plan. This audit has three outcomes: pass, revise before scheduling, or stop and resolve a hard dependency. Do not calculate a reassuring total. Missing ownership, an unsafe correction path, or an unlimited active queue remains visible even when other checks pass.

Use current board records, publication history, reviewer availability, and due maintenance rather than memory. The Kanban Guide supports explicit workflow and flow measures; the Scrum Guide offers shared completion and recurring inspection. They are reference points, not proof that a particular editorial policy fits. Record the evidence date beside every answer and expire the audit when team structure or quality requirements change.

Evidence: Kanban Guides; Scrum Guides

Checks 1–4: workflow and completion

First, confirm that every active state appears on the board, including waiting, evidence review, production verification, and rework. Second, write an observable entry and exit rule for each state. Third, define Done separately for a new article, major refresh, and correction. Fourth, walk one recent card through its actual history and reconcile any hidden step or off-board handoff.

A failed workflow check means the team cannot reliably interpret its own counts. Fix definitions before setting numeric limits. If a draft can be called finished while links, disclosures, or accessibility remain unresolved, the calendar will overstate capacity. Preserve exceptions encountered during the walkthrough; they often identify the real process more accurately than the documented one.

1. Every waiting and active state is visible.

2. Entry and exit evidence is written for each stage.

3. Done is defined by content class.

4. One recent card reconciles with the displayed path.

Evidence: Kanban Guides; Scrum Guides

Checks 5–8: capacity and WIP policy

Fifth, derive a planning range from recent completions by content class. Sixth, record the oldest active item and the stage where age concentrates. Seventh, assign explicit limits to constrained active stages. Eighth, verify that blocked and returned cards still count against those limits. An empty history is not permission to invent precision; start with a conservative limit and label it a hypothesis.

Challenge each number with a plausible stress case: reviewer absence, urgent factual correction, or a research item whose source disappears. A board at full utilization has no resilience. DORA’s balanced measurement guidance supports reading speed with stability and quality; the editorial adaptation should therefore protect headroom and monitor review returns rather than maximize starts.

5. Completion evidence is separated by work type.

6. Oldest-item age is visible at replenishment.

7. Constrained stages have numerical limits.

8. Blocked and rework items consume capacity.

Evidence: Kanban Guides; DORA / Google Cloud

Checks 9–12: mix, maintenance, and exceptions

Ninth, reserve capacity for updates, corrections, research, and technical care. Tenth, define which obligations qualify for a dated or expedite lane. Eleventh, require every exception to name what it displaces and when the exception ends. Twelfth, place an expiry or reconsideration date on speculative work so stale cards do not occupy attention forever.

GOV.UK’s alpha guidance is relevant to the research check because early work should answer risky questions rather than silently become a full production commitment. Verify that discovery has an output such as a brief, evidence gap, or closure decision. Likewise, verify that maintenance demand is based on the current library’s age and risk, not a percentage copied from another publisher.

9. Non-new work has protected capacity.

10. Dated and expedite eligibility is narrow.

11. Each exception records displacement and end date.

12. Speculative cards expire or return for decision.

Evidence: DORA / Google Cloud; UK Government Digital Service

Checks 13–15: governance and review

Thirteenth, name the person who can unblock, split, or cancel an aging item. Fourteenth, schedule a recurring replenishment review that examines age before intake. Fifteenth, keep a policy-change log with date, reason, expected effect, and recheck point. These controls make the board an accountable decision system instead of a passive display.

Run a short scenario: a correction arrives while the review column is at its limit. The team should be able to state whether the correction qualifies for expedite, which card pauses, who tells affected owners, and how the displaced work re-enters. If the answer is “everyone works harder,” Checks 10, 11, or 13 have failed. Correct the policy before scheduling another discretionary article.

13. Aging work has an unblock or cancellation authority.

14. Replenishment reviews age and due care before starts.

15. Policy changes are dated, reasoned, and scheduled for review.

Evidence: Kanban Guides; Scrum Guides; UK Government Digital Service

Record the result without turning it into certification

For each failed check, assign an owner, repair, evidence required, and due date. Re-run that item plus any dependent checks; changing Done, for example, invalidates capacity estimates. Archive the prior audit so the evolution remains understandable. Set the next full review for 2027-02-10 at the latest, and earlier after staffing, channel, disclosure, or publishing-risk changes.

Passing this audit does not guarantee traffic, quality, revenue, or a stress-free schedule. It shows that the operating assumptions are visible enough to make commitments responsibly. Start with only the next replenishment horizon, observe completion and age, and resist filling distant dates for appearance. A deliberately unfilled slot can be evidence that the board is protecting real limits.

Evidence: Kanban Guides; DORA / Google Cloud

Sources and further reading

These references informed this article. A source supports a claim; it does not imply endorsement of TenMultigure or any future product reference.

  1. The Kanban GuideKanban Guides · Accessed August 10, 2026

    Used to define the audit checks for workflow visibility, WIP limits, age, and blocked work; these are the minimum controls needed to interpret an editorial board coherently.

  2. The Scrum GuideScrum Guides · Accessed August 10, 2026

    Supports shared completion rules, goal focus, and recurring review, informing the walkthrough and governance checks without requiring adoption of Scrum roles or terminology.

  3. DORA’s software delivery performance metricsDORA / Google Cloud · Accessed August 10, 2026

    Provides independent support for balanced system measures and cautions against output-only optimization, used in the capacity section to preserve quality and resilience.

  4. How the alpha phase worksUK Government Digital Service · Accessed August 10, 2026

    Informs the bounded-discovery check so research has a decision output and does not become an unlimited preproduction queue disguised as learning.

Reviewed for clarity and evidence

Reviewed by TenMultigure Editorial Team. See an error or a source that has changed? Tell the editorial team.

Review method: AI-assisted desk research with editorial checks. Reviewed ; next scheduled review . Rebuilt TM-210 as a fifteen-point readiness audit spanning workflow, capacity, WIP, maintenance, exceptions, and governance, with dependent-check reruns and explicit non-certification limits.