Building a Board Committee Calendar That Prevents Packet Collisions

List every committee and its decision rights

Start with a complete list of board and leadership committees, including the ones that meet only twice a year. For each committee, record the decisions it owns, the materials it must review, and the person who prepares the packet. A calendar built without the decision rights will schedule meetings but miss the work that makes them useful. The list should be short enough to review at a glance.

Separate standing committees from temporary ones and note the end date for each temporary body. A committee created for a transaction or a search can consume the same packet weeks as a permanent committee, but its deadline may be less predictable. Mark the period when its work is most intense. That note helps the office see collisions that a recurring calendar hides.

Confirm the list with the board secretary and the committee chairs before building the schedule. A committee may have a charter that names required materials or a minimum review period. Capture those rules beside the meeting dates. A calendar that ignores the charter creates a packet that looks complete but cannot be approved in the time available.

Work backward from packet deadlines

For each meeting, start with the date the packet must be final and count backward through review, legal check, chair approval, and drafting. Put each milestone on the calendar with an owner. The meeting date is the least useful date for planning because it arrives after every other deadline. A backward schedule shows where the real pressure sits.

Include the time needed for external contributors, such as auditors, counsel, or a compensation consultant. Their drafts often arrive later than internal material and require a separate review. Add a buffer before the chair review rather than after it. A buffer at the end hides the delay, while a buffer before the review gives the chair a usable document.

Record the actual completion date for each milestone in the current cycle. Compare it with the planned date and note the recurring gaps. A packet that is always late at the legal review needs a different fix than one that is late at drafting. The pattern is more useful than a single postmortem after a difficult meeting.

Find the weeks where packets collide

Plot all committee packets on one timeline and mark the weeks when two or more require the same reviewer. Collisions are not only about the board meeting date, because the review work often lands in the same short window. Highlight the people who appear in more than one packet. A calendar that shows only meeting dates will miss the week when the general counsel is expected to review three documents.

Look for collisions with other executive obligations, such as earnings, audits, or a major customer event. A board packet that arrives during a product launch may be technically on time but practically unread. Add those obligations to the same timeline. The goal is to see the real capacity of the people who must review and approve the material.

Rank the collisions by the consequence of a delay, not by the size of the packet. A short compensation paper may be more time-sensitive than a long strategy update. Use that ranking to decide which packet gets the first review slot. A simple priority note beside each week is enough to guide the scheduling conversation.

Reserve review capacity before the collision

Block time for the reviewers before the packet is drafted, not after it is late. A standing review window on the calendar is easier to protect than an ad hoc request. Give the reviewer the scope of the material and the decision required. That preparation reduces the chance that the slot is used to ask basic questions instead of reviewing the document.

Stagger the drafting schedule when two packets would otherwise land together. Start the earlier packet one week sooner or move a lower-priority item to the next cycle. Tell the committee chairs what changed and why. A deliberate stagger is easier to defend than a last-minute request to review two documents in one afternoon.

Keep one reserve week each quarter for packets that cannot be moved. Use it for a regulatory filing, a transaction, or an unexpected committee request. Do not fill the reserve with routine work. A visible reserve gives the office room to absorb a collision without asking the same small group of reviewers to absorb it every time.

Publish one calendar everyone can trust

Publish a single calendar that shows the meeting, the packet deadline, the review window, and the owner. Keep it in the place where the executive team already looks for board work. A second calendar in a personal tool will drift within a month. The published version should be the one used in planning conversations.

Review the calendar at the start of each quarter and update it after every meeting. Record the dates that moved and the reason, so the next cycle can avoid the same conflict. Share the changes with the committee chairs and the preparers. A calendar earns trust when it reflects reality rather than an ideal schedule.

Use the calendar to start one conversation about capacity, not to add another reporting requirement. Ask which week looks impossible and which packet could move. The answer may be a different deadline, a smaller packet, or an additional reviewer. A calendar is useful when it changes a decision, not when it is merely complete.

Related resources

• A Board Paper Redaction Checklist That Holds Up Under Review
• Handling a Last-Minute Board Observer Request
• What last-minute board observer records can and cannot show

Frequently asked questions