Table of Contents

• What is Band Manager?
• Bands Manager and Band Sets
• Compensation Bands
• Band Set Configuration
• Job Identifiers
• HRIS Employee Matchers
• Pay Types
• Generating CSV
• Uploading Bands to the Band Set
• Hidden Fields on Bands Manager
• Editing Bands
• Troubleshooting Upload errors
  • Download a CSV with Errors
• Publishing Band Sets to Merit Cycles or Live Set
• Duplicating Band Sets
• Chart View

What is Band Manager?

Pave’s Band Manager allows customers to store, edit and share compensation bands across their company. Compensation bands are the foundational data resource used to make compensation decisions within a company - from how much to offer a new employee hired into a specific job and location, to how to adjust employee compensation during a merit cycle.

Bands Manager and Band Sets

The Bands Manager enables customers to view and edit “band sets”, which represent a set of bands that are used within products across the Pave app - Compensation Planning, Team View, and Total Rewards.

There are 3 types of band sets:

1. The “Live” Band Set - This is used in Team View and Total Rewards
2. Merit Cycle Band Sets - Each of these is assigned to a specific merit cycle
3. Draft Band Sets - These are sets that have are not designated as Live or associated with a merit cycle yet. Draft band sets can be “published” to “Live” or a “Merit Cycle” set

A Pave customer can upload and manage multiple band sets. Every merit cycle within the Plan product has its own band set. To generate a band set for a merit cycle, admins must:

1. Create a draft band set
2. Publish that draft to the appropriate merit cycle

This merit cycle band set will then appear under the merit cycle list in Bands Manager.

Maintaining multiple band sets in Pave allows a company to run a merit cycle with an updated set of bands, while continuing to use and communicate an existing band set within their company until the merit cycle is complete.

Admins can also workshop draft band sets without impacting any products.

Compensation Bands

Compensation bands are defined by a uniquejob, with an option to also group by geolocation (payzone). Each band contains compensation ranges for the employees matching to this job.

Every compensation band is assigned to a single job. When uploading a Band Set CSV, the corresponding job is identified in the same row.

• Job identifiers include: function, ladder, and ladder rank
• Here’s an example of a unique job:
• Function Engineering
• Ladder Engineering Management
• Ladder Rank 3

• A company may optionally use location-based pay practices, in which case each band must also include a payzone. When using payzone bands must be unique across Function, Ladder, Ladder Rank, and Payzone. For example, these are two unique bands:
  • Function Product Design, Ladder Product Designer, Ladder Rank 3, Payzone Tier 1
  • Function Product Design, Ladder Product Designer, Ladder Rank 3, Payzone Tier 2
• Compensation bands typically include a base pay range (min + max, and/or target) and may often include variable pay, total pay, and equity ranges as well.

HRIS Matchers

Pave also requires that companies provide HRIS fields to match employees to their corresponding job (and therefore band) in Pave. The following combinations are accepted:

• Family and Level (e.g. Engineering, P4)
• Title and Level (e.g. Software Engineer, P5)
• Title (e.g. Senior Software Engineer)
• Job Code (e.g. SWE-13A)

If a company uses location-based pay practices, Pave will use the metro field in the HRIS to match employees to their corresponding payzone (and therefore band). Companies may often define metro with cities or tiers.

These fields will have the “HRIS-” prefix on your bands to represent that they are coming from the HRIS and are only used to match employees to a band

Below you can see an example set of bands and their corresponding jobs in the Band Manager:

Note: Customers who have compensation bands pre-October 2022 may see legacy band sets without required job identifiers. These band sets are marked with a legacy tag in the app.

Below you can see an example legacy Live set in the Band Manager. These sets do not include the new job architecture fields and thus have limited functionality around permissions, filtering, and sharing.

Band Set Configuration

When setting up a new band set, customers must first define which HRIS fields they’ll be using to match employees to Bands within Pave and the company’s pay types. Once the band set is configured, Pave will generate a CSV template for the customer to fill out with bands and re-upload into the Band Set.

To create a new band set, click on the “Create Draft” button.

Rename the band set by hovering over the title and clicking the Pencil icon. Then, follow instructions to set up the Band Set Configuration.

Job Identifiers

In the first step, customers will be able to preview the fields Pave requires for each job and its corresponding band. You can view these required fields here by expanding the table preview.

For each row in the uploaded CSV, the combination of Function - Ladder - Ladder Rank - Payzone (payzone only if using location-based pay) must be unique as each job should have its own unique set of identifiers.

HRIS Employee Matchers

Next, define the fields in the HRIS that map to the concept of a unique job. The following combinations are allowed.

• Family and Level (e.g. Engineering, P4)
• Title and Level (e.g. Software Engineer, P5)
• Title (e.g. Senior Software Engineer)
• Job Code (e.g. SWE-13A)

Admins then need to select whether or not the company uses location-based pay. If a company uses location-based pay practices, Pave will use the metro field in the HRIS to match employees to their corresponding job (and its band). Companies may often define metro with cities or tiers.

Additionally, if a company selects that they use location-based pay, the CSV will be populated with the Payzone column. This payzone column can be filled with the same values as the metro field if desired, and can be used to set granular access controls. For example, a recruiter for the SF office may have permissions set to only view Software Engineering bands in Payzone: San Francisco.

Once an option is selected, the table preview on the right will populate with values found in the company’s HRIS for that specific field(s). For example, if Title and Level is selected, all unique title and level combinations from your HRIS will be pre-populated in the CSV. This allows the admin to easily fill out the CSV with all the bands for each job and ensure all employees have a matching job (and Band) in Pave.

If no values are populated for a selected option, either the integration isn’t connected or values do not exist for those fields in the HRIS.

Only Band Admins will be able to view the HRIS matchers in the Band Manager once the CSV is successfully uploaded. Users with the Band Viewer permission will only be able to view the required job identifier fields and relevant pay ranges on the band.

Pay Types

Next, admins must select the compensation pay types defined on the band. A band set can have multiple pay types, but cannot only have equity shares selected.

Generating CSV

Finally, download the custom CSV template and fill it out before re-uploading to the band set.

The Band Set Configurations can be modified before the CSV is uploaded. This may be the case if an admin realizes they use only base pay min and max rather than base pay min, target and max, for example.

Uploading Bands to the Band Set

In a separate CSV editor, add the required values for each row in the generated CSV.

As a reminder, each row must have a distinct combination of Function, Ladder, and Ladder Rank (and Payzone, if using location-based pay) as well as distinct HRIS fields.

A CSV upload that does not contain the exact columns checked in the Band Set Configuration will need to be re-uploaded.

Once a CSV is successfully uploaded to the band set, the Band Admin will be able to edit, publish and share the band set.

Hidden Fields on Bands Manager

Bands Admins can determine the columns that are visible in the Bands Manager for Bands Viewers.

Common examples why Bands Admins would utilize this feature are:

• To align columns to fields that Bands Viewers are familiar with such as family and level
• HRIS job matchers are not relevant to people managers or recruiters

Band Admins will have the ability to toggle between hiding and unhiding the columns using the “Show Hidden Columns”/“Hide Hidden Columns” button.

This allows Bands Admins to replicate Bands Viewers’ column visibility.

To configure which columns that should be hidden from Bands Viewers, a Bands Admin clicks on the “Settings” button for a given Compensation Band Set.

Pave defaults to hiding HRIS matchersFamily , Level , and Metrofor Bands Viewers.

A Bands Admin can selectively choose which columns should be hidden from Bands Viewers by selecting the corresponding toggle on.

• Please note: toggling a Hidden Field “on” hides it from a Bands Viewer’s visibility rather than enabling it.

Bands Hidden Fields settings are specific for a given Compensation Band Set. This granularity allows admins to unhide columns for newer sets as Bands Viewers gain familiarity with Pave’s Job Architecture or hide columns as the number of active Bands Viewers increases.

Editing Bands

Once a CSV has been uploaded, admins can continue to make edits to band values in the Band Manager.

Editing In-Line

To make one-off changes to the values within a band, click the Edit button above the table to start editing band values.

Values can be edited for any pay type. Simply clear a field to remove a value, or add to an empty field to add a value.

The app will highlight any errors in red. Hover over the error icon to understand the error and then resolve it before continuing.

After clicking “Review Changes”, a change log will appear where all changes can be reviewed and directly reverted if needed. Then, to confirm the changes, click Save Changes.

Those changes will then immediately be reflected in either the associated merit cycle or in Total Rewards and Team View.

