A Day in the Life of a Chief of Staff: What the Work Really Looks Like
Takeaway: A chief of staff's day isn't one job but a constant switch between running the leadership rhythm, driving priority projects, and absorbing whatever is about to fall through the cracks.
Job descriptions tell you what a chief of staff is responsible for. They don't tell you what the work feels like hour to hour. It's a lot of context switching, a lot of quiet coordination that never shows up in a deliverable, and a steady pressure to be the person who notices the thing everyone else missed.
No two days are identical, because the role bends to the leader it serves. But there's a recognizable shape. Here is a grounded walk through a typical day, followed by the patterns that hold across most of them.
A note on why the day varies
More than most jobs, the chief of staff role is defined by one specific relationship. The parallel is the COO role, which Nathan Bennett and Stephen Miles found in Harvard Business Review tends to be shaped by the individual CEO rather than by a fixed set of duties. The same is true here. A chief of staff for a heads-down product CEO spends their day differently than one supporting a founder who is constantly out raising money or selling. Treat the schedule below as a representative day, not a universal one.
Morning: set the agenda before the day sets it for you
Early: triage and orient. The day usually starts before the leadership team is online. The chief of staff scans what changed overnight, what decisions are pending, and what is about to become urgent. This is the air traffic controller function Dan Ciampa describes in HBR: deciding what deserves the principal's attention today, what can wait, and what someone else should own. The goal is to walk into the day with a point of view about the two or three things that actually matter, not just a full inbox.
Prep the principal. Before the leader's first meaningful meeting, the chief of staff makes sure they're ready. That can mean a short briefing, a decision memo with a clear recommendation, or a heads-up about a tension the leader is about to walk into. The work is to reduce the number of moments where the leader has to react cold.
A working block, if you protected one. The strongest chiefs of staff guard time for the one project that needs deep work, before the day fragments. In practice this block is the first thing sacrificed when something breaks, which is why protecting it is a skill in itself.
Midday: the operating rhythm
Run or feed the leadership meetings. Much of a chief of staff's visible value shows up here. They set the agenda so the leadership team spends its limited time on the right questions, capture the decisions made, and record the owners and next steps. A meeting without a clear record of who decided what tends to get relitigated a week later, and preventing that is core to the job.
Work the seams between teams. Between meetings, the chief of staff does the integrator work: connecting two functions that are about to collide, chasing a decision that's stuck between departments, and translating a leadership decision into something a team can actually act on. Little of this is glamorous. Most of it is a series of short, targeted conversations that keep work moving.
Be the honest broker. Somewhere in the day, someone brings the chief of staff a problem they can't raise cleanly through the normal channels, or the leader asks for an unvarnished read on an issue clouded by turf. Because the role has no functional empire to protect, the chief of staff can name the real problem. That neutrality is one of the most valuable things the role offers (HBR).
Afternoon: projects, people, and the unplanned
Push the priority projects. The chief of staff usually owns two or three initiatives that matter and lack a natural home. The afternoon is often where that ownership lives: moving a cross-functional project forward, unblocking a team, or building the analysis behind a decision the leader needs to make soon.
Manage the information flow. A recurring task is keeping the single source of truth honest, the shared view of goals, metrics, and open decisions that keeps the leadership team arguing about reality rather than about who remembers what. When that source is clean, decisions get faster. When it isn't , the chief of staff spends the day reconciling versions.
Absorb the unplanned. The defining feature of the role is that the day rarely goes as planned. A deal wobbles, a leader needs a sensitive conversation handled, a board update is suddenly due. The chief of staff is often the person who quietly catches these before they become fires. This is why the job is intense and why, as McKinsey found, the average tenure sits around 2.3 years, a sign the role's pace is hard to sustain over the long term (McKinsey).
End of day: close the loops
Follow up on decisions. The value of a decision is in the follow-through. Late in the day the chief of staff confirms owners have what they need, sends the notes that turn a discussion into action, and flags anything that stalled.
Brief the principal, briefly. A tight end-of-day sync, even a few lines, keeps the leader current on what moved and what needs them tomorrow. Good chiefs of staff make this efficient, respecting that the leader's attention is the scarcest thing in the building.
Reset for tomorrow. The last task is often re-sequencing priorities for the next day based on what changed, so the morning starts with a point of view instead of a scramble.
The patterns behind the day
Across all the variation, a few things stay constant.
- Constant context switching. The role moves between strategy, logistics, people, and firefighting many times a day. Comfort with that whiplash is a core requirement.
- Influence without authority. Most of the work gets done through relationships and the principal's mandate, not through command. The chief of staff rarely orders anyone to do anything.
- Invisible value. Much of the best work, the problem quietly prevented, the misalignment caught early, never shows up in a deliverable. The role is often measured by what didn't go wrong.
- Trust as the operating system. The job runs on being a discreet, reliable confidant. Everything else depends on that trust holding (HBR).
FAQ
Is a chief of staff's day mostly meetings? A large share of it, yes, because the role owns the leadership operating rhythm. But the meetings are the visible part. The higher-value work often happens in the short conversations and prep around them.
Do chiefs of staff work long hours? The role is intense, and its pace is one reason average tenure is only about 2.3 years (McKinsey). Hours vary by leader and company, but the cognitive load of constant context switching is real regardless of the clock.
How is the day different from an executive assistant's? An executive assistant's day centers on the leader's time and logistics, the calendar, travel, and inbox. A chief of staff's day centers on the leader's priorities and decisions. The two are complementary, and many leaders have both.
What makes a good day versus a bad one? A good day is one where the priority project moved, decisions turned into action, and a problem got caught early. A bad day is one that was entirely reactive, spent absorbing other people's fires with nothing of your own advanced.
What does a chief of staff actually do all day? The day splits between three things: running the leadership operating rhythm, driving the two or three priority projects that lack an owner, and absorbing whatever is about to fall through the cracks. Mornings go to triage and preparing the principal, middays to leadership meetings and connecting teams, afternoons to project work and the unplanned. Underneath it all is constant context switching and quiet coordination that rarely shows up in a deliverable.
If you want the systems that make a chief of staff's day run instead of run over you, we publish free operator tools, including a weekly executive priorities brief and a leadership meeting run sheet. Join the email list to get them and new breakdowns as they publish.
