Stealing Confidential Information, Quirky Question # 78

Quirky Question # 78:

I am the HR Director at our company.  I just learned that one of our most valuable employees has resigned and taken a position with a competitor.  I requested our IT Department to make an evaluation of his computer.  They reported to me that before he left, he emailed to himself and his new employer customer and rate information  We consider that information to be highly sensitive, potentially providing our ex-employee the chance to divert a significant portion of our business to his new employer.

Most of our employees have non-competition agreements but, as it turns out, the employee who just quit never signed one.  I also doubt that we could claim the data he took is trade secret.  Unfortunately, we have not taken reasonable steps to protect the confidentiality of this information.  Are we out of luck?

[Readers: The question below was posed to my partner, Nick Akerman, who works in Dorsey's New York office. Nick, an expert on the Computer Fraud and Abuse Act, provides the following analysis. If you would like to communicate with Nick, don't hesitate to contact him at 212.415.9217 or akerman.nick@dorsey.com. More information about Nick is available on our firm's Website; see http://www.dorsey.com/akerman_nick/. Regards, Roy]

Nick’s Analysis:

As you recognize, your company’s position would be enhanced either if: a) your employee had executed an agreement containing post-employment restrictive covenants such as a non-compete or non-disclosure obligation, or b) your company had taken appropriate steps to protect the confidentiality of the data so that you could seek protection pursuant to the Uniform Trade Secrets Act. Despite the unavailability of potential contract or statutory claims based on these legal theories, however, you are not out of luck.

When data has been stolen, a company also has the option under the Computer Fraud and Abuse Act (“CFAA”) to file a lawsuit in federal court for injunctive relief and damages. Title 18, U.S.C.§ 1030. The injunction can direct the employee and his new employer to return the stolen data and prevent the employee and his new employer from contacting the customers who are the subject of the stolen data. In other words, you may be able to obtain the same relief as if your employee had a valid restrictive covenant requiring him not to conduct business with your customers.

Primarily a criminal statute, the CFAA provides that “[a]ny person who suffers damage or loss by reason of a violation of this section may maintain a civil action against the violator to obtain compensatory damages and injunctive relief or other equitable relief.” § 1030(g). Because it is a federal statute, you can file in federal court. (State causes of action for theft of trade secrets and breach of a restrictive covenant cannot be filed in federal court unless there is diversity of citizenship or there are other federal claims.)

The CFAA was enacted in 1984 as a criminal statute to criminalize the theft of national security and banking data. In 1992 it was amended to include the ability for an individual injured by a violation of the statute to bring a civil action, much like the Racketeer Influenced and Corrupt Organizations (“RICO”) statute, Title 18, U.S.C. § 1961, et seq. The CFAA has since been amended a number of times to keep up with new technologies and the ubiquity of computers in society. The CFAA was last amended in 2001 in the U. S. Patriot Act to include computers located outside the United States if they communicate with the United States or are involved in commerce with the United States.

The CFAA outlaws the entire panoply of computer crime including stealing computer data. There is no need to show that the data is trade secret protected, copyrighted, confidential or proprietary. Rather, one of the key elements necessary to prove a CFAA civil action, as explained in more detail below, is to show that the employee accessed the company computer without authorization or exceeded the authorization he had been granted.

As a jurisdictional prerequisite to filing a civil CFAA action, the plaintiff company must allege and ultimately prove $5,000 in loss. “Loss” is defined by the CFAA as

“any reasonable cost to any victim, including the cost of responding to an offense, conducting a damage assessment, and restoring the data, program, system, or information to its condition prior to the offense, and any revenue lost, cost incurred, or other consequential damages incurred because of interruption of service.”

The “federal courts have sustained actions based on allegations of costs to investigate and take remedial steps in response to a defendant’s misappropriation of data.” Modis, Inc. v. Bardelli, 531 F. Supp. 2d 314, 320 (D. Conn. Jan. 22, 2008). Such costs must of course relate to the computer. In Nexans Wires, SA 319 F.Supp. 2d 468, (S.D.N.Y 2004), aff’d, 166 Fed. Appx. 559, 562-63 (2d Cir. 2006), for example, the court held that $8,000 spent by two corporate executives to fly to Manhattan from Germany to examine the computer intrusion and discuss the breach at the French restaurant Le Cirque did not qualify for the $5,000 loss because the expense was not sufficiently related to the company computer.

The CFAA encompasses what it defines as a “protected computer.” The CFAA’s definition of protected computer, however, covers every conceivable type of computer. § 1030(e)(1). As the defendant rightly claimed in United States v. Mitra, 405 F. 3d 492, 495 (8th Cir. 2005), “[e]very cell phone and cell tower is a ‘computer’ under this statute’s definition; so is every iPod, every wireless base station in the corner coffee shop, and many another gadget.”

Four of the seven causes of action under this statute require proof that the person who accessed the computer did so “without authorization or exceeding authorization.” Title 18, U.S.C., §§ 1030(a)(2), (a)(4), 5(A)(ii), and 5(A)(iii). The courts have acknowledged that the difference between unauthorized access and exceeding authorized access is “paper thin.” Inter’al Airport Centers, LLC v. Citrin, 440 F.3d 418, 420 (2006). For example, in the employee/employer context an employee is authorized to access the company computers to perform work for the company but exceeds that authorization when the computer is accessed to steal data for a competitor. Lack of authorization, as interpreted by the courts, can be established in four separate ways.

