Audit recurring meetings to reclaim team focus time

Evaluate your team's recurring calendar load and turn wasteful status meetings into async updates, shorter syncs, or cancellations.

Prompt

Prompt
Act as an executive operations advisor. Review the list of recurring team meetings pasted below and deliver a rigorous calendar audit to reduce meeting load and return deep-work time to the team.

- Evaluate every meeting against a strict test: clear decision-making need versus passive status reporting.
- Assign each meeting an explicit recommendation: Cancel, Make Async, Shorten/Reduce Cadence, or Keep.
- Provide a specific justification and replacement mechanism for every item not kept as-is.
- Total the estimated hours saved weekly for the entire group.

Output format:
### Meeting Triage Table (Columns: Meeting Name | Current Schedule | Recommendation | Action & Replacement)
### Implementation Steps (Phased rollout to avoid operational gaps)
### Total Estimated Time Reclaimed (Weekly summary)

My meeting list is below:

Example output

Example for: an engineering team's current weekly recurring calendar

Meeting Triage Table
Meeting NameCurrent ScheduleRecommendationAction & Replacement
Daily StandupMon-Fri, 30 mins (2.5 hrs/wk)Make AsyncReplace with a daily 9:00 AM Slack post covering wins, plans, and blockers. Hold a 15-minute live sync on Mondays only.
Bi-weekly Sprint PlanningEvery 2 weeks, 90 mins (0.75 hrs/wk)KeepEssential for cross-functional alignment. Require backlog pre-reads 24 hours prior to prevent overruns.
Weekly Department StatusWeekly, 60 mins (1 hr/wk)CancelPure passive reporting. Replace with a shared Friday bulletin document updated by project leads.
Design & Dev Office HoursWeekly, 60 mins (1 hr/wk)Shorten/Reduce CadenceCut to 30 minutes, twice monthly. Keep an open sign-up doc; if empty 2 hours before, automatically cancel.
Project Omega Check-inTwice weekly, 30 mins (1 hr/wk)Make AsyncMigrate updates to Jira ticket comments and escalate blockers via direct tagging instead of scheduled calls.
Implementation Steps
  1. Announce changes one week ahead in the primary team channel, framing the shift around uninterrupted maker time.
  2. Set up automated Slack prompts for async standups and share a shared template for the Friday bulletin.
  3. Run the new cadence for two full sprint cycles, then collect brief feedback on communication gaps.
Total Estimated Time Reclaimed
  • Individual hours saved: 5 hours per person per week (standup 2.25, status 1, office hours 0.75, Omega check-in 1).
  • Team total (for a 6-person team): approximately 30 engineering hours returned each week to focused build time.
Written by AI from this prompt. Your results will vary.

Paste your team's recurring meetings directly beneath the prompt in ChatGPT, Claude, or Gemini. As a follow-up, ask the model to draft an announcement email explaining the schedule adjustments to the wider team.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management