If you are a General Schedule (GS) employee, your paycheck is split into two parts: your Base Pay (a fixed national number) and your Locality Pay (a percentage boost based on where you work).
Many federal employees assume that if their local rent, groceries, and gas prices go up, their locality pay should automatically go up to match it. That is the "Cost of Living" myth. In reality, the federal government does not care how much your apartment costs. They only care about how much private-sector companies are paying their employees in your city.
Here is the step-by-step breakdown of how the government calculates the "Cost of Labor" and determines your locality pay.
1. The Core Metric: Cost of Living vs. Cost of Labor
To understand locality pay, you must understand the difference between the Cost of Living and the Cost of Labor.
Step-by-Step Execution
Step 1: The Cost of Living (Ignored). Cost of Living measures how much it costs to survive in a city (rent, food, taxes, utilities). The federal government explicitly ignores this data when setting your locality pay.
Step 2: The Cost of Labor (The Real Metric). Cost of Labor measures how much private-sector employers are paying their workers for specific jobs.
Step 3: The Gap Analysis. The government compares the federal Base Pay for a job (e.g., a GS-12 IT Specialist) to the average salary of a private-sector IT Specialist in that specific geographic area. The difference between those two numbers is the "Pay Gap." Locality pay exists solely to close that specific Pay Gap, ensuring the government can compete with local corporate salaries.
The Foundation
This methodology is mandated by the Federal Employees Pay Comparability Act of 1990 (FEPCA). FEPCA legally dictates that federal pay must be comparable to non-federal pay for the same levels of work within the same local wage area. It explicitly ties locality pay to local labor market rates, not consumer price indexes or housing costs.
2. The Data Gatherers: The BLS
The government cannot just guess what private-sector companies are paying; they need hard data. This is where the Bureau of Labor Statistics (BLS) comes in.
Step-by-Step Execution
Step 1: The National Compensation Survey (NCS). The BLS conducts a massive, ongoing survey of private-sector businesses and state/local governments.
Step 2: Occupational Employment and Wage Statistics (OEWS). The BLS combines the NCS data with the OEWS program to get highly granular, statistically valid salary data for hundreds of different occupations across the country.
Step 3: Data Weighting. The BLS weights this data to match the actual makeup of the federal workforce. If the federal government employs thousands of accountants but very few retail workers in a specific city, the BLS data prioritizes the accounting salaries to calculate the true federal pay gap for that area.
The Foundation
The BLS operates as the principal fact-finding agency for the federal government in the broad field of labor economics and statistics. Their methodologies are strictly regulated to ensure statistical validity and prevent political manipulation of the wage data.
3. The Decision Makers: The FSC and the Pay Agent
Once the BLS gathers the data, it must be analyzed and turned into actual policy recommendations. This involves two major governing bodies.
Step-by-Step Execution
Step 1: The Federal Salary Council (FSC). The FSC is an advisory body composed of labor relations experts and federal employee union representatives. They review the raw BLS wage data, calculate the official "Pay Gaps" for every city, and formally recommend the creation of new locality pay areas or changes to existing boundaries.
Step 2: The President's Pay Agent. The FSC sends their recommendations to the Pay Agent, which consists of the Secretary of Labor, the Director of the Office of Management and Budget (OMB), and the Director of the Office of Personnel Management (OPM).
Step 3: The Final Recommendation. The Pay Agent reviews the FSC's recommendations and submits an annual report to the President.
Step 4: The Executive Order. Finally, the President reviews the Pay Agent's report and issues an Executive Order before the end of the year, officially cementing the new locality pay percentages for the upcoming January.
The Foundation
Both the Federal Salary Council and the President's Pay Agent were established by FEPCA (5 U.S.C. 5304). Their distinct roles create a system of checks and balances, ensuring that labor unions have a voice in the data analysis (via the FSC) before the executive branch makes the final budgetary decisions (via the Pay Agent).
Key Takeaways
- 01Cost of Labor, Not Living: Your locality pay is based entirely on how much private-sector companies are paying their employees in your city, not how high your rent or grocery bills are.
- 02The Tourist Trap Effect: Cities heavily reliant on tourism (like Honolulu) often have massive Costs of Living but relatively low Costs of Labor (due to a high concentration of hospitality jobs). Therefore, their locality pay is often lower than federal employees expect.
- 03The Tech Hub Effect: Cities with massive corporate tech and finance sectors (like San Francisco or New York) drive the local Cost of Labor sky-high, resulting in the highest locality pay percentages in the country.
- 04The BLS Drives the Math: All locality pay adjustments begin with raw wage data collected by the Bureau of Labor Statistics.
Official Sources & Further Reading
- 5 U.S.C. 5304 (Locality-Based Comparability Payments)
The statutory bedrock (FEPCA) that legally defines the locality pay system and the roles of the Pay Agent.
- OPM: Federal Salary Council
Official reports, meeting minutes, and methodology documents from the FSC.
- OPM: President's Pay Agent Reports
The final annual reports detailing the exact pay gaps and BLS data used to set each year's locality rates.
- BLS: National Compensation Survey
The primary data source used to measure the cost of labor across the United States.