Deleting Bands

To delete a band, click “Edit” and select the bands you’d like to delete via the checkboxes on the left hand side of the row. You can then click “Delete”.

You can then click “Review Changes” to review your deleted bands before saving changes by clicking “Save Changes.”

Re-Uploading the Band Set

The admin will need to upload a new CSV to replace the current band set to perform the following modifications:

• Add new bands
• Change a large amount of bands in which case in-line editing becomes too cumbersome
• Apply a formula to all bands
• Edit the job identifiers or HRIS fields

To do so:

1. Download the CSV.
2. Perform the necessary updates in the downloaded CSV without changing any column names.
3. Save the changes
4. Click “Upload CSV” in the band set
5. Resolve errors if they exist
6. Upload CSV successfully

Troubleshooting Upload errors

Any errors will block upload of bands. There are two types of errors customers can encounter:

• Duplicate Band Errors
• Invalid Band Value Errors

Download a CSV with Errors

After an unsuccessful upload due to errors, Bands Admins can now download a CSV with all bands with an additional “errors” column that indicates the errors for each failed band.

The CSV Row Number is surfaced in the error preview page to be referenced quickly for small or easily identified errors.

All applicable errors will be noted on a given band in the CSV Download. Please reference the below documentation on exact Bands Errors and most efficient paths to resolution in sections “Duplicate Band Errors” and Invalid Band Value Errors”.

Once the errors are resolved, the same CSV can be re-uploaded with the additional “errors” column. You do not need to remove the “errors” column. This information will be filtered out upon successful upload.

There may often be cases where an upload will have multiple errors. In that situation, here is the order in which to resolve the errors.

Order of Operations:

1. Solve any missing field/extra field errors.
   1. First ensure that you are uploading bands with the correct columns. For ex: any missing columns must be inputted.
2. Solve duplicate bands errors
   1. Duplicate bands errors will cause other errors.
   2. It’s often the case that solving duplicate band errors will also get rid of all the additional errors related to job architecture and matchers
3. Solve all other errors.

Duplicate Band Errors

Duplicate Bands Errors

**Duplicate Bands Detected**

When does this happen?

• This error occurs when there are duplicate (non-unique) job architecture combinations
• The combination of Function - Ladder - Ladder Rank or Function - Ladder - Ladder Rank - Payzone (if location-based pay) must be unique for every band
• These fields are how we define a unique job and every unique job should only have one band

How to resolve?

• To resolve, one of the bands needs to be removed or updated
  • If the bands are exactly the same → delete one of them
  • If one of the bands has different pay values → confirm which band has the correct values and delete the other one

NOTE: Always resolve this error before any other job architecture errors. This error may be the cause behind the other job arch-related errors below.

Jobs and HRIS job matcher errors

You will see two different types of errors for this:

• Jobs without Unique HRIS Job Matchers
• HRIS job matcher combos matching to multiple jobs

Rules:

• Non-payzone job architecture fields (Function - Ladder - Ladder Rank) must always match to the same HRIS job matcher(s)
• HRIS job matcher(s) must always match to the same “role”

Causes:

• When you have the same HRIS job matcher(s) on multiple bands with different combinations of Function - Ladder - Ladder Rank
• When you have multiple bands with the same combination of Function - Ladder - Ladder Rank on multiple bands but not the same HRIS job matcher(s) on each of these bands

Examples:

• Jobs without Unique HRIS Job Matchers

Function	Ladder	Ladder Rank	Payzone	HRIS Job Code	HRIS Metro
Engineering	Software Engineer	3	NYC	SWE3	NYC
Engineering	Software Engineer	3	Austin	SWE4	Austin

There’s an error here because these bands have the same Function - Ladder - Ladder Rank but different HRIS Job Codes

• HRIS job matcher combos matching to multiple jobs

Function	Ladder	Ladder Rank	Payzone	HRIS Job Code	HRIS Metro
Engineering	Engineering Manager	3	NYC	SWE3	NYC
Engineering	Software Engineer	3	Austin	SWE3	Austin

There’s an error here because these bands have the same HRIS Job Codes, but different combinations of Function - Ladder - Ladder Rank

This chart shows which fields need to be one to one with each other

Payzone and HRIS location matcher errors

You will see two different types of errors for this:

• Payzone matching to multiple hris location matcher combos
• HRIS location matcher combos matching to multiple payzones

