HR & RECRUITING

Merit-cycle raise sweep with manager justification emails

At the close of a merit cycle, it audits every proposed raise against the post-raise band and emails managers a justification request for each raise that pushes an employee out…

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMerit-cycle close schedule fires
  • ActionQuery proposed raises joined to current bandsGoogle BigQueryBigQuery
  • LogicKeep raises that land out of band
  • ActionEmail managers a justification requestGmailGmail
  • OutputLog pending requests to a Notion trackerNotionNotion

What it does

When a merit cycle's proposed raises are finalized, this workflow recomputes each employee's new salary and checks it against their band. Raises that leave someone above the ceiling or, despite the increase, still below the floor are flagged. For each flagged raise it emails the proposing manager a structured request asking for written justification, and logs the outstanding requests to a Notion tracker so HR can see what is still pending.

When to use it

Use this once per review cycle to catch band breaches introduced by the raises themselves, and to gather manager rationale in one pass instead of chasing people individually.

How it works

  1. 1A schedule aligned to the merit-cycle close triggers the sweep.
  2. 2Query BigQuery for proposed raises joined to current bands; compute post-raise position.
  3. 3Filter to raises that land out of band.
  4. 4Email each affected manager a justification request via Gmail.
  5. 5Log every pending request and its status to a Notion tracker.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect GmailRead, draft, send, label.
  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.