The Salary Bands screen is where you compare your organisation's committed pay ranges against the market and your own employees. Each band is one cell in a track's ladder (e.g. IC2, M3) with a min, mid, and max in the country's currency. The screen surfaces who sits where, which bands are healthy or mispriced, and which roles still need mapping.
This guide covers the overview screen and what you can do from it. For first-time setup, see How to set up Salary Bands.
Before you start
Your HR and payroll systems should be connected — internal pay data depends on it. See the Integration Guide.
Salary Bands need to be set up at least once per country. If you land on the empty state instead of the overview, see How to set up Salary Bands first.
Your role needs BANDS_VIEW to read the screen, and BANDS_EDIT to add, edit, or remove tracks, bands, and role mappings.
Switching between countries
The top of the screen has a country picker. Bands are country-scoped — switching countries swaps the entire view (tracks, bands, mappings, currency) to that country's set.
When you have one country set up, the picker shows that country as a pill plus a + Add country chip.
When you have more than one, each country becomes a clickable pill — the selected one is highlighted.
Your last-used country is remembered across sessions.
To the right of the picker, the kebab (…) menu carries country-scoped actions — currently Delete this country, which archives the country and all of its tracks, bands, and role mappings together (recoverable via support; the audit log keeps the change).
The KPI strip
Four cards across the top summarise the country's bands at a glance:
Bands — total bands defined and how many tracks they span.
Roles mapped — count of LiveRem roles attached to at least one band, with unmapped roles as the sub-line.
People in bands — count of currently-employed people whose role maps to a band. The sub-line shows how many people fall outside any band (e.g. unmapped role, or no salary on file).
Bands needing review — count of bands where the market median sits above the band ceiling. Anything > 0 turns the card red.
Unmapped alert
If you have LiveRem roles without a band mapping, or people whose role isn't mapped to a band, a yellow alert sits above the track tabs. Click Map roles on it to jump into the mapping screen. Mapping the missing roles makes them count toward "People in bands" instead of "unmapped".
Track tabs and band rows
Below the alert you'll find tabs for each track plus an All tab. Clicking a track tab filters the band rows beneath to just that track's ladder.
Each row is one band, showing:
Level tag — short code + level (e.g.
IC2).Band name — e.g. "Engineer".
Roles · People count — how many roles are mapped to this band and how many people sit in it.
Defined range — the min and max you set during setup, in the country's currency.
Status chip — Healthy, Spillover, Mispriced, or Not used.
Inline triple — a small visualisation showing where the defined range sits on the country's axis. Market and internal medians overlay when data exists.
Click anywhere on a row to expand it.
Band status
Healthy — market median sits inside the defined range and your own people sit roughly inside it. Nothing to do.
Spillover — at least one employee in this band is paid outside the defined range (above the ceiling or below the floor). The insight line in the expanded view explains which way and by how much.
Mispriced — the market median for the mapped roles is above your band's ceiling. Either widen the band or split into another level — your defined range is now lagging the market.
Not used — no people sit in the band yet. Common right after setup or when a role you'd planned to put here isn't mapped yet.
Inside an expanded row
Expanding a band gives you three cards side-by-side, an insight line, and the list of roles mapped to the band.
Defined band
The range you committed to during setup — min · mid · max. Click Edit range in the corner to change min/mid/max for this band only.
Market value
P25, P50 (median), and P75 across LiveRem's market data for the roles mapped to this band. Weighted by how many of your own people each mapped role represents — so a band with one Admin and three Engineers leans toward the Engineer market.
Internal actual
P25, median, and P75 of your own employees' actual pay across the people mapped into this band. Helper line shows how many people the spread is built from.
Employees with no salary (or a $0 salary) are skipped from the internal calculation — they're a data-quality hole rather than band members.
Insight line
A short sentence translating the status into action — e.g. "Market median is $135,000 — $20,000 above this band's max. Either widen the band or split into another level."
Roles in this band
Below the cards, every LiveRem role currently mapped to the band is shown as a chip with its current people count. From the chip row you can:
+ Map a role — opens the mapping screen with this band's track pre-selected so you can drag roles in without hunting.
View people — opens a dialog listing every employee in the band with their name, LiveRem role, current salary, and whether their pay sits below / inside / above the defined range.
[SCREENSHOT: View people dialog with the columned employee list and position pills.]
The ladder rail
On the right of the screen, the ladder rail visualises every band across every track on a single salary axis. Each band is a rectangle stacked at its defined range, with the level code in the centre.
Rectangles are coloured by status (healthy = neutral, mispriced = red tint, spillover = orange tint).
The salary axis adjusts to fit your bands plus the market and internal data — high outliers don't blow up the scale.
Click a rectangle to scroll the list to that band and select it.
Add a new band
Click + New band on the page header.
Pick the track the band belongs to, set the level number (e.g. 5 for a new IC5), give it a name, and enter min / mid / max in whole dollars.
The save button is disabled unless
0 < min < mid < max— the inputs glow red when the range is invalid.
Edit or remove a band
Edit range — expand the band and click the pencil on the Defined card. Only name and range are editable; the track and level are read-only to avoid orphaning the role mappings underneath.
Archive — coming soon from the same dialog. Until then, contact support to retire a band.
Add a new track
Click + New track on the page header. Two modes:
Configure manually — same flow as the wizard's Set bands step but for one track: name, short code, colour, levels, bottom band, spread (percent / dollar / manual), live preview.
Upload CSV — drop in a CSV using the same template as the whole-country import. Only the rows matching the new track's short code are taken; everything else is ignored.
Save writes the track and every band in one go. Map roles to the new track from Map roles or from any of the new bands' Map a role link.
Remove a track
From the per-track view inside Map roles, click Remove track. The track is archived and stops showing on the overview; its bands stay in the audit log.
⚠️ Roles mapped to the removed track lose their mapping for that ladder. They keep any other mappings (e.g. a role mapped to both IC and M only loses the IC mapping).
Delete a country's bands
The kebab (…) menu next to the country picker carries a Delete this country action. A confirmation dialog shows what's about to be archived; clicking Delete country archives the country together with its tracks, bands, and role mappings.
⚠️ Deletion is a soft archive — the data stays in the audit log and support can restore on request, but the country disappears from the picker for everyone in the organisation immediately.
Filters
The Bands screen shares its benchmark filters with People Data and Role Atlas — industry, company size, revenue, community, exclude founders, new hires only, non-profits. Changing a filter recalculates the market and internal aggregates on both screens.
See How to use the People Data Page for the full filter reference.
By following this guide, you'll be able to read the Bands overview at a glance, compare your defined ranges to the market and your own people, and make changes to the structure without re-running the wizard.