A day in the life of a Chief of Staff

Ask a Chief of Staff what they did today and you'll usually get a pause. The best work of the day was a decision made on time, a conflict that never reached the CEO, a deadline nobody missed, and none of it shows up on a calendar.

Below is a sample day hour by hour, the weekly rhythm that holds it together, and real schedules from Chiefs of Staff at a media startup, a fractional practice, Google, Box and Zapier, drawn from the Chief of Staff Podcast. For the role itself, start with what a Chief of Staff does.

What does a Chief of Staff do all day, hour by hour?

A typical day starts with a short priorities check with the principal, moves into a protected block for writing, then runs through leadership meetings, one-to-ones and escalations, and ends with follow-ups that turn the day's decisions into owners and dates. Each block serves one of the four core responsibilities: priorities and decisions, the operating rhythm, communication up and down, and cross-functional projects.

The day below is a composite, built from routines Chiefs of Staff have described to us, for a Chief of Staff to the CEO at a 150-person, Series B software company. It's illustrative; no single person's diary looks exactly like it. [SCOTT: one line on what a normal Tuesday looked like for you at Spring?]

Most of the scheduled time goes to the operating rhythm. The other three responsibilities happen in the gaps: one-to-ones, quick calls and the escalation that arrives at 3pm with no owner. Three blocks matter more than the rest.

The first is the morning call. At beehiiv, Chief of Staff Brian Schneider and his CEO talk every weekday at around seven, on the CEO's drive to the gym, to compare priorities for the day, as they describe on our episode about beehiiv's Chief of Staff model. A 15-minute daily call survives busy weeks better than a long weekly meeting that keeps getting moved.

The second is the hour after the leadership meeting. Most decisions die between the meeting and the follow-up. Send the decision log within the hour, with an owner and a date on each line, and the meeting becomes a system; send it the next afternoon and it becomes a memory. The third is the block before nine, the only part of the day nobody else wants. Use it for the writing that makes the rest of the day go faster: pre-reads, memos, the board narrative.

Send the decision log within an hour of the leadership meeting, with an owner and a date on every line.

How to handle the escalation nobody owns

The 2:30 block is where most Chiefs of Staff lose the afternoon. Escalations sit between two teams, so neither team's leader can close them without the other, and you're the one person who works for both. Here's how that hour can run, using the stuck customer issue from the table.

1. Spend ten minutes finding the decision. The customer wants a fix by Friday. Support says it's a product bug; product says it's a configuration problem. The real decision is who owns the diagnosis, and who tells the customer what by when.
2. Name an owner for each half. Product owns the diagnosis by Wednesday noon. Support owns the customer update by end of day today, with a holding message you help draft.
3. Write it down where both teams see it, four lines: the issue, the two owners, the two dates and the point at which it comes back to you.
4. Decide whether the CEO hears about it. Tell them only if the customer is large enough to show up in the board deck, or if the fix needs a trade-off between the two teams' roadmaps. Otherwise it goes in Friday's note as resolved.

Fix it yourself only when there's no plausible owner, the customer risk lands inside a day and the fix takes you under an hour. If you solve every escalation, teams learn that the fastest path to a decision is your inbox, and by month three you've become the company's help desk. If the same two teams keep appearing in your escalations, the fix is a conversation about who owns that seam.

How does a Chief of Staff's week run?

A Chief of Staff's week usually runs on two fixed points with the principal: a priorities check at the start of the week and a review at the end. Everything else, from the leadership meeting to the metrics review to board prep, hangs between those two points.

The week is the smallest unit where the principal can change their mind without chaos: a day is too short to re-plan, and a month too long to wait. If I could protect only one meeting in the week, I'd protect the end-of-week review with the principal. Eric Nehrlich learned this the hard way as Chief of Staff for Google Search Ads. For his first few months he didn't send a weekly plan, and his principal kept asking why he was working on the wrong things.

His fix was a Monday-morning email with the top three things he'd get done that week, which his principal signed off on. When a request for a CEO presentation landed on Wednesday, the question became "which of the three can wait?" You can only protect priorities you wrote down first.

Here's a week that works for most Chiefs of Staff to a single principal. Adjust the days to your company's rhythm.

# Weekly calendar: Chief of Staff to [principal]

## Every day
- 15 min: check-in with [principal] (same time daily)
- 90 min: protected focus block (writing, analysis, decisions)
- 2 x 10 min: buffers after your longest meetings
- 30 min: close loops (decision log, follow-ups, tracker)

## Sunday or Monday morning (30 to 60 min)
- Draft this week's top 3 to 5 priorities
- Email them to [principal] with links to the relevant docs

## Monday
- 30 min: priorities sync with [principal]
- Leadership team meeting (you own agenda, pre-read and decision log)
- Send decision log within 1 hour

