## **Overview**

The Manager Compression Flag identifies situations where a manager's compensation is less than or dangerously close to their direct reports' pay. This flag is essential for maintaining healthy organizational hierarchies and manager credibility during merit cycles by:

* **Preserving leadership authority**: Ensure managers maintain appropriate compensation differentials that reflect their broader responsibilities
* **Preventing retention risks**: Surface compression issues before they lead to manager dissatisfaction or turnover
* **Guiding promotion decisions**: Identify when promoting high performers might create compression problems
* **Informing merit allocation**: Help managers understand when they need meaningful increases to maintain appropriate gaps with their teams

## **Understanding Manager Compression**

Manager compensation compression occurs when the pay gap between a manager and their direct reports becomes too narrow. This can happen through several common scenarios:

* High-performing individual contributors receive substantial raises over time, approaching their manager's salary
* New hires are brought in at market rates that exceed or nearly match their manager's pay
* Managers are promoted without sufficient salary adjustments to reflect their new scope
* Market rate increases for technical roles outpace increases for management roles

Left unaddressed, compression can undermine manager effectiveness, create awkward team dynamics, and increase the risk of losing valuable leaders.

## **How It Works**

The Manager Compression Flag uses a straightforward comparison approach:


1. **Identifies manager-report relationships** in your organizational structure
2. **Compares the manager's compensation** to each of their direct reports' compensation
3. **Flags the manager** when any direct report's pay falls within the threshold you define

### **What the Flag Detects**

The flag triggers when **at least one direct report's compensation is within X% (or $X) of the manager's compensation**, where X is the threshold you set.

**Example**: If you set a 10% threshold and select New Base Salary:

* Manager's new base salary: $150,000
* Direct report's new base salary: $138,000 (92% of manager's salary)
* **Result**: Manager is flagged because the direct report is within 10% of the manager's compensation

## **Important Considerations**

**The flag evaluates each direct report individually**: If a manager has five direct reports and only one is within the compression threshold, the manager will be flagged. You'll need to review the team composition to understand which relationship(s) are creating the compression concern.

**Compression thresholds vary by organization and level**: A 10% gap might be appropriate for a manager with highly skilled senior individual contributors, while a 20-25% gap might be more appropriate for directors managing managers. Consider your organizational norms and career ladders when setting thresholds.

**Not all compression is problematic**: In some cases, especially with highly specialized individual contributors or technical fellows, narrow pay gaps may be intentional and appropriate to your compensation philosophy.

## **Configuration Guide**

 ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001gA5&feoid=00NUn00000C06g9&refid=0EMTV00000EngxJ)

### **1. Name Your Flag**

Use a clear name like "Manager compression" or "Manager-report pay gap" that immediately conveys the issue being flagged.

### **2. Add a Description**

Write a description that helps planners understand what's being flagged. For example:

* "Manager salary is lower than one of their reports"
* "Manager's pay is within 10% of a direct report"
* "Flags managers with insufficient compensation differential from their team"

### **3. Choose a Color**

Select a color for easy identification. Consider using:

* **Yellow or orange** for moderate compression requiring attention
* **Red** for critical compression issues requiring immediate action
* **Light green** for standard review items

### **4. Set Visibility**

By default, the flag appears in both the Smart Flags column and worksheet filters. Check "Hide from Smart Flags column and only show in worksheet filters" if you prefer the flag to be visible only when actively filtering, not as a persistent indicator.

## **Setting Up Conditions**

### **Step 1: Select a Compensation Component**

Choose which compensation element to compare between managers and their direct reports. Common options include:

* **New Base Salary** (most common - reflects post-merit cycle compensation)
* **Current Base Salary** (useful for identifying existing compression before planning)
* **Salary Raise** (identifies when a direct report's increase will create or worsen compression)
* **Total Cash Compensation** (includes bonuses and variable pay)

**Recommendation**: Start with New Base Salary to understand where compression will exist after your merit cycle. You can create additional flags using Current Base Salary to identify existing issues or Salary Raise to catch compression-creating increases.

### **Step 2: Set the Compression Threshold**

Define how close a direct report's compensation can be to their manager's before triggering the flag:

**Threshold amount**: Enter a numeric value (e.g., 10)

**Unit**: Choose between:

* **% percent** (recommended) - creates proportional thresholds that scale with compensation levels
* **$ dollar** - creates fixed dollar gap requirements regardless of compensation level

**How to read the threshold**: "Where a manager's direct report's compensation is within \[10\] \[%\] of manager's compensation"

This means: If a direct report's compensation is 90% or more of the manager's compensation (within 10% of the manager's pay), the flag will appear on the manager's record.

### **Choosing the Right Threshold**

Your threshold should reflect your organization's compensation philosophy and career architecture:

**10-15% threshold**: Appropriate for:

* Managers of highly skilled senior individual contributors
* Technical organizations where IC and management tracks have similar pay scales
* Flat organizational structures

**15-20% threshold**: Appropriate for:

* Traditional management hierarchies
* Organizations with clear pay differentiation between levels
* Managers of mid-career professionals

**20-25%+ threshold**: Appropriate for:

* Senior leaders managing directors or senior managers
* Organizations with steep hierarchical pay curves
* Executive-level compression monitoring

**Consider multiple flags**: Organizations sometimes create multiple Manager Compression flags with different thresholds (e.g., one at 10% marked yellow for "monitor," one at 5% marked red for "critical") to create tiered alerts.

### **Step 3: Add Additional Filters (Optional)**

By default, the flag analyzes all manager-report relationships in your organization. Use additional filters to narrow the analysis to specific populations:

**When to use filters**:

* Reviewing compression in a specific department undergoing restructuring
* Analyzing only senior leadership levels (e.g., Director and above)
* Focusing on a particular location or business unit
* Examining compression within high-turnover roles or teams

To add a filter:


1. Click the "Additional filters" section
2. Select an attribute to filter on (Department, Level, Location, etc.)
3. Choose specific values to include in the analysis


## **Using the Flag in Your Merit Cycle**

Once configured, the Manager Compression Flag will automatically identify managers who meet your compression criteria. Use these insights to:

### **1. Review Flagged Managers Individually**

For each flagged manager:

* Identify which direct report(s) are causing the compression flag
* Review both individuals' compensation history
* Assess whether the compression is appropriate given role scope and performance

### **2. Address Compression Through Merit Decisions**

**Option A: Increase the manager's compensation**

* Provide a larger merit increase to the manager to restore appropriate differential
* Consider an off-cycle adjustment if compression is severe
* Document the rationale as maintaining organizational structure

**Option B: Moderate the direct report's increase**

* If the direct report is receiving an unusually large increase that would create compression, consider whether it's sustainable
* Evaluate whether promotion to a higher level (potentially lateral to management) is more appropriate than a large in-role increase

**Option C: Accept the compression**

* Document why the narrow gap is appropriate (e.g., specialized technical expert, market-driven rates for scarce skills)
* Ensure the manager is aware and comfortable with the pay relationship
* Monitor for signs of manager dissatisfaction or retention risk

### **3. Plan Proactively for Future Cycles**

* Track managers who are approaching compression thresholds but not yet flagged
* Budget for manager adjustments when planning high-performer increases
* Review compression patterns to identify systemic issues in your career ladder or pay scales

### **4. Communicate Thoughtfully**

When discussing compression with managers:

* Frame it as organizational health, not a criticism of their performance
* Explain the rationale for addressing (or accepting) the compression
* Be transparent about budget constraints and prioritization decisions

## **Best Practices**

**Run the flag early in planning**: Identify compression issues before finalizing merit decisions so you can adjust allocations proactively rather than reactively.

**Consider the full team context**: If a manager has ten direct reports and only one creates compression, the situation may be different than if half the team is compressed.

**Account for promotion timing**: If you're promoting a high performer to management, ensure their new salary creates appropriate distance from their former peers who will now report to them.

**Review span of control**: Persistent compression in a team might signal that the manager's scope isn't sufficiently different from their reports, suggesting organizational design issues beyond compensation.

**Create escalation paths**: Define clear processes for addressing severe compression (e.g., less than 5% gap) that might require off-cycle adjustments or emergency budget.

**Use percentage-based thresholds for consistency across levels**: Percentage thresholds scale proportionally with compensation levels, ensuring fair compression standards throughout your organization. A $10,000 gap might be substantial for roles paying $60,000 (17% differential) but minimal for roles paying $200,000 (5% differential). Dollar-based thresholds can create inconsistent standards that are either too strict for lower-paid roles or too lenient for higher-paid roles.

Manager Compression Flag

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

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

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

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

Survey aging

Edit and apply benchmarks

Set weights and logic

Map data sources to jobs

Supported survey providers

Manage Pave data sources

Manage survey data sources

Benchmarks overview

Step 2: Benchmarking

Band Sets

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

Manually Create New Band Sets

Bands Set Audit Log

How to duplicate band sets

Managing & Reordering Calculated Columns

Calculated Columns

Unmatched Employees

Upload/Download Bands

View changes

Editing Bands

Employee Distribution in Bands

Pay Zone Manager

Job Architecture 101

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

Relative Permissions

Generate Bands for New Jobs in Your Job Architecture

Compare Bands

Advanced Filters

Ongoing Management & Analysis

Market Pricing

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?

Manager Compression Flag

Share

Share

Manager Compression Flag

Share

Share