PERSONAL PRODUCTIVITY

Monthly Meeting-Load Scorecard to Notion

On the first of each month, aggregates the prior month's meeting hours per person and per recurring series, computes load and fragmentation scores.

CategoryPersonal Productivity
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule on the 1st
  • ActionFetch prior-month eventsGoogle CalendarGoogle Calendar
  • LogicAggregate hours and fragmentation score
  • ActionWrite narrative on top load driversOpenAI
  • OutputUpsert scorecard rows to NotionNotionNotion

What it does

Builds a durable monthly record of how the team actually spent its time in meetings. It rolls up total hours, recurring-series cost, and a fragmentation score (how chopped-up each person's days were) into a Notion database so you can watch trends and justify killing low-value standing meetings.

When to use it

Use it when leadership wants data, not anecdotes, about meeting overhead. Ideal for monthly ops reviews where you decide which recurring meetings to cut or shorten.

How it works

  1. 1A monthly schedule fires on the 1st for the prior calendar month.
  2. 2It pulls every tracked person's events for that month from Google Calendar.
  3. 3A logic step aggregates hours per person and per recurring series and computes a fragmentation score.
  4. 4OpenAI writes a short narrative on the biggest load drivers and what to cut.
  5. 5The workflow upserts one row per person into a Notion database, preserving month-over-month history.

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 NotionPages, databases, comments.
  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.