There are two reasons a band may not be linked to a benchmark:
- Benchmarking data has a small sample size (under 5 data points): If we don’t have at least 5 data points for the benchmarking slice we will not pull the benchmarking data since we have insufficient data. In most cases, we will “predict” what the band mid-point should be based on the data available for other levels in the job family, but that band is not tied to a specific benchmarking data slice.
- Manually added bands: If you manually add a compensation band using the “New +” flow when you are creating bands and choose to write in a job family that Pave does not have data for, we will not be able to tie it to benchmarking data.