The story budget: turning the morning list into data the platform reads
In short
A story budget is the newsroom's forward list of what it intends to publish, argued out at the morning conference and revised through the day. Most desks keep it in a document, which is why nobody can answer what was planned against what ran. Held as records — one row per intended item, each owning the story that fulfils it — it yields capacity, duplicate detection and a fill rate.
Key takeaways
- The budget is a plan, not a queue: a row can exist for weeks before any story object does.
- Make the budget line the parent of the story, not a tag on it, or planned-versus-ran stays unanswerable.
- Two required fields — an owner and a confidence value — are enough; everything else must be optional.
- Fill rate is the share of firm items that ran, and a desk that cannot compute it has a document.
- Duplicate effort is found by joining budget lines to the diary event they came from, not by reading titles.
A story budget is the list of what a newsroom intends to publish — built before the 09:30 conference, argued over during it, revised until the last item lands. It is a plan rather than a queue: an item can sit on it for 3 weeks before anyone writes a word, and items leave without ever becoming stories. Almost every desk keeps it as a document, and so cannot answer the simplest question about its own output: what it intended to run, against what ran.
One structural change unlocks the rest. Make the budget line a record in its own right, and the parent of the story object that fulfils it — not a tag applied to a published story afterwards, but a parent created first. Everything below follows from that relationship.
The same list under several names
| Name | Where you hear it | What it is ordered by |
|---|---|---|
| The budget | Most commonly in US newsrooms | Desk, then prominence |
| The news list or the schedule | Common in UK and Commonwealth newsrooms | Desk, then filing time |
| The diary | The forward-planned subset: known events, embargoed releases, court dates | Date, weeks or months ahead |
| The rundown | Broadcast and streaming | Airtime, with durations that must sum to a fixed total |
The distinctions matter for modelling, not vocabulary. A diary entry is a forward commitment with no owner yet; a budget line is today's version with an owner; a rundown adds a constraint the others lack, because 22 minutes of durations must sum to 22 minutes. A platform modelling only today cannot hold the diary, and a diary that cannot be promoted into a budget line means the same event is typed twice.
The minimal schema
- Slot. Lead, second, feature, column, live coverage — and for a rundown, its duration. This is what shows the shape of the day rather than a list of titles.
- Desk and edition. Which team owns it, and which masthead. Multi-market operations need the second field from day one: a slot filled for one edition and empty for another is a fallback decision rather than a gap — see the fallback annotation most editions get wrong.
- Owner. One named person, not a team. A line assigned to a desk is assigned to nobody, and the queue-age evidence is in stories that sit between review states.
- Target time. When it is expected to be ready, distinct from when it publishes. The gap between those 2 numbers is the real buffer.
- Confidence. A 4-value enum — firm, likely, hoped, speculative. The field that makes the list honest, and the one editors resist until they see the capacity view.
- Source event. The diary entry, press conference or tip the line came from, which makes duplicate effort findable by a join.
- Story object, nullable for a long time; plus dependencies — photography, video, a graphic, a legal read — each able to be late independently of the copy.
What becomes answerable once it is a record
- Fill rate. The share of items marked firm at conference that published that day — one number, computed nightly, and the first honest measure most desks have of their own forecasting. A newsroom running 6 of 10 firm items has a planning problem, not a capacity problem.
- Capacity against demand. Firm items per desk against the slots the surfaces need — front page, app front, newsletter, each edition. The shortfall surfaces at 09:00 rather than 16:00.
- Duplicate effort. Join lines to their source event. Two desks working one press conference is invisible in a document and one query against records.
- The diary tail. Every forward commitment whose date passed with nothing produced — always longer than expected, and the cheapest source of stories in the building.
- Where the day fell over. Which slot was empty at which hour, and which dependency was late. Attributing lateness to a graphic rather than a reporter is what makes a post-mortem useful.
A newsroom that cannot say how many of this morning's firm items actually ran is not measuring its plan. It is remembering it.
Two boundaries are worth stating. Confidence forecasts whether an item runs and says nothing about whether the reporting stands up; conflating the two is how a planning field ends up quoted in a complaint. Verification lives in its own record, built around the claim — see a fact-check record that survives a complaint. And the line closes at publication: what happens afterwards belongs to the story, as a typed event rather than a revision of the plan — see correction, update or clarification.
A budget tool is a small build with a high adoption bar, because it competes with a document that already works well enough. Modest scope, ruthless attention to what the desk will actually fill in: the shape of work we take on as MVP and product builds. The rest of this silo sits under editorial workflow and newsroom AI, inside our media and publishing practice.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is a story budget in a newsroom?
The list of stories a newsroom intends to publish, prepared before the morning conference and revised through the day. It carries what each item is, who is doing it, when it is expected and how likely it is to run. It is a plan rather than a work queue: some items leave it without ever becoming stories.
How is a budget different from an editorial calendar?
A budget is short-horizon and provisional; a calendar is long-horizon and mostly fixed. The budget is today and tomorrow, with confidence attached because half of it may not happen. The forward-planned material in between — known events, court dates, embargoed releases — is the diary, which feeds the budget.
Which fields should be mandatory on a budget line?
An owner and a confidence value, and nothing else. Every additional required field reduces the chance the list gets filled in at all, and a budget the desk works around is worse than no budget, because the platform now reports a plan that is not the real one.
What does a story budget make possible that a document does not?
A fill rate: firm items at conference against items published that day. Then three more queries a document cannot answer — a capacity view per desk against the slots each surface needs, duplicate effort found by joining lines to their source event, and forward commitments whose date passed with nothing produced.
- editorial planning
- content modelling
- newsroom tools
The work behind this page
Builds from our portfolio that this page draws on.
Notewell
An AI meeting assistant that records and transcribes every meeting, extracts the decisions and action items, assigns owners and due dates, and tracks follow-through until it's done.
Productivity AIBrief Forge
Contract review AI for solo lawyers and small firms — extract, score, and redline contracts in minutes.
Legal TechRead next
- Embargoes as a field the platform enforces, not a line in an emailAn embargo is a condition set by someone outside the newsroom, and a platform can only enforce it if it is a typed record with a source, a lift instant, a scope and a list of surfaces.definition
- Stories that sit between review states and nobody can say whose they areStalled stories are not a discipline problem. Measure age in each state per transition for two weeks: four distinct distributions appear, and each one points at a different broken step.diagnostic
- Machine-drafted copy is reaching the live site unreviewedUnreviewed machine drafts are a missing-field problem in costume. Five paths put generated text on the site with nothing attached, and only two of them are closed by asking people to be careful.diagnostic
- Dunning as a state machine: retries, grace and when access stopsDunning is not a sequence of emails. It is a state machine, and every state must be written into the entitlement record so access, messaging and reporting cannot drift.definition
- News sitemaps: the two-day window, and what the archive stays out ofA news sitemap is a rolling window, not an index. At publisher scale the failure is inclusion — archives, republished timestamps and paginated lists leaking into a file meant for two days of news.definition
- Paying subscribers are hitting the wall, and only on the popular storiesThe symptom tracks popularity because the hit ratio is the exposure: the more cacheable a story is, the more likely a subscriber gets served the anonymous copy of it.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation