Coyote Blog

Hans Bader of the CEI takes my post the other day on Obama's Executive Order 13673 and runs with it much further.  I had written

Government contractors would be insane to operate in California (and perhaps other regulatory hell-holes, but I am familiar with California).  California has a myriad of arcane labor laws (like break laws and heat stress laws) that are difficult to comply with, combined with a legislature that shifts the laws every year to make it hard to keep up, combined with a regulatory and judicial culture that assumes businesses are guilty until proven innocent.  If state labor violations or suits lead to loss of business at the national level, why the hell would a contractor ever want to have employees in California?

Bader provides the numbers:

Whether a large company is sued for discrimination or labor law violations often has more to do with its location than whether it violated the law. A recent study shows that “California has the most frequent incidences of [employment-practices] charges in the country, with a 42 percent higher chance of being sued by an employee for establishments . . . over the national average. Other states and jurisdictions where employers are at a high risk of employee suits include the District of Columbia (32% above the national average) [and] Illinois (26%).” It’s because of their location, not because California employers are more racist or anti-union than employers in other states (indeed, California employers spend more time and money on compliance mechanisms than employers elsewhere).

He goes on to discuss what I think is actually is a bigger issue than differential penalties, which is the criminalization of things in California that are perfectly legal in other places.  The best example is lunch breaks.  Companies don't just have to provide lunch breaks, they have an affirmative responsibility to make sure an employee takes a non-working lunch.  An employee who voluntarily does some work while taking a lunch break (e.g. answers a question from a customer that might walk up to her) makes the company liable for a penalty.  I kid you not.  That is why California corporations have sometimes made it a firing offense to be caught doing work at lunch, because it makes the company liable under the law.

Apparently there is yet another executive order with far reaching consequences for government contractors, Executive Order 13673  (does it bother anyone else that we are up in the 13 thousands on these?  Did they start numbering at 1?)  Hans Bader has the details:

A July 31 executive order by President Obama will make it very costly for employers to challenge dubious allegations of wrongdoing against them, if they are government contractors (which employ a quarter of the American workforce). Executive Order 13,673 will allow trial lawyers to extort larger settlements from companies, and enable bureaucratic agencies to extract costly settlements over conduct that may have been perfectly legal. That’s the conclusion of The Wall Street Journal and prominent labor lawyer Eugene Scalia.

This “Fair Pay and Safe Workplaces” order allows government officials to cut off the contracts of contractors and subcontractors that do not “consistently adhere” to a wide array of complex labor, antidiscrimination, harassment, workplace-safety and disabilities-rights laws. Never mind that every large national business, no matter how conscientious, has at least one successful lawsuit against it under federal labor and employment laws, which is inevitable when a company has thousands of employees who can sue it in hundreds of different courts that often have differing interpretations of the law. The order also bans using perfectly legal arbitration agreements, overstepping the President’s legal authority.

I can say as someone who absolutely bends over backwards to be in compliance, it just is not possible to be totally clean.  We have won most all of the lawsuits and actions against us over the years vis a vis labor laws and related charges.  A lot of these are pro forma discrimination charges that some employees in protected groups file automatically when terminated, usually without any evidence of specific discrimination.  We have, to date, won all of these "was he a Hispanic that was terminated rather than he was terminated because he was Hispanic" suits.  We have only lost one case.  To give you an idea of how hard it can be to be 100% in compliance, let me describe it:

We had a government contract governed by the Service Contract Act, which sets out minimum wages to be paid for different types of jobs.  These wages typically are in two parts - a base wage and, if the company does not have benefits, a fringe payment in lieu of such benefits.  For example, it might say that a day laborer must be paid (I will use round numbers for simplicity) $12 an hour base wages plus $4 an hour for fringes.  So we paid the worker $16 and hour and felt ourselves in compliance.  

Then we had a Department of Labor audit.  The investigator insisted that the law required that we break these two payments into two lines on the paycheck.  So instead of having  a paycheck that said 40 hours times $16, it needed to say 40 hours times $12 and 40 hours times $4.  Thus we were found to be in violation and issued a huge fine.  I protested that the law said no such thing -- the law said I had to have a clear paper trail of what I paid people.  It did not say the labor and fringes had to be shown separately on the paycheck, nor did any DOL published regulation require this  (and of course I also pointed out that the intent of the law that someone get paid a minimum amount had been fulfilled).  

Apparently, the DOL had an internal handbook that suggested this as a correct practice, but this had never been tested in court nor embodied in a published regulation.  To impose the fine, my attorney said they had to take me to court.  I said go for it.  The DOL chose not to press the case, and we adjusted our paycheck practices to avoid the issue in the future.  I was happy to comply with this, as stupid as it was, but it was impossible to know it was an actual requirement until I got busted for violating this double-secret practice.  But there it is on my record - VIOLATION!

