← All use cases
Use case 14

Team remuneration visualiser

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.

Vibe-coded tool No AI needed to run it For people managers
Try itUse the real tool. Watch itFive steps, animated. Build itPrompts you can paste. Check the dataWhat is safe, and where. Take itDownload the finished file.

What it does and why it matters

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.

1Try 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.

2Watch it

Five steps from a team file to a better-informed pay conversation. Press Play, or step through at your own pace.

Step 1 of 5Invented data
data-and-analytics-team.csv
namejob_titlelevelreference_point_tfrtfrratingyearscritical
Priya RamanData AnalystLevel 2$95,000$82,000Meets0.5No
Mark PetersenSenior Data AnalystLevel 3$118,000$124,500Meets3No
Daniel ItoData EngineerLevel 4$140,000$163,000Meets4No
James OkaforSenior Data ScientistLevel 5$165,000$144,000Exceeds1.2Yes

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.

One person: James, a Senior Data Scientist at Level 5
$144,000TFR
÷
$165,000Reference point
=
0.87compa-ratio

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.

The team, most junior on the left
Level 2Level 3Level 4Level 5Level 6 3 people2 people2 people2 people1 person
Stretch / entryDevelopingFully proficientSuperstar / critical

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.

Hover over James
James OkaforSenior Data Scientist · Level 5
TFR
$144,000
Reference point
$165,000
Compa-ratio
0.87
Stretch / entry to role (below 0.90)
  • ✓Still within the 12 to 24 months the guidelines allow to reach 0.90.
  • ?Rated Exceeds expectations but below 0.90. Is pay keeping up with performance?
  • ?Marked critical but below 0.90. Is there a retention risk?
  • !Outside 0.90 to 1.10: document the rationale.

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.

What if James gets 8%?
$144,000TFR now
+8% =
$155,520Proposed
Compa-ratio 0.87 → 0.94 Stretch / entry → Developing
? Rated Exceeds expectations and marked critical, but paid below the reference point. Is there a retention risk?
+$11,520a year, 0.9% of the team's TFR
6 of 10in the target range (prior to changes: 5)

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.

3Build it

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".

Step 1: Describe the tool

Say what the tool is, what goes in, and who will use it.

I work in reward in Australia and I am not a developer. Please build me a "team remuneration visualiser" for people managers, as a single HTML file that I can save to my computer and open in a browser by double-clicking it. Requirements: - It must run offline. Use no external libraries, fonts, images or links, and send no data anywhere. Draw the charts yourself. - It saves nothing. No cookies, local storage or network requests. Refreshing the page clears everything. - The user loads a CSV file with one row per person in one team. Needed columns: name, reference_point_tfr, tfr. Optional: employee_id, job_title, level, performance_rating (Below, Meets or Exceeds expectations), years_in_role, critical (Yes or No), gender, proposed_tfr, rationale_tags, rationale_note. Add a button to download a blank template. - TFR means total fixed remuneration: base salary plus super plus fixed allowances, annual and full-time equivalent. The reference point is on the same basis. - Let me also type, edit, add and remove people on screen. - Build in an invented sample team of 10 people in 5 roles across 5 levels, with at least two people in each positioning band (described in my next message), and a few cases a manager should question. Label it clearly as invented. - The audience is people managers. Use plain English and Australian spelling. Keep the design clean. Before you write any code, tell me in a few sentences what you plan to build, and ask me about anything that is unclear.

Step 2: Give it your guidelines and the rules

Do not let the AI guess what is appropriate. Give it your bands, and say exactly when to ask a question.

Now add the calculations and our positioning guidelines. Follow these definitions exactly. Do not substitute your own. 1. Compa-ratio = TFR รท reference point. Show it to two decimals. 2. Target range: fixed at 10% either side of the reference point (0.90 to 1.10). Both edges count as inside. 3. Custom range: an optional second range with separate "% below" and "% above" settings, shown alongside the target range, never replacing it. 4. Positioning bands, fixed whatever the custom range: below 0.90 "Stretch / entry to role"; 0.90 to under 1.00 "Developing in role"; 1.00 to 1.10 "Fully proficient / experienced"; above 1.10 "Superstar / critical talent". For each band, show the reasons and the expectation from the guidelines pasted at the end of this message. 5. Two charts with a switch between them: (a) one floating column per person showing their target range in dollars, a line at the reference point and a dot for their TFR; (b) everyone's compa-ratio on one scale with the four bands shaded. Order people by level, most junior on the left, then by TFR, and label each level group with its headcount. Colour each dot by its band. 6. Hovering over a person shows TFR, reference point, compa-ratio, their band, a one-line summary of when that band is appropriate, and the checks below. 7. Checks, written as questions, never verdicts: - Below 0.90: ask if in role 2 years or more ("is there a plan to reach 0.90?"), if rated Exceeds ("is pay keeping up?"), and if critical ("is there a retention risk?"). - 0.90 to 1.00: ask if in role 4 years or more and rated Meets or Exceeds, and if rated Exceeds and critical. - 1.00 to 1.10: ask if in role under a year, and if rated Below. - Above 1.10: ask if rated Below, or rated Meets and not critical, and if in role under a year. - Any band: ask when someone with the same job title is rated higher but has a compa-ratio at least 0.05 lower. - Also show "what the data supports" lines where the data matches a band reason, and policy lines: outside 0.90 to 1.10 "document the rationale"; above 1.10 "needs additional approval". 8. What-if: let me enter a % or a new TFR for anyone. Show the proposed figure as a second dot with an arrow, re-run the band and checks on the proposed figure, show the total cost in dollars and as a % of the team's TFR, and let me add an optional reason picked from tags based on the band's reasons, plus a short note. 9. Below the chart, one card per person showing everything from the hover, in full. 10. Headline boxes above the chart: the number of people in each band and in the target range after any changes, with the figure prior to changes underneath. Explain each definition in one plain-English sentence on the page. Our positioning guidelines: [paste your guidelines here: for each band, the reasons a person might be positioned there and the expectation]

