Fun With Government-Employee Data

Breaking News- Teachers give back in Colchester and ranks '166 of 169': Article -HERE-
Academy Increase Comes in at 1.99%: Article -HERE-
____________________________________________________________________________
The Nutmeg State’s public-employee unions tell taxpayers that government here isn’t overloaded with staff. Based on Connecticut’s population, they assert, the public payroll ranks below the national average. So, too, does government employment as a percentage of the total workforce.

Surprisingly, both claims are largely accurate. But when you look at the rest of the data, the exorbitant cost of bureaucracy in Connecticut becomes blindingly clear.

The period between 1992 and 2007 is a good decade-and-a-half to examine, since it offers reliable statistics for both government and private-sector jobs in Connecticut. Let’s start with state employees. In 1992, according to the U.S. Census Bureau, the state had 54,184 full-time equivalent (FTE) workers. (In census-speak, FTE “is calculated by dividing the ‘part-time hours paid’ by the standard number of hours for full-time employees … and then adding the resulting quotient to the number of full-time employees.”)

By 2007, FTE employees had reached 61,823 — a growth rate of 14.1 percent, during a time when private employment grew by only 9.7 percent. (Nationally, nongovernment jobs grew by about 28 percent — nearly three times Connecticut’s anemic performance.)

As for wages and salaries, Connecticut’s state-employee unions and their lackeys in the legislature made sure that pay more than keep pace with inflation. In 2007, the average annual earnings by an FTE employee were $59,802 — up from an inflation-adjusted $57,123 in 1992.

Many taxpayers assume the story must be different at the local level — after all, aren’t budgets regularly defeated by voters, prompting municipal officials to complain about brutal “layoffs”?

If local bureaucrats faced mass termination in the last 15 years, the Census Bureau can’t find any evidence. Between 1992 and 2007, the number of FTE employees in municipal government rose 27.4 percent, from 98,711 to 125,722.

Unlike state employees, the average municipal staffer saw his or her inflation-adjusted income drop just a bit, from $55,385 to $52,483. Tough break, but given cities’ and towns’ massive hiring binge, the total payroll cost to taxpayers still rose by 20.7 percent.

How does state- and local-worker pay fare against the private sector? According to the latest survey by the U.S. Bureau of Labor Statistics, in the all-worker category, government employees in the New York metro area (which includes municipalities in Fairfield, New Haven, and Litchfield Counties) earn 27.7 percent more in average hourly wages. In Greater Hartford, the public premium is a stunner: 48 percent. In the service sector, pay is nearly double for government jobs in both regions.

Remember, the numbers we’ve scrutinized are wages and salaries. They don’t represent total compensation. Benefits in Connecticut government still exist in a Neverland with a surfeit of paid holidays/vacations, ludicrously low copays and pathetically small premium-sharing, plus set-for life, defined-benefit pensions.

The retirement-income obligation faced by taxpayers was enormous even before Wall Street began its harrowing plunge. Pols in Hartford underfunded the pension accounts for state employee and teachers for years, even when times were good. Combined, the two unmet liabilities top $15 billion.
 
Big pension gaps also exist at the local level. In March, the (Bridgeport) Connecticut Post’s Bill Cummings reported that since the stock-market tumble, “Fairfield’s pension fund … lost nearly $100 million, or 28 percent of its value. Bridgeport lost $70 million in one fund, or about 30 percent of value. Milford’s pension fund dropped $158 million.”

But wait — there’s more. Other post-employment benefits (OPEB ), a compensation category that includes most of the perks employers supply to retirees but pensions, is a giant asteroid aimed right at taxpayers’ wallets. At the state level, the OPEB burden is $21.5 billion. (No one has bothered to document the figure for municipal government.)

The truly maddening thing about public payrolls in Connecticut is that unless you’re adept at tracking down — and processing — employment data from state and federal agencies, you’re likely to get an incomplete picture about the bill we face for bureaucrats. Into that vacuum step our friends in state and local government, who use scare tactics and claims of their “efficiency” to cling to excessive pay and benefits.

Here’s a proposal: Each municipality’s website, as well as the state’s, should post average salaries, detailed overviews of employee benefits, retirement-income liabilities, OPEB costs, and how staffs have grown/shrunk, relative to population, over the last few decades. How could anyone object to creating such cheap, easily accessible tools for taxpayers to judge the price and productivity of their “public servants”? It’s not as if Connecticut’s government-employee unions have anything to hide. Do they?

D. Dowd Muska is a writer, commentator and lecturer. His website is www.dowdmuska.com.

                                                                        # # # # #

To unsubscribe or add a name to our subscriber list, email dowd@dowdmuska.com.

 

What did you think of this article?




Trackbacks
  • Trackbacks are closed for this post.
Comments

  • 4/25/2009 10:25 PM A Voice wrote:
    Where is all the chatter. Your opposing website seems to have gone silent. I would have expected more during the the budget season. Thanks for your updates. I must admit the tape speaks for itself.
  • 5/25/2009 3:34 PM Ross Bunnell wrote:
    Although I fully agree with the author's proposal to post certain state budget data on personnel expenses (as far as I'm concerned, transparency in government is always a good thing), I have to strongly disagree with his implications about state employee compensation based on census data. First of all, comparing data on state employes versus data on all workers in a geographic region is a poor comparison, and bound to lead to gross misrepresentations. This is because the skill and qualifications of public sector employees simply don't match those of the general population. Most state agencies have disproportionate numbers of college educated workers, as well as workers with valuable technical skills. Take my agency for example. My Division in the state agency that I work for has about 50 people in it. Of that 50 people, a handful are clerical staff, whereas the remainder are almost all college-educated, with about half having egineering degrees and the other half having degrees in the sciences. Many of us have advanced degrees. Would this be typical of the general population of Hartford, CT? I think not. And my Division is pretty much typical of the other divisions in my agency.

    Truth is, there are a LOT of members of the general public who are flipping burgers and working as "associates" in Walmart -- all low skill, low-paying jobs. There simply are not that many state employees that fall into this category.

    A fairer comparison would be to match up state workers with thir career counterparts, and a completely different picture would emerge. I'll offer myself as an example. After graduating from a top-20 school with an engineering degree, I worked several jobs in the private sector. At that point I decided that doing good works was more important to me than making big bucks, so I pursued a career in the public sector. After a couple of near-misses, I was hired by the agency for which I have been working for the last 20 years. My starting salary as a state employee was 30% lower than my previous position, and it took me nearly five years to regain my former salary. When I worked in the private sector, I got a bonus every year. I can assure you that I have never received a bonus as a state employee. And, comparing myself to my fellow enginering graduates who are working in the private sector, I make far less money and have far less wealth than they do. Don't get me wrong -- I'm not complaining. I made this choice because public service is what I wanted to do for a living. But to represent that we are vastly overpaid is simply untrue.

    And consider who we are talking about here. We are talking about state police officers, prosecuters, judges, corrections officers, the people that design your roads and bridges, the people that police polluters and clean up the environmental messes that our entrpreneurial friends in the private sector create. Remember the old phrase, "you get what you pay for?" Well, what do you want?
    1. 5/25/2009 4:07 PM Admin wrote:
      Thanks for stopping in. I will be sure to send your comment on to Dowd Muska, the author of the piece.
Leave a comment

Comments are closed.