A content operation without a board lives in chat history and good intentions. This appendix gives you a minimal board — six columns matching the pipeline from Lesson 85.2 — that a small team (or one builder plus AI) can run weekly. Copy the layout into any tracker; the discipline is in the handoffs, not the tool.

The six columns and their exit rules

| Column | Holds | May leave only when |

|---|---|---|

| Backlog | audience questions + requested artifacts (85.1) | brief assigned: owner + due date set |

| Brief | research packet + angle + standard | sources dated, unknowns marked, review checklist attached (85.3) |

| Draft | AI-assisted draft + assets in progress | producer declares ready + self-check passed |

| Review | pieces awaiting editorial gate | human approves all gates (factual/source/voice/image/links/progression) or rejects with named cause |

| Publish | approved pieces queued to ship | metadata, links, and cross-links verified live |

| Reuse + Update | shipped pieces with derivative potential or decay risk | six-derivative map or update scheduled (85.4), metrics logged (85.5) |

The iron rule from 85.2: every handoff is a file or structured record. A card moves only with its artifact attached — no "it's in the chat" cards in Draft or Review.

WIP limits and weekly rhythm

Keep work-in-progress small: Draft ≤ 2, Review ≤ 3 per reviewer. Overflow stays in Backlog, visible and prioritized, rather than clogging Review into a graveyard. Weekly (30 min): clear Review first (approve/reject with causes), pull one card per free Draft slot, retire or update one shipped piece (decay check from inventory), and log one quality signal + one business signal per shipped piece (Lesson 85.5).

Worked mini-example — ByeBuy classroom: Backlog holds "how do webhooks verify?" → Brief attaches the Stripe docs link and the checkout→access example → Draft produces lesson + checklist → Review applies the six ByeBuy gates → Publish ships with hero image and docs links → Reuse spawns the failure checklist, an FAQ, and a workshop prompt. One card, six artifacts, zero lost context — because each move carried a file.

Card template (copy per item)

## Card: [audience question]
- Audience job: ___ / Requested artifact: ___ (lesson, checklist, email, FAQ)
- Owner: ___ / Due: ___ / Current column: ___
- Attachments by column: brief → research packet ___ / draft → draft file + asset list ___ / review → checklist result ___ / publish → live URL ___ / reuse → derivatives ___
- Blocked on: ___ / Next action + date: ___

Every card names its audience job from EDITORIAL-JOBS.md (85.1) so the board never fills with "post something" cards. If a card can't state the job it serves, it returns to Backlog until someone can.

Common failure modes

The chat pipeline. Cards move on verbal "looks good" with no attached file. Two weeks later nobody can find the approved version. Fix: the board tool enforces an attachment before the column change — process over willpower.

The review graveyard. Ten cards pile in Review because rejection feels rude. Fix: rejections are mandatory data — each names the failing gate and returns the card to Draft or Brief with a note. A reviewer who never rejects isn't reviewing.

The publish-and-forget. Shipped cards close instead of moving to Reuse + Update. Fix: every Publish exit creates the Reuse card automatically — six-derivative map due within 30 days (CONTENT-REUSE-MAP.md, 85.4) and a decay check date on the calendar. Compounding only happens if the board forces the last column.