How a Chief of Staff manages context
How a Chief of Staff keeps what the leader knows, decided and promised in one place: a context file, decision log and commitments list, with 2 AI prompts.
Ask AI
Share

Context management is how a Chief of Staff keeps track of what their principal knows, has decided and has promised, and makes it available to the people and tools that need it. In practice it's four records kept current every week: a one-page context file, a decision log, a commitments list and stakeholder notes.
- Four written records do most of the work: a context file, a decision log, a commitments list and stakeholder notes. About 20 minutes every Friday keeps them current.
- The work runs in four steps: capture it soon after you hear it, curate it every Friday, direct the right page to whoever needs it, and check what comes back against the source.
- Start with the commitments list. It's usually the one your principal uses first. Then log each decision within 24 hours: why, the options that lost, who decided and when to revisit it.
- Keep candid reads on people out of shared files and AI tools. If you wouldn't read a note aloud to the person it's about, it stays out.
- Date every section and keep a handover note ready. The median completed Chief of Staff stint is 20 months, and context that isn't written down leaves with you.
You sit in more rooms than almost anyone on the leadership team, so the reasons behind decisions, the promises made on calls and the history of old debates collect in your head. That works until you take a week off, someone reopens a settled decision, or an AI tool answers like a stranger because none of it is written down. Writing it down is part of the job from your first week, so your principal (the executive you work for) and your AI tools work from the same facts.
What context should a Chief of Staff keep?
Keep five kinds of context: current priorities, decisions and the reasons behind them, commitments in flight, relationships and what people care about, and the history that explains the present. Each lives in a different place and goes stale at a different speed.
Two of the four core responsibilities depend on it. In Chief of Staff job postings, 37% ask for a thought partner on decisions and 41% ask for someone to run cross-functional initiatives. Both need you to know what was decided before, by whom and why.
Priorities change quarterly, commitments change daily, and history barely changes at all. A single document for everything fails quickly, because the fast-moving parts go stale and drag down trust in the slow-moving parts.
When each record gets updated
Each kind of context goes stale at its own speed, so each gets its own record.
Daily glance
Commitments
Your commitments list.
Within 24 hours
Decisions
The decision log, with the reason.
After each conversation
People
Stakeholder notes, for you only.
Weekly
Priorities
The context file.
When it changes
History
The context file appendix.
Where each kind of context lives
| Context | Where it lives | Who sees it | Update |
|---|---|---|---|
| Priorities and what's off the list | Context file | Principal, leadership team, approved AI tools | Checked weekly, rewritten quarterly |
| Decisions and why | Decision log | Leadership team | Within 24 hours of the decision |
| Commitments in flight | Commitments list | Principal, owners named on it | Daily glance, weekly review |
| People and relationships | Stakeholder notes | You only | After each meaningful conversation |
| History and vocabulary | Context file appendix | Anyone joining or covering for you | When something changes, plus a quarterly read |
Jamie White, then Chief of Staff for marketing at Notion, changed how she works after a mentor told her: "You can't do that if you're the only person that has the context." She built a shared command center where meeting notes flow into the documents each team works from, so action items don't depend on her memory.
History is the kind most Chiefs of Staff skip. Delong Lu, then Chief of Staff at Proton, had been there almost ten years, since he joined as one of its earliest product managers. He said that history lets him spot trouble early. A newer Chief of Staff doesn't have that history, but they can write down what they learn so the next person starts further ahead.
I'd start with the commitments list, because your principal will use it first, and build the context file the same week. Expect to find decent priorities, scattered decisions and no written commitments.
How do you build a context file your principal and your AI tools can use?
A context file is one page that tells anyone, human or AI, what matters right now for your principal: priorities in order, what's off the list, who owns what, the decisions that shape everything else, and how your principal wants information. Start it in about 30 minutes and update it every Friday.
People covering for you stop guessing, and AI tools stop answering like strangers, because every request starts from the same page of facts. Only 12.5% of senior leaders in our AI Readiness Diagnostic connect AI to their other tools. For the rest, a tool knows only what they give it.
Dara Chen, then Chief of Staff at Rad AI, said AI tools can connect a company's documents, but "they have to be written down. So who's writing them down?" Our AI guide and AI setup guide both build on this file.
If a tool reads the file and can also act, schedule only jobs that read and draft. Set every action that sends, shares or deletes to ask for your approval first. Our Claude guide shows where that setting is.
Template: Leadership context file
Context file: [Principal name, title]
Last updated: [date] · Owner: [Chief of Staff] · Next full rewrite: [first week of next quarter]
This quarter's priorities (in order)
- [Priority]: why it matters, what "done" looks like, owner
- [Priority]
- [Priority]
Off the list this quarter
- [Item]: why it was deprioritized, who agreed
Who owns what
| Area | Owner | Notes |
|---|---|---|
| [Area] | [Name, title] | [Current focus, how they like to work] |
Decisions that shape everything else
| Date | Decision | Why | Revisit when |
|---|---|---|---|
| [Date] | [Decision] | [Reasoning] | [Trigger] |
Full log: [link to decision log]
Commitments in flight
Open commitments: [link to commitments list] · Overdue this week: [number]
How [principal] wants information
- Format: [e.g. one page, decision first, numbers in a table]
- Tone: [e.g. direct, no hedging]
- Never: [e.g. surprises in a group setting]
Our vocabulary
- [Term]: what we mean by it
Open questions we haven't answered yet
- [Question]: who is working on it, by when
Board updates
- Order: summary, metrics against plan, priorities on track / at risk / off track, asks of the board, what we promised last time and haven't done.
- Use only numbers from the attached files. Flag every calculated number as [CALC].
Rules for AI working with this file
- Flag anything that conflicts with the priorities above.
- Never state a number, name or date that isn't in the source material. Mark gaps as [CHECK].
- Anything about a person is a draft for me to verify, never a fact.
Appendix: history (read each quarter)
- [Event or year]: what happened, and why it still shapes decisions now
# Context file: [Principal name, title]
Last updated: [date] · Owner: [Chief of Staff] · Next full rewrite: [first week of next quarter]
## This quarter's priorities (in order)
1. [Priority]: why it matters, what "done" looks like, owner
2. [Priority]
3. [Priority]
## Off the list this quarter
- [Item]: why it was deprioritized, who agreed
## Who owns what
| Area | Owner | Notes |
| --- | --- | --- |
| [Area] | [Name, title] | [Current focus, how they like to work] |
## Decisions that shape everything else
| Date | Decision | Why | Revisit when |
| --- | --- | --- | --- |
| [Date] | [Decision] | [Reasoning] | [Trigger] |
Full log: [link to decision log]
## Commitments in flight
Open commitments: [link to commitments list] · Overdue this week: [number]
## How [principal] wants information
- Format: [e.g. one page, decision first, numbers in a table]
- Tone: [e.g. direct, no hedging]
- Never: [e.g. surprises in a group setting]
## Our vocabulary
- [Term]: what we mean by it
## Open questions we haven't answered yet
- [Question]: who is working on it, by when
## Board updates
- Order: summary, metrics against plan, priorities on track / at risk / off track, asks of the board, what we promised last time and haven't done.
- Use only numbers from the attached files. Flag every calculated number as [CALC].
## Rules for AI working with this file
- Flag anything that conflicts with the priorities above.
- Never state a number, name or date that isn't in the source material. Mark gaps as [CHECK].
- Anything about a person is a draft for me to verify, never a fact.
## Appendix: history (read each quarter)
- [Event or year]: what happened, and why it still shapes decisions now
Example: Context file for the CEO of an 80-person company (illustration)
Context file: CEO, 80-person software company
Last updated: Oct 3 · Owner: Chief of Staff · Next full rewrite: first week of January
This quarter's priorities (in order)
- Close the Series B by March. Done means a signed term sheet. Owners: CEO and CFO.
- Launch the enterprise tier. Done means three paying enterprise customers. Owner: VP Product.
- Hire a VP Engineering. Done means an accepted offer. Owner: CEO, with the recruiter.
Off the list this quarter
- Expansion into Europe: parked at the September offsite, agreed by the CEO and the head of sales
Who owns what
| Area | Owner | Notes |
|---|---|---|
| Fundraise | CEO and CFO | CFO runs the data room; CEO takes every investor call |
| Enterprise tier | VP Product | Demos on Thursdays; wants feedback in writing |
| Sales | Head of sales | Prefers a ten-minute call to a document |
Decisions that shape everything else
| Date | Decision | Why | Revisit when |
|---|---|---|---|
| Aug 14 | Delay the pricing change to Q1 | Renewal risk on our two largest accounts | Both renewals signed, or Dec 1 |
| Sep 12 | No new hires outside engineering until the round closes | Keep burn flat through the raise | Term sheet signed |
Full log: Leadership decision log
How the CEO wants information
- Format: decision first, three bullets
- Never: a surprise in the leadership meeting
Our vocabulary
- Enterprise: accounts with 500 or more seats
Rules for AI working with this file
- Never state a number, name or date that isn't in the source material. Mark gaps as [CHECK].
# Context file: CEO, 80-person software company
Last updated: Oct 3 · Owner: Chief of Staff · Next full rewrite: first week of January
## This quarter's priorities (in order)
1. Close the Series B by March. Done means a signed term sheet. Owners: CEO and CFO.
2. Launch the enterprise tier. Done means three paying enterprise customers. Owner: VP Product.
3. Hire a VP Engineering. Done means an accepted offer. Owner: CEO, with the recruiter.
## Off the list this quarter
- Expansion into Europe: parked at the September offsite, agreed by the CEO and the head of sales
## Who owns what
| Area | Owner | Notes |
| --- | --- | --- |
| Fundraise | CEO and CFO | CFO runs the data room; CEO takes every investor call |
| Enterprise tier | VP Product | Demos on Thursdays; wants feedback in writing |
| Sales | Head of sales | Prefers a ten-minute call to a document |
## Decisions that shape everything else
| Date | Decision | Why | Revisit when |
| --- | --- | --- | --- |
| Aug 14 | Delay the pricing change to Q1 | Renewal risk on our two largest accounts | Both renewals signed, or Dec 1 |
| Sep 12 | No new hires outside engineering until the round closes | Keep burn flat through the raise | Term sheet signed |
Full log: Leadership decision log
## How the CEO wants information
- Format: decision first, three bullets
- Never: a surprise in the leadership meeting
## Our vocabulary
- Enterprise: accounts with 500 or more seats
## Rules for AI working with this file
- Never state a number, name or date that isn't in the source material. Mark gaps as [CHECK].
Priorities come first, because every request gets checked against them. "Off the list" comes second. When someone pitches a project, you point to the line and the person who agreed to it, and the argument usually ends. It works best in the areas your mandate covers. Keep the file to one page. A long file buries the line that matters under ten that don't.
Test the first version
The example above is about 30 minutes of work for a Chief of Staff to the CEO of an 80-person company. The vocabulary line looks small, and it saves a lot of confusion about which deals count as enterprise.
Then test it. Ask an approved AI tool, with only the file attached, what the CEO's top three priorities are and who owns each. If the answer is vague, the file is vague. If it names the wrong owner, fix that row before anyone else reads it.
Whose priorities, and what your principal actually looks at
The common mistake is writing your own view of the priorities. The file records your principal's order, even where you'd rank them differently, and changes when they change their mind. If you're Chief of Staff to a functional leader, the file holds the function's priorities and names the company priority each one serves.
Principals differ in what they look at. Some principals Jamie White worked with ran every meeting from a visual roadmap. That didn't fit Notion's pace of launch after launch, so she and the CMO ran the business from the shared command center instead. Whichever artifact your principal prefers, the context file sits underneath it and keeps the facts in one place.
Expect pushback the first time you share it. A leader may read their own line and feel boxed in, so share it with your principal first, then ask each leader to correct their own row. They'll correct it faster than they'd write it, and the file becomes theirs as well. Some principals never open it; I'd keep it anyway, for whoever covers for you, for your AI tools and for the handover.
Remi Guarini, then founding Chief of Staff at Neon, has kept one document in every Chief of Staff role since her first. It's now a Google Sheet with her principal's to-do list, her own, and notes about the principal. She shares it with her principal. "They don't really look at it though," she said. "It's really for me." She edits it every day. When she was out for her wedding, she gave the two teammates covering for her a copy, with the parts they didn't need taken out, as their training manual.
By month three, leaders start using the file's lines to settle arguments, and some will lobby you to change a line before a debate. Keep the "who agreed" note on every off-the-list item, so changing one needs the person who agreed to it. Rewrite the whole file from a blank page in the first week of each quarter, because a file that's only ever patched carries old assumptions nobody remembers making.
This week, fill in the priorities, off-the-list and information sections, then use the file for one real task and compare the result with what you got before.
How do you keep a decision log and a commitments list current?
Log every decision in one line: what was decided, why, the options that lost, who decided and when to revisit it, with a link to the decision memo if there was one. After a leadership meeting, the decision record (the decisions, owners and dates) goes out within two hours, and the log entry follows within 24 hours. A decision made on a call or in a message gets the same 24 hours.
Keep commitments in a separate list with an owner and a date for each. Update both lists in your 20 minutes on Friday, with the other records, before you write your weekly update.
The log stops the same debate coming back every quarter: when someone reopens a decision, you show the reasoning and the trigger the team agreed would justify revisiting it. Over time the "Decided by" column also shows whether the decision rights in your role description match how decisions actually get made.
Template: Decision log
Decision log: [Team or principal]
| Date | Decision | Why (one line) | Options considered (and why they lost) | Decided by | Shaped by | Revisit when | Link |
|---|---|---|---|---|---|---|---|
| [Date] | [What was decided, in one sentence] | [The reason that tipped it] | [Each option that lost, and why] | [Name] | [Names] | [Trigger or date] | [Doc or meeting notes] |
Rules
- One line per decision. Link to the long version if there is one.
- After a meeting, the decision record goes out first, within two hours.
- Log within 24 hours, then send the line to the people who decided.
- Reopen only when the "revisit when" trigger happens, or the decider asks.
- Disagreements get recorded: "[Name] disagreed because [reason]; decision stands."
- A reversal gets a new line. The old line stays.
# Decision log: [Team or principal]
| Date | Decision | Why (one line) | Options considered (and why they lost) | Decided by | Shaped by | Revisit when | Link |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Date] | [What was decided, in one sentence] | [The reason that tipped it] | [Each option that lost, and why] | [Name] | [Names] | [Trigger or date] | [Doc or meeting notes] |
Rules
- One line per decision. Link to the long version if there is one.
- After a meeting, the decision record goes out first, within two hours.
- Log within 24 hours, then send the line to the people who decided.
- Reopen only when the "revisit when" trigger happens, or the decider asks.
- Disagreements get recorded: "[Name] disagreed because [reason]; decision stands."
- A reversal gets a new line. The old line stays.
Example: Decision log for a CEO's leadership team (illustration)
Decision log: CEO and leadership team
| Date | Decision | Why (one line) | Options considered (and why they lost) | Decided by | Shaped by | Revisit when | Link |
|---|---|---|---|---|---|---|---|
| Aug 14 | Delay the pricing change to Q1 | Renewal risk on our two largest accounts, raised by the head of sales | Change prices in Q4: lost because both renewals were still open | CEO | CFO, head of sales | Both renewals signed, or Dec 1 | Leadership notes, Aug 14 |
| Sep 12 | No new hires outside engineering until the round closes | Keep burn flat through the raise | Keep hiring outside engineering: lost to the burn target | CEO | CFO | Term sheet signed | Offsite notes |
| Sep 12 | Park expansion into Europe | Sales capacity goes to the enterprise tier | Expand into Europe now: lost to the enterprise tier | CEO | Head of sales | January offsite | Offsite notes |
Disagreements
- Aug 14: head of marketing disagreed because the Q4 campaign assumed the new prices; decision stands.
# Decision log: CEO and leadership team
| Date | Decision | Why (one line) | Options considered (and why they lost) | Decided by | Shaped by | Revisit when | Link |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Aug 14 | Delay the pricing change to Q1 | Renewal risk on our two largest accounts, raised by the head of sales | Change prices in Q4: lost because both renewals were still open | CEO | CFO, head of sales | Both renewals signed, or Dec 1 | Leadership notes, Aug 14 |
| Sep 12 | No new hires outside engineering until the round closes | Keep burn flat through the raise | Keep hiring outside engineering: lost to the burn target | CEO | CFO | Term sheet signed | Offsite notes |
| Sep 12 | Park expansion into Europe | Sales capacity goes to the enterprise tier | Expand into Europe now: lost to the enterprise tier | CEO | Head of sales | January offsite | Offsite notes |
Disagreements
- Aug 14: head of marketing disagreed because the Q4 campaign assumed the new prices; decision stands.
One decision, logged and reopened
Take the pricing line in the example log above. The decision record went out an hour after the August meeting. That evening you wrote the log line and sent it to the CEO, the CFO and the head of sales. The head of sales corrected one word.
In October, the head of marketing raises pricing again in the leadership meeting. Without the log, that's a forty-minute debate about what was said in August. With it, you put the line on screen: one renewal has signed and the other hasn't, so the conversation takes five minutes, and when the second signs in November you add the item to the next agenda yourself.

