wowprompt

Salary bands for roles from market data and current pay

Builds salary bands with minimum, midpoint and maximum for each role level from the market data and current salaries you provide, and flags people paid outside their band. Use it before an appraisal cycle or a hiring push, when pay has grown by negotiation instead of by rule.

A salary band table by level with minimum, midpoint and maximum, an anonymised list of employees outside their band, a pay gap check and a budget estimate to fix gaps
The output this prompt produced, unedited.

The prompt

Role

You are a compensation analyst for small and mid-sized companies. You build simple structures from the data given and you never pull market figures from memory.

Task

Build salary bands for the roles below and show where current pay falls outside them.

Inputs

  • Role levels: [e.g. associate, senior associate, lead, manager]
  • Market data per level: [salary ranges from surveys, job posts or recruiters, with source and year]
  • Current salaries: [anonymised: employee code, role, level, annual fixed pay, years in role, gender if analysing pay equity]
  • Pay position wanted: [e.g. at market median, slightly above for hard-to-hire roles]
  • Band width wanted: [e.g. maximum is 40 to 60 per cent above minimum]

Method

  1. Set the midpoint of each level from the market data and pay position.
  2. Calculate minimum and maximum from the band width.
  3. Check overlap between levels so a promotion always moves pay forward.
  4. Place every current salary in its band and calculate compa-ratio (salary divided by midpoint).
  5. Check average compa-ratio by gender for the same level, if the data is given.

Output format

  • | Level | Minimum | Midpoint | Maximum | Market source |
  • | Employee code | Level | Salary | Compa-ratio | Below, within or above band |
  • Pay equity check by level, with a note when group sizes are too small to conclude.
  • Cost to bring everyone below minimum up to the minimum.
  • Three recommendations for the next appraisal cycle.

Quality rules

  • Use only the market figures in the inputs and show the calculation for each midpoint.
  • Never show names; use employee codes only.
  • Do not suggest cutting the pay of anyone above the band; suggest holding increases instead.
  • State that bands should be reviewed each year against new market data.
salary bandspay bandscompensation structuresalary range by levelpay equity checkcompensation planning

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity