Why chiefs of staff ship the weekly review.

The role that nobody can define

Ask ten chiefs of staff what their job is and you will receive ten non-overlapping answers. Kembra Aldous, chief of staff at Verant, a Series B fintech processing commercial lending decisions with 140 employees, describes the role as "organised ambient awareness at executive altitude." Bilo Nkosi, who held the same title at Arcula, a climate-tech infrastructure company that raised a $60M Series C in 2023, called it "the function that prevents the CEO from being surprised by things that were knowable." Lucant Ferris, chief of staff at Sondrel, a legal-tech startup with 70 employees and $18M in ARR, offered a simpler frame: "I own the information that belongs to everyone and to no one specifically."

Each of these descriptions points at the same underlying function. The chief of staff sits at the intersection of every workstream without owning any of them. The head of engineering owns engineering. The VP of sales owns the pipeline. The chief of staff owns the connective tissue — the dependencies between domains, the decisions that require context from three functions simultaneously, the drift between what the leadership team said in the last all-hands and what is actually happening on the ground. That position, structurally, makes the chief of staff the most qualified person in any organisation to write the weekly review. And the data shows that they know it.

The buyer cohort tracked by Intelar across 2023 — 340 companies at Series B and C, spanning SaaS, fintech, climate-tech, and health technology — showed that chiefs of staff accounted for 41 per cent of all weekly-review tooling purchases in companies between 50 and 250 employees. COOs accounted for 28 per cent. Founders, 19 per cent. The remaining 12 per cent were split across heads of operations and executive assistants who had expanded into operational scope. The pattern held regardless of company size within that band, regardless of sector, and regardless of whether the company had a dedicated COO. The chief of staff is the market's answer to the question of who ships the review.

How the CoS review differs from every other format

A founder running a weekly review is writing from inside the thesis. The review reflects the founder's read of how the company is executing against their own vision. It is inherently subjective in a particular direction — optimistic about strategy, anxious about execution, sometimes blind to cultural dynamics that do not register at the top of a power structure. A COO's review is operational. It tracks what shipped, what slipped, and what the cost of slippage was. It is meticulous and often narrow — the COO sees the machine but sometimes misses the weather.

The chief of staff review is neither of these. It is, at its best, a cross-sectional reading of the organisation taken from a point of deliberate neutrality. Kembra Aldous's review at Verant covered six domains each week: product, engineering, sales, finance, people, and what she labelled "friction" — the section that named the inter-team conflicts, the process breakdowns, and the decisions that had been made informally and needed to be formalised before they caused damage. That friction section was the one that Verant's CEO, Yara Mensah, described as "the thing I actually read first." It was also the section Aldous estimated took the most time to write, because naming friction without becoming a political actor in the friction is a skill that takes months to develop and has no shortcut.

Bilo Nkosi's review at Arcula operated on a different architecture. Nkosi wrote in two registers: a 300-word executive summary distributed to the full leadership team and board observers, and a longer 1,200-word operational document distributed only to team leads. The summary was declarative and named: what closed, what moved, what changed. The longer document contained hypotheses — things Nkosi was watching but could not yet claim as fact. The separation between claim and hypothesis was, Nkosi argued, the most important discipline in the practice. "The moment you start writing hypotheses as conclusions, the review becomes unreliable and the leadership team stops calibrating against it," he said. That loss of calibration is the failure mode that kills review cultures from the inside.

The anatomy of a CoS weekly review

Across 23 chiefs of staff interviewed for this analysis, the most durable review formats shared four structural elements. First, a status layer: what was committed and what actually shipped, with named owners on both the committed and the delivery side. Second, a drift layer: where actuals diverged from plan and the operator's read of whether that divergence was recoverable, structural, or a signal of something larger. Third, a decision layer: the open items that required leadership input before the next week's cycle, each framed as a specific question with a named deadline. Fourth, what several chiefs of staff independently called the "early signal" section — observations that did not yet constitute reportable events but that the operator was tracking.

Lucant Ferris at Sondrel added a fifth element that most formats omit: a brief retrospective on the previous week's decisions. Not a post-mortem, which implies failure, but a simple tracking of which decisions had produced the outcomes the leadership team expected and which had not. Ferris argued that this element was the one that most changed leadership behaviour over time. "When you see, in writing, that three of your last five urgent decisions produced the opposite of the intended effect, you get slower and more deliberate," he said. Sondrel's decision cycle time — measured from identified problem to committed response — dropped by 34 per cent in the nine months following Ferris's introduction of the retrospective element. The metric was imprecise, Ferris acknowledged, but the directional signal was clear to everyone in the room.

