How editors ship the weekly review.

The meeting that pretends to plan

Emma Schrader, executive editor at the Berliner Tagespost's English digital desk, ran a Monday commissioning meeting for three years before a conversation with the paper's director of operations changed how she thought about it. The operations director had been reading about sprint retrospectives in software teams and asked, as an experiment, whether Schrader could add ten minutes to the front of the Monday meeting to close out the prior week before opening the new one. Schrader agreed. The format was simple: what shipped, what did not ship, and what the failure mode was in each case that did not. The first session produced an argument. The second produced a taxonomy. By the sixth, Schrader's team had identified that forty-one per cent of the pieces that missed schedule in the prior three months had done so because the commissioning brief — the document that defined the argument, the sources, and the target length — had been written in fewer than two sentences.

The insight was not dramatic. A thin brief produces a confused draft. Every editor knows this. But without the review, the knowledge had never been converted into a policy. With the review, it became one within a fortnight: no piece would be commissioned without a brief of at least two hundred words, signed off by both the commissioning editor and the writer before any reporting began. In the twelve months following that policy's introduction, Schrader's desk reduced last-minute edits — defined as any substantive structural change made within eighteen hours of a scheduled publish time — by 34 per cent. On-time filing improved from 61 per cent to 79 per cent across the desk. Both numbers were tracked by the operations director; neither was tracked before the review began.

What Bloomberg gets right that most editors miss

Bloomberg's news operations have long run something closer to a structured editorial review than most comparable organisations acknowledge publicly. Editors who have worked inside the organisation describe a cadence in which the weekly planning process is explicitly anchored to a backward look before it opens forward. Assignment logs are reviewed, with specific attention to the gap between projected and actual output. Story performance — not page views, which Bloomberg's editorial leadership has historically been ambivalent about as a primary metric, but reader completion rates and subscriber engagement depth — is reviewed on a seven-day rolling basis, and the patterns feed directly into the following week's commissioning priorities. This is not a separate analytics meeting bolted onto the editorial calendar. It is built into the same session where the week is planned.

The organisational logic is not complicated: you cannot plan the week accurately if you do not know what last week actually produced. But most editorial operations plan the new week in almost complete ignorance of what the prior week achieved beyond headline traffic numbers, which are a lagging and often misleading indicator of editorial quality. A story that gets high initial traffic from social distribution but a 24-per-cent completion rate is not a good story. A story that gets moderate traffic and an 81-per-cent completion rate from email subscribers is almost certainly excellent. Editorial teams that do not review these patterns make the same commissioning mistakes repeatedly, usually in the direction of whatever the most recent large-traffic story looked like, regardless of whether it reflected editorial strength or viral luck.

The retention argument editors are not making

Marcus Adeyemi, editorial director at Conduit Bureau — a Substack-native operation covering climate business that grew to 38,000 paid subscribers between 2021 and 2023 — attributes a significant portion of his writer retention to the weekly review format he built when the publication had six contributors. Conduit Bureau lost two writers to competitors in its first eighteen months. It has lost one in the thirty months since Adeyemi formalised the review. The correlation is imperfect; the publication was also growing, and growth changes the economics of staying. But Adeyemi argues the review is the mechanism, not the growth.

His reasoning is specific. Experienced writers leave editorial environments for two reasons above all others: they feel their work is being shaped without sufficient explanation of why, and they feel the publication's direction is opaque to them in ways that make their own contribution feel arbitrary. The weekly review addresses both. When the editorial team reviews what shipped and why it worked, writers receive the feedback loop that most editorial environments defer to annual performance conversations. When the review includes a structured look at what is coming and why those stories are being prioritised, writers understand the editorial strategy rather than simply receiving assignments from it. A writer who understands the strategy is a writer who can contribute to it. A writer who can contribute to the strategy is rarely the writer who leaves.

The ROI question editorial directors avoid

Editorial output quality is not easily measured, and editorial leadership generally resists the pressure to measure it in ways that reduce complexity to a single number. That resistance is legitimate. A publication that optimises for average story quality scores risks systematically underprioritising the ambitious, difficult, or structurally unusual story that defines a publication's character but that individual quality rubrics often score poorly. The risk is real. But the discomfort with measurement has produced an editorial culture in which the connection between editorial process and editorial output is almost never examined rigorously, which means the case for process investment — including the investment of one structured weekly review — is almost never made with the specificity that would make it persuasive to the budget-holders who are always, in every newsroom, asking for justification of editorial overhead.

The Financial Intelligence Weekly, a London-based subscription publication covering European private markets, ran a six-month internal experiment in 2022 in which two of its three editorial desks adopted a structured weekly review and one continued with the existing planning-only format. At the experiment's conclusion, the two desks running reviews showed an average of 22 per cent fewer editorial revisions per piece in post-filing stages, a 19 per cent reduction in the time between commission and file, and a 31 per cent reduction in the number of pieces that were commissioned and subsequently spiked without publication. The third desk's numbers were flat across all three metrics. Editorial director Ciara Malone, who designed the experiment, did not present the findings as proof of causation. She presented them to the publication's owners as "the strongest process-level signal we have found for output consistency in five years of operation," and received budget approval for the review format to become standard across all desks in the following quarter.

How the best editors structure the review

