Review benchmarks
Reviewing Benchmarks
The Benchmarking tab shows market data for your jobs and helps identify issues with your benchmark configuration. This guide covers benchmark statuses, filters, and quick fixes for missing mappings and data rules.
Table of Contents
- Overview
- Benchmark Completion
- Filters and Quick Actions
- Missing Mapping Callouts
- Missing Data Rule Callouts
- Requirements for Benchmarks
- Related Articles
Overview
Centralized action: All benchmarking happens within the band set. The Benchmarking tab shows market data alongside your jobs, making it easy to see what's working and what needs attention.
What you'll do in this tab:
- Review benchmark completion status
- Identify jobs missing mappings or data rules
- Click directly to fix issues
- Review benchmark values for all jobs
- Filter by status to find gaps
Benchmark Completion
At the top of the Benchmarking tab, you'll see benchmark completion status.
Benchmark Completion Card
Left side:
Benchmark completion
- Base pay: Progress bar (blue filled, orange remaining)
- Percentage: e.g., "70%"
Shows what percentage of jobs have benchmark data for each pay type.
Benchmark Inputs Card
Right side:
Data sources
- Count: "10"
- Link: "View sources"
Jobs mapped
- Count: "1,512"
- Warning: "⚠ 28 unmapped jobs" (if any unmapped)
- Link: "View mappings"
Click View mappings to go directly to the job mapping interface.
Missing Mapping Callouts
When jobs are missing ladder, level, or pay zone mappings, the Benchmarking tab shows clear callouts.
Missing Mapping Indicator
In the table, jobs without complete mappings show:
Benchmark column: Empty or placeholder Data rule column: "Map to ladder →" button
What this means:
- The job is missing a ladder mapping
- Without a ladder mapping, Pave can't pull benchmark data
- Clicking the button takes you directly to the Ladders mapping tab
Quick Fix Flow
- Click Map to ladder → button
- You're taken directly to the Ladders tab in job mappings
- The specific ladder that needs mapping is highlighted or filtered
- Add the mapping (see Job Mapping article)
- Return to Benchmarking tab
- Benchmark data now appears
Alternative callouts:
- "Map family" - Missing family mapping
- "Map level" - Missing level mapping
- "Map pay zone" - Missing pay zone mapping
Missing Data Rule Callouts
When jobs aren't assigned to a data rule, the Benchmarking tab shows a callout.
Missing Data Rule Indicator
In the table, jobs without data rules show:
Data rule column: "Add to data rule" text or button
What this means:
- The job has mappings but isn't in any data rule
- Without a data rule, Pave doesn't know which surveys/percentiles to use
- You need to assign this job to a data rule
Quick Fix Flow
- Select the job(s) missing data rules (checkboxes)
- Click Apply data rules button in toolbar
- Choose:
- Create new rule - Make a new data rule for these jobs
- Add to existing rule - Add to an existing data rule
- Configure the rule (see Data Rules article)
- Benchmark data now appears
Requirements for Benchmarks
To generate a benchmark for a job, you need:
1. Ladder Mapping
The job's ladder must be mapped to survey families.
Check: Go to Benchmarking → View mappings → Ladders tab
If missing: You'll see "Map to ladder" callout in Benchmarking tab
2. Level Mapping
The job's level must be mapped to survey levels.
Check: Go to Benchmarking → View mappings → Levels tab
If missing: You'll see "Map level" callout
3. Pay Zone Mapping
The job's pay zone must be mapped to survey locations.
Check: Go to Benchmarking → View mappings → Pay Zones tab
If missing: You'll see "Map pay zone" callout
4. Data Rule
The job must be assigned to a data rule that specifies which surveys and percentiles to use.
Check: Data rule column in Benchmarking tab
If missing: You'll see "Add to data rule" callout
Complete Requirements
Formula:
Ladder mapping + Level mapping + Pay Zone mapping + Data rule = Benchmark
If any component is missing, no benchmark will be generated.
Benchmark Statuses
Once mappings and data rules are in place, jobs show different statuses:
Has Benchmark ✓
Job has valid market data from configured sources.
Action: No action needed.
No Data Found
Job mapped correctly but survey has no data for this position.
Action:
- Use different survey
- Map to different survey job
- Use fallback data sources
Failed to Autosmooth
Auto-smoothing attempted but failed for this job.
Action: Review manually or adjust auto-smooth settings.
Irregular Progression
Benchmark values don't follow expected pattern across levels.
Action: Review mappings or data quality.
Related Articles
- Job Mapping: Fixing missing ladder, level, and pay zone mappings
- Data Rules: Creating and assigning data rules
- Benchmarking Bulk Edits: Applying benchmarks to bands
- Manage Data Sources: Adding survey data