Distinguish the job, the person and the system

Salary concerns can become difficult to resolve when three separate questions are treated as one. The first is the relative value of the position. The second is where an employee should sit within the position’s range. The third is how the whole structure should change as organizational needs and labour markets evolve.

A job evaluation addresses the first question. Placement and progression rules address the second. Periodic review of ranges and policy addresses the third. A defensible structure connects these decisions while preserving their distinct purposes.

Arcus recommends explaining these distinctions before showing employees a proposed grid. Otherwise, a change to a range may be mistaken for a promise of an individual raise, or recognition of an employee’s contribution may be mistaken for evidence that the job belongs in a different grade.

Fairness also has a procedural dimension. Employees should understand how decisions are reached, how factual errors can be corrected and who is accountable for applying the rules. A technically sophisticated structure can lose credibility if those processes are unclear.

Establish principles before evaluating positions

Agree what the structure is meant to achieve. Possible principles include consistent recognition of responsibility, a credible employment proposition, transparent progression and sustainable administration. Translate broad intentions into choices that can guide difficult cases.

For example, “recognize capability” requires clarity about whether capability affects entry placement, progression, promotion or all three. “Remain competitive” requires a definition of relevant labour markets and a process for considering evidence. Neither statement alone determines a salary.

Identify the population covered and any distinct arrangements. Different employee groups may operate under agreements or policies that affect design. Resolve those boundaries before assuming a single structure can cover every situation.

Confirm the applicable legal, contractual and policy requirements through appropriate expertise. A general management framework cannot determine which employment or pay-equity obligations apply to a particular Nation or organization.

Set governance for the project: an accountable sponsor, accurate role information, a method for employee input, an approval route and a way to resolve disagreements about facts.

Evaluate actual work consistently

Use current descriptions of responsibilities, authority, working relationships and conditions. Evaluate the role required by the organization, not the personal reputation or negotiating history of its incumbent.

A structured method can compare relevant dimensions such as knowledge, problem-solving, accountability and working demands. Select and define factors that fit the work, then test whether they recognize contributions across different functions without double counting the same responsibility.

Community relationships, cultural responsibilities and language capability may be material requirements in particular roles. Describe the actual work and required capability precisely so the evaluation can consider it consistently. Avoid treating broad cultural labels as a substitute for role analysis.

Calibrate results across departments. If similar responsibilities produce different outcomes, investigate whether the descriptions, evidence or scoring interpretation differ. A review panel should be able to explain the result using the method rather than personal preferences.

Keep an evidence record and a factual reconsideration route. A challenge may reveal a missing responsibility or changed mandate; it does not automatically mean the methodology is wrong. Conversely, repeated inconsistent outcomes may expose a design problem that individual corrections will not fix.

Choose a structure the administration can maintain

A stepped grid offers defined salary points and can make movement easier to explain. Its effectiveness depends on clear eligibility rules and reliable administration. Steps can create expectations that must be reflected in the budget.

Ranges with more discretion can accommodate varied experience and capability. They require stronger placement guidance, manager judgment and calibration. Without those controls, similar employees may receive different treatment because different managers negotiate differently.

Broader bands can support flexible roles and career development, but they place more weight on the rules governing movement within the band. Narrower grades can distinguish responsibility more finely, while increasing classification and maintenance work.

Choose the simplest structure that represents meaningful differences in the Nation’s work. A small administration may not need many grades. Nor should distinct levels of accountability be compressed into one range solely to simplify a spreadsheet.

Test the design with realistic cases: an experienced new hire, an internal promotion, a substantially changed role, an employee at the maximum and a difficult-to-recruit specialist. If each case requires an improvised exception, the design needs more work.

Separate placement, progression and market movement

Starting placement should use defined, job-relevant criteria and documented approval. Decide how relevant experience, demonstrated capability and other approved considerations influence placement. Review the effect on comparable existing employees before making an offer.