Step 3: Be deliberate about who sees what

This tool shows named pay to a manager. Say so on purpose, and add the protections that still matter.

Now set the rules for showing people. - This tool shows named individuals' pay to their own manager. Show a clear notice near the top saying so, and telling managers to load only their own team. - Add a "Hide names" switch that shows the employee ID instead of the name everywhere (chart, tables, cards, print and export), for when a manager shares their screen. Do not use initials: in a small team they still identify people. - Add a check comparing the average compa-ratio of women and men. Hide it unless there are at least 3 women and 3 men. - Add an "Export spreadsheet" button that writes a CSV in the same layout as the upload, plus the calculated columns, so it loads straight back in. Put an apostrophe in front of any text that starts with =, +, - or @ so a spreadsheet cannot run it as a formula, and take it off again when the file is loaded back in. - Add a print-ready page. - Show a clear line near the top: "Your file is read by your own browser. Nothing is uploaded or saved." When you finish, list every place in the code that could store or send data, and confirm there are none other than the files I choose to download.

Step 4: Make it prove itself

Load a small file where you can work out every answer by hand, including the edges.

Please help me check the calculations. 1. Create a test CSV of exactly these 7 people: name,job_title,reference_point_tfr,tfr,performance_rating,years_in_role,critical,gender,proposed_tfr A,Analyst,100000,89999,Meets,3,No,Woman, B,Analyst,100000,90000,Exceeds,4.5,No,Man, C,Analyst,100000,100000,Meets,0.5,No,Woman, D,Engineer,120000,132000,Below,2,Yes,Man, E,Engineer,120000,132120,Meets,5,No,Woman, F,Engineer,120000,102000,Exceeds,1.5,Yes,Man,114000 G,Engineer,120000,,Meets,1,No,Man, 2. Before I load it, tell me what the tool should show for each person: compa-ratio, band before and after any change, and which questions appear. Also: the band counts after the change, the number in the target range before and after, the cost of the change, and the average compa-ratio of women and men before and after. 3. If any result does not match a hand calculation, say so plainly and fix the calculation. Do not adjust the test data to make it fit.

The answers you should get

Invented example
PersonCompa-ratioBandQuestions that appear
A0.90 (really 0.89999)Stretch / entryBelow 0.90 for 2+ years
B0.90Developing4+ years and still below 1.00
C1.00Fully proficientUnder a year in role; paid more than B, who is rated higher
D1.10Fully proficientRated Below; paid more than F, who is rated higher
E1.10 (really 1.101)Superstar / criticalRated Meets and not critical; paid more than F
F0.85 → 0.95Stretch → DevelopingRated Exceeds and critical, but below the reference point
GNoneNot shownLeft out: no TFR
In the target range, prior to changes and after3 → 4
Cost of F's change: $12,000 ÷ $646,119 of team TFR1.9%
Average compa-ratio, women and men, after the change1.00 / 0.98

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.

Good habits

  • Check the rules with a second AI. Give it only the rules and the test file, never the code, and compare its answers with the tool's. That is how this tool was checked.
  • Make sure pay and the reference point are on the same basis (here both are TFR). A base salary compared with a TFR reference point gives a wrong compa-ratio for everyone.
  • Keep the questions as questions. The manager knows the person; the tool only knows the data.
  • Keep the prompts you used, so you can rebuild or audit the tool when the guidelines change.

4Check the data

What this touches

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.

What is safe

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.

Ask before you start

  • Are managers here allowed to see individual pay, ratings and gender for their own team?
  • Who prepares each manager's file, and how does it reach them safely?
  • Where will exports be saved, and for how long?
  • Is this AI tool approved for our data?

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.

5Take it

Download the tool Open it in a new tab

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.