## Tuesday
- Focus block for the biggest deliverable of the week
- 1:1s with 2 to 3 functional leaders on cross-team work

## Wednesday
- Metrics or OKR review
- Midweek check: what new request landed, and what moves to make room?

## Thursday
- Board, investor or exec-review prep
- Prep [principal] for next week: key meetings, decisions, risks

## Friday
- 30 min: review with [principal] (done / slipped / decisions needed)
- Send your weekly update
- Plan next week's focus blocks before you log off

Keep the touchpoints short and fixed, so they survive busy weeks, and put the focus blocks on the calendar before anyone else can, because a Chief of Staff's open time is everyone's open time. If your company already has an operating rhythm, the week should mirror it: your metrics review lands where the business reviews its numbers. Our guide to building an operating rhythm covers the company-level calendar this week plugs into.

Send your principal a Sunday or Monday note with three priorities and ask for a yes, a no or a swap, four weeks in a row before you judge it. The prompt below turns that note into a calendar.

I'm a Chief of Staff to [principal, title] at a [size, stage] company.

Here are my principal's priorities for next week: [paste the Sunday or Monday priorities email]
Here is my calendar for next week: [paste calendar export: titles, durations, attendees]
Here are the deliverables due: [list]

1. Match every meeting to one of the priorities, or mark it "unrelated".
2. Propose which unrelated meetings I should decline, shorten or send a delegate to, with a one-line reason I can send.
3. Place two 90-minute focus blocks a day where they protect the biggest deliverables.
4. Add prep slots before the three meetings that matter most, and say what I should prepare.
5. Draft a two-line note to my principal confirming the plan and flagging any priority that has no time against it.

Treat the output as a draft: you know which declined meeting will cause a problem.

How does the day change by company and role?

The shape of the day changes with who you support and how big the company is. A startup CEO's Chief of Staff lives in short cycles with daily touchpoints. A Chief of Staff to a technical leader runs planning across teams. An enterprise Chief of Staff runs a calendar of reviews. A fractional Chief of Staff runs several of these at once.

Only 41% of Chief of Staff postings say who the role supports, and where they do, 44% name the CEO, founder or president, according to the Chief of Staff Network's 2026 Pathways Report. If you're choosing between offers, I'd pick the setting whose week you'd happily repeat 50 times, because its shape barely changes once you're in it.

A startup CEO's Chief of Staff: Kyle Hagge's week at Morning Brew

Kyle Hagge, Chief of Staff to the CEO at Morning Brew, runs his week off three fixed points, as he explains on the episode recorded live at our New York Brain Trust. On Sunday, for one to two hours, he turns a running list of objectives into three to five priorities for the week and emails them to his CEO, which he says helps him avoid the "Sunday scaries". On Monday at 10am they meet to confirm the list. On Friday they review what got done and what slipped.

The CEO's priorities can shift weekly, sometimes daily, and most of the work is cross-functional projects with no clear owner, because a 50 to 300 person company has more problems than owners. The common risk is becoming the person who keeps everything running and never gets time to think, so protect one focus block a day, even if it's 60 minutes.

A fractional Chief of Staff: Zoe Jakubowich's day

Zoe Jakubowich runs a fractional practice with several clients at once, as she describes on our episode on managing five clients at once. She's up around 5:00, does heads-down client work from 5:30 to 7:00 before anyone can call, walks outside until 8:00, keeps late morning for coffees and business development, and runs client calls from about 11:00 to 5:00. Evenings go to proposals when there are any, and Friday keeps time for learning.

The structure has to come from you, because no single principal sets your calendar. Our fractional Chief of Staff guide covers how to set up that kind of practice.

A large company: Eric Nehrlich's planning year at Google

In a big company, the day is often one step of a long cycle. Eric Nehrlich ran the annual planning process for Google Search Ads. It started in July with strategic questions and position papers, moved through an offsite and a month of budget and headcount requests, and ended with a final budget in December, so a week in October looked very different from a week in March. The enterprise job is a calendar of reviews: annual plans, quarterly business reviews and steering committees, with the Chief of Staff keeping the machinery running and the rooms small.

A technical leader's Chief of Staff: Sarah Kislak's two-by-two at Box

Sarah Kislak was Chief of Staff to the head of engineering at Box. She ran a weekly "two-by-two" with a peer Chief of Staff: both Chiefs of Staff and both principals met in one room to review deliverables and pressure-test anything that cut across both teams, like a new planning process, as she explains on our episode about following your talent. Days in this setting go to planning and translation: roadmaps, planning cycles and making sure engineering priorities match the business.

A remote Chief of Staff: Karly Gelardi at Zapier

