Skip to main content
Pre-onboarding Salary Bands checklist

Make sure you complete this checklist before the onboarding on salary bands with our customer success team.

Updated over a month ago

Prerequisites

☑️ Choose your methodology

Before we can onboard you into the module, you must choose between these two options and communicate this to your CSM before the onboarding call:

Import existing bands

You already have salary bands in place and want to import them. Please, send them to your dedicated Figures CSM before the onboarding call.

Create bands from scratch in Figures

While our team is here to help with the best setup, we can’t define your compensation strategy for you. It’s essential to come prepared with an idea of the appropriate band structure, aligned with your compensation philosophy. Mandatory:

  1. Have an established Compensation Policy

  2. Have an idea of your Salary bands structure (percentil, market positioning, level of seniority...)

Please, send those elements to your dedicated Figures CSM before the onboarding call.

☑️ Choose your sharing options

You'll be able to manage permissions and sharing options later, but it's helpful to have an idea of who you want to share your bands with beforehand.

To better understand the importance of sharing your bands and how to do it at your own pace, we recommend consulting our dedicated section.

☑️ Watch the module introduction video

Before your onboarding session with our Customer Success team, please watch this video. ⚠️ This step is mandatory to ensure we can provide the most valuable onboarding experience, as it requires some prior knowledge of our module.

Onboarding steps with Figures

Once you've completed the prerequisites and watched the video, you're ready for onboarding with our team. Here's what to expect during the onboarding process:

Training session #1 : Introduction to your strategy

This first meeting will be dedicated to:

  • Review your objectives

  • Understand your compensation policy and salary bands ideal structure

  • Make sure you have everything ready to create a first version of your bands

Create the first version of your salary bands

It's important to familiarize yourself with the module before the second training session so we can then focus on high-value actions. We ask that you create an initial version of your salary grids on your own, with our team's assistance if needed. We'll review and refine it together during training session #2.

  1. You will either import your salary bands or follow together our step by step guide on how to create your salary bands.

  2. Then your dedicated customer success manager will proceed to a verification.

  3. Finally, you will follow our step by step guide to Map your employee data. Mapping your employee data to your salary bands is essential to benefit from the right positioning in bands.

Training session #2 : Module tour based on your salary bands V1

This second meeting will be dedicated to:

  • Review together the first version of your salary bands

  • Answer potential questions and guide you through potential blurry zones

  • Make sure you have everything ready to manager your bands on a regular basis

Adjust your bands following the training session #2

On your side, make all the changes needed to ensure your salary bands are clean and ready to be share, step by step. Once ready, we can discuss about sharing your salary bands.

Share your salary bands

Salary bands are designed to be shared internally, and you can control the pace of that process. You might start by sharing with leadership, then gradually involve managers, and eventually the entire organization. Our tool allows you to manage permissions and adjust access as you’re ready to expand visibility.

To support stakeholder engagement in the salary bands process, we’ve created an Internal Communication Kit with tailored messaging for different levels of your organization. For more details on sharing salary bands, please refer to our dedicated section.

Congratulations, you're ready to be onboarded on Salary Bands! 🥳

Did this answer your question?