Schrader's format at the Berliner Tagespost runs to three questions: what shipped and what did it do, what did not ship and why, and what does the pattern across both tell us about the week ahead. The session has a hard stop at fifteen minutes. Adeyemi at Conduit Bureau runs a written version on Sunday evenings — a four-section document he distributes to contributors before Monday's planning call, so that the planning call itself can be shorter and sharper. Malone at Financial Intelligence Weekly runs a fifty-minute session that combines the retrospective with the prospective, with the first twenty minutes always allocated to the prior week before anyone discusses new commissions. The formats are different. The structure is the same: close the week before you open the next one, and make the closing deliberate enough to produce information the planning session can use.

The editors who do this well share one additional habit: they track the categories of failure, not just the instances. A single missed filing deadline is an event. Three missed filing deadlines in six weeks in which two involved the same writer and one involved a different writer but the same commissioning editor is a pattern. Patterns have causes that can be addressed. Events have explanations that are usually post-hoc rationalisation. The weekly review, done consistently, converts events into patterns fast enough for the patterns to be addressed before they become structural. Without the review, most editorial teams diagnose the structural problem only when it has already cost them either a writer, a story, or both.

What to watch

The trends and signals worth tracking as editorial operations build more structured review practices into their weekly cadence:

• Whether Substack's editorial tools — currently oriented almost entirely toward publishing mechanics and subscriber analytics — develop any operational layer for editorial teams managing multiple contributors. The gap between what Substack offers a solo writer and what it offers a publication with five or more contributors is wide, and several mid-size Substack-native operations have built bespoke Notion or Airtable systems to manage the editorial review workflow that the platform does not support natively. The first Substack-native editorial operations tool that closes this gap will solve a real problem.
• How the AI-assisted editing layer — specifically tools like Lex, Grammarly Business, and Claude-integrated editorial workflows — changes the downstream economics of editorial review. If AI substantially reduces the revision load per piece, the case for structured commissioning discipline becomes even stronger: the savings from reduced revision time accrue most fully to teams that are also reducing spike rates and late filing, which the review directly addresses.
• The emergence of completion rate as a first-class editorial metric. Traffic has been the dominant editorial measurement for fifteen years. Subscriber completion rate — the percentage of subscribers who read a piece to its end — is a better leading indicator of retention and renewal than any traffic figure, and several independent publishers have made it their primary weekly editorial benchmark. When completion rate replaces traffic as the weekly review's anchor metric, commissioning decisions change: longer, more demanding pieces score well; viral-optimised short pieces often do not.
• The question of whether editorial reviews transfer to distributed teams. Schrader, Adeyemi, and Malone all run primarily co-located or semi-co-located editorial teams. Several publication operations that are fully distributed — contributors across four or five time zones, no shared office — report that the asynchronous written version of the editorial review works as well or better than the synchronous meeting format, because the written record forces precision that conversation allows editors to elide. The format question is not settled.
• The next generation of editorial leadership's appetite for operational discipline. Editors promoted from strong-writer backgrounds — the dominant promotion track in most newsrooms — often have limited exposure to process thinking before they take on leadership roles. Several journalism schools, including Columbia and Northwestern's Medill, have added operational management components to editorial leadership curricula in the last two years. Whether those components include structured review practice is a meaningful variable for how the next cohort of editorial directors will think about weekly cadence.

Frequently asked

How long should an editorial weekly review actually take?

The editors who run it well set a hard stop at fifteen to twenty minutes for the retrospective alone — not including forward planning. Sessions that run past thirty minutes have lost the distinction between examination and relitigating: the team is processing emotion about the prior week rather than extracting the operational signal from it. The constraint forces the team to stay at the level of pattern rather than descending into narrative.

Should writers attend the editorial weekly review or only editors?

The publications with the strongest retention data include contributors in at least a portion of the weekly review — specifically the forward-planning section, in which editorial priorities are explained rather than simply announced. Adeyemi at Conduit Bureau includes all contributors in the written Sunday review document, which means every writer has visibility into both last week's performance and next week's priorities before Monday's call. Writers who attend only planning meetings but not review sessions report, consistently, that they feel treated as execution resources rather than editorial partners. The distinction matters for retention.

What metrics should an editorial review actually track?

Three operational metrics and one quality metric. Operationally: on-time filing rate, spike rate, and revision load per piece in post-filing stages. For quality: completion rate, not page views. Traffic is a distribution metric, not an editorial quality metric. Completion rate — available in most newsletter analytics platforms and in Google Analytics 4's scroll-depth data — tells you whether the pieces you commissioned and edited are holding the readers you already have. That is the editorial question. Traffic tells you whether your distribution is working. Those are different questions and they should not share the same metric.

How do you run an editorial review without it becoming a blame session?

The framing is the mechanism. Schrader's formulation — "what did the system allow to happen?" rather than "who missed?" — is the right starting frame for any review that involves missed deadlines or spiked stories. The editor running the review needs to demonstrate, in the first two or three sessions, that the question is always systemic: a missed brief, an under-specified commission, a scheduling collision, an unclear approval process. When contributors learn that the review produces process improvements rather than individual censure, they stop defending themselves and start diagnosing. That shift, which typically takes three to six weekly cycles to establish, is when the review begins to produce information rather than just consuming time.

Does the editorial weekly review work at smaller publications, or is it an enterprise practice?

It works most clearly at smaller publications, because the feedback loop is tighter and the operational data is simpler to interpret. A solo editor managing four contributors who reviews last week's output in fifteen minutes on a Sunday evening is running a more rigorous editorial operation than most mid-size newsrooms with dedicated staff. The practice scales down more easily than it scales up: at scale, the review must have a clear owner with the authority to implement what it identifies, a coordination problem smaller publications do not face.