Why the first week sets the pattern
A new chief of staff arrives with authority that is still being defined. The first week shows whether the role will operate through clear agreements or through improvisation. A pack of operating information reduces the number of questions that have to be asked twice. It also gives the executive a shared reference for what the role is meant to do.
The pack is not a policy manual. It should be short enough to read in the first two days and specific enough to use in the first two weeks. The goal is to explain how the office actually works, not how the organisation says it works. Honest notes about current problems are more useful than polished descriptions.
Clarify the role and decision rights
Write down the decisions the chief of staff can make alone, the decisions that require consultation, and the decisions reserved for the executive. Use examples from recent weeks so the boundaries are concrete. Include the escalation path for urgent matters and the person to contact when the executive is unavailable. Ambiguity here creates friction in every later task.
Record how the role relates to the executive assistant, the finance lead, and the leadership team. Explain who owns the calendar, who owns the meeting agenda, and who speaks for the executive in each forum. A simple responsibility map prevents duplicated work and silent gaps. Review the map with the executive before the first week ends.
Include the budget and approval limits that come with the role. A chief of staff who cannot authorize a small purchase or approve a travel change will escalate work that should be routine. State the limits in the same place as the decision rights. Review them with finance before the first week.
Hand over the calendar and meeting system
Explain the recurring commitments, the preparation cycle, and the standing meetings that the chief of staff will influence. Identify the meetings that are fragile, the ones that consume disproportionate preparation, and the ones that already have a clear owner. Give the new person the current calendar audit if one exists. The context is more useful than a list of dates.
Show how agendas are built, where papers are stored, and how decisions are recorded. Walk through one upcoming meeting from preparation to follow-up. Explain the support desk's role and the point at which the chief of staff should step in. A live walkthrough teaches more than a written process alone.
Map the key relationships
List the people the chief of staff must meet in the first two weeks and why each relationship matters. Include the executive, the leadership team, the board secretary, finance, legal, and any external adviser with a standing role. Add a one-line note about the current state of each relationship. The list should help the new person prioritise limited time.
Explain the communication norms for each group, such as which channel to use and what response time is expected. Note any sensitive history that could affect a first conversation. Do not include personal opinions that are not relevant to the work. The aim is context, not gossip.
Surface the open issues honestly
Give the new chief of staff a short list of open issues, decisions, and risks that need attention in the first month. State what has been tried and what remains unresolved. Avoid presenting a clean version that hides the difficult parts. A new leader cannot help if the handover is written for appearance.
Separate urgent issues from structural ones so the new person knows where to start. Name the owner of each issue and the next decision point. Include the questions that the executive wants answered first. The list should be reviewed together rather than left as a document to discover.
Set a thirty-day check-in
Agree on what the first thirty days should produce and how the executive will judge progress. Choose two or three outcomes rather than a long list of activities. Put the check-in in the calendar before the first week ends. A clear near-term goal helps the new person prioritise the many requests that will arrive.
Ask the new chief of staff what information was missing from the pack. Update the pack for the next hire or handover. The first month is also a test of the onboarding process itself. A short feedback note is enough to improve the next version.
Ask the new chief of staff to identify one process that feels unclear after thirty days. The answer is often more useful than a satisfaction survey. Use it to improve the pack and the handover for the next person. The review should leave a concrete change, not just a meeting note.
Keep the pack current
Store the pack where the executive and the chief of staff can both edit it. Assign an owner to review it each quarter or after a major change. Remove outdated names, dates, and decisions rather than layering new notes on top. A current pack is a working tool, not a historical record.
For related guidance, see our article on handover notes for executive coverage and our consultation page. A thoughtful first-week pack shortens the learning curve and gives the new chief of staff a credible starting point. A pack that is reviewed after each handover becomes easier to maintain. Keep the owner and the review date visible on the first page.
Key takeaways
- Define the chief of staff's decision rights with recent examples.
- Map responsibilities across the executive, assistant, finance, and leadership team.
- Walk through one live meeting cycle rather than only describing it.
- List key relationships and the context needed for the first conversations.
- Agree on two or three thirty-day outcomes and a scheduled check-in.