The State Worker: See pre- and post-furlough state payroll figures

The State Worker

Chronicling civil-service life for California state workers

September 24, 2009

See pre- and post-furlough state payroll figures

So how much have furloughs boomeranged to hit the state with lost employee payroll taxes?

We've collected data from the controller's office about state income tax withheld from state workers' pay from January 2006 through August of this year. The figures give an indication of how furloughs have affected state tax receipts from workforce payroll.

The state's cut of employee payroll took a $6 million hit in last February, the first month of furloughs, compared with the same month in 2008. Gross payroll for the month also shrank by $62 million, despite nearly 6,000 more full-time employees. (Departments lost about 500 more part-time and intermittent workers, so the overall state worker count for February of this year was down compared to February 2008.)

Click here for the February 2008-09 comparison. You can also check out a July 2008-09 table here. We picked that month for a snapshot, since it was the first with three "Furlough Fridays."

Access the controller's month-by-month data by clicking here.

(The data isn't in a form that can be immediately manipulated. We invite enterprising State Worker blog users to take up the cause and share tables, graphs and observations they cull from the information.)

About Comments

Reader comments on Sacbee.com are the opinions of the writer, not The Sacramento Bee. If you see an objectionable comment, click the "report abuse" button below it. We will delete comments containing inappropriate links, obscenities, hate speech, and personal attacks. Flagrant or repeat violators will be banned. See more about comments here.

What You Should Know About Comments on Sacbee.com

Sacbee.com is happy to provide a forum for reader interaction, discussion, feedback and reaction to our stories. However, we reserve the right to delete inappropriate comments or ban users who can't play nice. (See our full terms of service here.)

Here are some rules of the road:

• Keep your comments civil. Don't insult one another or the subjects of our articles. If you think a comment violates our guidelines click the "report abuse" button to notify the moderators. Responding to the comment will only encourage bad behavior.

• Don't use profanities, vulgarities or hate speech. This is a general interest news site. Sometimes, there are children present. Don't say anything in a way you wouldn't want your own child to hear.

• Do not attack other users; focus your comments on issues, not individuals.

• Stay on topic. Only post comments relevant to the article at hand. If you want to discuss an issue with a specific user, click on his profile name and send him a direct message.

• Do not copy and paste outside material into the comment box.

• Don't repeat the same comment over and over. We heard you the first time.

• Do not use the commenting system for advertising. That's spam and it isn't allowed.

• Don't use all capital letters. That's akin to yelling and not appreciated by the audience.

You should also know that The Sacramento Bee does not screen comments before they are posted. You are more likely to see inappropriate comments before our staff does, so we ask that you click the "report abuse" button to submit those comments for moderator review. You also may notify us via email at feedback@sacbee.com. Note the headline on which the comment is made and tell us the profile name of the user who made the comment. Remember, comment moderation is subjective. You may find some material objectionable that we won't and vice versa.

If you submit a comment, the user name of your account will appear along with it. Users cannot remove their own comments once they have submitted them, but you may ask our staff to retract one of your comments by sending an email to feedback@sacbee.com. Again, make sure you note the headline on which the comment is made and tell us your profile name.

blog comments powered by Disqus