---
title: "[Legacy] Manually Create New Band Sets"
description: "When manually creating a new band set, you must first define which HRIS fields you'll be using to match employees to Bands within Pave and your company’s pay types. Once the band set is configured, Pave will generate a CSV template you can fill out with your bands, and you can then re-upload the completed CSV into the band set."
canonical_url: "https://support.pave.com/articles/legacy-manually-create-new-band-sets-4bg7UAWXIC"
md_url: "https://support.pave.com/articles/legacy-manually-create-new-band-sets-4bg7UAWXIC.md"
---
# [Legacy] Manually Create New Band Sets

When manually creating a new band set, you must first define which HRIS fields you'll be using to match employees to Bands within Pave and your company’s pay types. Once the band set is configured, Pave will generate a CSV template you can fill out with your bands, and you can then re-upload the completed CSV into the band set. 

### Steps:


1. Click on the **Market Pricing** button in the left tool bar. ![](https://support.pave.com/api/attachments.redirect?id=428c4665-2d4a-4bd2-bd59-ee6366346a03) 
2. Click **Import existing compensation bands:** ![](https://support.pave.com/api/attachments.redirect?id=80fe41b2-2c01-40f6-a21c-ea5ace43ba28) 
3. Choose the compensation types. You 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: ![](https://support.pave.com/api/attachments.redirect?id=776526f9-b8bd-4195-af31-3758aff2c121) 

   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)

   ### Location-Based Pay:

   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.
4. Name the Band Set and generate the CSV: ![](https://support.pave.com/api/attachments.redirect?id=c83eea6b-99e7-4d0f-a475-45b0f17997b7) 
5. Download your Pave generated CSV template:  ![](https://support.pave.com/api/attachments.redirect?id=6e3122a5-0166-4e7e-aac2-8bf605158427) 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.
6. Once the CSV Band template has been filled out, re-upload the completed CSV into the band set within Pave: ![](https://support.pave.com/api/attachments.redirect?id=bf91698f-34e0-4796-b4ad-0de89a5453ca) 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.

   ### Job Identifiers

   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: ![](https://support.pave.com/api/attachments.redirect?id=5792ebfb-fd92-44b0-8523-728af4269b85)

    ![](https://support.pave.com/api/attachments.redirect?id=0a50792a-a516-4b89-84da-c655fa60c957)

 7. Fix any errors that you may encounter. Please contact our Support team at [support@pave.com](mailto:support@pave.com) if you have any questions!