How to write a Chief of Staff mandate

Six months into the job, a lot of Chiefs of Staff hit the same wall. You're praised for keeping things moving, then told to focus on your own work, then blamed for passing something to another team that was apparently yours all along, all in the same month and from the same person.

The usual cause is a missing document. A mandate takes an afternoon to draft and an hour to agree, and it becomes the record you'll point to when you ask for a bigger role. The one-page template is below; if the role itself is new to you, start with our Chief of Staff handbook.

What is a Chief of Staff mandate?

A Chief of Staff mandate is the written version of the authority you borrow from your principal. It says what the role is for right now, what it should achieve, and which decisions you can make without asking.

In everyday use, a mandate is the authority to act on someone's behalf, as a government has from voters or a fund has to invest. For a Chief of Staff, it means acting for your principal inside limits you both agreed. Most Chiefs of Staff have the authority without the limits written down.

A job description is written to attract people, so it lists everything the role might touch. A mandate lists what the role will own and what it won't. Your OKRs sit inside the mandate as the quarter's version of its outcomes; our guide to OKRs vs KPIs covers those.

Most roles start without one because a leader feels stretched before they can say what's missing. The new Chief of Staff says yes to everything, each favor becomes a standing task, and by month six the role is a pile of inherited work nobody would have designed. Taraneh Ansari, who moved from HR into the role at OpenSponsorship, summed up the early-stage ethos as "nothing is not my job", and at a small company that's often true. Even a generalist needs a short list of what they won't own. [SCOTT: one line on Spring. Did you have a written mandate, and what would have been on your "not my job" list?]

My read: a posting that can't name the principal rarely names the decisions. The cost shows up at review time, when your principal can't see which outcomes were yours, the review rewards the meetings you ran and the fires you put out, and the feedback says "be more strategic" without saying what that would look like.

What goes in a Chief of Staff mandate?

A good mandate has seven parts, and it fits on one page. Outcomes and decision rights do most of the work.

1. Why the role exists now. Two sentences on what changed in the business, such as a funding round, a reorg or a CEO who now spends half the week fundraising. When the trigger ends, the mandate should change too.
2. The principal and the level. Who you support, and the level of the role on our Leveling Framework, from Analyst to Executive. The level matters later when you talk about pay and title.
3. Priorities for this role, ranked. Rank the four core responsibilities from 1 to 4: priorities and decisions, the operating rhythm, communication up and down, and cross-functional projects. The ranking tells you what to protect when everything is urgent.
4. Three outcomes for the next six months, each with a measure. "The weekly leadership meeting runs without the principal chairing it." "Annual planning closes on time with an owner for every priority."
5. Decision rights in three tiers. Decide: what you decide alone. Recommend: what you shape while your principal decides. Not own: work that belongs to someone else, with their name.
6. How you work together. The 1:1 cadence, the written update, the access you need, the date your principal introduces the mandate to the leadership team, and where you can speak for your principal versus only relay context.
7. A review date. First review at 90 days, then every six months. Put it in both calendars now.

# Chief of Staff mandate

- Principal: [name, title]
- Chief of Staff: [name] · Level: [Analyst to Executive, from the Leveling Framework]
- Start date: [date] · First review: [date, 90 days on] · Then: every 6 months

## Why this role exists now
[Two sentences. What changed in the business that created the need?]

## Priorities for this role (rank 1 to 4)
- [ ] Priorities and decisions: what reaches the principal, what gets delegated or declined, which decisions you prepare
- [ ] Rhythm: leadership meetings, planning, OKRs, board and business reviews
- [ ] Communication: honest information up, clear decisions down
- [ ] Projects: cross-functional projects without a home, each with an exit date

## Three outcomes for the next six months
1. [Outcome with a measure, e.g. the weekly leadership meeting runs without the principal chairing it]
2. [Outcome with a measure, e.g. annual planning closes on time with an owner for every priority]
3. [Outcome with a measure]

## Meetings and processes the Chief of Staff runs
- [e.g. Weekly leadership meeting: agenda, notes, follow-ups]
- [e.g. Monthly business review, board prep]

