Intel Contractors Again


The ODNI announced some new results from the second survey of intelligence contractors. Government Inc. listened in and posted part of a story that appeared in The Post. The gist:

Contractor workers make up about 27 percent of the intelligence community workforce. Along the way, though, officials took up the issue of the differences in costs for government and contract workers.

Ronald Sanders, the chief human capital officer at the national intelligence office, said contract workers each cost the government about $207,000 annually, compared with about $125,000 for a civilian government employee's salary and benefits.


One reader, apparently someone who has worked both as a civil servant and government contractor, offered a sensible and provocative assessment of the government estimates. This from someone who signed off as Been on Both Sides:

"Sanders' cost comparison figures don't pass the smell test. On the government side, it's simply not credible that the "full lifecycle cost" of an IC employee is that low; not when the current year average salary is already around 90k and the benefit load is another 30-50%. Tack on 15 to 25 years of annuity payments (even those modest FERS ones) plus health care costs, and the true lifecycle cost figure has got to be higher.

"The contractor number is similarly suspect. Not that 207k isn't a realistic average annual cost, but if the IC thinks they're not paying a good chunk of these companies' overhead as part of that, they're incredibly naive. As a government vendor you can "build up" your rate in different ways, depending on circumstances, to suit your purposes. For example, because so many IC contractors are housed in government facilities, it's likely not kosher to charge a "full" overhead percentage; so, you just bury it in inflated direct labor rates. But it's a safe bet that contractor staff aren't taking home 50% more than govies in salary. The difference is paying for all those contractor palaces off the Dulles Toll road, and huge bonuses for the firms' officers.

"If you read the transcript of Sanders' telecon with the media on this report, it's clear that the cost comparison question is "really, really fuzzy." (his words) It's a complex issue but important to the larger question of appropriately balancing government and contractor resources. Reporters shouldn't take any of this at face value -- everyone involved has incentive to obfuscate, and it'd be better if the media helped cut through the noise, rather than perpetuating it."

Other remarks, anyone? These issues go to the heart of some important policy questions. Government Inc. needs and wants the input.

Meanwhile, thanks to Been on Both Sides for the thoughts.

Here are some more thoughts from Michael Lent:

"It's good that other observers and commenters see the apples-to-guavas nature of Sanders' cost comparison. He's a smart guy, knows contractors well in most respects, and should have dealt with that data problem.

"It's true that many people in the "media" and Congress do not understand the diff between a fully loaded rate and a contractor employee's salary; glad that was straightened out.

"On the government side of the comparison, unless it is specified in some detail that is unpresented so far, we should be skeptical that the "load" on the salary includes the full measure of benefits and retirement plans. The figure does not--because government never includes it except in A-76 studies--likely include the true cost of government overhead, for example a slice of the loaded costs of all sources of supervision and management, up to minute slices of the compensation of McConnell and Bush, plus their retinues and facilities, etc. Further, government compensation never takes into account the very valuable, but hard to monetize, worth of employment security, or being shielded in most cases from any accountability. If you captured all the tangible and intangible costs left out of such comparisons, you might find the figures rather similar. But Congress doesn't appropriate that way and agencies don't budget that way. Nonetheless, the costs are absolutely real, even if we can't identify them precisely.".

By Robert O'Harrow |  August 29, 2008; 3:08 PM ET
Previous: Nice Try | Next: GSA, Networx and Money

Comments

Please email us to report offensive comments.



I'm a bit confused by this sensible and provocative assessment. Let's assume the average gov't salary for these workers is 90K. 30-50% is way to high for benefits. Most generous benefit packages run around 30-35% and INCLUDE health care, which is listed later as an additional cost.

The point about retirement/pension/annuities is a fair one, but the $207,000 number for the gov't contractor is not counting the double costs of overhead for the government (both its own and the contractors).

If we don't have good numbers on what the comparative costs are between adding additional government workers and outsourcing jobs to the private sector, we better get them. How else are we supposed to be able to make a judgment call on when and where it is appropriate to outsource?

