“When are members of Congress going to cut their own benefits?!?”
That has to be just about the favorite rant on this blog.
Well, this month, a bunch of House lawmakers – a half dozen in fact – reminded us that they want to do just that. Or at least give the appearance of wanting to.
A whole passel of them—or rather, a panel of them—provided testimony on how their retirement benefits should be cut or restricted, and hyped bills they have proposed that would do those things. They did it at a Jan. 26 hearing on the federal retirement system held by House Committee on Oversight and Government Reform federal workforce subcommittee.
If you want to take a look at what they had to say, click on any of the lawmakers’ names below to pull up their testimony:
Rep. Howard Coble (R-N.C.)
Rep. Mike Coffman (R-Colo.)
Rep. Robert J. Dold (R-Ill.)
Rep. Tim Griffin (R-Ark.)
Rep. Richard B. Nugent (R-Fla.)
Rep. Robert T. Schilling (R-Ill.)
Some of the lawmakers seem to think their measures are just common sense. But then some may not need a federal retirement, or even a salary. Others, on the other hand, while they want reforms, do want to grandfather long-timers.
And one, to make his point from the git-go, has named his bill the Congress is Not a Career Act (H.R. 981).
The catch with some of these bills in which members of Congress target themselves is that although the sponsor or sponsors offer to bite the bullet on retirement, they also want the entire federal workforce to bite that bullet, too. The Securing Annuities for Federal Employees (SAFE) Act (H.R.3813), introduced Jan. 24 by Rep. Dennis Ross (R-Fla.), is one of those bills.
Luckily, feds can take comfort in the fact that most bills that are introduced in Congress never make it very far. And some of the bills cited above have been around for a while, or are retreads of earlier efforts. A person might even posit that a secondary—or perhaps even primary—motivation behind some of this legislation is its PR value back home.
Nonetheless, many who represent the interests of federal employees probably would agree with Rep. Gerry Connolly (D-Va.), who told The Washington Post that he believes that the real GOP agenda behind these bills is to use them as a “portal” into cutting back retirement benefits for the whole federal workforce.
So, if you are asking the question, “When are members of Congress are going to cut their own benefits?”
Maybe the answer is: “Be careful what you wish for.”
Posted by Phil Piemonte on Jan 27, 2012 at 1:42 PM10 comments
Congressional leaders are sharpening their budget axes, and gearing up to take another look at federal pay and benefits.
Advocates of a smaller, leaner federal workforce will try once more to make the case that the government cannot afford you, and that the only way to fix this is to downsize the workforce, freeze or reduce pay, and trim benefits.
A few of them will imply—or state outright—that the government needs to do these things also because federal workers are inefficient, overcompensated and too many in number for the work they perform.
A lot of this sentiment has been drifting down to the public over the past year or so, inciting Joe Sixpack to start railing against federal workers.
But luckily, John Q. Public generally knows better—as evidenced by American Customer Satisfaction Index results released this week. According to those results, Americans were more satisfied with services provided by the federal government in 2011 than they were a year earlier.
ACSI, a self-professed “national economic indicator of customer evaluations of the quality of products and services available to household consumers in the United States,” says its research results show that citizen satisfaction with federal government services is up 2.3 percent to 66.9 (on a scale of 100) for 2011, after several years of decline.
Ratings vary within the government, of course. According to ASCI, the Defense Department scored a 76 and the Interior Department a 74, versus the Departments of Homeland Security and Treasury at 59 and 57, respectively. ACSI results also indicate that departments and agencies that deliver benefits have higher scores in general than agencies with regulatory missions.
We could list other findings here, but ACSI has posted the materials online, so you can click through to their site if you want to take a closer look.
But for our purposes here, it’s probably better to cut to the chase, as would Prof. Warwick (“please don’t call me ‘Dr.’”) Blood, who currently teaches communication research methods, public opinion research and other subjects at the University of Canberra, and who was often heard to remark in class:
“Any mug can come up with a number! What does it mean?”
In terms of these particular research findings, ACSI founder Claes Fornell answers that question quite well:
“While people generally distrust federal government as a whole, they are much more positive towards the job that individual agencies are performing. Paradoxically perhaps, these findings suggest that the more people come into contact with government service, the more they actually like it. The lack of trust has much more to do with politicians than it does with federal workers and the services of the federal government.”
Enough said.
Posted by Phil Piemonte on Jan 20, 2012 at 11:47 AM12 comments
Pity the Transportation Security Administration, having to devote time and effort (paid for, as some would be sure to point out, with taxpayer dollars) to defend a recent decision to forbid a cupcake from being taken past an airport screening check-point.
But that is what the agency was compelled to do after the media picked up the story of the confiscated cake this week, and the incident quickly devolved into Cupcakegate.
But as a post on TSA’s blog points out, this cupcake was a cupcake in name only.
As evidence, the agency posted on its blog site a photo of what most people think of as a cupcake, and a photo of what actually was confiscated—a “cupcake in a jar” that more closely resembles one of those premixed jars of peanut butter and jelly that groceries sell to lazy PBJ-makers.
As the blog post explains, the large amount of icing (which qualifies as a gel under TSA guidelines) in the jar appeared to exceed the 3.4-oz. limit, so the item was confiscated.
Simple enough. The blog admits that the incident “may seem like a silly move to many of our critics...” But it also notes that “when we can’t be exactly sure of what something is, every officer has the discretion to not allow it on the plane.” In other words, screeners should err on the side of caution. That is what they are trained to do.
We’ve been through a few airports lately, and we have to say that screeners have for the most part have been reasonable. And this is coming from someone who has had bars of his Trader Joe’s fair-trade dark chocolate dug out of a carry-on and swabbed for explosives.
Sounds ridiculous, right? Not entirely. Explosive chocolate bars are nothing new. They debuted almost 70 years ago. The Germans equipped saboteurs with explosives masquerading as bars of chocolate during World War II. Exploding cupcakes? Sure, why not?
So, look. Anyone who travels with any regularity eventually pays the price for today’s security, whether it’s a pat-down, a hand-search of a bag, or confiscation of an item. That’s just the way of modern air travel.
And though it’s inconvenient and sometimes irritating, it’s a necessary evil—like dental work. Feds do a lot of that kind of work—jobs that need to be done whether everyone likes it or not.
With a little luck, maybe more members of the citizens they serve will figure that out.
Posted by Phil Piemonte on Jan 10, 2012 at 7:12 PM26 comments
One union says it can help you find out.
The International Federation of Professional and Technical Engineers, which represents feds at a dozen or so federal departments and agencies, has posted a free online calculator that the union says will help you see how much you are losing under the federal civilian pay freeze.
The calculator, which IFPTE says assumes a 2 percent inflation rate on base salary, lets you enter a salary, say $50,000, and then automatically generates figures showing your annual salary over 20 years, three ways—with no pay freeze, a two-year freeze and a three-year freeze. For each year, the calculator also computes your cumulative loss under each of the two freeze scenarios.
According to the IFPTE calculator, over the course of 20 years, a two-year freeze for the $50,000 salary example cited above would cost that hypothetical employee nearly the current value of his or her salary—$47,138. Under a three-year freeze, that person would lose $68,550 over 20 years.
We don't know how this calculator works, but a union of engineers probably has decent math credentials, right?
Click here to take a look for yourself.
Posted by Phil Piemonte on Jan 04, 2012 at 7:19 AM23 comments
One union says it can help you find out.
The International Federation of Professional and Technical Engineers, which represents feds at a dozen or so federal departments and agencies, has posted a free online calculator that the union says will help you see how much you are losing under the federal civilian pay freeze.
The calculator, which IFPTE says assumes a 2 percent inflation rate on base salary, lets you enter a salary, say $50,000, and then automatically generates figures showing your annual salary over 20 years, three ways—with no pay freeze, a two-year freeze and a three-year freeze. For each year, the calculator also computes your cumulative loss under each of the two freeze scenarios.
According to the IFPTE calculator, over the course of 20 years, a two-year freeze for the $50,000 salary example cited above would cost that hypothetical employee nearly the current value of his or her salary—$47,138. Under a three-year freeze, that person would lose $68,550 over 20 years.
We don't know how this calculator works, but a union of engineers probably has decent math credentials, right?
Click here to take a look for yourself.
Posted by Phil Piemonte on Jan 04, 2012 at 7:23 AM23 comments
As the year winds down, Congress—at this moment in time—seems to be frozen in a state of suspended animation. The House won’t budge. Neither will the Senate.
The issue this time is the payroll tax cut extension. The extension, as well as a number of other measures, were rolled up together into a piece of compromise legislation that days ago seemed ready to pass. But it was not to be. New opposition to the compromise appeared at the last minute, and as a result, most legislators now are at home in their districts sipping hot toddies.
Even though congressional lawmakers appear to have their hands off the levers for a few weeks, most federal employees probably continue to suffer through the holidays with a now-familiar level of anxiety. Because they know that while legislators have not yet crafted a bill containing a pay freeze extension that can pass muster in both the House and Senate, more such legislation will appear in the future.
Of course, a pay freeze extension is perhaps the least of it. Other, longer-term provisions that are likely to continue to creep into new legislation include measures to dump the annuity supplement for feds who are not subject to early retirement requirements, measures to implement very deep workforce cuts, and measures to restructure or reinvent federal retirement systems in ways that are not particularly beneficial to current and/or future employees.
While these measures often face an uphill battle when they are introduced as stand-alone legislation, they often also are included as part of larger, more complicated bills, some parts of which may have broad-based support.
Witness the bill that culminated in the standoff cited above. The House passed that bill, H.R. 3630, earlier this month. The bill extended the expiring payroll tax cut, but it also contained what amounted to a chamber of horrors for employee pay and benefits.
Luckily for feds, the Senate refused to support the bill. With Congress racing against the clock as the end of the year approached, the provisions harmful to feds were stripped from a subsequent short-term House-Senate compromise, which in turn later was snubbed by House leaders. At this writing, Congress remains at a stalemate.
But federal employee advocates worry that one or more of these harmful measures eventually could make it into the “right” bill—one that contains enough prizes for both parties, and/or which would be politically useful in securing the support of a broad part of the electorate later on.
When the stakes are thus elevated, horse-trading often ensues. And feds continue to fear, with good reason, that they may end up being the horse that gets traded.
Congress has kept federal unions and employee groups busy trying to head off such situations. The Federal Workers Alliance, for example, which is a coalition of 22 labor unions, has activated an effort among feds to “tell Congress you’re not a political bargaining chip.”
Such groups are trying to remind feds that there is strength in numbers, particularly if those numbers translate into prospective voters when November rolls around. A handful of phone calls, emails or letters to a lawmaker won’t do much good, but when they arrive in the thousands, they get noticed.
A quick Internet search shows that the numbers are significant: There are about 2 million civilian feds, and a half million or so postal workers. There are also 1.4 million military service members who face some of the same issues related to pay and benefits, as well as some unique to the armed forces. Add in millions more federal and military retirees and spouses, and that is a lot of people—enough for feds to flex significant political muscle if they make themselves heard.
This year has not been a great one for federal employees, and plenty of people believe 2012 is going to be worse. But the current political environment got where it is in part through anti-government grassroots activism. As a group, feds seem to have enough critical mass to launch their own grassroots offensive -- to defend their jobs, pay and benefits simply by reminding policymakers that they too go to the polls.
The question is: Will 2012 be the year they do it?
Posted by Phil Piemonte on Dec 22, 2011 at 6:44 AM24 comments