TOPICS

Locality pay dreams

Every year, dozens of federal officials from outside the Beltway call, e-mail, write and fax the Office of Personnel Management, begging to be something more than merely "Rest of the United States."


RELATED STORIES

When it comes to federal pay, Rest of the U.S. is the lowest of the low. It's the 32nd of 32 locality pay areas.

Huntsville, Ala., is on the locality pay map - it's one of 31 designated locality pay areas where federal employees get special pay increases each year based on the cost of labor in particular metropolitan areas. Even Dayton, Ohio has its own pay area. But federal employees in Springfield, Mass.; Key West, Fla.; San Antonio; Norfolk, Va.; and Washoe County, Nev., all get the same catch-all Rest of the U.S. pay increase - 4.52 percent this year.

Many of them aren't too happy about it.

The government established the locality pay system under the 1990 Federal Employees Pay Comparability Act, in recognition of the fact that wages vary significantly across the country. In the private sector, workers in New York City doing the same jobs as workers in Milwaukee usually get paid at different rates. The comparability act brought at least some sense of that "market sensitivity," as it is known in human resources circles, to the federal government's pay scales.

But ever since the locality rates took effect in 1994, federal officials in the Rest of the U.S. have tried to get special locality rates applied to them. Representatives of agencies with offices in such cities as Raleigh, N.C., and Louisville, Ky., have sought to have their own locality pay areas. In places on the outskirts of existing locality pay areas, officials have tried to get their workplaces covered by the neighboring locality rate. Federal employees in western Massachusetts, for example, want to be included in the Hartford, Conn., locality pay area. In Hartford, federal workers get paid about 5 percent more than workers in the Rest of the U.S.

Officials in the Rest of the U.S. plead their cases each year before the Federal Salary Council, an Office of Personnel Management group that recommends changes in locality pay to the administration each year. In the past, the council has been cautious about recommending new locality pay areas or including more cities and counties in existing pay areas because of a concern that such changes would open the floodgates to petitioners from across the country.

But Sam Wallace, the new head of the Federal Salary Council, said at the council's August meeting that he doesn't think the "floodgate effect" should be a concern. Instead, every application should be considered on its own merits, Wallace said.

That change in philosophy was welcome news to Jeffrey Anliker, chairman of the Federal Executive Association of Western Massachusetts. Anliker and other federal managers from the Connecticut River Valley have petitioned the council repeatedly in recent years to be shifted into the Hartford pay area. Anliker and Bruce Sylvia, vice-chairman of the Western Massachusetts executive association, appeared again before the council this month.

Anliker cited several cases of agencies having trouble recruiting and retaining employees because of the low Rest of the U.S. locality rate. One candidate for an Agriculture Department administrative officer position in Amherst, Mass., for example, turned down the job when the candidate realized Amherst isn't part of the Boston locality pay area.

The application of the western Massachusetts group faces several obstacles, however. First, the council has said it won't apply special locality rates to areas with fewer than 2,000 federal employees paid under the General Schedule. Western Massachusetts has about 1,600 such employees. Second, communities are supposed to show economic and workforce ties with the core of the locality pay area that they want to be a part of. An old study questioned the tie of western Massachusetts to Hartford.

Anliker and Sylvia asked the council at the August meeting to change the 2,000-employee criterion, given the federal downsizing of the 1990s. They also made the case that western Massachusetts and Hartford have strong economic links. Many workers commute between the two areas, they said.

Wallace told the executives that the council would consider their case. One factor in the Massachusetts group's favor is its persistence. Only one other group, from Monroe County and Palm Beach, Fla., showed up at the August meeting to plead its case. Officials from other areas submitted only written applications.

But if recent history is any guide, the salary council will recommend few if any changes to the borders of locality pay areas this year. And for another year, officials across the country will have to get by being just Rest of the U.S.

COMMENTS

  • To me, locality pay seems to indicate federal employees aren't paid enough. Lord knows, we don't make what our counterparts in private industry do. But then, we don't have to work 10-12 hour days either. I get a very nice locality pay, so I'm not complaining. By the way, we need that little addition to live reasonably well in this area. But my sister, on the other side of the country, gets almost half what I get for locality pay. Having lived in both places, I know there is no real difference in the cost of living in either location. Why doesn't someone simply set the pay scale where it should be for the job one is performing; regardless of where you are located. Oh, that's right, they already did that; and a previous president set the rules aside and didn't allow federal employees to get the pay scales increased. A simple solution to a simple problem compounded by committees, Congress, and presidents; and they wonder why it's so hard to get good help anymore.
  • I have to say that it is very difficult to feel sorry for those who live CONUS [standard continental United States rate] and complain about not getting equitable locality pay under the "Rest of the U.S." blanket. Those of us...serving in the U.S. in Alaska and Hawaii, are not considered at all in the locality rates. Many would say that this is fair, given that we receive a non-taxable COLA [cost-of-living adjustment] between 20-25 percent above our base pay; however, we cannot consider COLA when giving to our TSP accounts or when retiring. I understand that locality pays are based on the costs of salaries and COLA is based on the cost of living. However, when COLA was established, it was established to enable federal employees living in high cost of living areas to generally enjoy the same standard of living as their peers at the same grade/step throughout the service (whether in Washington, DC; Honolulu, HI; London). This also encourages federal career employees to consider career moves CONUS, OCONUS and overseas. With the advent of a "Rest of the U.S." locality pay which covers all 48 states and omits Hawaii, Alaska and overseas employees, the standards of living have, and will continue to be, skewed in favor of staying at home in the U.S. The 25 percent COLA for Hawaii and Alaska employees has been declining in value at a rate of 1 percent each year since Congress's decision to base raises on locality areas. Since Congress gives an across-the-board pay raise which is generally 1 percent lower (in Hawaii, Alaska, and overseas), the value of pay for those who serve there is declining at about that same rate each year. In just 11 years, the pay for those who receive a 25 percent COLA will be the same as those who live in Washington, DC. The COLA will no longer allow the same standard of living for those who serve in these areas. The Office of Personnel Management will have an even-greater difficulty in encouraging federal employees to transfer overseas for rotational assignments, as these employees will actually have to take a pay cut to move overseas. I, personally, would like to see locality pays either be granted to everyone or only given to those in the 30 or so MSAs who actually have proven their need for locality pays.