Start from the fixed obligations
An annual calendar should begin with the dates the organization cannot move: board meetings, the annual meeting, the fiscal close, the audit committee, the compensation cycle, and the major customer or investor events. Collect them from the owners, not from last year's calendar. A date that was correct last year may have moved because the fiscal calendar or the board chair changed.
Record the source and the owner for each fixed obligation. Distinguish a confirmed date from a probable date. A planning calendar that mixes the two will create false confidence and a scramble when the probable date becomes real. Mark the uncertain items and the date by which they must be confirmed.
Map the board, earnings, and travel cycles
Build the year in layers: the board cycle, the earnings and disclosure cycle, the budget and planning cycle, the travel pattern, and the recurring leadership meetings. Then look for the weeks where those layers collide. A board packet deadline that lands in the same week as an earnings release and a customer conference is not a normal week, even if each item looks manageable alone.
Include the preparation windows, not only the events. A board meeting needs a packet freeze, a review session, and a pre-read. An earnings release needs legal and IR review. A customer conference needs a briefing and travel. The calendar should show the work behind the date so the office can protect the time.
Protect preparation time, not just event time
Executives often have a calendar full of meetings and no time to prepare for them. Block preparation time before the board meeting, the earnings call, the keynote, and the performance review. Treat those blocks as commitments, not as optional white space that can be filled by a routine request.
Coordinate the blocks with the people who prepare the materials. If the CFO's team cannot deliver the numbers until the morning of the board meeting, a preparation block the night before is useless. Move the block or move the deadline. The annual plan should show the dependency, not just a color-coded hour.
Identify collision weeks and decision points
List the weeks with three or more high-consequence obligations and name the decision point for each: what must be ready, who signs off, and what can move. A collision week is not solved by working longer; it is solved by moving a lower-priority event, reducing the executive's attendance, or adding a delegate.
Share the collision map with the chief of staff and the relevant function leads early enough to change the plan. Do not wait until the month begins. A short list of weeks with a proposed mitigation is more useful than a perfect calendar that nobody can follow.
Publish a planning calendar with owners
The published calendar should show the obligation, the date, the preparation window, the owner, the required input, and the status. Keep it at the right altitude: a leadership team needs the milestones, not every prep call. Link to the detailed work plan for the people who need it.
Version the calendar and note what changed. If a board meeting moves, update the dependent preparation windows and notify the owners. A calendar that is published once and never maintained becomes a historical artifact within a month.
Review quarterly and adjust
At the end of each quarter, compare the plan with what actually happened: which preparation blocks were consumed by meetings, which deadlines slipped, which travel weeks were unsustainable, and which events could have been delegated. Ask the executive and the chief of staff what to protect in the next quarter.
Adjust the plan with the evidence. If the same week collides every year, change the pattern rather than heroically surviving it again. The annual calendar is a tool for making choices about executive attention, not a prediction that every commitment will be met.