First, lack of authorization can be shown when an employee violates his agency relationship with his employer by accessing the employer’s computer for a purpose that is contrary to the interests of the employer. It is the breach of the “duty of loyalty” that terminates “the agency relationship “and with it” the “authority to access” the computer. Citrin, 440 F.3d at 420-21. In Citrin, the defendant employee Citrin used an erasure program to destroy data on his employer’s computer immediately prior to his resignation from the company to join a competitor. Thus, the court found that Citrin’s authorization to access the computer terminated when he “resolved to destroy files that incriminated himself and other files that were also the property of his employer.” Citrin, 440 F.3d at 420.

The agency theory upon which authorization is based is not universally accepted by the lower courts. There are at least five reported federal district court decisions that have refused to adopt the agency standard as a predicate to an employee’s authorization to use an employer’s computers. These district courts take the simplistic view that if the employee was authorized to use the employer’s computer, he was authorized to use if for all purposes. Thus, even if the employee accessed the computer to steal the employer’s data, the employee did not violate the CFAA because the employee, as part of his duties, was authorized to access the computer.

For that reason, these courts ruled that the intent of the employee in accessing the computer was irrelevant to the question of authorization and that “the phrase ‘without authorization’ generally only reaches conduct by outsiders who do not have permission to access the plaintiff’s computer in the first place.” Shamrock Foods Co. v. Gast, 535 F.Supp.2d 962, 964-65 (D. Ariz. 2008); Diamond Power Intern., Inc. v. Davidson, Nos. 1:04-CV-0091-RWS-CCH and 1:04-CV-1708-RWS-CCH, 2007 WL 2904119, at *13 (N.D. Ga. Oct. 1, 2007); Brett Senior & Assocs., P.C. v. Fitzgerald, No. 06-1412, 2007 WL 2043377, at *2-4 (E.D. Pa. July 13, 2007); Lockheed Martin Corp. v. Speed, No 6:05-CV-1580-ORL-31, 2006 WL 2683058, at *5 (M.D. Fl. Aug. 1, 2006); Int’l Ass’n of Machinists and Aerospace Workers v. Werner-Masuda, 390 F.Supp.2d 479, 495 (D.Md. 2005).