Posted by: Adam Hughes | August 29, 2008 4:37 PM

Contract workers "cost the govt" $207,000 a piece for their work - that doesn't mean the employee receives that - it means the company contracting receives that on average. That's more that $125,000, even, I suspect, with other costs factored in.

The real point is that privatizing government functions inserts a profit overhead for private contractors that doesn't exist for public employees. The government is not a for-profit institution, so it can be run more efficiently in the provision of services (not always goods).

Posted by: Erik | August 31, 2008 1:57 PM

It's good that other observers and commenters see the apples-to-guavas nature of Sanders' cost comparison. He's a smart guy, knows contractors well in most respects, and should have dealt with that data problem.
It's true that many people in the "media" and Congress do not understand the diff between a fully loaded rate and a contractor employee's salary; glad that was straightened out.
On the government side of the comparison, unless it is specified in some detail that is unpresented so far, we should be skeptical that the "load" on the salary includes the full measure of benefits and retirement plans. The figure does not--because government never includes it except in A-76 studies--likely include the true cost of government overhead, for example a slice of the loaded costs of all sources of supervision and management, up to minute slices of the compensation of McConnell and Bush, plus their retinues and facilities, etc. Further, government compensation never takes into account the very valuable, but hard to monetize, worth of employment security, or being shielded in most cases from any accountability. If you captured all the tangible and intangible costs left out of such comparisons, you might find the figures rather similar. But Congress doesn't appropriate that way and agencies don't budget that way. Nonetheless, the costs are absolutely real, even if we can't identify them precisely.

Posted by: Michael Lent | September 1, 2008 10:56 AM

Thanks to Michael Lent for elaborating/expanding on the challenges of comparing contractor vs. govie costs. He's absolutely right about the intangible value of government job security, protection from market forces, etc. -- very difficult to quantify but absolutely part of the equation. By the same token, the flexibility you gain by hiring contractors vs. govies (as Sanders noted) also has significant value: every contract has one form or another of "escape clause" for the government; all are time-limited, ultimately; and individual contractors who aren't up to snuff can be removed immediately, with little fuss. Compared to what's involved in canning a govie, that alone can be darn near priceless. It's also true that the contractor world can attract and provide to government some categories of talent the Feds simply couldn't get on their own.

Perhaps the important thing isn't figuring out who costs more or less, but recognizing that they cost "different" -- you're acquiring or foregoing distinct things when you choose to contract vs. hire career staff, and vice versa. What concerns me is that in recent years, it's become less a choice than a default: contracting out has become the path of least resistance, for a variety of reasons; this seems to have been especially true of the IC post-9/11. Lots of reactive, short-term thinking vs. what we like to call strategic human capital management.

Sanders and co. have incentive to hold down the price tag for govies, and bulk it up for contractors, in hopes of persuading Congress to lift personnel ceilings and allow the IC to hire more staff. And it seems a few on the Hill are already sniffing the bait. It may well be that contractors are doing things govies ought to be doing, but I hope the discussion doesn't focus solely or even primarily on dollars and cents. In many ways that's a distraction from the core issues at stake here.

Posted by: Been on Both Sides | September 1, 2008 3:55 PM

Even if the costs of doing government work in house or through contractors was roughly the same, and I doubt that after figuring profit, there would still be a problem. As we have learned to our dismay in Iraq outsourcing opens the door to all sorts of waste, theft and corruption.

Posted by: marc | September 4, 2008 4:17 AM

I have been on both sides of the fence; just short of forty years as a military and civilian intelligence operative, and some four years as a civilian counterintelligence lecturer at the Pentagon. One of the advantages--and it happened to me--at contract renewable time the contractor can be let go without much ado; not so with a government employee
Gerhardt

Posted by: GBTHAMM | September 9, 2008 2:47 PM

The comments to this entry are closed.

 
 

© 2007 The Washington Post Company