[Legacy] Edit and apply benchmarks

After mapping your data sources and setting weights and logic, you can generate benchmarks, review the results, and make any adjustments.

Generate benchmarks

Benchmarks are only generated when you prompt the system to refresh them. This preserves a stable snapshot of benchmarks until you’re ready to regenerate.

To generate benchmarks:

1. Go to Market Pricing > Benchmarking > Edit job mapping > Survey mapping
2. Click Generate matches and choose which benchmarks you want to generate:

• Re-generate all matches - benchmarks will be generated for all mapped jobs. This will overwrite all previously-generated benchmarks.
• Re-generate affected matches - benchmarks will be generated for only new/updated jobs, mappings, weights, or survey logic since the last benchmark generation. This will only overwrite benchmarks for the impacted benchmarks.

:::info Note: Generating benchmarks can take up to 1 hour depending on how much data processed. You will be notified when the process is complete.

:::

Review benchmarks

Use the Benchmarking table to review your generated benchmarks and apply any edits. To start, go to Market Pricing > Benchmarking.

How benchmarking is structured

1. Job architecture - job ladder, pay zone, and pay type create a distinct row
2. Mappings - all relevant data source mappings that contribute to the composite benchmarks in this job ladder (data source/provider, percentiles, job families, and pay zones/locations)
3. Composite benchmarks - the composite benchmarks based on weights and logic from the mapped data sources for each job level
4. Status - any detected data anomalies or details for a given row

Cells in the Composite benchmarks are color coded for easy scanning:

1. White - job level has a composite benchmark
2. Red - job level is missing a composite benchmark. This can be caused by missing data from the data source or an issue in mapping.
3. Grey - job level doesn’t exist on this job ladder, so no composite benchmark was attempted

Benchmark data review

At the top of the page, you can get a quick overview of your benchmark coverage and anomalies across your jobs:

• Rows with complete data: The # of ladders in a specific pay zone for a specific pay type (row) where a benchmark is present for each level in the ladder.
• Rows with missing data: The # of ladders in a specific pay zone for a specific pay type (row) where at least one level is missing a benchmark.
• Rows with irregular progression: The # of ladders in a specific pay zone for a specific pay type where the benchmark for at least 1 level is higher than the level above it or lower than the level below it.
• Rows with no data: The # of ladders in a specific pay zone for a specific pay type where no data is present for any level in the ladder.

Filter benchmarks

Filter the jobs displayed in the table by using the filter bar:

• Filter options include:
  • Issue Type (Missing Data, Irregular Progression)
  • Number of Issues in Ladder
  • Pay Type (base, total cash, etc)
  • Job Ladder
  • Ladder Track (IC, Manager, etc)
  • Pay Zone
  • Data Source
  • Percentile
  • Job Family Mapping
  • Location Mapping

View composite benchmark details

You can explore more details of each data source that contributed to a composite benchmark by clicking the arrow on any job ladder row:

Download benchmarks

Click Download matches to export your benchmarks and issues column to CSV.

Edit benchmarks

You can improve data coverage and accuracy with bulk actions in benchmarking.

You can apply the following edits to a row:

• Update survey cut - updates the data source(s), breakout, percentile and weight
  • Only available if selected ladders have the same data source(s)
  • Optionally apply a % premium/discount to all composite benchmarks on the row
• Replace job code - updates the job family / code and weight for data source(s)
  • Only available if selected ladders have the same job family / code mapping
  • Optionally apply a % premium/discount to all composite benchmarks on the row
• Apply geo differential - sets benchmarks based on relative pay zone percentages
  • Uses anchor pay zone as basis
  • Available for ladders with a relative pay zone setup in Market Pricing > Pay Zones
• Apply level progression - fills in missing benchmarks or resolves irregular progressions
  • Creates benchmark values for missing levels based on existing level data
  • Smooths progression issues by applying a % progression
  • Uses closest non-issue data point as the anchor value
• Reset changes - reverts the selected rows back to their original composite benchmarks when generated, undoing any edits applied.

:::info Note: Benchmark edits only affect the composite benchmark, but not the defined mappings. So regenerating benchmarks will overwrite any changes made with these actions.

:::

Update survey cut

Update the survey source(s), breakout, percentile, and weight. This edit can be useful when your original data source did not return data.

• Only available if selected ladders have the same data source(s)
• Optionally apply a % premium/discount to all composite benchmarks on the row
  • Adjustments default to 100%, so an 80% adjustment would decrease the composite benchmark by 20%. A 120% adjustment would increase the composite benchmark values by 20%.
• Upon applying changes:
  • The mapping columns in the table reflect the new job codes.
  • The composite benchmark details shows the data source, job code, and data values if they were present in the source.
  • If an optional adjustment was applied, the composite benchmark details composite benchmark represents the survey values + the adjustment.

Replace job code

Update the survey code and weight for any provider. This edit can be used when your preferred survey code did not return data.

• Only available if selected ladders have the same job family / code mapping

• Optionally apply a % premium/discount to all composite benchmarks on the row

  • Adjustments default to 100%, so an 80% adjustment would decrease the composite benchmark by 20%. A 120% adjustment would increase the composite benchmark values by 20%.

• Upon applying changes:

  • The mapping columns in the table reflect the new job codes.

• The composite benchmark details shows the data source, job code, and data values if they were present in the source.

• If an optional adjustment was applied, the composite benchmark details composite benchmark represents the survey values + the adjustment.

Apply geo differential

Adjust the benchmark values based on your relative pay zone values.

• The selected rows benchmarks are updated by using the anchor pay zone’s benchmark values and applying a relative value %, based on your company’s pay zone relative values set up in Pay Zone Manager
• If no data is present in the primary pay zone, the values for the selected ladder will not be updated.

Apply level progression

Fill in missing data or fix irregular progressions for levels in a ladder

• Updates the specific levels that have missing data or irregular progression issues, and not to the whole ladder.
  • If missing data: creates benchmark values for levels missing data based on the benchmark values of the other levels in the ladder
  • If irregular progression issue: This edit smooths irregular progression issues by applying a % progression to the levels in the ladder w/ irregular progression issues
• When applying % progression to fill in missing levels or updating irregular progression, we use the closest data point with no issue, in logic order, as the anchor. If there are two data points the same distance away, we use this prioritization to resolve as mid-levels tend to provide the most reliable data:
  • P3
  • P4
  • P2
  • P5
  • P1
  • P6
• For example:

  • [No P1] - P2 - P3 - P4 - [No P5] - P6: First resolve P5 using P4, then resolve P1 using P2.

  • P1 - P2 - [No P3] - [No P4] - P5 - P6: First resolve P3 using P2. Then resolve P4 using the calculated P3 value.

  • P1 - P2 - P3 - [No P4] - P5 - P6: Resolve P4 using P3.

Reset changes

This action will revert the selected rows back to their original composite benchmarks when generated, undoing any edits applied. This action is irreversible.

View activity log

Maintain a history of your edits, so you can understand what updates you made. You can view the activity log in the composite benchmark details for each ladder.

The activity log shows each edit applied with a history of the actions taken and the resulting composite values.

Apply benchmarks to bands

Once benchmarks are ready, you can apply them to your bands in order to reference benchmark data while viewing and updating your band sets.

There are 2 methods to apply benchmarks to a band set:

1. Apply benchmarks to existing band set - will overwrite benchmarks on any existing band set
2. Duplicate band set and apply benchmarks - will duplicate the band set and then overwrite benchmarks