A Day in the Life of a Chief of Staff: What the Work Really Looks Like

Takeaway: A chief of staff's day moves among leadership preparation, cross-functional work, decisions, and follow-through, with priorities changing as new information arrives.

Job descriptions list responsibilities. The day itself is a sequence of judgment calls about what needs attention, who needs context, and which commitment is at risk.

No two schedules are identical because the role is shaped around one leader and one organization. The representative day below follows a chief of staff at a growing company through a leadership meeting, a launch conflict, and project work that has to move around both. It is an illustration, not a universal schedule.

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 Nate Bennett and Stephen A. Miles argued 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.

7:45 a.m.: orient before the first decision

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 role that Patrick Aylward, a chief of staff quoted in Dan Ciampa's HBR article, puts first: 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.

Protect a working block. The chief of staff uses the first open block for a planning proposal that needs sustained attention. It may move when urgent work appears, but reserving it makes the cost of that choice visible.

10:00 a.m.: run 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. At 11:30, Sales and Product surface different customer launch dates. The chief of staff confirms the decision owner, brings in Support for the customer-impact discussion, and gets the group to state the tradeoffs. The relevant executive makes the date decision; the chief of staff records it and checks that each downstream owner understands the change.

Give the principal a usable read. Someone may raise a problem that is difficult to surface through normal channels, or the leader may ask for a view on an issue shaped by functional interests. The chief of staff should separate direct observation, reported concern, and interpretation, then raise the issue privately in a form the leader can evaluate (HBR).

1:00 p.m.: projects, people, and a changed plan

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 deliberately. At 2:15, a board analysis becomes due a day earlier than expected. The chief of staff confirms the new deadline and required output before moving the project block. Finance can supply part of the analysis; the chief of staff keeps the narrative and final quality check. The plan changes, but the change is explicit rather than a reflex to the newest request.

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. A short update covers what moved, what changed, and what needs the principal tomorrow. Each item makes clear whether the leader needs to decide, review, or simply know.

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? Hours vary by leader, company stage, and current priorities. Ask about the principal's working pattern, travel, time zones, and how the team handles after-hours issues. McKinsey found a median tenure of about 2.3 years in its sample, but the figure doesn't establish why people left or whether hours caused the tenure (McKinsey).

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 this mix of work appeals to you, the free Chief of Staff readiness quiz helps you examine your evidence across six competencies.