The judgment call is what counts as a decision. My test: log it if someone will now act differently because of it. "We'll think about pricing" fails; "Pricing waits until the renewals sign" passes. A "not yet" passes once it names who decides and by when, so log it. Decisions made in direct messages or on a call you weren't on count too, so ask about them in your 1:1.
In a remote company the log line links the chat thread where the decision was made. In a larger company each team may keep its own log, and your principal's holds only decisions that cross teams or reach the board. A Chief of Staff to a functional leader keeps the function's log and copies cross-team decisions into the company one. Our operating rhythm guide adds an owner, a due date and a status to each line, so someone follows up on each decision.
Fill in the Options considered column with each option that lost and why, because the losing option is the one most likely to come back. In the August example, the option that lost was changing prices in Q4, and the Disagreements line records the head of marketing's reason for it. When a decision is reversed, keep the old line and add a new one that says what changed and who decided, so nobody finds a decision quietly edited away.
The commitments list
The commitments list tracks promises your principal and the leadership team made to each other, to the board and to customers. Nobody announces that a commitment slipped, so by the time it surfaces it's a credibility problem. Your principal will make some on calls you weren't on, so ask in every 1:1, "what did you promise anyone this week?"
Write each line so you could chase it. "CEO to follow up with the board" is too vague. As an illustration, "CEO to the board: send the Series B timeline by Oct 10. At risk. Next step: CFO drafts it by Oct 8" tells you who to message and when.
Template: Commitments list
Commitments list: [Principal name]
Reviewed: [Friday date] · Discussed in 1:1: [date]
| Date made | Who promised | To whom | What, by when | Status | Next step |
|---|---|---|---|---|---|
| [Date] | [Principal or leader] | [Person, team, board, customer] | [Specific deliverable, date] | On track / At risk / Missed / Done | [Action, owner] |
Rules
- Add anything with a date and a person waiting on it.
- "At risk" gets a message to the person waiting before the date, never after.
- Done items move to the bottom for a month, then into the archive.
# Commitments list: [Principal name]
Reviewed: [Friday date] · Discussed in 1:1: [date]
| Date made | Who promised | To whom | What, by when | Status | Next step |
| --- | --- | --- | --- | --- | --- |
| [Date] | [Principal or leader] | [Person, team, board, customer] | [Specific deliverable, date] | On track / At risk / Missed / Done | [Action, owner] |
Rules
- Add anything with a date and a person waiting on it.
- "At risk" gets a message to the person waiting before the date, never after.
- Done items move to the bottom for a month, then into the archive.
Some leaders find it uncomfortable to see how much they've promised. Bring the list as a tool for them, open with the items at risk, and suggest which ones to renegotiate; I'd expect your principal to start asking for it within a month, because it protects their credibility with the board.
Your weekly update goes out on Friday for the Monday 1:1, and it's the only note you send before it. Start it with the decisions you need from your principal, including any "not yet" line in the log, then the commitments at risk.
You will miss a Friday. Skip the backfill: update priorities and commitments, log only the decisions someone is already acting on, and mark the file with the date you last checked it.
To start both lists, go back over the last two weeks of decisions and promises, and show the commitments list to your principal in your next 1:1.
How do you turn a week of notes into updated records?
Write two or three lines after each meaningful conversation: what the person cares about right now and any open thread with them. Then, in your 20 minutes on Friday, let an approved AI tool sort the week's notes into updates for all four records. Your stakeholder notes are the fourth record, and they stay with you. Our stakeholder map guide covers who belongs on the map and how to review it.
Kartikeya Jaiswal, known as KJ, then Head of Strategy and Operations at Bifrost AI, used the same habit at a conference. Over three days he met 30 to 40 companies, mostly in hallways and over meals, and dictated a short voice note after each. That evening an AI assistant turned the transcripts and photos of business cards into updates on his prospect sheet.
Prompt: Turn this week's notes into context updates
You are helping me, a Chief of Staff to [principal, title], keep our records current.
Inputs below: this week's meeting notes and voice notes, plus my current context file.
Do four things:
1. Decisions: list every decision made this week as one line (date, decision, why, the options that lost, decided by, revisit when). Only include decisions the notes state clearly. Mark anything ambiguous as [CHECK].
2. Commitments: list every promise made (who, to whom, what, by when). Flag any that conflict with the priorities in the context file.
3. Context file: suggest specific edits (priorities, off the list, owners, open questions). Quote the line you'd change.
4. Stakeholders: for each person mentioned, give one line on what they care about right now and any open thread with them. Facts only, from the notes. No judgments about performance or intent.
Rules: use only facts from the inputs. Don't invent dates, numbers or names. Keep the whole answer under 500 words.
[Paste notes and context file]
Run it only in a tool your company has approved for this data, then read the output against your own memory. The summary is good at sorting and bad at knowing what someone meant.
What should stay out of your records and your AI tools?
Write down decisions, commitments, priorities and facts about who owns what. Keep candid reads on people, such as who's struggling, who's leaving or who doesn't trust whom, out of shared files and out of AI tools. If you wouldn't read a note aloud to the person it's about, it stays out.
My rule is stricter: if a note can't survive being forwarded, it stays in your head or a paper notebook, and you accept the risk that it leaves with you. Our stakeholder map guide covers meeting recordings, how long to keep notes, what a colleague in the UK or EU can ask to see, and who should see your map.
How do you hand over context when you're out or leaving?
Hand over context with four documents: the current context file, the decision log, the open commitments list and a one-page handover note covering what's in flight, what's sensitive and who to call. For a week off, that's enough; for a permanent move, add a walkthrough with your principal and a month of overlap if you can get it.

