Run the whole pay review from one place. Load each manager's submission as it arrives and see progress, spend against budget, every exception, and any skew between women and men across the organisation.
The reward team's view of a review usually lives in a pile of spreadsheets, stitched together late at night. Exceptions get lost in the pile. Patterns across teams are only seen afterwards, when there is little left to do about them.
This tool is the reward team's half of a pair. Managers use use case 07 to propose increases for their own team and download a submission file. You load each file here as it arrives, and the whole picture builds up while there is still time to act.
The fairness view matters most. A pattern that no single team can see can show up once everyone is put together. Better to find it now than in next year's pay gap figures.
Both tools are ordinary code, built by describing what you want to an AI assistant. Neither uses AI when you run it. This one is "stateful": it keeps your work between sittings, so it needs somewhere to keep it. Here, that is a file you save.
This is the real tool, running in your browser on an invented review of five teams. Three have already submitted. Load a submission, record decisions, change the minimum group size, or save your work.
Your files are read by your own browser. Nothing is uploaded.
Five steps from a folder of submissions to a pattern across the organisation. Press Play, or step through at your own pace.
Submissions arrive. Each manager sends one file. Load them one at a time or all together, and each team flips to Submitted.
Where everyone is up to. One table shows who has submitted and who has not. Teams still working show dashes instead of money figures, so nothing is guessed.
Spend against budget. Two teams are under. One is over by about $5,500. The organisation as a whole can look fine while one team is not.
Every exception in one list. The manager's reason sits next to the proposal. You record Approve, Decline or Query, and a note.
The pattern no single team can see. No one team has enough women and men at a level to show this. Put together, level 3 stands out. It is a prompt to look closer, not proof.
All figures in this walkthrough are invented, for illustration only. They match the sample data in the tool above.
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.
This one is harder than a single tool, because two tools have to work together. The steps below put the hard part first: agreeing what travels between them. Build with invented data, never your real review files. Expect two or three rounds of "that's not quite right, change X".
When two tools pass a file between them, they need a written agreement on exactly what is in it: every field, what each one means, and how every figure is worked out. If they disagree, even slightly, the totals will not match and nobody will know which tool is right. Writing the agreement down first is the single most useful habit for anything bigger than a one-off tool.
Say who uses the tool and what each view shows. Name the views, so you can ask for changes to them later.
A file can be out of date, edited by hand, or made by a different version of the other tool. A total you have not checked is a total you should not report, so the reward tool works everything out again for itself.
A tool that "remembers" has to keep your work somewhere. A browser can keep it for you, but only in that one browser on that one computer. It can be cleared without warning, you cannot see where it is, and you cannot put it in a controlled folder. A file you save and open is different. You choose where it lives, who can reach it, and how long you keep it. This site chose a file, because pay data belongs in a folder you control, not in a browser you do not.
Test the two tools together, not one at a time. Use a small invented team, and work out the answers by hand before you load anything.
Pay, ratings and managers' written reasons for everyone in the review. This is the largest collection of pay data on this site.
Written reasons can say more than a salary does. Treat them with the same care.
The tool stores nothing and sends nothing. The risk is the files: the submissions coming in, and the workspace you save.
One saved workspace holds the whole review. Treat it like the remuneration committee paper.
Use ids, not names, in every file.
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.
If several people need to work on the review at the same time, or the review has to be audited, a file passed around stops being safe or practical. That is the point to talk to IT about a proper shared build. See the foundry use case and the ways to build for what that looks like.
The tool is a single file. Save it anywhere and double-click to open it. Load the sample submission to see what a manager's file looks like and how the tool reads it.
What next: Use case 07, the manager's tracker · Back to all use cases