Start with the decisions the role owns
A new chief of staff needs a clear map of the decisions the role can make, the ones it prepares, and the ones it only tracks. Write the map before the first week and review it with the executive. Use concrete examples such as approving a meeting agenda or resolving a scheduling conflict. A role described only as strategic will leave the new person guessing about daily authority.
Include the decisions that stay with the executive even when the chief of staff runs the process. A search, a board appointment, or a sensitive personnel matter may need the executive's explicit sign-off. Naming the boundary protects both people from an early misunderstanding. It also gives the executive a reason to delegate the work that is genuinely safe to hand over.
Ask the previous office holder or the executive assistant which decisions caused friction in the past. Their examples are more useful than an abstract role description. Add the top three to the onboarding pack with a short note on how each was handled. A new leader can learn from a real precedent without inheriting every old habit.
Explain the operating rhythm in plain language
Describe the weekly and monthly rhythm in the order it actually happens. Start with the Monday priorities meeting, then the midweek decision review, then the Friday follow-up note. For each event, name the owner, the input, and the output. A new chief of staff should be able to see where their work enters the cycle.
Explain the exceptions as clearly as the routine. What happens when a board meeting moves, a quarter closes early, or the executive travels for a week? A rhythm that only works in a normal week will fail in the first unusual one. Add a short exception note for each recurring event.
Use the pack to show one real example of a weekly note or agenda, not a blank template. An annotated example teaches judgment faster than a list of instructions. Mark the parts that are essential and the parts that can change. The new person can then adapt the format without losing the purpose.
List the people and the boundaries
Give the new chief of staff a map of the people they will work with, including the executive assistants, finance, legal, communications, and the board secretary. For each relationship, note what the role can ask for and what requires the executive. A contact list without boundaries invites either overreach or unnecessary escalation. A written map also helps the executive see where the role is expected to grow.
Include the external relationships that matter, such as auditors, counsel, investors, and key customers. Note who owns each relationship and whether the chief of staff should join a call or stay behind the scenes. A new person can damage a delicate relationship by appearing in the wrong conversation. The map should make the invisible boundaries visible.
Identify the two or three people who can answer questions when the executive is unavailable. Name their scope and the best way to reach them. A new chief of staff should not have to discover the informal network during a crisis. The pack should shorten that search without pretending the network is formal.
Include the unfinished work
List the projects, decisions, and commitments that are still open on the first day. For each one, give the current state, the next action, and the person who owns it. A new chief of staff who walks into a clean description of the role but no view of the unfinished work will spend the first month rediscovering the backlog. That review should happen before the first monthly leadership meeting so the list is current.
Mark the items that are sensitive, stalled, or waiting on the executive. Add a short note on why each one is stuck. The new person needs to know which items can be pushed and which need a quiet conversation. A list of projects without that context is only a longer to-do list.
Review the unfinished work at the end of the first week and update the owners. Some items may be closed, some may move, and some may no longer matter. The review gives the new chief of staff a reason to meet the owners early. It also shows the executive which commitments survived the transition.
Review the pack after thirty days
Ask the new chief of staff which parts of the pack were useful and which were wrong. A document built before the role starts will contain assumptions that only the first month can test. Record the corrections and update the pack for the next transition. The review is a small investment that prevents the same gaps from repeating.
Look for the questions the new person asked most often in the first month. If the same question appears three times, the pack is missing a section or the answer is hard to find. Add the answer where the question arose rather than in a separate FAQ. The pack should improve from observed use, not from a planning meeting.
Share the revised pack with the executive and the people who contributed to it. A short note on what changed and why closes the loop. Keep the pack with the operating record so it is available for the next transition. The best onboarding pack is a living document that reflects how the office actually works.
Related resources
Read also: chief of staff weekly agenda and coverage plan for planned absences.
Frequently asked questions
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation