Pay & Benefits Watch Pay & Benefits WatchPay & Benefits Watch
Key developments in the world of federal employee benefits: health, pay, and much more.

Locality pay decision coming

ARCHIVES
Wouldn't an 18.8 percent pay raise next year be nice? That's how much the average federal employee would receive in 2002 under the 1990 Federal Employees Pay Comparability Act. But as it has been for the past eight years, that law will be ignored again in 2002. So instead, federal workers will have to wait a few weeks to know exactly how much of a pay raise they will get in January. In the 2002 Treasury-Postal spending bill, Congress ordered President Bush to give employees an average 4.6 percent pay raise. The raise will be divided in two parts. First, employees will receive an across-the-board raise. Based on the President's actions earlier this year, the across-the-board raise will likely be 3.6 percent. Second, employees will receive an added raise based on where they work. Under locality-based payments, the less you're paid compared to private sector workers in your city, the bigger your raise will be. Because Congress ordered an average raise of 4.6 percent, the 1 percent left over after the across-the-board increase will likely be divided up depending on salary rates in the government's 32 locality-pay areas. By the end of December, and probably sooner, President Bush will announce by executive order how the locality-based portion of the raise will be divvied up. Last year, federal workers found out on Nov. 30 what their pay raises would be. President Clinton was forced by federal law (U.S. Code Title 5, Section 5304a, for all you chapter-and-verse types) to issue an alternative locality pay plan that set out raises by city. Had he not acted, the total pay increase for most employees would have been about 15 percent, instead of the average 3.7 percent that Clinton decided on. But this year, President Bush doesn't have to issue an alternative locality pay plan by the end of November. Because Congress has already passed a specific raise and because the President has already signed it into law, there's no chance that federal workers will get a double-digit pay raise. Instead, Bush has until the end of December to decide how to allocate locality-based pay raises. Locality-based raises became a fixture of federal pay in 1994, following implementation of the 1990 Federal Employees Pay Comparability Act. The act's proponents identified a gap between public and private sector salaries of about 30 percent a decade ago. The act was designed to close the gap to about 5 percent. But the Clinton administration, and now the Bush administration, has ignored the act every year, implementing smaller raises than called for under the law. This table shows what raises should have been if the law had been followed every year, versus what the raises actually were.
Year FEPCA
mandated
raise
Actual
raise
1994 6.2% 4.0%
1995 4.3% 2.6%
1996 4.2% 2.4%
1997 4.3% 3.0%
1998 5.0% 2.8%
1999 5.2% 3.6%
2000 6.3% 4.8%
2001 4.5% 3.7%
Clinton and Bush both used the same basic argument against the larger raises: They would be too expensive. They also contend that the methodology under the law is flawed, so that some federal workers are probably overpaid and some federal workers are probably underpaid, depending on their occupation and work location. People who argue for the higher raises contend that the government cannot attract and keep top-notch people if it won't pay them in the ballpark of private-sector employers. The pay gap is down to 21.7 percent based on calculations by the Office of Personnel Management. As mentioned at the beginning of the column, it would take an 18.8 percent average pay raise-a 3.6 percent across-the-board increase plus an average 14.7 percent locality-based increase-to catch up to the remaining pay gap in 2002. That would never happen. OPM is conducting a strategic compensation review that could lead, in just a few years, to changes in the way pay raises are calculated. More Locality Pay Three new locality pay areas may be created in 2002: Austin, Texas; Raleigh-Durham-Chapel Hill, N.C.; and Louisville, Ky. The President's Pay Agent, a body made up of the Office of Personnel Management director, the Office of Management and Budget director and the Labor Secretary, will decide whether to give the three areas locality-pay designation. That would mean more money for federal employees who work in those areas. The Pay Agent has until the end of the year to decide whether to add the three locations to the list of locality pay areas.
 

Brian Friel is founder of One Nation Analytics, an independent research, analytics and consulting firm for the federal market.

FROM OUR SPONSORS
JOIN THE DISCUSSION
Close [ x ] More from GovExec
 
 

Thank you for subscribing to newsletters from GovExec.com.
We think these reports might interest you:

  • Sponsored by Brocade

    Best of 2016 Federal Forum eBook

    Earlier this summer, Federal and tech industry leaders convened to talk security, machine learning, network modernization, DevOps, and much more at the 2016 Federal Forum. This eBook includes a useful summary highlighting the best content shared at the 2016 Federal Forum to help agencies modernize their network infrastructure.

    Download
  • Sponsored by CDW-G

    GBC Flash Poll Series: Merger & Acquisitions

    Download this GBC Flash Poll to learn more about federal perspectives on the impact of industry consolidation.

    Download
  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

    Download
  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

    Download
  • Sponsored by Aquilent

    A DevOps Roadmap for the Federal Government

    This GBC Report discusses how DevOps is steadily gaining traction among some of government's leading IT developers and agencies.

    Download
  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

    Download
  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

    Download
  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.

    Download
  • Sponsored by CDW-G

    Joint Enterprise Licensing Agreements

    Read this eBook to learn how defense agencies can achieve savings and efficiencies with an Enterprise Software Agreement.

    Download
  • Sponsored by Cloudera

    Government Forum Content Library

    Get all the essential resources needed for effective technology strategies in the federal landscape.

    Download

When you download a report, your information may be shared with the underwriters of that document.