## How parsing works

Pave parses your uploaded survey data into data slices that are then mapped to your jobs. Pave automatically parses the job family and job level from your data source’s job code in order to simplify the mapping process to your job architecture.

 ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001lT7&feoid=00NUn00000C06g9&refid=0EMTV00000EmTUH " =862x581")

## List of survey providers

Here is a list of common survey providers that Pave supports and the expected job code formats. `X`will be parsed to Job family. `Y` will be parsed to Job level.

| Survey provider | Support | Supported job code formats |
|----|----|----|
| Radford | Full support | `XX.XXXX.YY` (ex: `EN.SODE.P4`) |
| Mercer | Full support | `XXX.XX.XXX.YY` (ex: `ITC.06.022.M20`) |
| Comptryx | Full support | `XXXYY` (ex: `AFAP4`) |
| Willis Towers Watson | Full support | `XXXXXX-YY-YY` (ex: `ARE000-EX-10`)`XXX-YY-YY` (ex: `ARE-EX-10`)`XXXXXX-YY` (ex: `ARE000-25`)`XXXXXX-YY` (ex: `ARE000-P2`)`XXXXXX-YY-YY` (ex: `ARE000-P2-10`) |
| Culpepper | Full support | `XXXX-XX-YYY` (ex: `TE65-05-150`) |
| Pave | Full support | For family/level mapping: Native integrationFor overrides: `XXX [space] YYY` (ex: `Software Engineering IC3`) |
| Zviran | Partial support | `XX.XXXX.YY` (ex: `HR.1310.P13` )Not supported: • O (Operational) track codes (ex: `IT.1411.*O*10`) • C (Contributor) track codes (ex: `IT.1110.*C*15`) • R suffix on levels (ex: `M16R`, `P15R`, `M14R`) |
| Korn Ferry | Overrides only | N/A |
| McLagan | Overrides only | N/A |

 If you are using a data provider that doesn’t match the supported job code formats above, you can use overrides or reach out to [support@pave.com](mailto:support@pave.com).

## File format

Pave supports survey data files in the following formats:

* Comma-separated values (.csv)
* Microsoft Excel (.xlsx)

## Supported properties

The following survey properties can be uploaded as columns in your file and used for benchmarking in Pave.

### **Job, Location, and Survey properties**

| Property | Description | Format | Example |
|----|----|----|----|
| Job Code | Required. `string` Unique job code identifier comprised of Job family + Level typically generated by a data provider. Used to map data sources to jobs. | See table above | EN.A0G1.E1 |
| Location | Required. `string` Unique location identifier to classify what location a job code and compensation properties are associated with. Used to map data sources to jobs. |    | United States - US |
| Currency | Required. `string` Identifies the currency that the numeric compensation properties are in. | ISO 4217 | USD |
| Breakout | Optional. `string` Custom segmentation identifier typically generated by a data provider. Used to map data sources to jobs. |    | US - Tier 1 |
| Data Effective Date | Optional. `date` Date when the benchmark should be considered effective, typically referred to as the date when the data was generated. Used to age data sources. | MM/DD/YYYY | 01/15/2025 |
| Job Family | Optional. `string` Job family for the benchmark. Used for more readable manual benchmark lookups in Pave. |    | Software Engineering |
| Job Title | Optional. `string` Job title for the benchmark. Used for more readable manual benchmark lookups in Pave. |    | Senior Software Engineer |
| Job Ladder Track | Optional. `string`Job ladder track for the benchmark. Used for more readable manual benchmark lookups in Pave. |    | IC |
| Job Level | Optional. `string` Job level for the benchmark. Used for more readable manual benchmark lookups in Pave. |    | 4 |

### **Compensation properties**

There are numerous properties available for each supported pay type. Each property (aka column in the file upload) is formatted as: `{pay type} {property}`(ex: `Market Base 10th percentile`).

The supported pay types for survey uploads are:

| Pay type | Description |
|----|----|
| Market Base | Base pay for a job. |
| Market Total Cash | Total cash pay for a job, typically base + variable. |
| Market Variable | Variable pay for a job, typically bonus + commission. |
| Market Total Direct Comp | Total direct pay for a job, typically total cash + annual equity value. |
| Market Total Equity Value | Total equity value for a job, typically the summed value of all equity grants regardless of vesting and tenure. |
| Market New Hire Equity Value | New hire equity value for a job, typically the total equity value for new hires. |
| Market Annual Equity Value | Annual equity value for a job, typically the annualized value of equity grants. |
| Market Refresh Equity Value | Refresh equity value for a job, typically the value of refresh/ongoing equity grants given to tenured employees but not new hires. |

The supported properties for each pay type are:

