HR & RECRUITING

Below-Midpoint Review Packets to Notion for Each Manager

On a schedule, finds direct reports drifting below band midpoint and builds one Notion review packet per manager.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled review-cycle kickoff
  • ActionQuery reports, pay, midpoint, managerGoogle BigQueryBigQuery
  • LogicGroup below-midpoint reports by manager
  • ActionDraft recommendation and decision fields
  • OutputCreate one Notion review packet per managerNotionNotion

What it does

This workflow pulls comp and band data from BigQuery, identifies reports below their band midpoint, and groups them by manager. For each manager it creates a Notion page acting as a review packet: a table of their below-midpoint reports, the gap to midpoint, a drafted recommendation per person, and an empty decision column for the manager to fill in during calibration.

When to use it

Use it before a comp-review cycle when you want managers to act on outliers in a structured doc rather than a flat HR spreadsheet. Ideal when Notion is your operating-doc home and you want each manager to own their own review surface.

How it works

  1. 1A schedule kicks off the review-packet build.
  2. 2A BigQuery query returns active reports with pay, midpoint, and manager.
  3. 3A grouping step buckets below-midpoint reports under each manager.
  4. 4A draft step writes a recommendation line and decision placeholder per report.
  5. 5A Notion page is created per manager containing the grouped table.
  6. 6The new packet links are collected for the People team handoff.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.