Rules:

• Payzone must always match to the same HRIS Metro
• HRIS Metro must always match to the same Payzone

Causes:

• When you have the same HRIS Metro on multiple bands with differentPayzones
• When you have the same Payzone on multiple bands with differentHRIS Metros

Examples:

• Payzone matching to multiple hris location matcher combos

Function	Ladder	Ladder Rank	Payzone	HRIS Job Code	HRIS Metro
Engineering	Engineering Manager	3	NYC	SWE3	NYC
Engineering	Software Engineer	3	NYC	SWE3	New York City

There’s an error here because these bands have the same Payzone but different HRIS Metros

• Payzone matching to multiple hris location matcher combos

Function	Ladder	Ladder Rank	Payzone	HRIS Job Code	HRIS Metro
Engineering	Engineering Manager	3	NYC	SWE3	NYC
Engineering	Software Engineer	3	New York City	SWE3	NYC

There’s an error here because these bands have the same HRIS Metros but different Payzones

This chart shows which fields need to be one to one with each other

Invalid Band Value Errors

• Invalid max value for {pay type} , Invalid min value for {pay type}
  • What does this mean? → If a min value exists for a pay type then there must also be a max (and vice versa)
  • Example →
    • Band = basePayMin: 100000, basePayTarget: 125000
    • This band has a min value but not a max! To resolve, just add a max → basePayMax: 150000
• Min must be less than or equal to target for {pay type}
  • What does this mean? → The min value on the band cannot be greater than the target. You will see this error if it is.
  • Example →
    • Band = basePayMin: 100000, basePayTarget: 90000, basePayMax: 150000
    • The min value of this band is greater than the target! To resolve, update either the min or the target → basePayTarget: 125000
• Min must be less than max for {pay type}
  • This is the same concept as the error above
• Target must be less than or equal to max for {pay type}
  • This is the same concept as the error above
• Target variable pay percent must be a number
  • What does this mean → The targetVariablePayPercent column must be a number. You will see this error if it’s not!
  • Example →
    • Band = targetVariablePayPercent: 20%
    • This is a string, not a number (you can tell because there is the % symbol in it!). To resolve, update to → targetVariablePayPercent: .2
• Target must be a number or valid currency value for {pay type}
  • What does this mean → Pay values must always be numbers or currency values (formatted in US Currency format X,XXX,XXX.YY) with any currency symbol
    • Valid values: $10,000, €10000, ¥10,000.00, 10,000, 10000
    • Invalid values: 10k, Ten Thousand Dollars, 10.000,00
• Ladder rank value must be a whole number greater than 0
  • Rank must be a whole number greater than 0 (eg. 2.5 is invalid)

Publishing Band Sets to Merit Cycles or Live Set

To publish a draft, click on “Publish” in the upper right-hand corner of the band set page. To publish a draft, all values must be valid. If there are errors that block publish, Admins will see errors listed and will need to edit those errors before publishing.

Once any errors are resolved, Admins can select whether they want to publish this draft to the Live set or to a Merit Cycle.

Selecting Merit Cycle will display a dropdown that contains all merit cycles:

Publishing the band set to a Live set or Merit Cycle where a band set already exists will archive the existing band set and replace it with the current version.

Duplicating Band Sets

Often times, an Admin may choose to duplicate an existing set when creating a new version of bands and edit from that draft rather than create a brand new band set from a scratch. This may preferred when only a handful of edits need to be made to the new set that could be used for a future Merit Cycle.

Duplicating the band set will also duplicate the band set configs. This means that any CSV re-upload will need to conform to the same columns selected in the original band set’s configurations. For example, if the duplicated band set had Equity Value Target but not Equity Value Min or Max, any new CSV upload into this duplicated set will only allow Equity Value Target.

Note: Legacy band sets cannot be duplicated. Admins will need to create a new draft and configure the band set with the required job identifiers. They will then need to merge the legacy set’s band values into the generated CSV.

Chart View

In addition to viewing all bands in a table, users can drill down to see bands in the Chart View. This is accessed via the “View” button above the Band Manager table. This view displays bands for a single ladder in a given payzone. Users can select which pay type they want displayed (e.g Base Pay or Total Pay). Bands are plotted on the same chart and scale and sorted to visualize the progression between levels.