HR & RECRUITING

Audit a merit-cycle raise batch against bands and log exceptions to Notion

When a merit-cycle raise file is uploaded, this workflow checks every proposed new salary against its level-and-geo band in BigQuery and writes each out-of-band raise to a Notion…

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMerit-cycle raise file uploadedGoogle DriveGoogle Drive
  • ActionLook up band per row from BigQueryGoogle BigQueryBigQuery
  • LogicTag raises that fall outside band
  • ActionWrite each exception to Notion trackerNotionNotion
  • OutputPost run summary to NotionNotionNotion

What it does

Merit cycles move hundreds of salaries at once, and bands are easy to blow past in bulk. This workflow takes an uploaded raise batch, looks up the approved band for each employee's level and geo in BigQuery, and evaluates every proposed new salary in one run. Raises that stay inside band pass silently; raises that push above the ceiling or sit below the floor become rows in a Notion exception tracker, each with the employee, manager, level, geo, current and proposed salary, the band range, and the dollar and percent variance. The result is a living review queue the comp team works through before the cycle is finalized, instead of discovering breaches after letters go out.

When to use it

Use it during planning or annual merit cycles when managers propose raises in a spreadsheet and comp needs a band check across the whole batch. It fits teams that run structured cycles and want every exception captured in one Notion board for review and sign-off.

How it works

  1. 1A trigger fires when the merit-cycle raise file lands in the watched cloud folder.
  2. 2The workflow reads the batch and, for each row, queries BigQuery for the approved band by level and geo.
  3. 3A logic step computes each proposed salary's position relative to its band and tags the out-of-band ones.
  4. 4Each exception is written as a row to the Notion comp-review tracker with variance and reason.
  5. 5A summary count of rows reviewed and exceptions logged closes the run in Notion.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  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.