How COOs ship the weekly review.

What the COO review is not

The confusion starts with role definition. A COO is not a senior chief of staff and is not a co-founder with a different title. The role carries explicit accountability for operational performance — for the machine that turns strategy into shipped product, closed revenue, and working infrastructure. That accountability changes what the weekly review is for. A founder's review is an act of self-reflection shared outward. A chief of staff's review is a cross-functional intelligence brief. A COO's review is an accountability document: it names what was committed, what was delivered, who owned each, and what the gap cost.

Renata Schwall, COO of Lendria, a B2B payments infrastructure company processing $2.4B in annual volume with 310 employees, frames it plainly. "The review I write is not about what I think," she said. "It is about what happened. Those are different documents." Schwall's weekly review at Lendria runs to four pages and is distributed to 22 people — the full leadership team, three board observers, and the general managers of each product line. It contains no opinions about strategy. It contains named delivery outcomes, cycle time data, headcount actuals against plan, and a brief section on where the week's results diverged from the prior week's commitments. The strategy questions belong in different conversations. The review answers: did we do what we said we would do.

That narrowing of scope is not a limitation — it is the design. A COO who uses the weekly review to surface strategic ambiguity or explore adjacent opportunities has misunderstood the instrument. The COO review derives its value from precision and predictability. Leadership teams that can trust the format — who know exactly what the document will contain and what it will not — calibrate against it efficiently. Leadership teams that must re-learn the document each week because its scope has shifted do not. The discipline of the format is not bureaucracy. It is the thing that makes the signal legible.

The anatomy of the COO review

Across interviews with 19 COOs at companies ranging from Series C scale-ups to public-company divisions, the highest-functioning review formats shared five structural elements. None of the 19 had arrived at these elements through a template or a management framework. All had converged on them through iteration — through writing reviews that did not work, distributing them to leadership teams that did not use them, and adjusting until the format produced the response it was designed to produce.

The first element is the commitment register: a table, usually brief, that lists last week's named commitments — the specific deliverables, with named owners, that the leadership team had agreed to hold — and records their actual status. Green, amber, or red, with a single explanatory line for every amber and red. Maro Duvall, COO of Vertara, a climate-tech company listed on Nasdaq in 2022 with 520 employees and $190M in revenue, uses a four-column format: commitment, owner, committed date, actual outcome. "If I can't fill in column four," Duvall said, "then we didn't actually commit to anything last week. We listed aspirations." The distinction between a commitment and an aspiration is the difference between an accountable organisation and a hopeful one.

The second element is cycle time data. Not output data — output data tells you what shipped. Cycle time tells you how long things took from commitment to delivery, and whether that duration is compressing or expanding over time. Schwall at Lendria tracks three cycle time metrics in every review: feature delivery from spec-complete to production, support escalation from first ticket to resolution, and hiring from open-requisition to offer-signed. "If any of the three moves more than ten per cent in the wrong direction in a single week, I call it out explicitly," she said. "If it moves in the same direction two weeks in a row, it is not noise. It is a system problem." The compounding of unaddressed cycle time drift is one of the most reliable predictors of a quarter close that surprises the leadership team. The COO review exists, in part, to prevent that surprise from being surprises.

The third element is the cost of slippage — the section that distinguishes the COO review most sharply from both the founder version and the CoS format. When a commitment slips, the COO review names what the slip cost: in engineering hours redirected, in customer commitments affected, in revenue delayed. Duvall at Vertara introduced a "slippage cost" line to her review format after a product delay in Q2 2023 that the leadership team had treated as a minor operational inconvenience until the quarterly board conversation, at which point the $1.7M in deferred contract revenue that the delay had produced became visible. "The board should not have been surprised by $1.7M," Duvall said. "I should have named it in week two of the slip, not in the board deck." The review is the mechanism by which operational reality reaches the people who need it, at the velocity at which they need it.

Where it diverges from the CoS and founder formats

The CoS review is a cross-functional intelligence brief from a position of deliberate neutrality. The founder review is a strategic reflection shaped by the founder's proximity to the thesis. The COO review is neither. Its primary axis is not insight but accountability, and its primary reader is not the CEO but the operational layer beneath the C-suite. This shapes distribution in ways that most companies get wrong.

