Blog
What a chief of staff actually does for a small nonprofit
A chief of staff at a small nonprofit is the operator who turns the executive director’s draft thinking into shipped work. Here is what they actually do each week, what stays with you, and how the role differs from an EA or COO.
What a chief of staff actually does day-to-day at a small nonprofit
At a small nonprofit, the chief of staff is the operator who turns the executive director’s draft thinking into shipped work. The role is concrete, not strategic. Eighty percent of a CoS’s week comes from three places: prep, integration, and follow-through.
The biggest single block is board and leadership prep. On most weeks that means compiling the board packet from the finance report, the program-team update, the development pipeline, and any carryover action items from the last meeting — usually turning four rough drafts into one clean briefing the ED can read on the train. Between board cycles it means prepping the weekly leadership-team meeting the same way: agenda from outstanding decisions, status against last week’s carries, and a one-page summary the ED skims before walking in.
The second block is integration. The ED is the only person who hears from every function — finance, programs, fundraising, operations — and most of that arrives voice-memo or slack-style. A CoS turns a voice-memo about a donor meeting into the donor’s last-touch email, the meeting note, the next-step ask, and the calendar event. They integrate upward to give the ED decision context and integrate downward so the rest of the team gets a clean direction the ED actually signed off on.
The third block is follow-through. Decisions get made in leadership-team meetings that nobody has time to execute. The CoS chases each one — what was decided, who owns it, what blocks the owner, when it will land. They maintain the operating dashboard the ED opens every morning: open decisions, blocked items, deadlines this week, and anything that has been waiting on the ED for more than 48 hours. The CoS is also the person who reviews an SOP, a program report, or a donor email draft before it goes to the ED — so the ED sees a polished version, not a raw one.
What to delegate to the chief of staff versus what stays with the executive director
The line is whether the work is drafting-and-following-through, or whether it is representing-the-organization. Delegate the first. Hold onto the second.
Delegate to the CoS: drafting, research, and follow-through. That includes the first draft of nearly everything written under the ED’s name — board memos, donor emails, funder proposals (the CoS does the drafts and integration, the ED signs off), program reports, hiring scorecards, vendor research, scheduling decisions, and weekly meeting design. The CoS owns the operational dashboard, the cross-team decision log, the board packet assembly, the intake questions for new hires, and the cycle of reminding each function about an open commitment until it ships. They also coordinate hiring loops — collecting candidates, scheduling panels, taking notes — without making the call.
Keep with the ED: anything that represents the organization to the outside world or to the board. Final hire / sign-off. Donor-relationship stewardship — a CoS can prep the meeting but the ED is in the room. The board chair relationship. External narrative and speaking voice — the Op-Ed, the keynote, the public statement. Final budget authority. The signature on the audit, the IRS filing, the grant commitment above any pre-set threshold. Anything where the founder or ED is the trust-holder for the funder, the board, or the staff. The CoS is the operator who gives the ED time to do these things — the CoS is not a substitute for doing them.
How the role differs from an executive assistant and from a COO
The chief of staff sits between two roles that get confused with it. They are not interchangeable — the confusion wastes both hiring and salary budget.
An executive assistant is assistant-first, transactional, and serves one person reactively. The EA owns the calendar, the travel, the inbox triage, the expense reports, the meeting logistics. Their day is shaped by what lands in front of them — a request from the ED becomes an action. They are the ED’s support system. They do not run anything that does not directly touch the ED.
A chief of staff is operator-first, project-shaped, and works laterally as much as upward. The CoS runs meetings the ED does not attend, integrates reports from every function into one briefing, designs the operating cadence, and gives the ED decision context. The CoS is the second pair of hands the ED uses to actually run the organization — the EA is the second pair of hands the ED uses to keep their own day intact.
A COO is the operational second-in-command. The COO manages functional heads (finance, ops, programs, sometimes fundraising), owns P&L or department outcomes, hires and develops their own direct reports, and sits below the ED in the org chart. In most small nonprofits, a COO exists only when the ED is purely external-facing — fundraising, board, narrative — and the COO runs everything else. At that size the COO is often a redundant role with the ED; the CoS is the right fit instead.
The simplest mental model: an EA is your calendar’s immune system. A CoS is the operating system that runs your week. A COO is the person who runs the org while you run the field.
Frequently Asked Questions
Frequently asked questions
How many hours a week does this role really take at a 2–5 person org?
Twenty-five to thirty-five hours a week is the realistic band for a real chief of staff at a 2–5 person nonprofit. Less than 25 means the ED is still doing most of the integration and follow-through themselves; more than 35 means the CoS is doing the ED’s representational work, which the CoS should not be doing. The role scales with how fragmented the ED’s week has become — every additional function (programs, fundraising, board, hiring) is roughly three to five more hours of CoS work.
Can the executive director and chief of staff be the same person for part of the week?
Yes, but only if you block it. The good pattern is a half-day of protected CoS time — Friday morning, say, or the first two hours of every weekday — when the ED sets the ED hat down and operates as their own CoS against a running task list. It does not work when the ED tries to CoS themselves between donor calls. Treat it like a meeting with yourself; if you will not show up for the meeting, the work will not happen.
What does a chief of staff NOT do?
A CoS does not steward donor relationships in person, does not sign the audit or the grant commitment, does not speak for the ED externally, does not sit as the trust-holder with the board chair, does not make the final hire or the final budget call. The CoS drafts, integrates, follows through, and preps — and then hands the ED the polished version and the clean decision context. Anything where the ED’s name matters more than the CoS’s analysis stays with the ED.
Is "chief of staff" just a fancy title for an executive assistant?
No. An EA is assistant-first, transactional, schedule-and-logistics-shaped, and serves one person reactively. A CoS is operator-first, project-shaped, runs meetings the ED does not attend, integrates reports, and gives the ED decision context. If the role is mostly calendar, travel, and inbox triage it is an EA and should be paid and hired as one. If the role is turning four rough function reports into one board packet and chasing blocked decisions across teams, it is a CoS and a different hire.
How is this different from a COO in a 10-person org?
A COO manages functional heads — finance, ops, programs — and owns department outcomes, hiring, and direct-report development. A CoS owns no function; the CoS integrates across functions on behalf of the ED. In a 10-person org the COO is the right role only if the ED is purely external and there is no other second-in-command. In most small nonprofits, adding a COO creates a layer you cannot afford; the CoS gives you most of what the COO would do for less than half the cost, and without owning headcount.
What is the first thing to delegate when the chief-of-staff role starts?
The board packet. Pick the next board cycle on the calendar and move the entire packet assembly — finance summary, program updates, development pipeline, last meeting’s carryover, the meeting itself — to the CoS on day one. It is a contained, two-week task, it forces the right relationships across functions, and it gives the ED a measurable time-back number to anchor the rest of the delegation conversation. After the second packet the rest of the delegation is easy, because everyone has seen the role work.
Ready to operationalize this?
Book a 20-minute discovery call.
We will look at your week, your team shape, and how a chief-of-staff role — human or AI — fits your operating reality.