Karly Gelardi, who was Chief of Staff to the Chief People Officer at Zapier when we spoke, saw her principal, Brandon Sammut, in person maybe twice a year, as they describe on our episode about working together remotely. They synced every Monday morning, where she reviewed his calendar and asked to join the meetings that mattered to her priorities, added a second hour later in the week, and kept a weekly one-to-one of at least an hour. Brandon's channel was pinned in Karly's Slack so his messages never got lost.

Remote work removes the hallway, so the information you'd overhear in an office has to come to you on purpose, through skip-levels on video, team channels and the decision log. If your leadership team spans more than a few time zones, put your focus block in the hours when nobody else is online, and write the decision log for readers who weren't in the room.

Why are Chief of Staff calendars back to back, and how do you fix it?

Chief of Staff calendars fill up because every process you build tends to stay with you. You set up the leadership meeting, the planning cycle and the intake for new initiatives, and a year later you're still running all three, with a one-to-one that has shrunk to 20 minutes of fire drills. The fix is to write more, meet less and give processes away once they work.

Replace the triage one-to-one with a weekly note

Send a short note before the one-to-one with what you need from the principal, what's in flight and what's coming. Most principals answer the decisions in writing before you meet, which frees the meeting for the forecast, the risks and, once in a while, your own path. Our guide to the weekly update has the template.

Give processes away once they run

The first time you run a process, you're the designer. The third time, you should be training its owner. Pick one process a quarter, write down how it works, and hand it to the function that should own it, with you as backup for one cycle: planning to finance or strategy, initiative intake to the PMO or the most relevant leader. You keep the design and the review, and hand over the weekly chasing.

Expect the handoff to dip for a cycle, and the first time something slips your principal may ask you to take it back. Agree with your principal beforehand what "good enough" looks like and how long the new owner gets to settle in, then hold that line, because taking a process back after one bad week tells every leader that work handed to them from your desk isn't really theirs. If there's truly no one to hand work to, that's a staffing case to make to your principal.

Hand one process a quarter to the team that should own it, with you as backup for one cycle.

Leave the meetings you don't own

A Chief of Staff gets invited to everything, because your presence signals the principal is paying attention, which is why declining feels risky. Mark each recurring meeting "own", "learn" or "signal". In your first 90 days, "learn" meetings earn their place. After that, keep the "own" meetings, drop most "learn" ones, and replace every "signal" meeting with a two-line written summary from its owner. Tell each organizer why you're stepping out and ask them to flag anything that needs your principal.

Around week six, someone will escalate something you'd have caught in a meeting you dropped. Ask that owner to add a "needs the principal" line to the summary, and don't rejoin unless it happens again.

Build recovery into the day

Back-to-back meetings with no gaps drain you in a way that compounds. Carrie McMahon, a two-time Chief of Staff now at Horizon3.ai and a breathwork teacher, told us that time blocking alone only got her so far. She built two- or three-minute resets into the day, like breathwork before a call, and matched tasks to her natural energy. If your sharpest hours are early, that's where the board narrative and the decision memos go, and the afternoon gets the one-to-ones and the triage. Ten-minute buffers after your longest meetings cost almost nothing. AI adds a twist: hand the easier tasks to tools, as our guide to AI and the Chief of Staff covers, and what's left is a week of hard calls back to back, so plan the recovery on purpose.

How do you take time off as a Chief of Staff?

You take real time off by making yourself unnecessary for a week before you leave: write a coverage plan that says who handles each part of your job and what they can decide, tell your principal and the leadership team, and set an out-of-office reply that routes people to the right owner. If nobody can cover for you, that's the risk to fix first.

New Chiefs of Staff, especially in small companies, often say their hours crept from a normal workday to most of the evening, and that they work through their time off. If one person holds the whole rhythm and nobody can step in, the business has a single point of failure. Work-life balance accounted for 9.4% of the reasons Chiefs of Staff gave for leaving a job, according to the Chief of Staff Network's 2025 Salary Report, and a burned-out Chief of Staff tends to hit the higher-ranked reasons too.

Then write an out-of-office reply with one line per topic: "For the leadership meeting, contact [name]. For board prep, [name]. For anything urgent, [principal's EA]." For more on boundaries, see our post on creating work-life balance as a Chief of Staff.

Before Friday, draft your coverage plan even if you have no time off booked, and share it with your principal. The parts of your job only you can do are your next handoff.

What does a good day look like for a Chief of Staff?

A good day for a Chief of Staff is one where the right decisions got made on time, nothing important waited on you, and the principal walked into every meeting prepared. Your list may not be finished.

That makes the job easy to undervalue, including by the person doing it. Once a week, write down the two or three outcomes you moved, one line each: the decision that got made, the conflict that got resolved, the plan that shipped. After a quarter you'll have the evidence for your review, your next salary conversation or your next role. If you're earlier in your career, the day described here is also good interview prep; our guide on how to become a Chief of Staff covers the routes in, and your first 90 days covers the start.