Callum Reese, COO of Harkon Health, a Series D digital health company with 280 employees and $44M in ARR, spent his first six months at the company distributing the weekly review to the seven-person leadership team only. His eighth month, he expanded distribution to 34 people — every team lead and senior individual contributor with multi-team dependencies. "The leadership team was the wrong primary audience," he said. "They already knew most of what was in it. The people who needed it were the team leads trying to prioritise against competing demands they couldn't see." The review became a coordination mechanism rather than a reporting mechanism. Decision-making friction at the team-lead level dropped measurably in the two quarters following the distribution change — Reese estimates the reduction in misaligned priorities eliminated approximately 140 hours per quarter of rework that had been invisible in the leadership team's field of view.

The cadence also differs. A founder's weekly review operates on the founder's natural week — Sunday night or Monday morning, shaped by the founder's rhythm. A CoS review is often timed to the CEO's information cycle. The COO review must close on a cadence that reflects the operational cycle, not the executive calendar. Schwall at Lendria closes her review Friday at 16:00 and distributes it Friday at 17:00, without exception. "The review closes when the week closes," she said. "If you move it to Monday you are writing about last week from inside this week, and the context has already started compressing." Duvall at Vertara closes on Thursday evening to give her leadership team the Friday to absorb the content before the weekend. The cadence is a design choice with downstream consequences for how the review is read and what is done with it.

The founder review can absorb strategic musing. The COO review cannot. Reese at Harkon Health included a strategic hypothesis section in his first version of the review format — a paragraph on what he was thinking about for the following quarter. Three weeks in, he removed it. "It was generating discussion about things that weren't the agenda," he said. "The review started to feel like a strategy document and stopped feeling like an operations document. People came to the Monday sync with questions about the hypothesis rather than responses to the commitments." The discipline of keeping the COO review purely operational is harder than it sounds for operators who are also close to strategy. It requires a deliberate editorial choice each week to leave insights in a different document.

The ROI evidence

Measuring the return on a weekly review is methodologically difficult and rarely attempted. The cohort tracked by Intelar across 2023 and into 2024 — 47 companies at Series C, D, and public-company division level — offers the most detailed picture available. The 28 companies in which the COO ran a documented, distributed weekly review meeting the structural criteria described above showed an average operational cycle time of 21 days from cross-functional commitment to resolved outcome. The 19 companies without a sustained COO review practice averaged 31 days. The ten-day gap is not explained by company size, sector, or headcount. The review practice is the strongest single variable in the model.

The talent data is consistent with the CoS cohort but larger in magnitude. Companies running a COO-level weekly review for more than nine months showed 12-month voluntary attrition of 13 per cent. Companies without the practice averaged 21 per cent. The mechanism is the same: information asymmetry drives disengagement, and the COO review — particularly when distributed below the leadership team — reduces that asymmetry at the operational layer where attrition is most costly to replace. An engineer who understands why a feature was delayed, who was responsible for the dependency that caused it, and what the company is doing about it is significantly less likely to attribute the delay to organisational dysfunction and update their options accordingly.

The board dynamics data is the least discussed and the most commercially material. Duvall at Vertara began distributing a lightly redacted version of her weekly review to board members on the Friday of each week, rather than waiting for the quarterly board meeting to surface operational detail. At the next three board meetings, the average duration dropped by 40 minutes per session. The question-to-decision ratio — the proportion of board meeting time spent on questions that could have been answered by pre-read material versus decisions that required board engagement — improved from roughly 60-40 to 30-70. The board had more context going in and spent less time constructing it in the room. For a public company division where each board session involves board members' time billed at rates that most operators do not want to calculate, the efficiency is not symbolic.

What to watch

The COO review is evolving under pressure from three concurrent forces: AI tooling that is changing the economics of production, investor expectations that are moving from quarterly to weekly transparency, and a generation of operators who learned the practice at fast-moving companies and are now bringing it into larger, slower institutions where the resistance is structural rather than cultural.

