The Chief of Staff Playbook: Cadence, Decisions, Follow-Through

A chief of staff playbook comes down to three things you run every week: an operating cadence, a decision log, and a ledger of commitments that someone chases until each one is closed. Everything else, the org charts, the special projects, the board prep, hangs off those three. This playbook walks through how to start, what to own, how to build the rhythm, and which tools belong in your toolkit.

It is written for chiefs of staff, executive assistants who are growing into the role, and founders who are acting as their own chief of staff because they have not hired one yet.

TL;DR

• Spend your first 30 days listening to your principal’s operating style. Do not try to fix processes yet.
• Own the recurring mechanisms (the weekly leadership meeting, the quarterly planning cycle), not a pile of one-off projects.
• Keep a decision log with a review trigger on every entry, and a single ledger of every promise made in meetings, email and chat.
• Write your role down by day 90 and review it quarterly, or you will become the dumping ground for unassigned work.
• Choose tools that share memory. If you are the one copying context between apps, the stack is doing your job badly.

Table of Contents

• What the role is, in one sentence
• The first 90 days
• The operating cadence
• The decision log
• The commitments ledger
• Building your toolkit
• Our perspective
• Try the ledger on your own week
• A 90-day checklist you can copy
• FAQ
• Sources

What the role is, in one sentence

A chief of staff is a force multiplier for a leader: you turn their priorities into decisions, owners and follow-through, and you protect their time for the work only they can do. A good one executes what is in front of them. A great one builds the system so that less lands in front of the leader in the first place.

If you are weighing this role against an executive assistant, the difference is mostly time horizon. We cover it in chief of staff vs executive assistant. In short, an assistant protects the days, and a chief of staff shapes the months.

The first 90 days

Most chief of staff failures happen early. Either the new hire moves too slowly for the CEO to see them operate, or too fast for the leadership team to trust them. A 30/60/90 frame keeps you in the middle lane. Day 30 produces a diagnostic, not a plan. Day 60 produces one thing killed and one thing fixed, not a transformation.

Days 1 to 30: learn the principal

Your instinct will be to learn the business first. Resist it, at least a little. The first 30 days should be a quiet listening tour focused on how your principal operates, and trying to solve problems before you have earned trust is a common cause of failure in the first 90 days.

Practical things to do in this window:

1. Shadow the principal’s week. Note where meetings run over, where decisions stall, and what they keep re-explaining.
2. Ask how they like to receive information: a morning brief, a written memo, a quick call.
3. Ask what they would never want sent without seeing it first. Those are your approval boundaries.
4. Sit in on every recurring meeting once and write down who owns it, what it decides, and what it produces.
5. Start your commitments ledger on day one, even if it is a plain document. You will be surprised how many promises are already floating.

Days 31 to 60: one kill, one fix

By now you have a diagnostic. Pick one recurring meeting or report that no longer earns its place and remove it. Pick one broken handoff and repair it. Small, visible wins matter more than a grand redesign, because they show the leadership team that you reduce load rather than add to it.

Days 61 to 90: install the mechanisms

This is where you take ownership of the recurring infrastructure. Experts argue that the mechanisms of work are worth more than individual projects: owning the weekly leadership meeting or the quarterly planning cycle gives you a permanent seat in the company’s operating system. We cover that in the next section.

Also by day 90, write your role down. The most common failure mode is becoming a dumping ground for ad hoc, unassigned tasks. A written scope, reviewed every quarter with your principal, is how you protect your leverage.

The operating cadence

An operating cadence is the repeatable system that turns priorities into decisions, ownership and follow-through. At minimum it connects a weekly priority review, a decision log and a dependency view. Here is a simple version for a team of 10 to 100 people.

Make the weekly meeting about decisions

Strategic leadership meetings should prioritize diagnosis and action over status updates. A practical agenda has three parts: what is off track (exceptions only), what needs a decision from this room, and what was committed last week and is still open. Status that can be read goes in a pre-read, not into the meeting.

The same source describes a useful habit, the send-back rule. When a decision reaches the top that belongs to someone lower down, you return it to its owner with guidance instead of holding it at the top. It sounds small. It is the single best defense against the leader becoming the bottleneck.

Design the rhythm to remove meetings

The best cadences eliminate meetings rather than adding to them. That matters more than it sounds. Research from Rob Cross and colleagues found that time spent in meetings, email and calls has grown by more than 50% over a decade, and that efficient collaborators can reclaim 18 to 24% of their work time by changing just four or five behaviors. Every meeting you retire is part of that gain. If you want to go further, our guide to asynchronous meetings shows which ones can become a written update.

If you are building this from scratch, our walkthrough of an executive operating system lays out the pieces in more detail.

The decision log

A decision log is not a meeting transcript. A transcript tells you what was said, and a log tells you what was decided, by whom, and when it should be questioned again. To be useful it needs a review trigger: the specific condition, such as a cost threshold or a market change, that forces the team to revisit the decision. Without one, decisions get relitigated or quietly forgotten.

A good entry fits on four lines:

• Decision: Move the enterprise pilot to Q1.
• Owner: VP Sales.
• Why: Security review will not clear before December.
• Review trigger: Reopen if the review clears early or a competing deal exceeds $200,000.

That example is illustrative, not a real company’s entry. The shape is what matters. You can keep the log in any shared document, and the discipline is in writing it the same day.

The commitments ledger

