Jottings By An Employer's Lawyer |
Tuesday, March 25, 2014
How Disruptive Can an Aggressive NLRB Be in a Non-Union Setting? More Than You Might Think
But if it does, then according to the NLRB, now buttressed by the 5th Circuit Court of Appeals, you are in violation of the NLRA because that policy infringes on employees Section 7 rights. Flex Frac Logistics v. NLRB (5th Cir. 3/24/14).Confidential InformationEmployees deal with and have access to information that must stay within the Organization. Confidential Information includes, but is not limited to, information that is related to: our customers, suppliers, distributors; [Company] organization management and marketing processes, plans and ideas, processes and plans, our financial information, including costs, prices; current and future business plans, our computer and software systems and processes; personnel information and documents, and our logos, and art work. No employee is permitted to share this Confidential Information outside the organization, or to remove or make copies of any [Company] records, reports or documents in any form, without prior management approval.Disclosure of Confidential Information could lead to termination, as well as other possible legal action. The 5th Circuit review of the Board's decision finding a violation is straightforward:
And less you think this is the opinion of some of the newer members of the 5th Circuit who might have a more liberal bent, the opinion is authored by Chief Judge Stewart and joined by Judges Higginbotham and Jones.
Confidentiality clauses are just one area of personnel policies that the new NLRB is putting under strict scrutiny. All employers, but particularly non-union employers, need to realize that there is a new entity around, and that not all its actions will be upended by the courts.
Comments:
Post a Comment
Monday, March 10, 2014
5th Circuit Short Circuits Plaintiff's Use of State Court
In Taylor v. Bailey Tool & Manufacturing (5th Cir. 3/10/14), plaintiff originally filed suit in state court alleging only violations of the Texas anti-discrimination statute. Unfortunately, for the plaintiff, the claim was not timely filed. Later plaintiff amended to add Title VII and a Section 1981 claim. Defendant removed and moved to dismiss arguing all claims were untimely. Both parties agreed that the state claims were untimely. Both parties also agreed that whether the federal claims were timely depended on whether Federal Rule of Civil Procedure 15(c) or the Texas relation back rule, TEX. CIV. PRAC. & REM. CODE ANN. § 16.068 applied. If Rule 15(c) applied, the federal claims, even though filed after the federal statute of limitations would be timely because they would relate back to the filing of the original claim. On the other hand, if the Texas rule applied, they would not be timely because § 16.068 prohibits relation back if the cause of action would have been subject to a plea of limitation when filed. The 5th Circuit joined the two other circuits (the 6th and 9th) that had ruled on this matter, holding that the state rule applied, thus barring the claim. The net result is that plaintiffs will have to make sure that their state claim is timely if they want to avoid federal court. A simple and straight forward, but important, holding.
Comments:
Post a Comment
How Much Would it Take to Wet Your Whistle?
It seems quite likely that headlines like that are apt to make many think that rather than continuing to work as an assistant vice president, as Keith Edwards did before reporting that JP Morgan was submitting mortgages for FHA and VA approval that did not qualify, and apparently not notifying the government that its own internal review had disclosed the problem, that it might make sense to play a new version of the lottery.
Couple that with the Supreme Court's decision last week expanding the reach of yet another major whistle-blowing statute, Supreme Court Exapnds Scope of Sarbanes-Oxley Whistleblower Liability, and employers and their counsel just have more to think about.
Comments:
Post a Comment
|
|
![]() |
WWW Jottings |