HR & RECRUITING
Detect comp bands going stale against market and alert before drift starts
On a weekly schedule this workflow compares each approved band's midpoint against recent in-region offer and market data in BigQuery, flags bands whose midpoint has fallen behind.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionRead bands + recent offers + market dataBigQuery
- LogicScore midpoint lag and flag stale bands
- LogicRank by lag size and headcount impact
- OutputEmail refresh priority list via OutlookOutlook
What it does
Most drift starts upstream: the band itself goes stale and every in-band offer quietly underpays the market. This workflow attacks the cause instead of the symptom. Weekly it reads your approved bands from BigQuery alongside recent actual offers and any imported market benchmark data, and for each level-and-geo band it computes whether the midpoint still tracks reality or has slipped behind. Bands where recent accepted offers consistently cluster near or above the ceiling, or where market benchmarks have moved past the midpoint, are flagged as stale. The output is a prioritized refresh list emailed to comp leadership through Outlook, ranked by how far behind each band has fallen and how many roles it covers.
When to use it
Use it when bands are reviewed only once a year and offers keep creeping toward the ceiling between reviews. It fits comp teams that want an early-warning signal telling them which specific bands to re-benchmark before drift forces a wave of exceptions.
How it works
- 1A weekly schedule trigger fires.
- 2The workflow queries BigQuery for each band plus recent accepted offers and market benchmarks for that level and geo.
- 3A logic step scores each band's midpoint against actuals and the market and flags the stale ones.
- 4It ranks flagged bands by lag size and headcount impact.
- 5The prioritized refresh list is emailed to comp leadership via Outlook.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect OutlookMail, calendar, contacts.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More HR & Recruiting workflows
Assemble and send the debrief packet after the final interview
Triggered when a candidate's final interview ends on the calendar, it waits a short window for scorecards, compiles the aggregated packet to Google Drive.
New-Hire Credential Intake to Renewal Calendar Holds
When a new credential is added to the tracker, it validates the record, files the document.
Credential Renewal Evidence Verification Agent
When an employee replies with a renewed credential document, an agent reads the attachment, extracts the new expiry date and credential number.
Escalate Compliance-Blocking Credential Lapses to Managers
Each day it finds credentials that have already expired or expire within 48 hours and are flagged compliance-blocking.
Day-one readiness orchestrator across all onboarding owners
An agent-driven coordinator that, when a hire is launched, plans the full provisioning program across IT, Facilities, and Finance, opens the work in your tracker.
Loom intake to req-tracker row in Airtable
Transcribes a hiring manager's Loom intake, scores the brief for completeness, and either logs a ready req in Airtable or routes incomplete intakes to a follow-up Slack ping.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.