--- title: "Add Bands (In App or Upload)" description: "Add bands creates new rows in your band set for jobs across one or more pay zones. This is where you add new jobs and pay zones to your band set, in app or via upload." canonical_url: "https://support.pave.com/articles/add-bands-in-app-or-upload-0KpWduemgx" md_url: "https://support.pave.com/articles/add-bands-in-app-or-upload-0KpWduemgx.md" --- # Add Bands (In App or Upload) Add bands creates new rows in your band set for jobs across one or more pay zones. This is where you add new jobs and pay zones to your band set, in app or via upload. --- ## Table of Contents 1. What is Adding Bands? 2. Adding Bands in the App 3. Uploading Bands 4. What Happens After Adding Bands 5. Related Articles --- ## What is Adding Bands? **Adding bands** creates new rows in your band set grid for jobs you want to price. The add bands flow allows you to: * **Add new pay zones** - Create pay zones that don’t exist yet (click “+ Add” in pay zones selector) and activate all or some jobs in that pay zone * **Add new jobs** - Create jobs that don’t exist in your job architecture yet and activate those jobs in some or all pay zones **What you’re creating:** * New rows in the Bands tab * Empty band values (min/mid/max start blank) * Jobs activated in selected pay zones --- ## In App or Upload? | | In the app | Upload a CSV | |:---|:---|:---| | Best for | • Adding a few new families or ladders \n• Activating all or some existing jobs in new pay zones | Hundreds of bands | | Band values | Start blank, priced later | Set in the same step | | Updating existing band values | No | Yes | | Building a new ladder | Yes, with live employee match counts | Yes, but without the guardrails | --- ## Entry Points There are multiple ways to access the add bands flow: **From Bands tab:** 1. Open your band set 2. Go to **Bands** tab 3. Click **Add bands** button (top right) **From a specific ladder:** 1. Find the ladder in your band set 2. Click the **+** button on the ladder row All fields are pre-filled, you can add levels to that ladder in that pay zone, or add to other pay zones. **To upload instead:** 1. Open your band set 2. Click the upload icon in the toolbar --- ## Adding Bands in the App ### Step 1: Select Pay Zones Choose which pay zones to add jobs to. Pay zones apply to every job you add in this session, so they sit at the top of the flow. **Pay zones field:** * Type or click to see list of existing pay zones * Select multiple pay zones (e.g., Brazil, India, London, Spain, United States - Tier 1) * Selected pay zones appear as tags in the field * Click **X** on a tag to remove it **Add new pay zone:** * Type the new pay zone and click “+Add” at the bottom of the pay zone list, you can add multiple new pay zones at once. * This creates a new pay zone that will be added to your band set * You can configure the new pay zone details later in the Pay zones tab ![CleanShot 2026-07-31 at 15.51.33.gif](https://support.pave.com/api/attachments.redirect?id=eeb8846e-5567-4cd0-9ca0-674af5b73678 " =800x556") ### Step 2: Select Job Hierarchy Choose jobs using the job architecture hierarchy. Each field appears only once the field above it has a value, and changing a field higher up clears everything below it. **Job function** * Select from dropdown (e.g., Engineering, Revenue, Product & Design), or type a new name to create one **Job family** * Select family within the function (e.g., Account Management, Data Engineering), or type a new name to create one **Track** * Select from Pave’s six tracks: Support, IC, Professional, L, Manager, or Executive **Job ladder** * Shows the ladder within the family (e.g., Account Management - IC, Data Engineering - IC), or type a new name to create one Every option shows how many jobs it already contains, so you can tell an established family from a new one. Two rules Pave enforces as you go: a ladder can belong to only one family, and a ladder can belong to only one track. ### Step 3: Review Job Levels * Pave shows the levels in the ladder you selected, ordered lowest to highest rank. Bands are created for every level in the ladder. * Rank determines the order bands are displayed in the band set, their midpoint progression, and user permissions * Each level shows where it stands against the pay zones you selected: which zones it will be **added to**, and which zones it is **already added to**. * You can edit a level, reorder levels, or add a new one from here. See Working with Job Levels. ### Step 4: Review and Add 1. Review your selections 2. Click **Add bands** button (bottom right) **Result:** * New rows appear in your Bands tab * One row per job × pay zone combination * Band values start empty (ready to be priced) --- ## Adding Several Families at Once In the Add Bands flow, click **Select another job** to queue up another one in the same session. From the second job onward you work against an overview: * Your pay zones sit at the top and apply to every job in the list * Each job below shows its function, family, track, and ladder, with its levels beneath * Click the pencil icon on a job to edit it, or **+ Select jobs** to add another * Click **Add bands** to create bands for everything in the list --- ## Filling Gaps in Job Architecture Each job field also offers an “All” option when there’s more than one thing to choose from: **All Pay zones, All functions**, **All families**, **All tracks**, and **All ladders**. **An All selection only creates bands for jobs that already exist.** Use it to give existing jobs bands in pay zones where they don’t have one yet. **When to use it:** * A company with an established Engineering family in their US pay zone opens an India office. Selecting the India pay zone and All functions creates bands for every job they already price, in the new zone, without rebuilding any ladders. * A company is building out a new AI Engineering family in all pay zones. Selecting All pay zones and adding new AI Engineering family will create that family in all pay zones. --- ## Working with Job Levels ### Adding a Level Click **Add** at the bottom of the level list. A new level needs: * **Job level** - Required, and unique within the ladder * **Job title** - Optional * **HRIS matchers** - At least one is required **HRIS matchers** tell Pave which employees belong to the job. The fields you see depend on how your band set matches employees: | Band set matching | Fields shown | |:---|:---| | HRIS family + HRIS level | HRIS family, HRIS level | | HRIS title + HRIS level | HRIS title, HRIS level | | HRIS title | HRIS title | | HRIS job code | HRIS job code | Click **Add HRIS matcher** to add more than one, for when the same job goes by different names or codes in your HRIS. As you fill in a matcher, Pave shows a running count, e.g. “12 employees found”. That count is the number of **active** employees whose HRIS fields match what you typed **and who aren’t already matched to a band in this band set**. A zero can mean the values don’t match anyone, or that the people you expected are already matched elsewhere. Matcher combinations must be unique across the whole band set, not just within the ladder. If another job already uses the combination you entered, Pave names that level so you can find the conflict. New levels are added at the end of the list with the next rank up from the highest one already there. Existing ranks are left alone, including gaps, so a ladder that starts at rank 4 stays that way. ### Reordering Levels Drag levels to reorder them when there’s more than one. Pave redistributes the ladder’s existing rank values across the new order rather than renumbering from 1. Note: This will impact permissions. ### Pre-Populating a New Ladder When a ladder has no levels yet and you already have a comparable ladder on the same track, Pave offers to build the structure for you: * **Pre-populate with common job levels** - Fills in a suggested structure of levels and ranks, copied from your most-populated ladder on that track. HRIS matchers are deliberately left empty, so you add those per level. * **Create levels manually** - Start from a blank level form instead ### Editing Levels Affects All Bands Levels are shared across pay zones. Editing the order, rank, title, or HRIS matchers of a level will affect all bands that use it, including bands in pay zones you didn’t select. --- ## Uploading Bands Uploading adds or changes many bands at once. You answer a few questions about what you’re uploading, Pave generates a CSV template with only the columns you need, and you upload the completed file. **Note:** This is not the same as the upload used when first creating a band set. This flow is built for adding to and updating a band set you already have. ### What an Upload Does Not Do Uploads add and update. They never delete, rename, or move anything. | You want to | Where it happens | |:---|:---| | Delete bands | Bands tab (see **Delete Bands**) | | Rename or move a job | Jobs tab (see **Manage & Edit Jobs**) | | Rename a grade or grade group | Grade panel (see **Manage & Edit Grade Structure**) | | Rename a pay zone | Pay zones tab (see **Manage Pay Zones**) | ### Step 1: Choose What You’re Uploading Click the upload icon in your band set. The first screen is **Start with a template**, which asks what you’d like to upload (you can select more than one). | Option | What it does | |:---|:---| | **New bands** | Blank template for bands that don’t exist yet | | **Updates to existing band values** | Includes the bandID column and exports your current data so you can edit values in place | | **Job associations to grades** | Adds the grade columns so you can group jobs into grades | Grades-based band sets see a different set of options. See **Manage & Edit Grade Structure**. Then choose one of: * **Download template and continue** - Builds your template and moves you to the upload step. Disabled until you check at least one option. * **Skip to upload** - Goes straight to the upload step. Use this when you already have a correctly formatted file. **How your template arrives:** * **Creating only new bands:** You get a blank headers-only template, and it downloads right away. * **Any of the “Updates to” options:** Pave exports your current band data in the same shape you can re-upload. ![CleanShot 2026-07-31 at 15.58.25.gif](https://support.pave.com/api/attachments.redirect?id=840e84ee-bcf5-4ac2-b659-9a5a47dededc " =800x451") ### Step 2: Upload Your File The second screen is **Upload bands**. It opens with a **How to use the template** panel listing instructions matched to what you selected in step 1, then the file upload itself. ### Required Columns For rows creating something new: function, ladder, track, rank, family, level, pay zone, and currency, plus the HRIS columns for your band set’s matching configuration. Optional: title, description, bandID (if new bands, leave blank), and the min/mid/max columns for each of your enabled pay types. ### When Something Is Wrong with Your File If any row fails a check, you’re notified that the upload couldn’t be completed, with a link to download an error report. The error report is your own file handed back with **Error** and **Warning** columns added, so you can see exactly which row and which cell is the problem. Row numbers count the header as row 1. Fix the flagged cells and start the upload again. **Common things the report flags:** * A required column missing from the file, or a column that doesn’t belong to this band set’s configuration * A required value missing on a row that’s creating something new * A track that isn’t one of Pave’s tracks, or a rank that isn’t a number * A currency code that isn’t a valid code * Pay values that aren’t numeric, or a minimum above a midpoint or maximum * A bandID that isn’t valid, or that doesn’t exist in this band set * Two rows describing the same band, or the same HRIS values pointing at two different jobs * A job title or currency that’s inconsistent across rows that should agree * A ladder appearing under more than one family or more than one track When the upload finishes cleanly, you’re notified that the band set is ready to view. --- ## How Uploaded Rows Are Matched This determines whether a row updates something or creates something new. ### Rows with a bandID **Matched on that ID alone.** Pave finds the exact band the ID points to and applies your value changes to it. Every other column on that row is ignored, including function, family, ladder, level, title, and pay zone. ### Rows with a blank bandID **Matched on job function, job family, job ladder, track, and rank, plus the pay zone.** If a job with that exact combination already exists, the row attaches to it. If nothing matches, Pave creates a new job and a new band. Level and title are deliberately not part of the match, so a row that changes only the level name attaches to the existing job and the new level name isn’t applied. ### What This Means in Practice ``` Goal: change base pay on 50 existing bands Do: select "Updates to existing band values", edit the exported file, keep bandID populated Goal: add a new ladder Do: leave bandID blank, fill in function/family/track/ladder/level/rank and the HRIS matcher columns Goal: move a job to a different ladder Don't: change the ladder column. That creates a SECOND job and a second band, and the original stays where it was. Move it on the Jobs tab. ``` Pay zone names are matched without regard to capitalization, so “US” and “us” are treated as the same pay zone. --- ## What Happens After Adding Bands ### Immediate Results **Bands tab:** * New rows appear for new job × pay zone combination * Bands created by upload show whatever values you supplied. **Jobs tab:** * If you created new jobs, they now appear in the Jobs view * Jobs are organized in the function/family/ladder hierarchy **Pay zones tab:** * If you created new pay zones, they now appear in the Pay zones view * You can edit them to configure HRIS matching and differentials ### Next Steps in the Pricing Workflow After adding bands, complete the pricing workflow: 1. **Configure market data mappings** (if not already done) * Map job families to survey taxonomies * See **Job Mapping** article 2. **Apply data rules** * Associate jobs with data rule configurations * Pave pulls benchmark data based on rules * See **Data Rules** article 3. **Review benchmarks** * Validate benchmark values loaded correctly * See **Reviewing Benchmarks** article 4. **Set band ranges** * Use benchmarks to define min/mid/max values * Apply bulk edits or enter values manually * See **Edit Bands** articles **For the complete end-to-end workflow, see the Price New Jobs article.** --- ## Grades-Based Band Sets The in-app flow works the same way, with these differences: * It’s called **Add jobs**, and the panel explains that you assign the jobs to grades after adding them * The jobs you create start without a grade * The confirmation links you to the jobs that have no grade yet For assigning jobs to grades, creating grades, and uploading job to grade associations, see **Manage & Edit Grade Structure**. ---