An empty date in the calendar does not automatically require another idea. I first ask which reader question remains unanswered that week. Sometimes the missing piece is a continuation of an existing thought rather than an entirely new subject.
Keep ideas in a shared pool
Alongside a proposed title, I record the reader question, source, owner and estimated workload. An idea without that context may need development before receiving a publication date. “New collection post” does not tell a writer which decision to support or which detail to explain.
Content pillars help keep the pool balanced. They do not require every pillar to receive an equal number of posts every week. A particular period may justify giving one subject more attention, provided the reason for doing so remains clear.
Use a few explicit priority criteria
I consider reader need, time sensitivity, evidence readiness and production capacity together. A genuine external deadline differs from an internal habit of calling everything urgent. Missing source information cannot be repaired by assigning a slot in the calendar.
For each idea, write one sentence explaining why it belongs now. If the only reason is that the topic has not appeared recently, reconsider its purpose. A growing number of product-use questions may provide a stronger reason to change the next scheduled piece.
Make dependencies visible
Material awaiting a shoot has a different preparation cycle from a text revision. Working backwards from publication, I identify the source, draft, approval and final review dates. A schedule that ignores the reviewer’s availability is unlikely to describe the work accurately.
I also reserve some capacity for emerging questions. Filling every available day in advance can prevent the team from responding thoughtfully to something readers actually need. Flexible space is not abandoned work; it is room for editorial judgement.
Review the calendar alongside outcomes
At the end of a period, I look beyond completed boxes. Which pieces were repeatedly delayed, where was information missing, and which publications generated useful follow-up questions? Moving towards a content system carries those observations into the next cycle. A good calendar makes work visible and coordinated without pretending to replace the decisions behind it.
When three requests compete for one week
Imagine a small team with enough production and review capacity for two pieces this week. It has three requests: an event whose applications close on Friday, a recurring product-care question, and a brand film requiring a new shoot. This is a fictional planning example, not a client project or performance result.
First separate importance from readiness. An urgent event announcement is not ready if its closing time has not been confirmed. A modest care guide may be achievable if someone can verify the product information. The film can matter strategically while still depending on an unavailable shoot. Promising a third delivery does not create capacity.
| Request | Decision for this week | What would change the decision? |
|---|---|---|
| Event closing for applications | Prioritise it once the date and link are verified | If the information owner misses the review deadline, do not publish an inaccurate announcement |
| Recurring care question | Allocate the second production slot if its source is ready | Resolve missing product information before drafting a definitive answer |
| New brand film | Plan the shoot without promising a publication date | Reassess when filming and review capacity actually become available |
Give each decision an owner and a review date. “Later” is not a rescheduling plan. If an urgent correction arrives, identify which planned item will move instead of silently adding it to everybody’s existing workload. Two pieces is the capacity assumed in this example, not a recommended publishing frequency for every team.
Check publication conditions before adding scores
A simple score can support a discussion. It cannot make an unsupported claim ready to publish. First resolve information accuracy, required permissions, equivalent meaning across languages and reviewer availability. Then choose among ready options using reader value and genuine deadlines.
GOV.UK’s roadmap guidance emphasises explicit priorities and revising plans as teams learn, in its service-development context. The two-slot example here is an editorial adaptation, not a universal scoring formula.
Record the deferred item, its reason and its reconsideration condition in the social media and content system. Use content pillars to consider topic coverage and the content system guide to manage information across publications. Prioritisation should make both the next publication and the promises the team is currently withholding clear.