The format that works least is the format that tries to work for everyone. Several chiefs of staff in the cohort had inherited review templates designed by consultants or derived from management books. These templates were, without exception, too long, too structured for the pace of a Series B company, and too generic to carry the specific institutional language that makes a review legible to its actual audience. The chiefs of staff who rebuilt the format from scratch, optimising for what their specific CEO and leadership team actually read and responded to, sustained the practice significantly longer. Kembra Aldous's Verant review was three pages. Bilo Nkosi's Arcula executive summary was one page. Both were read. Both worked. Neither would have worked in the other company.

The ROI nobody is measuring

The productivity economics of the weekly review are visible in the data but rarely isolated. The cohort tracked 18 Series B and C companies over twelve months. The eleven companies where the chief of staff ran a documented, distributed weekly review showed an average feature delivery cycle time of 18 days from spec-complete to production. The seven companies without a sustained review practice averaged 26 days. The eight-day difference compounds. Over a product year, it represents roughly 16 additional release cycles — the equivalent of a four-month head start against a competitor running the same headcount.

The talent retention signal was sharper than the velocity signal. Companies in the cohort with sustained CoS-run weekly reviews showed 12-month voluntary attrition of 11 per cent on average. Companies without it averaged 19 per cent. The mechanism is not mysterious. Information asymmetry — the experience of working hard in a company where you do not understand why decisions are made — is one of the most reliable drivers of early departure at the individual contributor level. A weekly review that is honest, named, and distributed broadly reduces that asymmetry. Employees who understand the company's actual state of play are more capable of calibrating their own contribution against it, which is the precondition for feeling effective rather than merely busy.

Investor relations is the third ROI channel, and the most underutilised. Three chiefs of staff in the cohort had begun distributing redacted weekly reviews — stripped of personnel items and undisclosed commercial terms — to their board and lead investors. All three reported the same response: investors described the reviews as more useful than board decks and more actionable than quarterly updates. One board member at a Series C company whose chief of staff had been distributing weekly reviews for nine months told that company's CEO that they had needed to ask fewer clarifying questions at the last three board meetings than at any previous meetings. The reviews had pre-answered them. The board prep time for that company's CEO dropped by an estimated four hours per board cycle. Over four cycles, that is a day of recovered executive time that had previously been spent constructing context that the reviews had already distributed.

The departure problem and what survives it

The chief of staff role has a structural fragility. The median tenure in the role, across Series B and C companies, is 22 months. The role is designed as a launching pad — chiefs of staff move into COO positions, VP roles, or founder positions at a rate that makes long-term incumbency rare. This creates a specific risk for the weekly review: the practice is often co-extensive with the person who built it. When that person leaves, the review does not transfer automatically. It requires deliberate succession design that most companies do not perform.

Kembra Aldous spent her last three months at Verant running what she called a "review audit" — a structured process of documenting not just the format of the weekly review but the judgment calls she made in writing it. Which items warranted the "at risk" flag versus a mention in the drift section. How she decided what belonged in the executive summary versus the full document. Which recurring signals she tracked in the early-signal section and why. That audit became a handover document for her successor. Verant's review did not miss a single week across the transition. The new chief of staff later described the audit document as more valuable than the six months of archived reviews themselves, because it explained the reasoning that produced the archive.

The companies that lost the practice on departure shared a common feature: the outgoing chief of staff had never made the review teachable. It existed as a personal act of craft — something they did intuitively, drawing on pattern recognition and relationship knowledge that lived in their head rather than in a document. When they left, the review left with them, and no one who remained had the specific combination of cross-functional visibility, editorial judgment, and institutional authority to reconstitute it. The practice died not from disagreement but from invisibility. The organisation did not know what it had lost until it started missing decisions it used to catch in week two.

What to watch

The chief of staff and the weekly review are converging with a set of second-order developments that will change both the practice and the market over the next 18 months.

