Show a manager how each person in their team is paid against their reference point and target range, why that position might be right under your positioning guidelines, and what a change would do before anyone commits to it.
Managers are often asked to make pay decisions with a spreadsheet of numbers and little sense of whether each person's position is reasonable. The positioning guidelines exist, but they sit in a separate document that few managers open at the right moment.
This tool puts the two side by side. It shows each person's total fixed remuneration (TFR: base salary plus super plus fixed allowances) against the reference point for their role and a target range of 10% either side. The manager can switch between floating columns in dollars and a single compa-ratio scale (compa-ratio is pay divided by the reference point, so 1.00 means paid exactly at it). A custom range can be laid over the top.
Hover over anyone and it explains, from the guidelines, when a position like theirs is appropriate, what in the data supports it, and which questions to ask. A manager can try a change, see where the person would land and what it would cost, and note why. A card for every person below the chart repeats it all, so nothing depends on hovering.
It shows named individuals, because a manager already knows their own team. It saves nothing: close the page and it is gone, unless you export a spreadsheet.
It was "vibe coded": you describe what you want to an AI assistant in plain English and let it write the code. Once built, it is ordinary code. It applies the same rules every time and uses no AI when you run it.
This is the real tool, running in your browser on an invented team of 10. Hover over a person, switch to the compa-ratio view, turn on a custom range, or type a change for someone in "Try a change".
Every name and figure is invented, and so are Banksia Example Co's positioning guidelines. If you load your own file, it is read by your own browser and nothing is uploaded.
Five steps from a team file to a better-informed pay conversation. Press Play, or step through at your own pace.
| name | job_title | level | reference_point_tfr | tfr | rating | years | critical |
|---|---|---|---|---|---|---|---|
| Priya Raman | Data Analyst | Level 2 | $95,000 | $82,000 | Meets | 0.5 | No |
| Mark Petersen | Senior Data Analyst | Level 3 | $118,000 | $124,500 | Meets | 3 | No |
| Daniel Ito | Data Engineer | Level 4 | $140,000 | $163,000 | Meets | 4 | No |
| James Okafor | Senior Data Scientist | Level 5 | $165,000 | $144,000 | Exceeds | 1.2 | Yes |
Start with your team. One row per person: their total fixed remuneration (TFR), the reference point for their role on the same basis, and three facts the guideline checks use: performance rating, years in role, and whether they are critical or hard to replace.
Work out the compa-ratio. Pay divided by the reference point. 0.87 means James is paid 13% below the reference point for his role, so he sits below the target range of 0.90 to 1.10.
See everyone against their range. Each column is a person's target range, 10% either side of their reference point (the line). The dot is their pay, coloured by the guideline band it falls in. In this invented team, 5 of 10 sit inside the target range.
Check against the guidelines. The guidelines say when a position below 0.90 is appropriate: a stretch appointment, someone new to the role, a recent promotion. James has been in role for over a year, is rated Exceeds and is marked critical. The tool turns that into questions for the manager. It uses fixed rules, not AI, and never gives a verdict.
Try a change. Type a % or a new figure and everything updates: the dot moves, the band and the questions follow, and the cost appears. An optional reason can be picked from the guideline reasons. Nothing changes anyone's actual pay.
All figures in this walkthrough are invented and match the tool's built-in sample team at its starting settings.
You can build your own version with any capable AI assistant your employer allows, for example Microsoft Copilot, Claude or ChatGPT. You describe what you want, it writes the code, and you check the answers.
Build it with invented data, never a real team's pay. Have your own positioning guidelines to hand, because the tool is only as good as the rules you give it. Expect two or three rounds of "that's not quite right, change X".
Say what the tool is, what goes in, and who will use it.
Do not let the AI guess what is appropriate. Give it your bands, and say exactly when to ask a question.
This tool shows named pay to a manager. Say so on purpose, and add the protections that still matter.
Load a small file where you can work out every answer by hand, including the edges.
| Person | Compa-ratio | Band | Questions that appear |
|---|---|---|---|
| A | 0.90 (really 0.89999) | Stretch / entry | Below 0.90 for 2+ years |
| B | 0.90 | Developing | 4+ years and still below 1.00 |
| C | 1.00 | Fully proficient | Under a year in role; paid more than B, who is rated higher |
| D | 1.10 | Fully proficient | Rated Below; paid more than F, who is rated higher |
| E | 1.10 (really 1.101) | Superstar / critical | Rated Meets and not critical; paid more than F |
| F | 0.85 → 0.95 | Stretch → Developing | Rated Exceeds and critical, but below the reference point |
| G | None | Not shown | Left out: no TFR |
After the change the bands hold 1 Stretch, 2 Developing, 2 Fully proficient and 1 Superstar. Two people test the edges. A shows 0.90 when rounded but is just below it, so A is in Stretch and below the target range. E shows 1.10 but is just above it, so E is a Superstar and above the target range. B and D sit exactly on the edges and count as inside. Men's average moves from 0.95 to 0.98 because of F's change.
If the tool gives a different answer, it is wrong. Tell the AI what you expected and ask it to fix the calculation.
Named individual pay for one team, plus performance ratings, time in role, a "critical" flag and gender, and any reasons a manager types. In a team this small, every figure on screen belongs to someone the viewer knows.
The finished tool runs in your browser, and nothing is uploaded or saved. Exports and printouts hold named pay, so treat them like a payslip. Use "Hide names" when sharing your screen. The gender check stays hidden unless there are at least 3 women and 3 men. When you build your own, give the AI assistant invented data only.
The guidelines in the tool are Banksia Example Co's invented guidelines; replace them with your own. The questions are prompts for a manager's judgement, not decisions, so changes still go through your normal approval process. For the review itself, the manager's review tracker handles budgets and submissions. Privacy rules for employee records differ between private employers and government agencies, so check with your privacy officer. Start with the OAIC's guidance on the Australian Privacy Principles and on employment and privacy. General information, not legal advice.
It is a single file. Save it anywhere and double-click to open it. The blank template downloads from inside the tool, and an exported spreadsheet loads straight back in.
What next: to see positioning across the whole organisation, try the position in range analyser. To run a team's pay review with a budget, try the manager's review tracker. Or go back to all use cases.