---
title: 'Content Plan: every article from brief to published, by status'
description: 'The Content Plan board and its eight status columns, the article page with its briefs, drafts, gate receipts and timeline, the controls on both, and their MCP equivalents.'
slug: content-plan
group: app
order: 27
keywords:
  [content plan, kanban, article status, content brief, gate receipt, update_article_status, list_article_suggestions]
related: [drafting-and-verification, publishing-and-attestation, suggestion-statuses, opportunities]
updated: '2026-10-26'
---

The Content Plan holds every article suggestion in a project, from the moment it is created to the day it goes live. It works on the free plan.

## The board

The board has one column per status, each with a count:

| Column           | What it means                                                                 |
| ---------------- | ----------------------------------------------------------------------------- |
| Planned          | Older suggestions waiting for a brief. New ones skip this column.             |
| Generating Brief | The brief is forging, or queued behind the free daily cap.                    |
| Brief Ready      | The brief is done and nobody has picked it up.                                |
| Drafting         | Someone has the brief and is writing.                                         |
| Draft Ready      | A draft was submitted and the gate flagged it.                                |
| Reviewing        | An agent marked the draft as under review.                                    |
| Ready to Publish | A draft passed the gate, or the article is waiting for its scheduled go-live. |
| Published        | The live URL is recorded.                                                     |

Each card shows the title, the cluster and search intent, a positioning chip on radar-born articles, an editorial badge (such as refresh or rewrite) with its reason, and a **Check** button or a **Checked** chip for the live search check that [From your own ideas](/docs/from-your-own-ideas) describes.

## Where the data comes from

The board reads the content plan live. Suggestions arrive from **Forge brief** and **Create Content Plan** on [Opportunities](/docs/opportunities), from the Desk's idea box, from the market radar and from this screen. Most statuses are set by actions: the brief forge, the gate in `lint_draft`, the publish record. Each change records whether you or the agent made it.

## What you can do on the board

- **New from idea** scores an idea and adds it. **Import** offers **Paste a list of titles** (up to 50, with **Add ideas** or **Add and check**) and **Import from a keyword list** (up to 500 keywords, run through a prompt in your own chat assistant).
- **Generate Brief** on a Planned card. A queued card reads **Queued — forges at reset**.
- **Get Brief** on a Brief Ready card opens **For Human Writers** (PDF), **For AI Agents** (markdown), **Open in ChatGPT** and **Open in Claude**. Each moves the card to Drafting. **Move up** and **Move down** set the order you mean to publish in, without touching status or score.
- **Mark as Published** on Drafting and Ready to Publish cards asks for the live URL.
- The trash icon deletes a suggestion at once, with no confirmation.

There is no drag between columns and no free status menu. Draft Ready and Reviewing cards carry no action on the board.

## The article page

Opening a card shows the title, status, intent, a link to its cluster, a priority score, a **Scheduled** chip when a future go-live date is set, the live URL once published, and the editorial recommendation. **Submit draft** pastes a draft and grades it against the brief, with the verdict and each check shown in place. **Mark as Published** records the URL.

Below that is one tab per content type the project publishes: Article, Reels / short-form, Long-form video, X thread and LinkedIn carousel, plus **+** to add a destination. A dot on a tab means that channel is live (green) or scheduled (amber). Each tab holds:

- The links already live on that channel, with dates.
- The timeline, which the app calls the Passport: how the article was born, brief forged, each **Draft submitted** or **Draft resubmitted** stamp with its gate receipt, published and detected, any flag, and an **Earning** stamp that fills in with Search Console clicks and impressions.
- The brief, collapsed behind **Show full brief**, with **Regenerate**, or **Generate** for a channel without one.
- **Drafts**: one row per destination, with **Copy** and **Download**.
- **How writing works**, with the **Get Brief** menu.

The live search check and **Target Queries** close the page.

## Scheduling

The app shows a scheduled date but has no control to set one. Your agent sets it with `update_article_status` and `scheduledFor`, and publish detection attests the article when it goes live, as [publishing and attestation](/docs/publishing-and-attestation) explains.

## The same plan over MCP

- `list_article_suggestions` is the board; `get_article_suggestion` and `get_article_brief` are the article page.
- `update_article_status` sets a status; for `published`, `mark_article_published` also records the URL.
- `lint_draft` is **Submit draft**; `get_draft_status` re-reads drafts and receipts for free. See [drafting and verification](/docs/drafting-and-verification).
- `download_brief_markdown` and `get_write_handoff` match **Get Brief**; `delete_article_suggestion` matches the trash icon; `check_idea` matches **Check**.