## Decision rights
- **Decide** (I decide alone): [e.g. leadership meeting agenda; which requests reach the principal's calendar]
- **Recommend** (I shape it, the principal decides): [e.g. quarterly priorities; executive hiring]
- **Not own** (owner named): [e.g. calendar and travel (EA); expense approvals (finance)]

## How we work together
- 1:1: [e.g. 45 minutes weekly, with a written update the day before]
- Access: [inbox, calendar, board materials, compensation data]
- Introduction: the principal introduces this mandate to the leadership team at [forum, date]
- Speaking for [principal]: [forums where I can state a decision vs. only share context]
- Information: [what [principal] shares with me by default; what I share with the leadership team]
- Support: [analyst, EA time, budget, if any]

## At each review
What moved, what we stop, and what changes in scope, level or title.

# Chief of Staff mandate

- Principal: Maria, CEO
- Chief of Staff: Sam · Level: Director
- Start date: February 2 · First review: May 4 · Then: every 6 months

## Why this role exists now
We closed our Series B in January and plan to grow from 120 to 200 people this year. Maria now spends two days a week on hiring and the board, so pricing and planning decisions wait on her.

## Priorities for this role (ranked)
1. Rhythm: leadership meeting, annual planning, board
2. Projects: new pricing, hiring two VPs
3. Priorities and decisions
4. Communication

## Three outcomes for the next six months
1. The pricing change is live by the end of Q2
2. Annual planning closes on the agreed date, with one owner per priority
3. Every board pre-read goes out five days early

## Meetings and processes the Chief of Staff runs
- Monday leadership meeting: agenda, decision log, follow-ups
- Annual planning calendar and templates; board prep

## Decision rights
- **Decide:** leadership meeting agenda; planning calendar, templates and deadlines; board deck structure; VP interview loop design
- **Recommend:** the pricing proposal; company priorities and cuts; the VP shortlist
- **Not own:** final price and offer decisions (Maria); team budgets (CFO); sales comp (VP Sales); the office move (office manager)

## How we work together
- 1:1: 45 minutes every Tuesday, with a written update on Monday
- Access: Maria's inbox and calendar, board materials, compensation data
- Introduction: Maria presents this page at the leadership meeting on March 2
- Speaking for Maria: I can state decisions at the leadership meeting and planning reviews; with the board, I share context only

Why decision rights do the work

Every leader asks one question before acting on your request: can this person decide, or do I need to check with the boss? When the answer isn't written down, careful leaders check, and every check puts a decision back on your principal's desk. So the Decide list is the part of the page that gives your principal hours back. A mandate with an empty Decide list describes a coordinator, however senior the title.

Be concrete. "Owns the leadership meeting agenda" is a decision right; "supports the leadership team" describes nothing anyone could check. Write the speaking-for-your-principal line carefully too: a leader who hears you state a decision your principal hasn't made will start checking everything you say.

If a leader can't find your decision rights in writing, expect them to check every call you make with your principal.

Turning an initiatives list into a mandate

Many new Chiefs of Staff get handed a list of initiatives instead of a mandate, and become the person who asks everyone for updates. Here's an illustration of turning that list into decision rights, for a Chief of Staff to a Series B CEO.

The Decide column is where the hours come back, and the Recommend column is where your judgment shows. The last row is the most useful on the page: an item that moved off your list on day one, with an owner. If every initiative already has an owner and you only chase them, you're running a program office, so take one to own outright.

How many Decide items is right?

The level gives you a guide. Our Leveling Framework describes Manager and Director-level Chiefs of Staff as giving meaningful input on strategic decisions, and VP and Executive-level ones as key influencers, so items move from Recommend to Decide as your level rises. An Associate-level role might have two or three Decide items, mostly about process. A Director should decide the agenda, the calendar and which requests reach the principal. At VP level and above, some company decisions move into Decide, such as resolving a cross-team trade-off when the principal is away.

When your principal won't put anything in Decide, ask for one decision for 30 days, such as which requests reach their calendar, and review it together. A trial is easier to grant than a permanent right. For the Not own list, name the owner every time: calendar and travel (the executive assistant), line management (the functional leader), expenses (finance). Our Chief of Staff vs executive assistant guide shows where the EA line usually falls.

How do you write a mandate with your principal?

Draft it yourself, then agree it with your principal in one working session. Your principal is unlikely to write it, and if you wait for them, they'll read the wait as passivity.

1. Weeks 1 to 3: map before you write. Meet every leader your principal works with, and a few people one level down. Ask what they need from the principal that they aren't getting, and learn who owns which decisions. Our guide to your first 90 days has a listening tour kit.
2. End of week 3: draft the page with your best guesses. A concrete draft your principal can cross out beats an open question.
3. Week 4: one 60-minute session. Expect your principal to move items between Decide and Recommend. Every item they move now is one you won't argue about in month five.
4. Same week: the introduction. Leaders act on a Chief of Staff's asks much faster once they've heard the principal say what the role owns. In our episode on how Zapier's Chief People Officer and his Chief of Staff work together, he briefs her before news lands, so she can support him from the first minute.

Expect one leader to read the page as a land grab, often a COO or head of operations whose work overlaps yours. Show them the draft before the introduction, ask what they'd change, and name them as owner of anything you hand their team.

Running the 60-minute session

Send the draft with this agenda two days ahead.

1. Minutes 0 to 5: why now. Read the two sentences aloud and ask whether they're still true. If the trigger has changed, everything below it will too.
2. Minutes 5 to 15: the ranking. Ask your principal to rank the four responsibilities before showing yours. Where the rankings differ, you've found the misunderstanding that would have surfaced in month five.
3. Minutes 15 to 45: decision rights. Go line by line. For each Decide item, ask "If I made this call without you, when would you be upset?" The answer tells you the real limit, and it often becomes a line in Recommend.
4. Minutes 45 to 55: Not own. Confirm every name. Your principal usually knows of an owner you don't.
5. Minutes 55 to 60: the introduction and the review date. Leave with both in the calendar.

Expect three kinds of pushback. Some principals add everything, so ask them to rank the additions against the three outcomes. Some move every Decide item to Recommend; accept it and ask for the 30-day trial on one. And some say "just do whatever you think is right", the most dangerous answer, because it gives you every decision and no protection. Write down what you'd do in the five most likely situations and get a yes on each.

If your principal resists writing anything down, ask for decisions one at a time: "When a leader asks me to chase their team on a deadline, do I do it, or do I bring it to you?" Write up the answers and send them as "here's what I heard". If you're the executive hiring, write the mandate before you post the role; our guide on how to hire a Chief of Staff shows where it fits.

This week, book the 60-minute session for the end of your first month. If you'd rather start from your notes than a blank page, this prompt turns them into a first draft.

I'm a Chief of Staff (or about to hire one). Draft a one-page Chief of Staff mandate from my notes below.

Use exactly these sections: Why this role exists now; Priorities for this role (rank priorities and decisions, the operating rhythm, communication up and down, and cross-functional projects from 1 to 4); Three outcomes for the next six months, each with a measure; Meetings and processes the Chief of Staff runs; Decision rights (Decide / Recommend / Not own, with the owner named for every Not own item); How we work together (1:1 cadence, written update, access, introduction to the leadership team); At each review.

Rules:
- Keep it to one page.
- Make every decision right specific enough that two people would agree whether it was followed.
- Put anything that belongs to an executive assistant, a functional leader or finance on the Not own list, with the owner.
- After the draft, list 5 questions I should ask my principal to settle anything you had to guess.

My notes:
- Principal and their role:
- Company stage and size:
- What changed that created this role:
- What I've been asked to do so far:
- What I've taken on that I think someone else should own:
- What my principal complains about most:

How do you handle scope creep as a Chief of Staff?

Run every new request through a scope check: which core responsibility does it belong to, which outcome does it serve, and who owns it after you? If it fits the mandate, take it. If it doesn't, route it to an owner or take it with an exit date. I'd choose the exit date over a flat no almost every time: it keeps goodwill and still protects the mandate.

You're the person who notices work with no owner, so work with no owner finds you. The trouble starts when temporary favors become permanent and the role turns into what our community calls the chief of stuff. A routing rule agreed in advance means a no doesn't land as a personal judgment.

The exit date matters most. Cross-functional projects are some of the most valuable work a Chief of Staff does and the easiest place to get stuck, so take each one with a date and a named next owner.

When the creep comes from your principal

The hardest scope creep comes from the person who signed the mandate. Separate what moves from what doesn't: the three outcomes and the decision rights stay fixed for six months, and the weekly priority list underneath them moves as often as it needs to. Each change gets one question: which outcome does this serve, and what drops to make room?

On our podcast, Richard Hoffman said that as his seed-stage fintech's priorities shifted, he recapped his biggest accomplishments, pain points and frustrations every three months, building a paper trail that shows whether he's tracking the work he says matters. Here's an illustration of one week's requests, routed with the table above.

1. Monday, the CEO asks for a competitor teardown before Thursday's board call. It serves the board outcome, so take it.
2. Monday, the VP of Sales asks you to clean up the CRM. Route it to revenue operations and unblock them with a deadline.
3. Tuesday, the CEO wants a new hiring dashboard. No owner, crosses teams: take it for six weeks, then hand it to the recruiting lead.
4. Wednesday, the CFO asks you to chase late expense reports. Decline, kindly, and point to the finance process.
5. Thursday, the CEO asks you to plan the offsite. It's on your Not own list under the EA. Raise it in your update, since the principal may want to move it.
6. Friday, two leaders ask you to referee a launch date. That's a cross-team decision, so write both positions and bring a recommendation.

Two of the six were taken on, one with an exit date. Record all six in the scope check line of your weekly update, so the next review is a conversation about evidence. By month three, the people you routed elsewhere either stop asking or ask better questions; if they go to your principal instead, your principal needs to back the routing.

This week, pick the two requests on your list that fit no outcome. Route one to an owner and put an exit date on the other.

How do you renegotiate your mandate after a few years?

Bring your principal a rewritten mandate, with the evidence for each change. Show what the role owns today against the original page, propose fewer doing items and more decisions, name the support you need, and tie the new scope to a level and a date. I'd bring it a month before the annual review, so you discuss the role first and your rating second.

Three or four years in, the usual story is that the principal has been promoted, the scope has doubled, and the title and level haven't moved. The review says you're an excellent executor but not yet a strategic partner, while back-to-back meetings leave no time to become one. David Kirby, former Chief of Staff at Ford, calls this the doer trap: the way out is moving from doing the work to orchestrating it.

The data backs renegotiating in place. In the Chief of Staff Network's 2026 Pathways Report, 61% of Chiefs of Staff step up when they stay at the same company, against 48% when they leave, and about 8% of completed stints end with a bigger Chief of Staff title at the same company. My read is that most of those were asked for, with evidence on the table. First, have the conversation with yourself about what you want the role to become.

Bring four things:

1. The inventory: everything you own today, sorted into the original mandate's sections, with what each item returned where you can name it (executive hours given back, decisions closed, revenue protected, a launch shipped). The difference between the two pages is your evidence.
2. A new page with fewer process items and more decision rights. Hand off the steady machinery and keep the decisions.
3. The support it needs: an analyst, a deputy, more EA time, or a process another team takes over. Juhi Kabra, who spent more than five years as Chief of Staff to the CEO at Redesign Health and now leads sessions in our Launchpad program, grew her role into an office of the CEO with a deputy reporting to her.
4. A level and a date. Map the new decision rights to the Leveling Framework and ask when level and title will match. According to the Chief of Staff Network's 2025 Salary Report (nearly 500 respondents), average base runs from $91,462 at Analyst to $193,999 at Executive; check yours in our salary guide.

If the answer is "not this year" twice, treat it as information about your principal's choice, and make yours. A new principal also means a new mandate: draft it in their first two weeks, before they define the role around someone else's habits. If you support two principals, keep one mandate with both names and a tie-break rule.

61% of Chiefs of Staff step up when they stay at the same company, against 48% when they leave, according to the Chief of Staff Network's 2026 Pathways Report.

Juhi runs an energy audit every six months: she exports a few weeks of her calendar, sorts it into buckets and checks which work gives energy and which drains it. This week, do the same with your last three weeks and sort what you find into keep, hand off and stop. That list is the first draft of your new mandate.

What does a Chief of Staff mandate look like in different settings?

The structure stays the same; the content changes with the principal. A startup CEO's Chief of Staff usually ranks cross-functional projects first, a functional executive's Chief of Staff the operating rhythm, and an investor's Chief of Staff priorities and decisions.

At a startup, the mandate changes fastest. Richard Hoffman's started in partnerships and new sales and, ten months in, was shifting toward operations as planned; a clear starting point made the change easy to see and agree. In a functional role, such as Chief of Staff to Zapier's Chief People Officer, name which company processes you feed and which you run, and which of the BizOps or PMO team's you never touch.

In an investment firm, the word mandate already means something. Alexa Gellman, who was Chief of Staff at Inspired Capital when we spoke, described the VC Chief of Staff's job as including triage of her managing partner's inbound against the fund's investment mandate. For part-time roles, the engagement scope is the mandate with hours added; our fractional Chief of Staff guide has a one-page scope to adapt.