This is the part most playbooks skip, and it is where chiefs of staff quietly lose hours. Work does not only live in project trackers. Promises are made out loud on calls (“I’ll send the revised terms Friday”), buried in email threads, and tossed off in chat. If they are not captured in one place, they depend on someone’s memory.

A workable ledger has five fields: who promised, to whom, what, by when, and where it came from. Then comes the part that makes it a ledger and not a list: someone chases each item until it is closed, and closed means the outcome happened, not that the task was ticked.

Two habits keep it honest:

• Capture in the moment. Within an hour of a meeting, log every promise, including the ones the principal made. Our guide to post-meeting follow-ups has templates for this.
• Verify before you send. A recap that misstates an action item is worse than none. See how to verify actions in a meeting recap email before it goes out.

Building your toolkit

A typical chief of staff stack has four layers: initiative tracking, documentation, meeting intelligence, and communication. According to one 2026 toolkit guide, most tools are good at tracking what is happening but weak at showing whether the strategy is understood and believed by the team. That gap is real, and no software closes it for you. You close it by asking people, in the listening tour and in the cadence.

If you are choosing between tracking tools, a Jira versus Asana comparison gives a clear way to weigh them against how your team actually works.

The integration-layer problem

The more tools you add, the more you become the connection between them. An AI notetaker has your meetings but has never seen your inbox. An email assistant sees your inbox but has no idea what you promised on a call. A contact manager knows your people but not your calendar. Each is clever inside its own box, so you end up copying context between them all day.

That is the problem to solve when you pick your stack. Ask of each tool: does it share what it knows with the others, or do I carry it across by hand?

Meeting intelligence that goes beyond transcripts

Researchers studying how people use meeting information afterward argue for “meeting bridges”: artifacts that help people make sense of a meeting and collaborate asynchronously, rather than static archives. Their finding is that current tools often stop at transcripts. In practice, you want a summary that maps to owners and dates, and a link from every action back to the moment it was agreed. Our pieces on meeting summaries that map notes to tasks and meeting transcription that closes promises cover how.

For how teams connect the discussion to later work, the executive search tech stack overview shows how another function structures its tools around shared understanding.

Our perspective

We build Otto, and we think the chief of staff job is mostly an integration job that nobody admits to. The value is not in any single tool. It is in holding one picture of what was said, promised and scheduled across email, calendar and meetings, and in noticing when those pictures disagree.

So we built around one shared memory. Otto listens in meetings, reads email and calendar, and captures every promise made in any of them into a single ledger that it chases until it is closed. Because it sees everything at once, it can answer the question that matters each morning: what should I focus on today?

We also hold a firm line on trust. Nothing is sent or finalized without explicit approval. Otto drafts, you decide. A chief of staff’s credibility is the product, and no software should spend it for you.

If your work is scattered across a dozen tools and you are tired of being the glue, that is the job we want to take off your plate. If you want the longer version of how we think about missed promises, read how to stop missing follow-ups.

— Eddie

Try the ledger on your own week

Otto has a free plan at $0 per month, an Upgraded plan at $20 per month for higher usage limits, integrations and advanced features, and a Max plan at $50 per month. Start with the free plan, connect your email and calendar, and see which promises from last week were still open. You can start with Otto today. If you already keep tasks elsewhere, we explain how to sync tasks to Notion.

A 90-day checklist you can copy

• Week 1: Agree approval boundaries. Start the commitments ledger.
• Week 2 to 4: Shadow, listen, and map every recurring meeting with its owner and output. Present a diagnostic, not a plan.
• Week 5 to 8: Remove one meeting or report. Fix one handoff. Start the decision log with review triggers.
• Week 9 to 12: Take ownership of the weekly leadership meeting and the quarterly planning cycle. Write down your role and set a quarterly review date.

Review it at day 90 with your principal. Ask two questions: what did I take off your plate, and what am I doing that someone else should own?

FAQ

What should a chief of staff do first?

Listen. Spend the first month learning how your principal works, who they trust, and where their time leaks, before you propose changes. Acting too early is a common cause of failure in the first 90 days. Deliver a diagnostic at day 30, not a plan.

How is a decision log different from meeting notes?

Notes record the conversation. A decision log records the outcome, the owner and a review trigger, the condition that means the decision should be reopened. That trigger is what stops decisions from being relitigated or lost over time.

How do I avoid becoming a dumping ground?

Define your role in writing by day 90 and review it every quarter with your principal. Own recurring mechanisms, such as the weekly leadership meeting, instead of accepting every ad hoc request. When a request is not yours, route it back to its owner with guidance.

What tools does a chief of staff need?

At minimum: something to track initiatives, a shared document space for the decision log and playbook, meeting capture, and a way to manage email and calendar. The deciding factor is whether they share context. If you are copying information between them by hand, you are the integration layer.

Sources

• Your First 30/60/90 Days as a New Chief of Staff
• The Onboarding Playbook Every New Chief of Staff Should Have in Their First 90 Days
• Chief of Staff Operating Cadence and Decision Log
• Reclaiming Your Day (Rob Cross)
• Chief of Staff Tools: The 2026 Toolkit Guide
• Meeting Bridges: Designing Information Artifacts that Bridge from Synchronous Meetings to Asynchronous Collaboration

Recommended

• Chief of Staff vs Executive Assistant: Leaders, Think Days or Months
• 5–15 Minute Executive Daily Briefing: EA Playbook, 3 Templates
• Reminders vs Tasks for Founders: How AI Chiefs of Staff Catch Promises
• Managers: 8 Steps to Schedule Recurring Check Ins on Major Calendars