Grades, Steps, and Rates: The Pay Structure Under Everything
Grade and step structures underpin pay, progression, and comp. Model them to match your real pay policy or you'll patch around them forever.
Grades and steps are the quiet scaffolding under your whole pay structure, and if they don't match your real pay policy, you'll spend years patching around them. Model them properly up front and progression, comp, and reporting all click into place.
Match grades to your actual pay policy
If you pay in bands with ranges, model grades with rate ranges. If you use fixed steps, model steps. Forcing a step structure onto a band-based policy, or vice versa, creates constant friction.
Decide how progression works
Automatic step progression on tenure? Manual on merit? Your policy decides, and the config must follow. Automatic progression configured for a merit-based org pays rises nobody approved.
Keep rates maintainable
Pay ranges change, annually at least. Configure grade rates so an annual update is a clean, bulk change, not a hand-edit of hundreds of records. You'll do this every year, so build for it.
Real scenario: a client modelled fixed steps because the template had them, but their real policy was salary bands with manager discretion. Every hire needed a fake 'step' picked to approximate a band salary, and reporting was meaningless. We remodelled as graded ranges matching the actual policy. Hiring got honest and the numbers meant something. Match the structure to the policy, not the template.