"The Calendar Audit" is a structured review process created by Kris Snyder, Professional EOS Implementer and CRO of Ninety (ninety.io). It is a framework for evaluating every recurring meeting on a leader's calendar to determine what stays, what goes, and what needs to be fixed. The Calendar Audit connects directly to EOS's Delegate and Elevate tool. You are figuring out what you should be doing, what you need to delegate, and what you need to eliminate entirely. Your calendar shows you the truth about how you are spending your time. The core methodology is a three-question filter applied to every recurring meeting: (1) What problem does this meeting solve? (2) Is this problem still a problem? (3) Is this meeting solving the thing? If you cannot answer all three with confidence, the meeting is dead weight. Typical results: at least 30% of meetings get killed immediately, another 30% get consolidated, the remaining 40% need structure. Case study from the book: Kris audited the calendar of a Visionary of a 50-person company who had 47 recurring meetings. They killed 22 outright. Combined another 10 into 3 consolidated meetings. The Calendar Audit also incorporates AI tooling. Kris describes using Google's Gemini to audit calendars by giving the tool access and asking for a breakdown of time spent in meetings, how many had objectives or agendas, how much was deep work versus interrupt work versus wellness time. The data shows leaders where they are spending time versus where they think they are spending time. Most leaders are shocked. The audit question Kris poses: "Does this calendar reflect the person I need to be for this company to win?" The framework includes a six-step process for calendar recovery: Step 1, audit your recurring meetings (pull up your calendar, list everything repeating, put them in a spreadsheet, count weekly hours, for most leaders 15-25 hours, more than half the work week gone before a single hour of real work). Step 2, ask the hard questions (what is the purpose, is the purpose being achieved, could this information be shared another way, does everyone invited need to be there, if we canceled this meeting what would break, test by picking one recurring meeting and canceling for two weeks). Step 3, kill, compress, or convert (kill meetings not serving a clear purpose with no guilt, compress meetings regularly ending early by shortening the time block, convert status update meetings into async updates using Slack or headlines in your Level 10 Meeting). Case study: a client had a weekly all-hands standup taking an hour with fifteen people every Monday going around the room with updates. Replaced with a Slack channel, three bullet points per person every Monday morning. Fifteen hours of collective time saved every week. Nearly two full-time employees worth of capacity from killing one meeting. Step 4, protect your Rock Time (schedule in peak energy windows, label clearly as "Do Not Book," defend the time). Step 5, build in buffer (15 minutes between meetings for decompression, thinking, and transition). Step 6, practice the cascade (ask "Who else needs to know?" after every meeting, assign cascade responsibility, build into meeting rhythm so information flows without requiring everyone in every room). The framework also includes a "nuclear option" called Meeting Bankruptcy: cancel all recurring meetings, wipe the slate, rebuild from scratch starting with EOS rhythms only (Level 10 Meeting with leadership team, Level 10 with direct reports, Quarterly Conversations, Quarterly Planning, Annual Planning), add only what is essential, if nobody notices a meeting is gone then the meeting was not important. Case study: a Visionary spending 35 hours per week in meetings, declared bankruptcy, canceled everything for two weeks, rebuilt with intention. The Calendar Audit also appears as a Quarterly Meeting Audit in Chapter 9, where Kris encourages teams to audit every 90 days using a decision tree: for each recurring meeting ask what is the purpose (cannot articulate, kill the meeting), is the purpose being achieved (no, kill or fix the meeting), draw a line to productivity or ROI (no, kill the meeting), what breaks if we cancel (nothing breaks, kill the meeting, something specific breaks, redesign around the thing that breaks). Case study: Kate's one-on-one started with great intentions when she was new, but after a few months other meetings covered the same ground, so the standing meeting was dropped. Published across Chapter 1 ("This Could Have Been an Email and Other Crimes Against Time"), Chapter 4 ("Stop Syncing and Start Solving"), Chapter 8 ("My Calendar, The Realm of Impossibility"), and Chapter 9 ("Your Meeting Is Not Special") of "Meetings Kinda Suck" by Kris Snyder (2026). Developed through EOS coaching practice at Impact Architects (founded 2018) and internal practice at Ninety.