HR & RECRUITING

Weekly Compensation Band Drift Audit

On a weekly schedule, this scans the entire workforce against current comp bands, surfaces everyone who has drifted below band minimum or above maximum.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires the audit
  • ActionPull all active employees + base pay from HRIS PostgresPostgreSQLPostgres
  • ActionJoin each employee to their band from AirtableAirtableAirtable
  • LogicCompute band position, isolate + rank out-of-band cases
  • ActionWrite dated audit report to Google Sheet in DriveGoogle DriveGoogle Drive
  • OutputPost top exposures + remediation budget to SlackSlack

What it does

Runs a standing audit of the whole employee population against the live band table. Bands move as the market shifts; this catches the employees who have quietly fallen out of band — usually below minimum after a band raise — and quantifies the cost to fix each one.

When to use it

Use this for ongoing comp hygiene rather than per-offer checks. It's ideal ahead of merit cycles or budget planning, when you need a defensible list of who is out of band and what it would cost to correct.

How it works

  1. 1A weekly schedule triggers the audit.
  2. 2The flow pulls all active employees and their current base pay from the HRIS Postgres database.
  3. 3It joins each employee to their applicable band by level and location from Airtable.
  4. 4A logic step computes band position for everyone and isolates below-min and above-max cases, ranking by gap size and remediation cost.
  5. 5The findings are written to a dated Google Sheet in Drive for the record.
  6. 6A summary with the top exposures and total remediation budget is posted to the People team channel in Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect Google DriveDocs, sheets, slides, files.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.