AI for Chiefs of Staff in 2026: Decision Logs, Board Packs and Speaking for the CEO

AI can take a chief of staff's assembly work in 2026: pulling decisions out of leadership meeting transcripts, drafting status rollups from project data and condensing pre-reads. It can't decide what reaches your CEO, speak with their authority, or tell you what a function head left out of an update.

This page is for the person in the job, working for a CEO or another senior executive (your principal, in the role's own vocabulary). It follows the meeting cadence you run, then covers the two risks that come with the title: messages that carry your principal's name, and material few others in the company can see.

An AI chief of staff, or a chief of staff using AI?

Those are two separate searches, and the results for this phrase mix them up. An "AI chief of staff" is an assistant app sold to an executive who wants coordination help. One top result, a roundup from alfred_, scores eight such tools out of 25 and puts alfred_ first, so read it as a vendor's page. Two other top results are training for people like you: a $47 guide from Nova Chief of Staff and the $499 Chief of AI Fellowship from Chief of Staff Network.

If you're an executive weighing an app against a hire, what to hand an AI chief of staff first is the better read. A Business Report summary of a New York Times story captures both sides of that choice: postings for the human role are up 85% since 2020, some leaders now prefer AI tools or working directly with their teams, and the executives interviewed argue AI can't replace a chief of staff's judgment or relationships.

The chief of staff's cadence, and where AI enters it

A chief of staff's work repeats on a schedule of meetings, so the useful question is which step of each loop AI can shorten. Harvard Business Review's case for the role frames it as support beyond what an executive assistant can provide. A Chief Executive article by a former corporate chief of staff lists running recurring meetings and processes, preparing the CEO for meetings, challenging the numbers behind key decisions and managing cross-department projects.

After the staff meeting: start with the decision log

The decision log is the best first job for AI in this role, because a transcript holds most of what the log needs and you were in the room to check it. Town's routine shows what the category aims at: after each recurring leadership meeting it adds each decision's date, owner and due date to one running log, flags reversals of earlier decisions and carries overdue items into the next meeting.

A transcript can't separate a decision from thinking aloud, though. If your CEO says "let's hold pricing until Q2," the head of sales may hear a decision and the CFO a suggestion, and a tool will log whatever the words support. Knowing which one it was is your contribution, so confirm anything ambiguous with your principal before the log circulates.

Attached: this week's leadership meeting transcript and our decision log.
1. List each decision actually made: what, who owns it, by when.
2. List separately anything that sounded like a decision but had no owner or date.
3. Flag anything that reverses or contradicts an earlier log entry.
4. List log items past their date that nobody mentioned.
Quote the transcript line for each. Don't guess at an owner.

Status rollups: the tool reads the tracker, not the hallway

A rollup drafted by AI is only as honest as the tracker behind it. A 2024 post on Asana's forum describes Smart status drafting portfolio and goal updates from real-time work data, looking for risks, open questions and roadblocks, on Advanced, Enterprise and Enterprise+ plans. Check Asana's current plans before you count on that. A project marked green in the tracker and slipping in every side conversation will still come back green, so let the draft save the typing, then go ask the owner of anything you doubt.

Keep AI away from reading people, too. Microsoft restricts Copilot from making inferences about an employee's performance, attitude or emotional state from workplace communication. Even where another tool will try, "which VP seems checked out?" is a question to answer from your own one-on-ones.

The board cycle: the calendar stays, the first draft moves

AI mostly shortens the deck-drafting step of board prep, not the rest of the cycle. Zeck's board playbook for chiefs of staff, a vendor's guide, sets out a standard timeline: agenda and goals with the CEO 30 days out, department inputs at 21, a first deck at 14, CEO review at 7, distribution at 3, and a recap with assigned tasks the day after. Diligent's Smart Builder can compress day 14, though Diligent says some of its AI features need a particular package or admin setup. Day 21 doesn't compress, because a late department head is a conversation.

Leave recording out of the boardroom. Cooley's guidance says AI note-taking tools should not be used in board or committee meetings, citing privilege, discoverability and the chill on candid discussion. Write the next-day recap from your own notes.

Your principal's time

Google Calendar's Time Insights shows how a person's meeting time splits and who they meet with most. You can open it for someone else's primary calendar if you can change that calendar and manage its sharing, on a computer only, and an admin can switch it off. Compare the split with the priorities your principal named this quarter, and bring the gap to your next one-on-one.

Speaking for your principal is the line to hold

A chief of staff's message already carries the CEO's authority, so an AI error in your draft can land as a CEO decision. When you write "the CEO wants pricing held until Q2," a VP treats that as an instruction and may never check it. Four habits keep that risk small:

• Trace every position to its source. An assistant fed your principal's emails can produce a plausible view on something they've never considered. Each stance in a draft should point to something they said or signed off on.
• Agree on three categories in advance. What you send as yourself, what you send on their behalf, and what only they send: hard news to an executive, anything to a board director, anything about pay.
• Search your drafts for "the CEO thinks." If you can't say where that phrase came from, delete it or go ask.
• Use AI to argue with the plan, not to voice it. Challenging the numbers is part of the job, so ask for the strongest case against a proposal before you take it to your principal, then bring your own view.

You can see more than the people you forward to

A chief of staff's access is often wider than the recipients of their briefs, so what AI pulls out for you needs as much care as what you paste in. Microsoft says Copilot summarizes only content you can access, so other participants may see a different summary. If your meeting brief draws on a reorg draft in your files and you forward it to a VP, you've disclosed the reorg. Read each brief as its next reader will.

• Reorgs, pay and deals. Microsoft stores Copilot prompts and responses and admins can view them through Content search or Purview. Asking how to sequence an unannounced layoff leaves a record, which you may want counsel's view on first.
• Counsel's advice. You may be in the room when it's given. Per Orrick's summary of United States v. Heppner (S.D.N.Y., February 2026), pasting counsel's advice into a consumer AI tool counts as disclosure that waives privilege. Enterprise terms haven't been tested, and Orrick says non-lawyers generally shouldn't use even private tools for legal analysis unless counsel directs it.
• Workspace tools. Google says Gemini Notebook data under enterprise-grade protections isn't reviewed by people or used to improve models, and that your data region settings don't apply to it. Check that against your own policy before uploading.
• The staff meeting itself. Say so before you record. California requires all parties to a confidential conversation to agree, which can reach a VP dialing in from there. Cooley's candor argument is about boards, but it's worth raising with your principal for a leadership meeting too, since a transcript changes what people say.

If the AI rollout lands on you too

Running company-wide AI adoption is a separate assignment from using AI yourself, and it's the premise of the Chief of AI Fellowship, whose curriculum covers validating use cases, rollout with governance and change management, and a plan to present to leadership. You're well placed for it because you already run the meeting where functions report to the same person. Three things make a good start: one page of approved tools by type of data, one pilot with a named owner in each function, and a standing agenda line at the staff meeting. Agree how long you'll own it, so the program doesn't swallow the role.

Where Merlin fits a chief of staff, and where it stops

Merlin, which we build for the Mac, helps with your own follow-through: what you promised, what others promised you, and who you're about to see. Running on your Mac, it sees your own Gmail, Google Calendar and recordings, plus any apps you connect, so your leadership team's inboxes stay out of reach.

• A staff meeting template. In Meetings, Manage templates… lets you write your own outline, so a staff meeting can come out with sections for Decisions, Owners, Reversals and Still open. Speaker-labeled transcripts are a paid feature. Later, ask in chat what your recordings say was decided about pricing this quarter.
• What's owed to you. Once a staff meeting is transcribed, Merlin may send you a short note listing your own commitments alongside the ones colleagues made to you. Nobody else receives it.
• Threads you owe. The Needs you group shows direct emails, two days to a month old, that you haven't answered. Its signal is mail alone, so a VP chasing you on Slack won't show up there.
• Function reviews and skip-levels. Meeting Brief shows up around ten minutes before the start, carrying attendee backgrounds, prior discussions, commitments and agenda suggestions. Prep me on an upcoming event asks for one sooner.
• A Friday check. A scheduled routine could write you a Friday summary of what's open in your email threads with the leadership team. Routines work unattended and can post to a connected app without asking you first, so point one at yourself, never at the leadership channel. A send requested in chat is different: nothing leaves until you approve it.

Merlin requires a Google account, so a work mailbox on Microsoft 365 can't connect. Recordings are yours only, with no share button, so the log everyone reads still belongs in Notion or a shared doc; Copy transcript is the way out. Asana tasks can't feed its To-do list yet, it isn't a board portal, and it can't place calls. Merlin reads every connected Google account at once, so don't add your principal's mailbox without their agreement and IT's. The audio file is kept locally, but on paid plans a copy goes to a transcription service and your Merlin account holds what comes back, so have the privacy policy reviewed before a work mailbox goes in. For other recorders, see our note taker comparison.

A first month, one loop at a time

Add one step of the cadence each week, and check every step against the version you already do by hand.

1. Week one, get the rules. Ask your general counsel which accounts are cleared for which material, and ask your principal whether the leadership meeting may be transcribed.
2. Week two, run the log beside your own. Keep writing your log as usual, run the prompt above on one transcript, and compare the two entry by entry.
3. Week three, draft one rollup from the tracker. Mark every line you changed after talking to its owner. That list is what the tool can't see.
4. Week four, agree the speaking rules. Take the three categories to your principal and get them to correct the list.

Leave the board cycle for next quarter, and try deck drafting on an internal business review first.