Progression should have a stated basis, whether defined steps, demonstrated competence, performance or another approved approach. Explain the evidence and timing. Managers need enough support to apply the approach consistently.

A market adjustment changes the structure or a defined part of it. An individual progression decision moves someone within the structure. A promotion reflects a different role. These changes may occur together, but the payroll record and employee explanation should identify each component.

Specialist premiums or temporary allowances should have a purpose, eligibility rule, authority and review date. Keeping them visible can preserve the meaning of the underlying grade. Hiding every market pressure inside job evaluation risks confusing role value with short-term recruitment conditions.

Review exceptions collectively. Several exceptions of the same type may indicate that the range, job design or employment proposition needs attention. A growing exception list is an early warning about maintainability.

Model transition and future costs separately

Map current salaries to the proposed structure before approval. Identify employees below the proposed minimum, within range and above the maximum. Each category needs a defined treatment consistent with applicable obligations and approved policy; a new grid is not automatic authority to reduce existing pay.

Consider a hypothetical group with a proposed minimum of $60,000. Three employees currently earn $55,000, $58,000 and $60,000. Bringing the first two to the minimum requires $7,000 in annual base pay. At an illustrative 20% associated employer-cost allowance, the annual increment is $8,400.

That calculation says nothing about the cost of future progression, adjustments to neighbouring grades or other employees elsewhere in the administration. Model these separately. If all three later receive a $2,000 step increase, that adds another $6,000 in base pay, or $7,200 with the same illustrative allowance.

Do not add a general structure adjustment and individual progression without specifying their interaction. For example, a 2% increase applied to $60,000 produces $61,200; adding a $2,000 step afterwards produces $63,200. Applying 2% after the step instead produces $63,240. The policy and payroll configuration must agree on the intended calculation.

Budget the implementation work as well: role validation, employee communication, manager training, payroll changes and resolution of questions. A structure that consumes excessive management time may need simplification even if its salary costs are affordable.

Investigate fairness concerns before changing the whole design

A perceived inconsistency can come from several sources. Roles may have been evaluated differently, employees may have been placed inconsistently, a manager may have communicated poorly, or a legitimate difference may not have been explained. A salary structure cannot solve every one of these problems by changing its ranges.

Test the explanation using the relevant record. If the role information is wrong, correct it and reconsider the evaluation. If the method was applied inconsistently, calibrate the decisions. If a new offer has created compression with experienced employees, examine placement and market policy together.

Choose a targeted correction when the underlying structure remains sound. Consider broader redesign when repeated cases reveal a systemic weakness. Avoid repeated ad hoc increases that resolve immediate pressure while making the overall system harder to defend.

Track whether questions are answered promptly, exceptions decline and decisions can be explained consistently. Recruitment and retention results provide useful context but are influenced by many factors; they do not independently prove the structure is fair.

Introduce the structure as an ongoing management responsibility

Validate role information first, test the proposed design on representative cases and model its costs. Then obtain approval through the Nation’s established process before making individual commitments.

Provide managers with worked examples and employees with a clear explanation of the method, their own placement, future progression and the route for questions. Protect confidential information while making the decision process understandable.

Assign one owner for policy versions and one controlled process for payroll instructions. Record the reason and authority for each material change. Review the design when services, roles or labour-market conditions change significantly.

A fair salary structure does not remove judgment. It makes judgment more consistent, visible and accountable, while preserving the Nation’s ability to respond to changing needs.

Evidence and source notes

1. K’ómoks First Nation, Wage Scale and Career Ladder Policy, effective November 1, 2024, main policy and appendices. A Nation-specific published design example.
2. Vuntut Gwitchin First Nation, Council resolution CO2024-01, January 4, 2024, Approval of Job Evaluation Plan.

Research reviewed October 18, 2026. Salary figures are hypothetical design examples, not recommended pay rates. The six connections are original Arcus management analysis.