PERSONAL PRODUCTIVITY

Weekly Meeting-Load Audit with Focus-Block Reclaim Plan

Every Friday, scans each team member's Google Calendar for the coming week, flags anyone whose meeting hours exceed a threshold.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFriday 3pm weekly schedule
  • ActionFetch next-week events per personGoogle CalendarGoogle Calendar
  • LogicSum hours, keep people over threshold
  • ActionRank meetings and draft reclaim planOpenAI
  • OutputPost per-person digest to SlackSlack

What it does

Runs a forward-looking audit of next week's calendars and turns raw meeting hours into an actionable triage list. For each person over the limit, it identifies the lowest-value recurring meetings and proposes concrete focus blocks to reclaim, then drops a tidy summary in a Slack channel so managers act before the week starts.

When to use it

Use it when your team is drowning in standing meetings and you want a proactive nudge instead of a retroactive complaint. Best for engineering, design, or product pods where deep-work time keeps getting eaten by recurring syncs.

How it works

  1. 1A Friday-afternoon schedule fires the workflow.
  2. 2It pulls each tracked person's events for the next 7 days from Google Calendar.
  3. 3A logic step sums meeting hours per person and keeps only those above the configured ceiling (e.g. 15 hrs/week).
  4. 4OpenAI ranks each overbooked person's meetings by reclaim value and drafts a 2-3 block focus plan.
  5. 5A formatted digest is posted to a Slack channel, one section per person, with declinable meetings called out.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.