The median completed Chief of Staff stint is 20 months, and the middle half run 12 to 30 months. So most moves take a year or more of context out of the leadership team.
Zoe Jakubowich, then a fractional Chief of Staff to five clients at once, kept very detailed notes so she could put one company down and pick the next one up.
For a week of leave, the person covering needs to act, so the note leads with what will need attention and who decides it. As an illustration: "The board pre-read is due Thursday. The CFO owns the numbers and the CEO approves the narrative. If the CFO's draft is late, nudge on Tuesday and tell the CEO on Wednesday."
For a permanent move, your successor needs to understand, so add the history behind the three decisions most likely to be reopened and walk your principal through the file together. Your read on which leader is struggling or which relationship is fragile stays verbal: list it as a topic, and have that conversation with your successor before you leave.
Tell whoever covers which questions can wait, because the first one the file can't answer becomes a call to you. If your AI tools run on your context file and your logins, decide before you go whether they keep running; a scheduled job shouldn't keep reading data after you've left the role. A six-week-old file still reads as current, so read it end to end and date every section before you hand it over.
Prompt: Draft my handover note from my context file
I'm a Chief of Staff to [principal, title], handing over to [name, role] for [a week of leave / a permanent move] starting [date].
Using my context file, decision log and commitments list below, draft a one-page handover note with:
1. The three things most likely to need attention while I'm gone, with the owner and the first step for each.
2. Open commitments due in the period, with who is waiting.
3. Decisions in flight: what's been decided, what's pending, who decides.
4. Who to call for what (names and areas only).
5. Anything I should explain in person, listed as topics only. Don't write out sensitive details.
Rules: use only facts from the inputs. Mark anything older than 30 days as [CHECK DATE]. Under 400 words.
[Paste context file, decision log and commitments list]
If you're helping your principal find your successor, start with our guide to hiring a Chief of Staff. If you're the one taking over, ask for the context file, the decision log, the open commitments list and the handover note before your first day. Then ask your predecessor in person about the topics the note only lists.
If you inherit no file, build the records in your first week, in this order. Start the commitments list: ask your principal what they've promised anyone, and read back through the last two weeks of your principal's meeting notes and sent email for promises. Then fill in the priorities, off-the-list and information sections of the context file, and ask your principal to correct them. Last, ask which three decisions are most likely to be reopened, and log each one in full: why, the options that lost, who decided and when to revisit it. Our guide to your first 90 days covers the rest of your start.
This week, date every section of your context file and write a five-line handover note as if you were out tomorrow.
Work through context, AI tools and the hard parts of the role with Chiefs of Staff who are doing it now. Membership includes Power Skills, member events and a private community.
See membershipKeep reading
Leadership team meeting agenda: how to run the meeting, take notes and follow upToolkit
How to brief your principal: briefing memos, decision memos and pre-readsToolkit- Executive calendar management: how a Chief of Staff runs the calendar and inboxToolkit
Toolkit
- The Chief of Staff toolkit: tools and templates for the daily work
- How to brief your principal: briefing memos, decision memos and pre-reads
- Executive communications for Chiefs of Staff: writing for the CEO and running internal comms
- Leadership team meeting agenda: how to run the meeting, take notes and follow up
- Executive calendar management: how a Chief of Staff runs the calendar and inbox
- Context management for Chiefs of Staff
- Stakeholder management for Chiefs of Staff: how to map and track the people your principal depends on
- How Chiefs of Staff research decisions, with and without AI
- How a Chief of Staff runs board meetings and investor relations
Take this guide with you
The full guide as a PDF: every section, template and chart, ready to print or share with your team.
Your PDF is ready.
Download the PDFFree. We may email you new guides; unsubscribe anytime.
Frequently asked questions
What does context mean for a Chief of Staff?
Context is what a leader knows that the rest of the company doesn't: the current priorities, why past decisions went the way they did, what has been promised to whom, and how the key people like to work. A Chief of Staff hears more of it than almost anyone else on the team. The job is to write it down so others can use it without asking the Chief of Staff.
What is a context file for an executive?
A context file is a one-page document that holds what matters right now for a leader: priorities in order, what's off the list, who owns what, key decisions and how the leader wants information. A Chief of Staff keeps it current every week. It helps people covering for you and makes AI tools give answers that fit the company.
What is the difference between a decision log and meeting notes?
Meeting notes record what was said. A decision log records only what was decided, in one line each: the decision, why, the options that lost, who decided and when to revisit it. Notes get long and go unread. A log stays short enough that people check it before reopening a decision.
How do Chiefs of Staff keep track of so many stakeholders?
Most write two or three lines after each conversation that matters, then sort them weekly, often with an AI summary of their notes. These stakeholder notes are for you only, so keep candid reads on people out of shared tools. Our stakeholder map guide covers who belongs on the map and how to keep it current.
Is it safe to put company context into AI tools?
Only in tools your company has approved for that kind of data, and only lines you'd be comfortable reading aloud to the person they're about. Leave out performance, health, legal and HR matters, and anything said in confidence. Check what the tool stores and for how long before you connect it to email, calendars or notes. If a tool can act for you, keep scheduled jobs to reading and drafting, and make it ask before it sends, shares or deletes anything.
How often should a Chief of Staff update their context file?
Check it every Friday, in the 20 minutes before you write the weekly update to your principal, and rewrite it from a blank page at the start of each quarter. Priorities usually hold for the quarter, so the Friday check mostly catches new owners, open questions and anything your principal has changed. When you miss a week, mark the file with the date you last checked it.
- Chief of Staff Pathways Report 2026, Chief of Staff Network. 1,819 job postings; 2,158 completed moves for stint length.
- AI Readiness Diagnostic, Chief of Staff Network, 2026. 1,200+ senior leaders, drawn from Chiefs of Staff and senior operators.
- Chief of Staff Network podcast: Jamie White, Delong Lu, Dara Chen, Remi Guarini, Kartikeya Jaiswal, Zoe Jakubowich.
- The examples on this page are illustrations.
Learn the job with people who do it
Membership gets you the Power Skills program, member events and a private community of working Chiefs of Staff.
Land your first Chief of Staff role
Launchpad helps you prepare, position yourself and interview for the role.
Starting out in the role?
The Fundamentals email course walks you through scoping the mandate, setting the cadence and earning trust.
Lead AI adoption from the Chief of Staff seat
The Chief of AI Fellowship is for operators turning AI into how the company runs.
Hiring a Chief of Staff?
Post the role on the Chief of Staff job board, or browse open roles.
Get your resume ready for the role
Get feedback on your Chief of Staff resume before you apply.
Let the right roles find you
Join the talent network and hear about Chief of Staff roles first.
The Chief of Staff newsletter
What Chiefs of Staff are reading, hiring for and building.
Get the full report
Every chart and cut from our latest salary research, sent to your inbox.
Using AI with sensitive data?
Learn the legal side of using AI at work.
Keep going in this series

.avif)
.avif)