I will leave it to Bader's article to explore some of the implications of this order, but I want to add some unintended(?) consequences of my own:

• Government contractors would be insane to operate in California (and perhaps other regulatory hell-holes, but I am familiar with California).  California has a myriad of arcane labor laws (like break laws and heat stress laws) that are difficult to comply with, combined with a legislature that shifts the laws every year to make it hard to keep up, combined with a regulatory and judicial culture that assumes businesses are guilty until proven innocent.  If state labor violations or suits lead to loss of business at the national level, why the hell would a contractor ever want to have employees in California?
• I have a couple of smaller competitors who have sent employees into the parks we operate who then filed extensive, manufactured complaints to the government about our service, timed to make it difficult on us when we bid against them for the contract renewal.  How tempting will it be for companies to place employees in their rival who then file serial labor complaints to undermine that rival in future contract awards?
• Companies that do government contracting as a sideline are going to be driven out of the business, reducing the choice and competition among contractors.   Earlier I discussed how 41 CFR 60-2.1  and 41 CFR 60-4.1, also the result of an Obama executive order, drove our company out of our last incidental contracting business (though we deal with the government all the time, it is generally through concession contracts where we get paid by the public, not by the government, so a lot of government contracting law does not apply to these contracts).

An Obama Administration executive order / regulation (hard to tell the difference any more)

Department of Labor
29 CFR Part 10
Establishing a Minimum Wage for Contractors; Proposed Rule

34568 Federal Register / Vol. 79, No. 116 / Tuesday, June 17, 2014 / Proposed Rules

This document proposes regulations to implement Executive Order13658, Establishing a Minimum Wage for Contractors, which was signed by President Barack Obama on February 12, 2014.

The Executive Order therefore seeks to increase efficiency and cost savings in the work performed by parties that contract with the Federal Government by raising the hourly minimum wage paid by those contractors to workers performing on covered Federal contracts to: $10.10 per hour, beginning January 1, 2015; and beginning January 1, 2016, and annually thereafter, an amount determined by the Secretary of Labor.

Liberal and leftish economists in the audience, please explain the line in bold.

The administration wants to apply this to concessionaires as well.  This will force us to raise a $20 camping rate by $4 a night.

After famously throwing out 200 years of bankruptcy law to hose secured creditors in favor of uni0ns at GM and Chrysler, the Obama Administration is again bailing out the unions that helped get him elected

Barely 15 percent of all construction-industry workers in the United States are union members, while the remaining 85 percent are nonunion, according to the U.S. Department of Labor's Bureau of Labor Statistics. So why has President Obama signed Executive Order 13502 directing federal agencies taking bids for government construction projects to accept only those from contractors who agree in advance to a project labor agreement that requires a union work force? Obama's new order applies to all federal construction projects with price tags of $25 million or more, and it means all such contracts will only be awarded to companies with unionized work forces.

The costs of this to the public are pretty obvious, not only in terms of fairness but in increased costs and reduced competition.

Another factor helps explain Obama's willingness to sign an executive order that will put millions more tax dollars in union coffers. Mix points out that unions under PLAs typically exact agreements that include requiring contractors to make payments to union pension funds. This is an increasingly urgent issue, as the Washington Examiner's Mark Hemingway has recently detailed in these pages. According to Labor Department filings, the average union pension has only enough money on hand to cover 62 percent of the benefits it has promised to union members. Pension plans with 80 percent funding are considered "endangered" by federal auditors, while those with less than 65 percent funding are put on the "critical" list. With this latest executive order, it's clear that Obama intends to give unions on the critical list a massive dose of federal tax dollars to cure what ails them.

I'll keep saying it - this is right from the playbook of the European-style corporate state.

Hollywood delivered for Obama in the last election, and he is ready to pay them back.  The world's most open and honest administration is again using closed hearings and executive fiat to force legal changes that likely would create a firestorm of controversy in a normal legislative process.

It's hard to know, then, which is more appalling: the fact that the Obama Administration has conducted the ACTA negotiations in secret, or that it has indicated that it plans to adopt the final Agreement as an "Executive Order," one that does not require submission to or ratification by the Senate (or any Congressional action whatsoever) to become effective. ...

But even this summary makes it clear that, once again (see Clinton Administration) the Democratic Party has caved in to Hollywood's demands regarding intellectual property enforcement. As David Fewer of the Canadian Internet Policy and Public Interest Clinic and the University of Ottawa noted, "if Hollywood could order intellectual property laws for Christmas what would they look like? This is pretty close."