None of the Circuit courts, however, have adopted this view of authorization, and this issue has not yet reached the Supreme Court. For example, the 11th Circuit in United States v. Salum, 257 Fed. Appx 225, 230 (11th Cir. 2007) upheld a criminal conviction for a violation of the CFAA, where the defendant employee was authorized to access the computer but did so for an improper purpose. In that case the court affirmed the criminal CFAA conviction of a police officer with the Montgomery Police Department, who had provided information from the FBI’s National Crime Information Center database to a private investigator. Although the defendant police officer “had authority to access the NCIC database” [just like any employee has the authority to access his company's computers] the Court held that there was sufficient evidence to convict on the element of lack of authorization because the defendant knew the information he accessed was to be used “for an improper purpose.” The court did not cite either the Diamond Power case or Lockheed Martin the two district court cases from the 11th Circuit which dismissed CFAA civil cases finding that the defendants’ motive in accessing the computers had no bearing on whether the access was authorized. Nonetheless, Salum effectively overruled these two lower court cases.

Second, the limits of authorization to access a computer can be set by agreement. In EF Cultural Travel BV v. Explorica, Inc., 274 F.3d 577, 583-84 (1st Cir. 2001) the court upheld a preliminary injunction entered by the district court based on a violation of the CFAA because the defendants, all former employees of the plaintiff, had accessed and downloaded pricing data on EF Cultural’s website by violating their confidentiality agreements with EF Cultural. In that case the former employees used EF Cultural’s confidential information concerning its public website to create an automatic robot to download from the website all 154,293 prices for high school tours in a two-day period.

Third, lack of authorization can be established by a violation of company rules and policies. The CFAA is a unique statute in the sense that it allows companies to set the rules that form the predicate for a violation of the statute. In EF Cultural Travel BV v. Zefer Corp., 318 F.3d 58, 63 (1st Cir. 2003), the court recognized that the “CFAA . . . is primarily a statute imposing limits on access and enhancing control by information providers.” Thus, a company “can easily spell out explicitly what is forbidden.” Id. at 63. Doe v. Dartmouth-Hitchcock Medical Center, 2001 WL 873063 *2 (D.N.H. 2001) provides a clear example of the critical nature of promulgating workplace rules for accessing data. In that case, the court interpreted “unauthorized access” based on the hospital’s Graduate Medical Training Manual which contained “policies governing the confidentiality of patient records, which generally prohibit interns and Fellows, like . . . [the Defendant] from accessing patient records absent a ‘professional ‘need to know.’” Based on these policies, the court found that the defendant, who was a resident in psychiatry at the Dartmouth hospital, “was granted only limited access to Dartmouth’s computerized patient records” and this limitation was imposed “for the very purpose of protecting patient confidentiality.” Id. at *5.

A patient whose records had been allegedly viewed by a hospital intern for reasons unrelated to treatment sued the hospital and the intern for violations of the CFAA. The court dismissed the CFAA claim against the hospital finding that it had been victimized by its “own policies.” Id. at * 5. For that reason it would be inconsistent with the purpose of the CFAA “to protect computer systems . . . from unauthorized access and concomitant damage – to find the hospital was vicariously liable for the actions of the resident.” Id.

Fourth, the courts have found that access is without authorization when it exceeds the expected norms of intended use of the computer. In United States v. Phillips, 477 F.3d 215 (5th Cir. 2007) a student at the University of Texas was provided access to a school secured network through a password consisting of his Social Security number. The student, however, used what is known as “’brute-force attack program’ which automatically transmitted to the website as many as six Social Security numbers per second, at least some of which would correspond to those of authorized . . . users.” Id. at 218. This program allowed Phillips “[o]ver a fourteen-month period” to gain “access to a mother lode of data about more than 45,000 current and prospective students, donors, and alumni.” Id. The court upheld the student’s criminal conviction under the CFAA, finding that his access to the computer was not authorized because the “brute force attack” exceeded the expected norms of intended use of the computer.

In sum, the CFAA provides your company a legitimate basis on which to seek redress for the wrongful conduct of your former employee, given that he used your company’s computers to copy critical customer and rate information, and forwarded that data to both himself and his new employer. Other claims may be available to your company as well, such as a claim for breach of fiduciary duty, or a claim based on your state’s unfair competition laws. In the future, however, you can further enhance the protections for your company by ensuring that all appropriate employees execute the agreement containing your post-employment restrictive covenants. Similarly, as you recognize, it would be prudent for your company to take appropriate measures to ensure that your company’s confidential information is treated in a manner that ensures protection under the Uniform Trade Secrets Act.

Discrimination Based on Inter-Racial Marriage, Quirky Question # 77

Quirky Question # 77:
One of our employees, who is Caucasian, recently complained that his manager has been treating him unfairly in a variety of ways.  He claims that his manager is discriminating against him because he is married to an African American woman.  Putting aside the issue of whether the manager actually is treating him unfairly, does Title VII even encompass discrimination on the basis of inter-racial marriage?

Roy’s Analysis:
 
The specific question you posed was, “Does Title VII . . . encompass discrimination on the basis of inter-racial marriage?”  Your lead-in to that question, however, (“Putting aside the issue of whether the manager actually is treating him unfairly . . ..”) is somewhat troubling. 

As I have suggested in other Blog analyses, employment issues often implicate at least two fundamental issues – what is legally permissible and what is right in a broader, ethical sense.  Frequently, the legal and ethical analyses align but that is not always true.  Sometimes, the law lags behind.

The starting point for my analysis, therefore, would be to ask you a question – if you assumed that Title VII did not prohibit discrimination based on inter-racial relationships, how would your company address this situation?  I would hope that your response would be that your company would promptly and carefully investigate this situation, and if it determined that your managerial employee was treating your other employee unfairly or discriminatorily based on his inter-racial marriage, institute appropriate disciplinary action.  Depending on the facts elicited in your company’s investigation, the appropriate discipline may well be discharge.

If your company’s reaction was the opposite, i.e., ‘if it’s not illegal, we’re not going to act,’ I’d simply ask, “Why not?”.  Do you really want to employ a managerial employee who is so bigoted that he would treat one of your other employee’s unfairly simply because he is married to a woman of another race?  Do you believe that denying equal opportunities to an employee based on the race of his marriage partner, rather than his intellect, diligence, integrity, work ethic, or any other performance-related factors, would likely contribute to a more competent and effective workforce? 

Another factor for your consideration is how a biased decision-maker (and the biased decisions he makes) is likely to affect the morale of your company’s workforce?  How would your minority employees react to this type of decision-making?  Or, as a corollary issue, would you have confidence that someone who discriminates against one of your employees based on the race of his spouse would be likely to treat your minority employees equitably? 

Finally, situations that implicate fundamental questions relating to racial equality or that smack of unfairness are likely to lead to litigation.  Play out this scenario from a pessimistic perspective.  Imagine airing the issues relating to your company’s treatment of minorities and/or majorities married to minorities in court.  Or in the newspaper or other public media.  Would you be comfortable with how your company would be portrayed? 

Well, enough of my posing questions back to you; let me turn to the legal question you asked.  The issue of whether Title VII reaches individuals involved in inter-racial marriages is a question that the courts have addressed periodically since Title VII was passed in 1964.  As you may have guessed, the judicial analyses in the late-60s and ’70s found that Title VII did not reach this type of discrimination.  In the earlier decisions, the courts noted that Title VII’s prohibition (“unlawful . . . for an employer . . . to discharge any individual . . . because of such individual’s race” 42 U.S.C. § 2000e-2(a)(1)), simply did not extend to discrimination based on those with whom the adversely affected employees (typically, Caucasian) associated, whether by marriage or otherwise. 

More recently, however, the judicial analysis has shifted.  Courts in a number of jurisdictions have held that Title VII reaches discrimination based on an employee’s marriage to a member of another race.  A good example of such a decision is the case of Holcomb v. Iona College, No. 06-3815-cv (2d Cir. April 1, 2008).   Interestingly, a number of courts that have explored this type of associational discrimination have concluded that the discriminatory conduct falls squarely within Title VII’s proscription of discrimination based on the “individual’s race.”  For example, as one court held, “Plaintiff has alleged discrimination as a result of his marriage to a black woman.  Had he been black, his marriage would not have been interracial.  Therefore, inherent in the complaint is the assertion that he has suffered racial discrimination because of his own race.”  Rosenblatt v. Bivona & Cohen, P.C., 946 F. Supp. 298, 300 (S.D.N.Y. 1996).  The Second Circuit adopted this same analysis: “We reject this restrictive reading [i.e., statute does not reach this conduct] of Title VII.  The reason is simple: where an employee is subjected to adverse action because an employer disapproves of interracial association, the employee suffers discrimination because of the employee’s own race.”  (Emphasis in original.)

The Holcomb facts are interesting and highlight a few of the points I referenced above.  In that case, Iona College terminated the employment of two of its three assistant basketball coaches.  One of these coaches (Holcomb) was married to an African American woman.  The other coach who was fired was African American.  The one assistant coach who was retained, the most junior of the three, was Caucasian.  As part of Holcomb’s allegations, he cited to a variety of crude racist comments made by one of the individuals involved in the decision to terminate him, the school’s former Athletic Director (since promoted to one of three Vice President positions at the college).  Typical of many discrimination cases, several other individuals who had heard this individual make racially insensitive remarks also came forward with this evidence.  Needless to point out, these well-publicized facts cannot be beneficial to Iona College.

Despite the evidence adduced by Holcomb, the District Court granted the College’s summary judgment motion.  Though the District Court found that Holcomb had established a prima facie case of discrimination, the lower court also found that the College had advanced non-discriminatory reasons for its discharge decision (the poor performance of the basketball team, the off-court problems of the players, etc.). 

In reversing the summary judgment grant, however, the Second Circuit emphasized that in a mixed motive case, the plaintiff is not required to prove that the employer’s stated reason was a pretext for discrimination.  “A plaintiff alleging that an employment decision was motivated both by legitimate and illegitimate reasons may establish that the ‘impermissible factor was a motivating factor, without proving that employer’s proffered explanation was not some part of the employer’s motivation.’” (Citations omitted.)  The appellate court concluded that Holcomb had come forward with sufficient evidence to present his case to the jury and that the jury could find that the College’s proffered reasons for its actions were not credible.

In sum, if your investigation reveals that your manager truly is discriminating against your employee because he is married to an African American woman, I think your company would be justified in terminating this individual.  And, if your company elects not to take this action, as the Holcomb decision and other cases demonstrate, you soon could be defending a Title VII lawsuit.  Many courts have held that Title VII reaches this type of discriminatory conduct. 

In Holcomb, the Second Circuit stated, “We hold, for the first time, than an employer may violate Title VII if it takes action against an employee because of the employee’s association with a person of another race.”  As the appellate court pointed out, the Fifth, Seventh and Eleventh Circuits agree.  Similarly, the Second Circuit observed that the District Courts within the circuit that had addressed this issue had determined that Title VII reached this type of discriminatory conduct.

Downsizing and Foreign Nationals, Quirky Question # 76

Quirky Question # 76:
 
I read with interest your analysis of alternatives to layoffs [Quirky Question # 71].  We have a slightly different issue.  Like many companies, we are facing the difficult prospect of downsizing staff.  We are a small technology company with operations in the US and an office abroad.  Among our professional staff are a number of foreign nationals with a veritable alphabet soup of immigration statuses.  We have a permanent resident, a couple of H-1B’s, and L-1A, an L-1B, a TN and an F-1 foreign student thrown in for good measure  If we lay off or reduce the hours or salaries of these individuals are there any special considerations we need to think about from an immigration perspective?

[Readers:  Although I have been practicing employment law for many years, the sub-specialty of immigration law is outside my area of expertise.  Fortunately, two terrific Minneapolis colleagues of mine, Saiko McIvor and Craig Peterson, have practices devoted exclusively to immigration issues.  Saiko is 1976 graduate of the University of Washington and a 1984 graduate of the Golden Gate University School of Law.  For more information on Saiko, go to http://www.dorsey.com/mcivor_saiko/.  Craig is 1987 graduate of Moorhead State University, a 1992 graduate of William Mitchell College of Law, and a 2001 graduate of the University of Minnesota (M.A.).  For more information on Craig, go to http://www.dorsey.com/peterson_craig/  Quirky Question # 76 was posed to Craig; his analysis is set forth below.  If you have any questions about the analysis below, don’t hesitate to contact Craig at peterson.craig@dorsey.com,  or 612.492.6766.  Regards, Roy]  

Craig’s Analysis:

Changes in employment, such as layoffs, changes in duties or salaries can expose employer and employee alike to variety of risks, or no risk at all, depending on the type of immigration legal status involved. The question posed listed a variety of immigration variants.  Let’s look at each status in turn.

Lawful Permanent Residents.

Also known as “green card” holders, these individuals are able to live and work indefinitely in the United States.  Generally, employers may treat US permanent residents as they would a US citizen worker.  A layoff, reduction in salary or hours, re-assignment or other change in employment does not typically affect a permanent resident differently than it would a US citizen, or raise any special considerations for the employer.  This is true even if the foreign national has acquired permanent residence based upon an offer of permanent employment, and it is the sponsoring employer which is later terminating employment.  In employment-based permanent residence processes, both employer and employee must intend permanent employment when the application is filed, and when approved.  Subsequent events, such as downsizing by the employer or discovery of a more attractive job offer by the employee can result in termination of employment without risk to the employer or to the employee’s immigration status.

H-1B’s. 

The H-1B is a temporary immigration status for “specialty occupations” which commonly means employment for which a Bachelor’s degree or equivalent is a minimum requirement for entry into the occupation.  There are employer and employee risks which arise with significant changes in H-1B employment.  Every H-1B petition rests in part on a Labor Condition Application (LCA), a US Department of Labor tool intended to protect wages and working conditions for US workers competing with foreign nationals for positions suitable for H-1B classification.  The LCA is a collection of attestations, or promises, made by the employer regarding the employment circumstances.  The Department of Labor has enforcement authority to ensure compliance with employer attestations made on the LCA.  Chief among the attestations is the employer’s promise to pay the prevailing wage for the occupation or the employer’s own wage, whichever is higher.  This obligation continues throughout the time period for which the LCA was certified and the related H-1B was granted.  An employer may not simply reduce the earnings of an H-1B employee without risking sanction by Department of Labor, typically in the forms of fines and back pay.  It is possible to change the level of employment from full time to part time, by filing of an amended H-1B petition with the US Citizenship & Immigration Services (US CIS) accompanied by a new LCA reflecting part-time employment.  In fact, this is the best approach to making a key H-1B employee less expensive to retain, despite the transactional costs incurred in filing an amended H-1B.

What about termination?  H-1B regulations do not prohibit terminations, but termination prior to the end date of the approved H-1B petition raises two employer obligations. The first is notice to US CIS that the employment has terminated.  While US CIS regulations do not provide for a penalty for failure to notify the agency of a termination, the Department of Labor has hinted it would take the extraordinary position that the employer’s obligation under the LCA  to pay the H-1B wage continues even after termination, unless the employer makes the notification to US CIS. The second employer obligation is to pay the cost of returning the H-1B employee to his or her home country. If the employee goes home as the result of termination, the employer has the obligation of paying the travel expense.  The obligation does not extend to transportation of household goods or dependent travel however. Also, the obligation does not arise if the employee does not go home, but instead chooses to look for another H-1B employer in the United States, or chooses to apply for a different type of visa, or chooses to remain in the US without legal status.

An H-1B employee who is terminated loses his/her immigration legal status immediately upon termination, and consequently loses the right to remain in the US.  From the employee’s perspective, it is helpful if an employer provides as much notice as possible, allowing the employee to search for another H-1B sponsoring employer, or to change to a different immigration legal status.

L-1A and L-1B 

These are intra-company transferees, for companies which have parent, subsidiary, branch or other affiliated offices outside the United States.  The L-1A is for executives and managers, while the L-1B is for workers who have specialized knowledge of the company’s products or processes.  Unlike the H-1B, there is no Labor Condition Application for L-1′s, hence no wage or working condition attestations enforced by the Department of Labor. The hours or earnings of an L-1 employee may be reduced without violating immigration laws or regulations applicable to the L-1 category.  A termination of employment would result in the loss of immigration status for the employee, but the L-1 regulations impose no specific requirement on the employer’s part to notify US CIS of the termination or to pay the cost of returning the employee home, as is the case with H-1B’s.  Other changes, such as changes in employment duties or relationships between the US and foreign affiliated entity may require an amended petition, however.

TN 

This is a temporary employment visa available to Canadian and Mexican citizens as part of the North American Free Trade Agreement (NAFTA.)  The treaty contains a list of approved occupations for which TN classification may be granted.  The regulations governing TN classification do not require any notice to US immigration agencies of termination or reduction in pay, nor do the regulations impose any requirement upon employers to pay the cost of returning the terminated employee home.  Termination of employment results in the employee’s loss of immigration status however.

F-1 

This is the most common type of foreign student visa. There are several types of work authorization available to students with F-1 visas, and recent graduates typically are authorized to engage in post-completion “optional practical training” (OPT) with off-campus employers. The usual duration of post-completion OPT is 12 months.  There are no employer wage or other attestations associated with F-1 work authorizations, nor is there a general requirement to report terminations or other changes in employment in most cases.  A new variant of OPT, for graduates in science, technology, engineering or mathematics programs (so-called STEM graduates) permits these graduates to apply for an extension of 17 months of post-completion OPT, for a total of 29 months.  In order to qualify for the additional 17-month extension however, the employee must show his/her employer is enrolled in the Department of Homeland Security’s E-Verify system. If an employer is enrolled in E-Verify, and employs a STEM graduate on OPT during this 17-month period, the employer is obligated to report termination of the student’s employment to the school’s designated school officer.  The reporting and E-Verify requirements are conditions of the additional 17-month extension available to STEM graduates, and do not apply to the initial 12-month grant of OPT.  Termination of OPT employment does not trigger any requirement for the employer to notify US CIS or to pay the cost of returning the student home.

An F-1 student whose employment is terminated or whose compensation is reduced does not necessarily lose his/her immigration status. The regulations governing OPT permit up to 90 days of unemployment during the initial 12-month grant of OPT, and a total of 120 days’ unemployment during the 29-month period available to a STEM graduate.

 

California Oddities, Quirky Question # 75

Quirky Question # 75:

We are a California employer and were just hit with a lawsuit by a former employee for acts that supposedly took place almost three years ago.  Our former employee alleges that in January 2006, his supervisor asked him to fire three Asian-Americans who work in an otherwise all Caucasian department.  The former employee alleges that he refused to follow his supervisor’s directive and did not fire anyone.  (Incidentally, this was the same supervisor who hired the employee who now is suing us.)

Our former employee also contends that from January 2006 through January 2008, he received very poor performance evaluations from his supervisor, which he attributes to his unwillingness to fire the three Asian-American employees.  Despite his “belief” about the supposed link between his performance reviews and his refusal to fire anyone, he never complained to our Human Resources Department or anyone on our management team.  He claims he had conversations about his supervisor’s behavior with one of his subordinates, an Assistant Manager who reported to him.

In February 2008, he quit without notice.  He immediately filed an administrative complaint with the Department of Fair Employment and Housing (DFEH), alleging race and age discrimination.  The DFEH conducted an investigation which ended in December 2008, and issued a right to sue letter soon thereafter.  We just were served with the Complaint, some three years after the primary incident on which his lawsuit is based.

First, can he file a race discrimination claim even though he is not Asian?  Second isn’t his lawsuit time-barred?  (I thought these types of lawsuits were limited to a one year statute of limitations.)  Finally, given that the employee did not take advantage of our very extensive internal complaint procedures (designed to address precisely these kinds of issues), doesn’t his failure to utilize this internal complaint process bar his claims?

[Readers:  The inquiries set forth in Quirky Question # 75 were posed to my colleague, Ed Raskin, in our Southern California office, which is located in Irvine.  Ed is a 2002 graduate of the University of California, Irvine, and a 2006 graduate of the University of California, Berkley, School of Law.  Ed's resume is available at:   http://www.dorsey.com/raskin_edward/.  If you have any questions about the issues addressed in Quirky Question # 75, don't hesitate to contact Ed by email at raskin.edward@dorsey.com, or by phone at 949.932.3602.  Regards, Roy]

Ed’s Analysis:

This is a complex scenario, so I think it would make the most sense if we treated each of your three questions separately:

Question 1

First, the broad question is asked: can a Caucasian can file a race discrimination claim even though he is not Asian, or part of any other ethnic minority for that matter?  The answer is yes.  Both federal law (Title VII) and California law (the Fair Employment and Housing Act (“FEHA”)) prohibit discrimination on the basis of race, color or national origin (among other bases).  Simply put, Caucasians are part of a specific race and their color happens to be white.  Therefore, an employer taking any adverse action against a person because of the employee’s status as a Caucasian, or any other race, does so in violation of the law.  Additionally, an employer may not take adverse action against any employee based on the color of the employee’s skin be it white, black or tan.  However, it is unlikely that your former employee will succeed in bringing such a claim because he supervised and works in an otherwise all Caucasian department.  He will have a difficult time proving that his Caucasian supervisor discriminated against him because he was Caucasian.   

Question 2

Second, the next question presented is whether this lawsuit is time-barred?  The answer is no, for two separate reasons.  The first reason is the continuing violations doctrine and the second is the rule of equitable tolling that applies to the FEHA.

The continuing violations doctrine permits an employee to bring a lawsuit for an employer’s unlawful conduct that begins before the limitations period and “continues” into the limitations period.  The California case on point is Richards v. CH2M Hill, Inc., 26 Cal. 4th 798 (2001).  In Richards the court explained that discrimination may occur as either an isolated one-time occurrence or as a continuous course of conduct taking place over a period of time.  In either case, the statute of limitations begins to run when the unlawful course of conduct ceases or when the employee is on notice that further efforts to end the unlawful conduct will be in vain. 

In 2005, the California Supreme Court affirmed and applied Richards in Yanowitz v. L’Oreal USA Inc., 36 Cal. 4th 1038 (2005), to a set of facts similar to the question submitted.  In Yanowitz, plaintiff sued her employer for failing to fire a female sales associate and replace her with someone more attractive.  Plaintiff refused to do so and thereafter alleged that plaintiff’s supervisor began criticizing her performance in written performance evaluations.  Notably, plaintiff never suffered a decrease in salary or benefits, nor was she ever fired or demoted.  More than one year after her supervisor began criticizing plaintiff’s work performance, she filed a complaint with the DFEH claiming that she was retaliated against for refusing to terminate an employee for an impermissible reason.  Applying Richards, the Court held that the supervisor’s criticisms and negative performance evaluations amounted to a continuing violation because the supervisor’s actions took place over time and amounted to a pattern of conduct.  Therefore, plaintiff’s lawsuit was not time-barred.

As applied to the question submitted, the actions taking place from January 2006 through January 2008 may amount to a continuing violation, effectively tolling the statue of limitations during that time.  Specifically, if your former employer can show that the poor performance evaluations he received over time were the result of his refusal to terminate the Asian-Americans because he thought that doing so was unlawful, then the continuing violations doctrine may apply.  In other words, every time your former employee received a poor performance evaluation based on his refusal to terminate in 2006, a new violation occurred connected to the 2006 event (i.e., the alleged refusal to terminate the three Asian-Americans).  This effectively makes the discriminatory conduct a pattern rather than one swift blow occurring from January 2006 to January 2008. 

Of course, the fact that the former employee never complained to Human Resources or anyone in the management team about his belief that he was receiving unfair and discriminatory performance evaluations cuts against such an argument.  Moreover, the company can argue that because these alleged discriminatory performance evaluations occurred over a two-year period, the unlawful conduct had reached a degree of permanency which put this former employee on notice that the unlawful conduct would not end.  If successful, this argument would stop the tolling of the statute of limitations on the date that the discriminatory conduct reached a level of permanency.  If the actions reached a level of permanency more than a year before your former employee filed his DFEH complaint (i.e., before February 2007), then the lawsuit would be time-barred.  Nonetheless, the Yanowitz case is a difficult hurdle to overcome.

As for the time period the DFEH was investigating your former employee’s complaint (February 2008 to December 2008), that time period is subject to equitable tolling.  Broadly speaking, equitable tolling is a judicially created principle designed to prevent a case from being disposed of on statute of limitations grounds when the defendant was provided timely notice of plaintiff’s claims.  As applied here, plaintiff is required to file a complaint with the DFEH prior to bringing suit in a civil action as provided by statute in the FEHA.  Therefore, California Courts have long held that the one year period for an employee to file a civil lawsuit is tolled until the DFEH completes its investigation. 

Question 3

The final question presented is whether the former employee must avail himself of the company’s internal complaint procedure prior to bringing suit?  Two recent California cases instruct that: (1) an employee is not required to utilize an employer’s internal complaint procedure before obtaining a right to sue letter from the DFEH if that process does not protect the employee’s due process rights to present evidence, and (2) the statute of limitations will be tolled while an employee utilizes an employer’s internal complaint procedure.

In Ahmadi-Kashani v. Regents, 149 Cal. App. 4th 449 (2008), the defendant employer argued that plaintiff’s lawsuit was barred because she initiated, but did not complete, a mandatory internal grievance process set forth in a collective bargaining agreement applicable to her.  The Court of Appeal found for plaintiff because the informal grievance procedure did not provide for a “quasi-judicial” hearing with sufficient due process and therefore the plaintiff was not required to see that process to completion before pursuing a claim with the DFEH. 

Next, in McDonald v. Antelope Valley Community College Dist., 45 Cal. 4th 88 (2005), defendant employer argued that plaintiff’s case was time-barred because she failed to file a DFEH complaint during the time period that she was participating in a voluntary internal complaint process.  The employer made the specific point that plaintiff was advised she could file her DFEH complaint while the internal complaint process was moving forward and that the internal complaint procedure was entirely voluntary.  The California Supreme Court disagreed with the employer and held that the statute of limitations was tolled during the time period that the voluntary internal complaint procedure transpired because the employer had adequate notice of the claim and refusing to toll the statute of limitations in such a situation would be fundamentally unfair. 

Thus, these two cases taken together instruct that an employer must likely pursue an internal complaint procedure through completion before filing a DFEH complaint when required by a collective bargaining agreement, so long as the internal procedure provides a “quasi-judicial” process for presenting evidence.  However, if the internal complaint process is voluntary, an employee need not see the process through to completion before filing a DFEH complaint.  In either case, the statute of limitations will be tolled because the employer is on notice of the former employees claims. 

In sum, the questions posed illustrate that it is entirely possible for events that occurred more than one year ago to give rise to a legal claim that is within the statute of limitations because of both the continuing violation and equitable tolling doctrines.  This situation should serve as a reminder to employers to keep good records beyond the one year statute of limitations when it comes to matters the employer believes may be subject of a lawsuit – even if it that lawsuit is filed several years down the line.

Of course, the fact that the former employee never complained to Human Resources or anyone in the management team about his belief that he was receiving unfair and discriminatory performance evaluations cuts against such an argument.  Moreover, the company can argue that because these alleged discriminatory performance evaluations occurred over a two-year period, the unlawful conduct had reached a degree of permanency which put this former employee on notice that the unlawful conduct would not end.  If successful, this argument would stop the tolling of the statute of limitations on the date that the discriminatory conduct reached a level of permanency.  If the actions reached a level of permanency more than a year before your former employee filed his DFEH complaint (i.e., before February 2007), then the lawsuit would be time-barred.  Nonetheless, the Yanowitz case is a difficult hurdle to overcome.

As for the time period the DFEH was investigating your former employee’s complaint (February 2008 to December 2008), that time period is subject to equitable tolling.  Broadly speaking, equitable tolling is a judicially created principle designed to prevent a case from being disposed of on statute of limitations grounds when the defendant was provided timely notice of plaintiff’s claims.  As applied here, plaintiff is required to file a complaint with the DFEH prior to bringing suit in a civil action as provided by statute in the FEHA.  Therefore, California Courts have long held that the one year period for an employee to file a civil lawsuit is tolled until the DFEH completes its investigation. 

 

Sarbanes-Oxley, Quirky Question # 74

Quirky Question # 74:

We have been having some performance issues with one of our mid-level marketing managers.  In October, we placed him on a performance improvement plan.  He has not been meeting the expectations established by the plan.  We are scheduled to meet with him about his performance again next week, and it is very likely that we will be moving him toward separation from the Company.  Yesterday, this individual complained to his manager that he was uncomfortable with the way that accounting manages travel receipts.  He reminded his manager about the Sarbanes-Oxley Act and noted that he wanted management to know that he was “blowing the whistle” on this accounting practice.  When pressed for details about his alleged concerns, the employee either could not describe what he found objectionable about corporate accounting’s handling of travel receipts or how he believes the process should be done.  It is obvious to us that he has no idea what he’s talking about and that this is just another way to try to avoid being terminated as a result of his performance issues.  We are a publicly-traded Company, so, of course, we have internal reporting and investigation procedures in place.  Must we really take this feeble “Sarbanes-Oxley complaint” seriously?

[Quirky Question # 74 was directed to my partner, Holly Eng, so her analysis is set forth below.  Holly is a 1989 graduate of St. Cloud State University and a 1993 graduate of the Georgetown University Law Center.  Holly has been practicing in the firm’s Labor & Employment Law Department since joining the firm following her graduation from Georgetown.  More information on Holly is available at http://www.dorsey.com/eng_holly/.  If you have any questions about QQ # 74, don’t hesitate to contact Holly at eng.holly@dorsey.com or 612.343.2164.  Regards, Roy]

Holly’s Analysis:

The short answer, particularly if yours is a publicly-traded company, is “yes”; you should take this complaint seriously and conduct an appropriate investigation (although what’s appropriate under these circumstances may be quite abbreviated).

While investigative processes vary among organizations, you should follow whatever corporate controls are in place within your organization and ensure that the Audit Committee of your Board of Directors receives any and all necessary information.

Moreover, you should ensure that no adverse employment action is taken against this employee because he asserted this complaint.  Of course, this does not mean that you should discontinue your performance-management activities.  You should continue to manage his performance, as necessary.  However, do not allow anything about this complaint to alter or enhance your performance-management activities in any way. 

By way of background, let me offer a few words about the Sarbanes-Oxley Act (“SOX”).  In response to highly-public whistleblower complaints, Section 806 of the SOX prohibits publicly-traded companies (and any officer, employee, contractor, subcontractor, or agent of such companies) from discharging, demoting, suspending, threatening, harassing, or otherwise discriminating against an employee because (1) the employee provides information or assistance to a Federal regulatory law enforcement agency, a Member of Congress or Congressional committee or the employee’s supervisor or other such person in the company who has the authority to investigate or terminate misconduct; and, (2) the employee reasonably believes the conduct at issue constitutes a violation of mail, wire, bank, or securities fraud laws, any rule or regulation of the SEC, or any provision of Federal law relating to fraud against shareholders.

There are a few things to keep in mind under the circumstances you’ve presented. 

First, the employee does not have to identify fraud correctly to be protected.  So long as the employee has provided information (to one or more the individuals listed in the Act) regarding conduct the employee “reasonably believes” constitutes a violation of various laws, the employee arguably falls within the gamut of the Act.  We may quibble about whether or not this employee has a “reasonable belief” that a violation exists.  However, it is difficult to know what someone is actually thinking, and any inquiry that an administrative body may do on this point is likely to be very fact intensive and to give the benefit of the doubt to the employee. 

Second, the individual’s simple statement that he is a “whistleblower” does not make it so.  If he does file a charge with the Occupational Safety and Health Administration (“OSHA”), (the division of the Department of Labor responsible for investigating and making final determinations with respect to whistleblower complaints under SOX), a “whistleblower” must be able to establish the following things to set forth a viable claim: 

            1.         He engaged in a protected activity (as defined by the Act);

            2.         The employer knew about (or reasonably suspected) the protected activity;

            3.         He suffered an unfavorable personnel action (in other words, something “bad” 
happened to his employment, such as a termination or demotion); and

            4.         There was a nexus between the unfavorable personnel action and the          protected activity sufficient to raise an inference that the whistle-blowing activity was a “contributing factor.”  

Third, notwithstanding a finding that these elements have been met, the Department of Labor will not proceed with an investigation if the employer demonstrates “by clear and convincing evidence” that it would have taken the same unfavorable personnel action in the absence of the complainant’s whistleblower activity.   

Finally, although it’s small consolation, if this individual does file a charge in bad faith, the SOX provides that the company may seek some attorneys’ fees and costs as a result.