• AI-assisted data aggregation is collapsing the production time of the COO review from two to three hours to under 45 minutes at the companies that have integrated it effectively. The tools pulling status from Linear, Jira, Salesforce, and Rippling into a structured draft are now good enough that the COO's time is spent editing and judging rather than assembling. The editing work is harder than the assembly work — it requires the operator's institutional knowledge to distinguish a recoverable slip from a structural problem — and it is now the full labour cost of the review rather than a fraction of it. COOs who invested the time to configure these pipelines in 2023 are running reviews in 2024 that their peers who did not invest cannot produce at comparable quality without significantly more calendar time.
• Investors at Series C and Series D are beginning to treat the presence of a structured COO review as a diligence signal. Two growth-equity firms in the cohort have added the review to their post-investment operating cadence requirements — not as a formal covenant but as an expectation documented in the initial board governance discussion. The implicit argument is that a COO who runs a weekly review is a COO who has thought carefully about what accountability infrastructure the company requires. The review is proxy evidence for operational maturity that the board deck cannot supply.
• The public-company division context is the hardest environment for the review and the one where the data shows the largest uplift. Division COOs operating inside large public companies face reporting environments designed for compliance, not for operational velocity. The weekly review format forces a parallel reporting layer that the enterprise ERP does not provide — a layer written in the operational language of the division rather than the accounting language of the parent. Duvall at Vertara argues that this is the single highest-leverage structural move available to a division COO: "You will never make the enterprise reporting system tell you what is actually happening. So you build your own instrument, and you protect it from being absorbed into the enterprise system."
• The COO review is beginning to replace the Monday all-hands at scale-up companies that have grown too large for the all-hands to function as an information mechanism. Companies between 200 and 400 employees in the cohort that shifted from weekly all-hands meetings to a weekly COO review plus an optional Q&A session reported freeing an average of 340 person-hours per month — 1.4 hours of all-hands time across 240 employees — that had previously been consumed by a format that most recipients rated as low-value. The review covers what the all-hands was supposed to cover and does it asynchronously, at each reader's optimal attention level rather than at a shared scheduled time.
• Succession design for the COO review is emerging as a distinct capability that search firms are beginning to ask about in executive placement conversations. Callum Reese at Harkon Health spent 30 days before his departure documenting the judgment logic of his review — which metrics he watched and why, how he evaluated the severity of a slip, what the distribution list was designed to do. That documentation became a hiring artefact. Harkon Health's incoming COO inherited not just the format but the reasoning behind it. The transition cost one week of review distribution rather than four months of institutional memory reconstruction. Search firms report that COO candidates who can show evidence of this kind of review succession planning are preferred in placements at companies where the incoming COO is inheriting a team rather than building one.

Frequently asked

How does the COO weekly review differ from the company's existing operational reporting?

Operational reporting systems — ERP dashboards, CRM summaries, sprint velocity charts — are designed for compliance and measurement. They answer the question of what the numbers say. The COO review is designed for accountability and decision-making. It answers the question of what the numbers mean, who owns the gap between plan and actuals, and what is being done about it before the quarter ends. These are different documents serving different functions. The companies that try to replace the review with a dashboard invariably find that the dashboard cannot carry the editorial judgment — the naming of risk, the flagging of drift — that the COO review provides when it is done well.

Should the COO review include financial metrics or is that the CFO's domain?

The COO review should contain the operational metrics that drive the financial outcomes — cycle times, delivery rates, headcount actuals against plan, capacity utilisation — rather than the financial outcomes themselves. Revenue, margin, and cash metrics belong in the CFO's reporting layer. The COO review is the upstream document that explains why those financial metrics are what they are. In the most functional executive teams, the CFO and COO coordinate their weekly reporting cadence so that the CFO's Friday financial summary and the COO's Friday operational review arrive together, creating a complete picture without overlap or redundancy. This coordination requires a deliberate decision by the CEO or CEO and COO together to design the reporting architecture rather than letting it accumulate organically.

How long should the COO weekly review be?

The COO reviews in the Intelar cohort that showed the highest engagement from their intended audiences ranged from 600 to 1,400 words of prose, plus a commitment register table that typically added two to three pages. The distribution that maximises both readership and impact is a 300-word executive summary followed by the full document as an appendix — the summary is read by everyone on the distribution list, the appendix by the people with functional responsibility for the items it contains. Reviews shorter than 600 words tend to lack the specificity that makes them actionable. Reviews longer than 1,800 words tend not to be read in full by the people who most need to read them.

What is the most common reason COO reviews fail to achieve operational impact?

Passive framing. COO reviews that describe what happened without naming who is responsible for what comes next are read once and forgotten. The commitment register in the following week's review has no entries because no commitments were made. The review becomes a historical document rather than an operational instrument. The fix is structural: every item in the COO review that identifies a gap, a slip, or an open risk must name an owner and a resolution date. Without those two fields, the item is observation rather than accountability, and observation without accountability does not change operational behaviour.

Can the COO weekly review replace the leadership team's weekly sync meeting?

The COO review replaces the information-transfer function of the weekly sync — the 40 minutes typically spent on status updates that all attendees could have read in advance. It does not replace the decision-making and relationship function of a well-run sync. The companies in the cohort that reduced their weekly leadership sync from 60 minutes to 25 minutes after introducing the COO review reported that the remaining 25 minutes produced more decisions per unit of time than the 60-minute session had previously. The review pre-distributes the context that the meeting would have constructed in real time, leaving the meeting for the work that requires people in the same room — or the same video call — to resolve.