HR & RECRUITING

Quarterly band-health drift report to leadership

Each quarter it aggregates band-drift across the whole company from BigQuery, computes how many employees and which departments are out of band and by how much.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerQuarterly schedule fires the report
  • ActionAggregate band position by department and levelGoogle BigQueryBigQuery
  • LogicRank teams by drift rate and dollar exposure
  • ActionRender the leadership-ready report
  • OutputEmail the report to HR leadershipGmailGmail

What it does

This workflow produces a quarterly view of how well compensation tracks its bands across the organization. It aggregates every active employee's band position from BigQuery, then rolls the data up by department and level: counts of below-floor and above-ceiling employees, total dollar exposure, and the departments drifting fastest versus the prior quarter. It assembles this into a ranked report and emails it to HR leadership so they can prioritize where to spend correction budget.

When to use it

Use this for board and leadership reviews when you need a trend-level read on comp-band integrity rather than individual flags, and want to see which teams are drifting before it becomes a retention or equity problem.

How it works

  1. 1A quarterly schedule triggers the report.
  2. 2Query BigQuery to aggregate band position by department and level.
  3. 3Rank departments by out-of-band rate and dollar exposure, comparing to last quarter.
  4. 4Render the ranked summary into a leadership-ready report.
  5. 5Email the report to the HR leadership distribution list via Gmail.

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
    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.