How to design clear status labels for a content workflow

Anyone who makes content on a schedule ends up with a board: a calendar, a spreadsheet, a set of cards. Each item needs a status, and the status needs to mean the same thing to everyone, including you in three weeks. Most boards fail for dull reasons. The statuses are vague, there are too many, colours carry meaning nobody remembers, and unfinished work piles up in the middle. This guide shows how to design statuses and labels that stay clear, with a worked example and a few accessibility checks that cost nothing.

Start with the workflow, not the labels

Before you choose words or icons, write down what actually happens to a piece of content. The Kanban Guide, a short reference for managing flow in knowledge work, says that optimising flow starts with defining what flow means in your context. It calls that shared understanding a Definition of Workflow and lists the minimum elements: what the individual work items are, when an item counts as started and finished, the states it passes through, how work in progress will be controlled, explicit policies for how items move, and a service level expectation.

You do not need Kanban to benefit from the questions. For a content calendar they translate simply:

• What is one item? A post, a video, an episode, a newsletter. Pick one unit and keep it.
• When does it start and finish? "Started" might be the moment you commit to making it, and "finished" the moment it is published.
• Which steps does it pass through? Only list steps where work really waits.
• What are the rules for moving on? "Review means a second person has the draft and I cannot edit it until they respond."

Define each status in one sentence

A status is a promise about where an item is and what happens next. Write one sentence for each, and put it where the team can see it. For example:

• Idea: noted, not yet committed to.
• Draft: someone is writing or recording it.
• Review: the draft is with a reviewer; the maker waits.
• Approved: the reviewer has said yes; nothing is left to change.
• Scheduled: it has a publication date and time.
• Published: it is live.
• Archive: it is done, and stored for reuse.

If two statuses are hard to tell apart, merge them. If one status holds items that need different treatment, split it. Keep "Blocked" or "On hold" as a flag, not a stage, so that work does not appear to be moving when it is not.

Separate status from priority

A common mistake is to mix status and priority in one label, such as "Urgent draft". Status tells you where the work is. Priority tells you how soon it matters. If you combine them, the number of labels grows quickly and the meaning blurs. Keep two fields, or use a badge for status and a simple mark for priority.

Limit work in progress

The Kanban Guide describes the items between a started point and a finished point as work in progress, and says a defined way of controlling it is part of a workflow definition. In plain terms: set a limit on how many items may sit in a step at once. A review step with no limit becomes a pile, and a pile hides delays. A limit forces a decision: finish something before starting more.

The right limit depends on your team and your work, so treat any number as a first guess. Start low, watch what happens, and change it when you have a reason.

Pair every colour with a word or a shape

Colour is useful on a board. It lets you scan quickly. It is not safe as the only signal. The W3C's Web Content Accessibility Guidelines 2.2, success criterion 1.4.1 (Use of Color), says that colour should not be the only visual means of conveying information, indicating an action, prompting a response or distinguishing a visual element, because not everyone sees colour or sees it the same way.

So give every status a word, and where it helps a shape or an icon, and treat the colour as a bonus. A badge that reads "Review" in red is clear to everyone. A plain red circle is not.

A second check concerns contrast. WCAG 1.4.11 (Non-text Contrast) asks for a contrast ratio of at least 3:1 against adjacent colours for the parts of a graphic that are needed to understand it, and for the visual information that identifies interface components. If an icon is the only thing that tells you what a control does, make sure its outline stands out from the background. A light, thin outline on a pale card fails this test even if it looks elegant. A dark outline with a light border, readable on light, dark and photo backgrounds, is a safer design.

Choose words that survive a skim

Short, plain verbs and nouns work best: Draft, Review, Approved, Scheduled, Published. Avoid in-jokes and abbreviations that only you know. Be consistent about tense, so that all labels describe a state or all describe an action, not a mix. And keep your vocabulary the same across tools: if the calendar says "Ready" and the task list says "Approved", someone will wonder whether they are the same.

Worked example: counting what is waiting

The numbers are invented. A solo creator has 40 items on a board for the month: 12 in Draft, 10 in Review, 8 Scheduled and 10 Published.

Items started but not finished are in progress. If Published is the finish, then work in progress is 12 + 10 + 8 = 30 items. That is 30 / 40 x 100 = 75 per cent of the board. The 10 published items are 25 per cent. This is a count at one moment. It is not a measure of how fast the creator works.

The more useful question is how long items take. Suppose the creator finished 20 items last month, with these cycle times in days from start to Published, sorted: 2, 2, 3, 3, 3, 4, 4, 4, 4, 5, 5, 5, 6, 6, 7, 7, 8, 9, 11, 14. Seventeen of the twenty took 8 days or less, and 17 / 20 = 85 per cent. The Kanban Guide describes a service level expectation as a period of time together with a probability, for example that 85 per cent of work items will be finished in eight days or less, and says it should be based on historical cycle time. Here the data support the same kind of sentence: "85 per cent of our items finished within 8 days". With only 20 items it is a rough guide, and you should say so, but it is more useful than guessing.

An audit once a month

• Does every status have a one-sentence definition?
• Is any status empty all month? Remove it.
• Is any status always full? Add a limit or split it.
• Are there items that have not moved in a long time? Decide: finish, park or drop.
• Can someone who cannot see colour read the board?
• Are badges and icons legible at the size you use them?

Tool that fits

Creator Workflow Stickers (EUR 12, paid once) is a visual kit for content calendars, video production boards, social post graphics and digital workspaces. It has 80 labelled badges, with status and stage words such as Draft, Review, Scheduled, Published, Update, Archive, Record, Edit, Export and Approved and 70 more, and 80 pictorial icons such as a calendar, camera, microphone, timeline, upload, chart and target. Each is a transparent 1024 x 1024 px PNG and an SVG with the text outlined, in one style with a white die-cut border. Two contact sheets and a CSV index help you find them. There are no platform logos. Unlimited personal and commercial projects of your own; the files may not be resold or shared.

Questions people ask

Sources

1. The Kanban Guide (May 2025), Defining and Visualizing the Workflow
2. W3C WAI, Understanding Success Criterion 1.4.1: Use of Color (WCAG 2.2)
3. W3C WAI, Understanding Success Criterion 1.4.11: Non-text Contrast (WCAG 2.2)
4. HiddenWay worked example: our own arithmetic, with invented numbers

We checked each source on 17 October 2026. If a fact here is out of date, tell us at hello@hiddenway.info.

Keep reading

• Social media content calendar for 2027: plan a year of posts
• How to use reaction stickers in newsletters and planners
• How to set levels for sound effects in video and UI demos
• More in Creator assets