Before a labor budget goes to Finance, seven things should be confirmed: your pay philosophy, your job descriptions, your current pay rates, the 50th percentile market rate for each role, sector trends, documentation for every outlier, and the roles that have drifted below market without anyone noticing.
1. Your pay philosophy
This is the item almost everyone skips, and it is the one concept your entire compensation program depends on.
A pay philosophy is a documented statement of how your organization approaches pay and why. Building your comp structure from the 50th percentile. Which roles you compete the hardest for. What total rewards include and what it does not. It gets skipped because it is abstract, and because writing it down requires a clear idea of who the company is.
It is also a part of your culture. It can be the reason people stay and the reason they leave. Every compensation question that reaches a budget meeting eventually traces back to it, which is why it is the first question worth asking before the numbers start moving.
If it does not exist in writing, October is not too late to define one. It is not too late to write down what you have been doing in practice, which is usually a philosophy nobody has articulated yet.
2. Job descriptions that reflect the work
Benchmarking accuracy is capped by job description accuracy. A description written four years ago for a Maintenance Technician who now handles predictive maintenance and vendor coordination will return a market rate for a job that no longer exists at your site.
Check the roles where the work has changed most, which are often the technical roles, anything that absorbed duties during a vacancy, and anything with "Coordinator" or "Specialist" in the title. Titles drift and descriptions rarely follow.
KaBLING can provide updated job descriptions where there are gaps or do not exist.
3. What you are actually paying right now
Pull current base rates from payroll rather than working from last year's budget file or the pay grid as designed. Off-cycle adjustments, negotiated hires, and retention increases all land in payroll without necessarily landing anywhere else.
The gap between the grid you think you have and the rates you are actually paying is the first thing a compensation review exposes.
4. The 50th percentile for every role you are budgeting
The 50th percentile market rate is the competitive space and what KaBLING matches to what each role actually involves, not to the title. Same title, different job, different number.
This is the reference point for every other decision in the budget. Without it, increases get applied evenly across a structure that is already uneven, and the discrepancies carry forward another year.
KaBLING returns the 50th percentile rate matched on duties, critical skills, operating environment, with the source, the method, and the date behind each match.
5. Sector trends for the market you operate in
Industrial labor markets move at sector speed, not at national average speed. General wage growth figures are a poor input for a mining operation competing against two other sites within driving distance.
Check what is happening in your sector and your geographical area, including project starts that will pull from the same labor pool next year.
6. Documentation for every outlier
Technical roles with long tenure are frequently paid well above the 50th percentile while carrying no managerial duties. These roles are genuinely different and the market reflects it.
It becomes a problem when nobody can explain why. Every outlier in the structure needs documented rationale, and budget season is when someone senior is most likely to ask for it. Write down what makes the role an outlier before the question arrives.
7. The roles that have drifted below market
Entry and mid-level administrative roles produce more pay discrepancies than any other category. They sit outside operations, they are not always front of mind during a compensation review, and general increases applied across the board do not keep pace with market movement for these positions.
The result is often base pay well below the 50th percentile and a catch-up cost that grows every year it goes unchecked. Check these roles specifically. They may not surface on their own.
What is still fixable in October and November
Base pay carries the most flexibility. Increases are typically executed in January or Q1, so there is room to adjust the assumption through late fall.
Benefits are usually decided by this point in the calendar. Those decisions are made and the cost is in the model.
Bonuses may still be open, depending on when final profit numbers arrive. If profit share is calculated on year-end results, the structure can still move.
The practical read is that October and November are for budgeting base pay and structure adjustments. Anything you want to change about benefits belongs in next year's cycle.
Frequently asked questions
What is a pay philosophy?
A pay philosophy is a documented statement of how your organization approaches pay and why, including its intended market position, which roles it competes hardest for, and what total rewards include. It guides every individual pay decision and provides the rationale when those decisions are questioned.
Do we need updated job descriptions before benchmarking?
Yes. Market matching is based on what a role involves, so an out-of-date description returns a rate for work nobody is doing. Job descriptions can be updated as part of a benchmarking project.
Should every role be paid at the 50th percentile?
No. The 50th percentile is a competitive reference point, not a target for every position. A pay philosophy determines where each role or level sits relative to that point, and a functioning structure will have roles above and below it for documented reasons.
How late is too late to benchmark for this budget cycle?
Average salary survey benchmarking takes weeks, KaBLING returns market rates in minutes and full projects run in weeks not months, so a benchmarking project started in late fall can still inform base pay decisions executed in January.