| Property | Description |
|----|----|
| {pay type} Employee Count | Option. `number` Number of employee data points used to generate the benchmark. Used for weighting benchmarks by employee counts (i.e. [market weighting](https://support.pave.com/hc/en-us/articles/36341228718231)). |
| {pay type} Company Count | Optional. `number` Number of companies used to generate the benchmark. Used for weighting benchmarks by company counts. |
| {pay type} 10th percentile | Optional. `number`10th percentile of the pay type distribution generated by data provider. |
| {pay type} 25th percentile | Optional. `number`25th percentile of the pay type distribution generated by data provider. |
| {pay type} 40th percentile | Optional. `number`40th percentile of the pay type distribution generated by data provider. |
| {pay type} 50th percentile | Optional. `number`50th percentile of the pay type distribution generated by data provider. |
| {pay type} 60th percentile | Optional. `number`60th percentile of the pay type distribution generated by data provider. |
| {pay type} 65th percentile | Optional. `number`65th percentile of the pay type distribution generated by data provider. |
| {pay type} 75th percentile | Optional. `number`75th percentile of the pay type distribution generated by data provider. |
| {pay type} 90th percentile | Optional. `number`90th percentile of the pay type distribution generated by data provider. |
| {pay type} 95th percentile | Optional. `number`95th percentile of the pay type distribution generated by data provider. |


:::info
Note: The name of the column headers don’t need to match the tables above as you will be prompted to map your survey columns to the right property in Pave when you upload.

:::




Supported survey providers

Pay Types: Calculated TDC, Annual Equity, and Refresh Equity

Band Sets

Employee Distribution in Bands

Editing Bands

View changes

Upload/Download Bands

Unmatched Employees

Calculated Columns

Managing & Reordering Calculated Columns

How to duplicate band sets

Survey aging

Edit and apply benchmarks

Set weights and logic

Map data sources to jobs

Manage Pave data sources

Manage survey data sources

Benchmarks overview

Step 2: Benchmarking

Bands Set Audit Log

Manually Create New Band Sets

Job Architecture 101

Pay Zone Manager

Grades

Setting up Company Job Architecture

Company Job Architecture

Step 1: Build Foundation

Generate Bands from Market Data

Bulk & Manually Associate Market Data to Bands

Step 3: Update Ranges

Generate Bands for New Jobs in Your Job Architecture

Compare Bands

Relative Permissions

Advanced Filters

Ongoing Management & Analysis

Market Pricing

Market Data Connections Set up

Market Data Connections Overview

Integrations 101

Integrations

Adding Columns

Team View Overview

Team View Column Configuration

Team View Customizations

Re-ordering Columns

Deleting Columns

Team View Settings

Team View

Comp Planner Configurations Overview

Compensation Planner 101

Getting Started - Compensation Planner

Compensation Planner FAQs

Cycle Specific Permissions

Employee Eligibility

Step 1: Initial Cycle Setup

First-Class Columns

Using Handlebars Formula for Calculated Columns

Columns

Step 2: Column Configuration

OTE Planning Configuration Guide

What is OTE Planning?

Step 3: OTE Planning

Am I able to update or change approval chains during a cycle?

Updating Approval Chains

Compensation Cycle Data Upload

Step 4: Data Management

How can I configure market adjustment recommendations for employees?

How can I configure variable raise recommendations for employees?

Recommendation Logic

What are Recommendations?

Step 5: Recommendation Logic

Budgets

Budget Dashboard

Top Down Budgets: In-app Configurations

Step 6: Budget Confirmation

Planning Windows Setup Guide

Planning Windows Overview

Monthly & Hourly Pay

Employee Compensation History Popout

UI Toggles

Filtering & Sorting

Approval Statuses

Step 7: Planner Experience

Smart Flags

Compensation Outliers

Manager Compression Flag

Vesting Drop Flag

Step 8: Controls & Governance

Peers Overview

Cycle Outcomes

Value Rounding in Compensation Planning

In App Reward Letter Editor

Reward Letters

Peers Configuration Guide

Cycle Progress Dashboard Overview

Other Cycle Actions

 Compensation Planner

Logging In

Custom Role Creation Guide

Creating an Account

How to add a colleague to Pave’s Market Data Platform

Market Data Role Management

Why does it matter to get levels and role families right?

SSO Configuration Guide

Account Setup

Contact Us

How much does Pave Market Data access cost?

How does Pave Work?

Intro to Pave

Pave 101

Compensation Philosophy

Total Compensation

Compensation 101

The Stock Option Lifecycle

ISO Tax Implications

The Basics of Stock Options

The Confusing AMT (Alternative Minimum Tax)

ISO Strategies

An Overview of How Stock Options Work

Equity 101

Account Creation Troubleshooting and FAQs

How to Benchmark Executive Compensation

Login Troubleshooting and FAQ

How does company size affect which department, job family and job level I should choose?

How does Pave determine a role level and role family?

What are Job Levels, Departments and Job Families? Why are they important?

Troubleshooting Rippling Zero Records Error

What Market Data Connections does Pave currently support?

FAQs

Getting Started

Option Driver Deprecation FAQs

Option Driver

Option Impact Deprecation FAQs

Option Impact

Option Impact & Option Driver

Executive Reporting Dashboard

Cycle Monitoring and Reporting

Building Market-Based Compensation Bands

Employee Groups

Cycle Configuration

How does Recommendation Logic work?

Am I able to change another user’s permissions or login credentials while impersonating?

Supported survey providers

Share

Share

Supported survey providers

Share

Share