Setting Up a New Executive's First Ninety Days of Calendar and Files

Start with the first week, not the whole quarter

Build the first week around the people the executive must meet and the decisions that cannot wait. A ninety-day plan that begins with a full calendar leaves no room for listening. Put the introductions and the context sessions first. The executive can add commitments after the first week. Leave one open block each day for the conversations that emerge.

Block time for the executive to read the strategy, the budget, and the current board materials. A new executive needs preparation time that the outgoing calendar did not include. Mark the blocks as real appointments. The assistant should protect them during the first month.

Ask the executive what kind of schedule helps them think. Some executives want a clear morning; others prefer meetings grouped by topic. Build the first two weeks around that preference and review it after the first month. A calendar that ignores the person will be rebuilt anyway.

Ask the outgoing assistant for the three things a new executive always asks in the first week. The answer is often more useful than a full document inventory. Record the list and check it against the plan. The first week should not repeat a known gap.

Create a document map the executive can use

Map the files by decision, not by department. The executive should find the budget, the board packet, the strategy, and the current project list without a tour of the shared drive. Use a short index with links. The map should fit on one page.

Name the owner of each document and the date it was last updated. A file with no owner may be stale or unofficial. The executive should know who can answer a question. The map is a directory, not an archive.

Put the access rules and the confidential files in a separate section. A new executive may have access to more information than the previous assistant expected. Check the permissions before the start date. The document map should not create a disclosure risk.

Map the recurring reports and the ad hoc files separately. A new executive needs to know which documents arrive on a schedule and which are produced for a decision. Record the owner and the cadence. The map should show the rhythm, not only the folder.

Set the recurring rhythm

Define the weekly leadership meeting, the monthly review, and the quarterly board cycle in one calendar. A new executive needs to see the rhythm before the individual invitations arrive. Put the standing events on the calendar with the owners and the preparation expectations. Record the first-week task that depended on the item.

Agree on the assistant's decision rights for the first ninety days. The new executive may want more or fewer approvals than the predecessor. Write the rule down and review it after thirty days. The assistant should not guess the boundary from the first few requests.

Schedule a short weekly review with the executive for the first month. Use it to check the calendar, the documents, and the open questions. The review should be short and practical. It is easier to correct the setup early than after the quarter.

Put the preparation deadlines on the calendar, not only the meetings. A board meeting with no packet deadline will consume the assistant's week. Record the deadline and the owner. The rhythm should include the work before the meeting.

Introduce the support network

List the people who keep the executive's work moving: the chief of staff, the finance lead, the board secretary, the IT contact, and the travel provider. Include the role and the best channel. A new executive should not have to discover the network through a crisis. Record the first-week task that depended on the item.

Explain the escalation path for an urgent request and the person who covers when the assistant is away. A new executive may not know who can approve a change. The path should be written and tested during the first month. Keep the executive's note with the document map.

Ask the executive to confirm the list after the first week. A name that is wrong or a role that has changed should be corrected immediately. The network is only useful if it is current. Report the item even when the executive found it without help.

Ask each contact to confirm the best channel and the expected response time. A name without a working channel is not a contact. Record the answer in the map. The network should be usable on the first urgent request.

Review the setup at thirty, sixty, and ninety days

At thirty days, check whether the calendar matches the executive's actual priorities. Remove the meetings that were placeholders and add the ones that emerged. The review should be based on the executive's experience, not on the original plan. Record the first-week task that depended on the item.

At sixty days, review the document map and the access rules. A new executive may need different files or a different level of confidentiality. Update the map and the permissions. The assistant should not wait for a problem to prompt the review.

At ninety days, write a short note on what worked and what should change for the next executive. Keep the note with the onboarding materials. The next transition should start from a better baseline, not from a blank calendar. The note should sit beside the next transition plan.

Keep the review notes in one place so the next transition can use them. A note that is scattered across email is not a handoff. Record the date and the change. The next executive should start from a better baseline.

Related resources

• Designing an Executive Office Coverage Plan for Planned Absences
• Auditing Decision Memo Completeness After Delegated Approvals
• Writing a Decision Memo That Survives an Executive's Absence

Frequently asked questions