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

Raising Expectations


Pay for performance and market-based pay for government workers came into vogue in part because of their use at the Government Accountability Office.

David M. Walker, the chief of GAO, has made federal human capital reform, as he calls it, a focus of his tenure, and has led by example. Many managers across government looked on as Walker began to pay GAO staff according to what similar private sector employees were paid and according to their job performance.

But now, the archetype is being questioned. First, a group of GAO employees began a campaign to form a union, with a vote planned in the coming months. And last week, GAO's system was scrutinized before Congress.

Curtis Copeland, head of executive branch operations in the government and finance division of the Congressional Research Service, testified about the GAO system before a House Oversight and Government Reform subcommittee on March 8.

Copeland, who worked at GAO for 23 years until moving to CRS in 2004, addressed why 308 GAO analysts, out of about 1,800 in the new system, received no pay raise last year even though they had satisfactory performance ratings.

The primary reason for their flat pay was a study conducted by the Watson Wyatt Worldwide consulting firm that compared GAO salaries to those for comparable private sector jobs. Watson Wyatt found that some employees already were paid more than the maximum market rate.

In September, nine congressmen sent a letter to Walker expressing disappointment with his decision not to give everyone at least a small pay increase.

In his testimony last week, Copeland noted that on seven different occasions, Walker had publicly promised that all employees with satisfactory performance ratings would receive raises. Among them was the GAO chief's testimony at a July 2003 House hearing in which he said, "I have made it clear that, as long as employees are performing at the 'meets expectation' level or better, then they will be protected against inflation."

According to Copeland, GAO officials explained in response to previous congressional questions that Walker's statements were "accurate at the time … [but] there have been significant subsequent events that have altered the comptroller general's views on whether and when employees should receive pay raises."

Watson Wyatt concluded that for some of the GAO analysts, their peers in the private sector were making at most $101,600 while they were earning around $110,000.

That may be a compelling argument for freezing some employees' pay. And whether Walker went back on his word is almost irrelevant. The more central point is that in pay for performance and market-sensitive pay systems, agency officials' word is all an employee has.

At a September 2006 hearing, Deputy Defense Secretary Gordon England assured Sen. Susan Collins, R-Maine, that the National Security Personnel System would not result in lower pay for employees.

"So Secretary England, just to close out this issue for the federal employees who are watching today or who may read about this hearing, there's no intention on the part of the department to spend less on overall pay under NSPS than under the old system?" Collins asked. "That's not a goal of the system?"

"It's not a goal," England said. "Employees can feel very confident that under NSPS there's a defined pot of money for employee raises and for pay for performance."

In the Defense Department's new system, as with its archetype at the GAO, employees will have to take their leaders at their word.

Close [ x ] More from GovExec

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

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • Federal IT Applications: Assessing Government's Core Drivers

    In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security


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