A Chief of Staff operating audit asks whether the role increases executive capacity or merely absorbs work. The title can look successful because the person is busy and trusted. The audit asks whether the system itself is getting better.

The first question is executive capacity. Is the CEO spending more time on work only they can do? Are lower-value meetings gone? Are pre-reads sharper? Are decisions better prepared? Is executive attention aligned with strategy? If not, the role may be helping the executive cope rather than improving the system.

The second question is context flow. Does leadership see risks earlier? Do weak signals move upward without becoming political? Do teams understand decisions after they are made? Is operating memory visible outside the CoS's head? A strong role makes context travel reliably in both directions.

The third question is decision hygiene. Can the company find what was decided, who owns it, why it was chosen, and when it returns for review? Are action items tied to real owners? Do repeated topics keep coming back unresolved? Decision drift shows the CoS operating system needs work.

The fourth question is cadence quality. Do staff meetings, reviews, offsites, and board prep have clear purpose? Are live meetings used for decisions rather than status? Are old rituals retired when they stop earning time? The CoS should improve the rhythm of leadership work.

The fifth question is role boundary. Does everyone know what the CoS owns? Are functional leaders strengthened or bypassed? Does the CoS hand off special projects cleanly, or do they accumulate orphan work? Boundary clarity prevents the role from becoming a permanent patch.

AI should be included in the audit. Are meeting summaries accurate? Are decision logs useful? Are briefing packets saving time? Are follow-up trackers creating clarity or noise? Are privacy and access rules clear? The tool layer should improve output, not create another operating burden.

Trust is hard to measure but easy to sense. Do people tell the CoS the truth early? Do leaders see the role as fair? Do teams understand when something will be escalated? Does the CoS avoid taking credit for functional work while owning the operating system? Trust is the medium the role works through.

The audit should ask if the company needs a CoS. Sometimes the role is hired to compensate for a CEO who will not decide, a team that will not own work, or an organization that lacks basic cadence. In those cases, a CoS may help temporarily while hiding the real problem.

When the role works, it leaves artifacts: cleaner calendars, better decision records, sharper operating reviews, clearer owner maps, stronger handoffs, and fewer ambiguous projects. The company should not infer value from the CoS's busyness.

The test: is the Chief of Staff making the executive system more capable, or making themselves more necessary? The best role does both for a while, then shifts value from personal heroics into durable operating systems.

The audit should use artifacts, not impressions. Show the calendar before and after. Show the decision log. Show the staff meeting agenda. Show the special-project handoff. Show the owner map. If the role improves the operating system, evidence should exist.

One section should ask what the CoS has stopped owning. This balances the instinct to list everything the person handles. Work that moved into a durable owner or process is a sign of success. Work that keeps accumulating is a sign of role sprawl.

The audit should also ask functional leaders how the role feels. Do they feel supported, bypassed, clarified, or watched? Their answers reveal trust health. A CoS can be effective for the CEO and still create damage if the rest of the executive team experiences the role as shadow authority.

AI use should be audited in practical terms. Which summaries are trusted? Which logs are actually used? Which reminders changed behavior? Which tools created noise? The point is to see whether the tool layer improves work or just creates a better-looking archive.

The CEO should be part of the audit. Many CoS problems are really CEO operating problems. If the CEO will not decide, delegate, or defend boundaries, the CoS cannot compensate forever. The audit should name that honestly.

The outcome should be a sharper charter. Maybe the role narrows. Maybe it hands off special projects. Maybe it shifts from CEO support to executive-team cadence. The role should evolve as the operating system matures.

The audit should end with a small set of operating changes, not a long performance narrative. Pick the two or three fixes that would most improve the system: a cleaner charter, a better decision log, a retired meeting, a handoff plan, or a clearer escalation path. A CoS audit that produces twenty recommendations is usually avoiding the hard choices.

It should also set a review date. The role changes as the company changes, so the audit should not be a one-time exercise. A quarterly or semiannual review is enough for most teams. The point is to keep the role tied to the operating need rather than the habits that formed around it.

The strongest signal is reduced mystery. People should know why the role exists, how to work with it, what it owns, and what it will hand back. When that is true, the Chief of Staff becomes less of a personality-dependent role and more of a durable part of the executive operating system.

Evidence note: this post uses local backlog framing and public Chief of Staff role context including https://review.firstround.com/the-secret-to-a-chief-of-staffs-success-starts-with-a-34-point-job-description/.

This is part 10 of 10 in The Chief of Staff Operating Model.