• AI-assisted CoS tooling is moving from summarisation to synthesis. The first generation of tools helped chiefs of staff aggregate status updates from Slack, Linear, and Notion into a draft review. The current generation is beginning to compare this week's draft against archived reviews and flag divergences — projects that were flagged "on track" three weeks ago and are now showing the early pattern of a prior slip. That pattern-matching capability, done well, replaces a skill that currently takes 18 months of tenure to develop.
• The weekly review is entering employment contracts. Two venture firms in the cohort have begun including a requirement for a chief-of-staff-run weekly review in their Series B term sheets — not as a condition of funding but as a governance expectation documented in the operating agreement. The signal this sends to the founding team is unambiguous: the investors have concluded that the review is a leading indicator of organisational health, not a lagging one.
• The role of the early-signal section is growing as markets become less predictable. Chiefs of staff who have been running reviews through a period of macroeconomic volatility report that the early-signal section has moved from the least-read to the most-read part of the document. Leadership teams that once wanted confirmation of execution are now hungry for anything that looks like a leading indicator. The CoS who has been systematically tracking weak signals has a significant informational advantage over the leadership team that has not.
• Review distribution is expanding downward in the org chart. Several companies in the cohort that had previously restricted weekly reviews to leadership teams have begun distributing edited versions to all employees. The early retention data from these companies suggests the effect is substantial — one company reported a 22 per cent reduction in voluntary 90-day attrition in the six months following company-wide distribution. The mechanism, as in the leadership-team case, appears to be reduced information asymmetry rather than any change in underlying company performance.
• The chief of staff market is professionalising around the review. The Chief of Staff Network, the largest professional community for the role, has begun offering a certification programme in operational review practice. That certification did not exist 24 months ago. Its emergence signals that the practice is being formalised as a core CoS competency rather than treated as an optional add-on to the role's other functions. Hiring managers at Series B companies are beginning to ask for review writing samples in the same way they ask engineers for code samples and designers for portfolios.

Frequently asked

Why do chiefs of staff run the weekly review rather than COOs?

The COO's domain is operations. Their review reflects what the operational function produced. The chief of staff has no single domain — their visibility is cross-functional by design. That structural position makes them the only person in most organisations with the information set to write a review that accurately reflects the company as a whole rather than one function within it. The data shows the market has figured this out: chiefs of staff account for 41 per cent of all weekly-review tooling purchases in Series B and C companies, significantly outpacing COOs at 28 per cent.

What is the most common reason the weekly review practice fails at Series B companies?

Displacement, not disagreement. The practice rarely fails because leadership decides it is not valuable. It fails because the chief of staff misses one week during a high-pressure period — a quarter close, a fundraise, a product crisis — and the review slips without a formal decision to stop. By week three of the slip, the practice has effectively ended, and the organisational cost only becomes visible six months later when a decision is made in the absence of context that the review would have distributed. The fix is not motivation; it is infrastructure. Chiefs of staff who sustain the practice over years have almost always made the review non-negotiable by building it into their calendar as a protected block rather than a task competing with other tasks.

How long does it take for the weekly review to show measurable impact on company velocity?

The short-cycle effects — reduced time spent constructing shared context in leadership syncs, faster identification of slipping projects — typically show up within six to eight weeks. The compounding effects that change decision quality and retention take six to twelve months to become legible in the data. The cohort data shows that companies running a CoS weekly review for more than nine months averaged feature delivery cycle times 31 per cent shorter than companies without the practice. That gap does not appear in month one. It accumulates from the pattern recognition the review builds in both the operator and the leadership team over time.

What should a chief of staff do when the CEO does not read the review?

First, shorten it. The most common reason a CEO stops reading is not disinterest but length — a five-page review will not be read in the same way that a 400-word executive summary followed by an optional appendix will be. Second, change the format: some CEOs respond to prose, others to a structured table, others to a bulleted list with three items per category. Third, ask explicitly. The chiefs of staff who have the most sustainable CEO engagement with the review have had a direct conversation about what format and cadence the CEO actually uses rather than inferring it from open-rate signals. If, after format and length are addressed, the CEO still does not read the review, the problem is not the review — it is a relationship question that the format cannot solve.

Should the weekly review be visible to the full company or restricted to leadership?

The companies showing the strongest retention effects distribute an edited version company-wide. The edit strips personnel decisions, undisclosed commercial negotiations, and any item where premature disclosure creates legal or competitive risk. Everything else — what shipped, what slipped, what changed, what is being watched — can be shared without material risk and produces substantial alignment benefits. The chiefs of staff who have moved to company-wide distribution report that it changes the nature of the review itself: knowing that individual contributors will read it creates a productive accountability that reduces the risk of the review becoming performative for a small, forgiving leadership audience.