Happy Birthday FMLA! Lots of Presents for Employers

Has it really been 20 years since President Clinton signed the law establishing the federal right to leaves of absence for many who work for larger employers? While many employees have appreciated the benefits of job-protected time away from work, HR managers and business owners have confronted complex amendments, regulations, rules, and scores of lawsuits. The DOL recently issued new regulations, forms and interpretations. Employers should take the time to update kitchen postings and ensure they understand current FMLA requirements.

The first 20 years: In earlier posts (first of a four-part series; second installment; third installment, and final installment), we outlined the traditional requirements of the FMLA and related Washington law. For more detail, we provided this comprehensive article which will be updated this summer. We more recently noted a link to new regulations expanding FMLA benefits for military caregivers.

New regulations: The US Department of Labor released 115 pages of new rules applying to military caregiver leave, qualifying exigency leave, and leave for airline flight crew employees. The DOL’s summary of the main provisions of the new rule can be found here.

New forms and posters: In case you missed it, a new poster should be adorning your workplace. A number of other FMLA forms are available on the DOL website. Check in periodically, since DOL may update the forms.

New spin: On the eve of FMLA’s 20th birthday, the Department of Labor took the opportunity to trumpet the success of the FMLA, with statistics that seem at odds with our experience. Specifically, the DOL claims that:

  • 91% of employers find that complying with the FMLA has had either a positive effect or no noticeable effect on absenteeism, turnover and morale.
  • 85% of employers say that complying with the FMLA is very easy, somewhat easy, or has no noticeable effect.
  • 24% of FMLA leave is intermittent leave, and fewer than 2% of employees who take intermittent leave do so a day or less at a time.
  • Employee misuse of FMLA is rare.

Our experience is closer to the findings on a SHRM survey from 2007, which found more frequent problems with FMLA, particularly with intermittent leave and employee misuse of the law.

If you have questions about FMLA requirements, please contact the Employment and Labor Relations attorneys at Foster Pepper.

Obama's Victory Secures Future of the Affordable Care Act

The battle over health care reform appears to be over, as President Obama's re-election eliminated the last major threat to the his signature healthcare reform law, the Affordable Care Act ("ACA"). The US Supreme Court's June 2012 decision upheld the ACA in its entirety, which means that employers must now prepare to implement its provisions.

In addition to those requirements which have already gone into effect, the ACA imposes several duties on employers and plan sponsors which are effective between now and 2014, including:

  • Mandatory Employee Coverage – Employers with an average of 50 full-time employees must offer health coverage that meets minimum essential coverage requirements or pay a fine ($2,000 per employee over 30 FTEs). Effective: January 1, 2014.
  • Summary of Benefits and Coverage – Employers are required to provide a standardized summary of benefits and coverage ("SBC") to all applicants and enrollees at initial enrollment and annual enrollment. Effective: Plan years beginning on or after September 23, 2012.
  • W-2 Reporting Requirement – Employers are required to report the aggregate cost of applicable employer-sponsored health coverage on W-2s provided to employees. Effective: Calendar year 2012.
  • Comparative Clinical Effectiveness Research Fee – The ACA imposes a fee on all health plans to fund comparative clinical effectiveness research. Effective: Plan years beginning November 1, 2011.
  • Limit on Flexible Spending Account Contributions – Employee pre-tax contributions to a Section 125 health flexible spending account ("FSA") will be limited to $2,500 annually. Effective date: Plan years beginning on or after January 1, 2013.
  • Medical Loss Ratio Rebates – Employers must begin handling medical loss ratios rebates received from insurers in accordance with guidance issued by the Department of Labor (for ERISA plans) and the Department of Health and Human Services (for non-federal governmental and church plans). Effective: First applied to 2011 plan year and the first rebate is due by August 1, 2012.
  • Health Insurance Exchange Notices – Employers must prepare notices to employees as to the availability of health insurance coverage through the state’s health insurance exchange, and eligibility for premium tax credits through the exchange, if the employer’s health care coverage does not satisfy the ACA’s minimum value test. Effective: March 2013.

While most employers are generally aware of the ACA's requirements, implementation of the legislation remains unclear without further regulatory guidance addressing vague and undefined provisions. Following President Obama’s victory, employers can expect increased activity by federal regulatory agencies to address critical aspects of the ACA, such as:

  • Essential Health Benefits – Guidance on the definition of essential health benefits, which will determine which benefits the health insurance exchange plans must offer and, for insured or self-insured plans, which benefits are subject to the prohibition on lifetime and annual limits (for plan years beginning before January 1, 2014).
  • Minimum Value Test – Rules for determining whether a plan satisfies the ACA's "minimum value" test (i.e., covers at least 60% of the costs of benefits that the employer has determined will be provided under its plan).
  • Shared Responsibility – For employers with 50 or more full-time employees, the ACA's “shared responsibility” provision imposes penalties on the employer if any full-time employee obtains subsidized coverage through a health insurance exchange, either because the employer does not offer coverage at all or because the coverage offered is "unaffordable" or does not satisfy the ACA’s "minimum value test."
  • "Full-Time" Employees – Standards for calculating the number of full-time employees.
  • Automatic Enrollment – Standards addressing the ACA's automatic enrollment provision, which requires employers with 200+ full-time employees to automatically enroll employees into a default plan if the employee does not affirmatively elect health plan coverage or opt-out.
  • Wellness Plans – Rules governing the design of employee-sponsored wellness programs and the ACA’s employee incentives to participate in such wellness plans.

Employers should take immediate action to begin the process of implementing ACA requirements, communicate plan changes to employees, and continue monitoring regulatory activity regarding implementation guidance. The Department of Labor website provides regulatory guidance and FAQs.

If you require assistance complying with the ACA's employer requirements, you may contact Amy Kauppila at kaupa@foster.com or (206)390-1071.

#1 Again: Washington State Raises Minimum Wage for 2013

The Washington Department of Labor and Industries (L&I) has announced a hike in minimum wage from $9.03 to $9.19, effective January 1, 2013.  The $.16 increase reflects the state’s higher cost of living as calculated by the Consumer Price Index. Washington will continue to have the highest minimum wage in the country, followed by Oregon at $8.95 per hour.

Washington’s minimum wage applies to workers in both agricultural and non-agricultural jobs, although 14- and 15-year-olds may be paid 85% of the minimum wage.

Washington employers are required to post the “Your Rights As A Worker” poster in designated workplace areas. The poster, which provides information about the minimum wage and other topics, are available on the L&I website. Employers do not need a new posting with the minimum wage increase, but should check to ensure that current postings are up to date.

For history buffs, L&I released a history of the minimum wage in Washington, beginning with $1.15 in 1961.

For more information on Washington wage requirements or related employment issues, please contact the Foster Pepper Employment & Labor Relations Practice Group.

Employers, Have You Prepared Your Retirement Plan Fee Disclosures?

By August 30, employers that sponsor 401(k) and other plans which provide for participant-directed investments must disclose retirement plan fees. This requirement is the second stage of the Department of Labor's initiative to ensure that sponsors of and participants in such plans receive more detailed information about fees charged to the plans. The first stage – DOL regulations requiring service providers to advise employers regarding fees that they charge to plans – became effective earlier this summer.

This second stage of the regulations now requires employer to adequately disclose such fees to participants. Most employers will have been led down the path toward compliance by third-party administrators. But employers that have not yet acted should understand that the compliance deadline is approaching and that failure to disclose is a fiduciary breach.

To comply with the regulations, employers must take several steps.

  • First, they must ensure that they received the disclosures that their service providers should have supplied.
  • Second, employers must organize that information into a format that is acceptable to the DOL. The DOL has provided a model comparative chart that employers may use as a starting point.
  • Finally, although not required by the regulations, employers also should, as a part of "best practices," determine whether the data raises issues of excessive fees or other problems. It is far better to resolve such issues before they prompt additional disclosures to participants.

DOL regulations require quarterly disclosures, so employers should ensure that they receive the necessary information from service providers on a timely basis, and promptly disseminate that information to participants.

If you require assistance in complying with the fee disclosure regulations, you may contact Scott Galloway at gallj@foster.com or (206) 447-8919.

Seattle Employers: Act Now To Comply With Seattle Paid Sick Leave Requirements

As of September 1, 2012, the majority of Seattle employers will be required to provide paid sick leave to Seattle-based employees. Seattle-based employers, as well as non-Seattle employers with employees who routinely work in Seattle, should review existing paid leave plans now to ensure compliance with the new requirements.

Foster Pepper invites you to join us on August 8, 2012 for an in-depth examination of the new ordinance and its effect on your organization. Registration is now open if you would like to attend the complimentary seminar (available live or via webinar). In the meantime, employers can use the information below to begin reviewing their existing leave plans for compliance. Employers may also review the City of Seattle’s information page, text of the ordinance, regulations, FAQs, and related information.

Coverage

Which Seattle-based employers are covered by the new ordinance? The new ordinance covers employers with five or more full-time equivalent employees. Employees working outside Seattle must be counted, so businesses or non-profits with two Seattle employees and four employees in Shoreline would be covered. While the ordinance covers City of Seattle employees, it does not cover federal, state, and other local government employees.

What about coverage for non-Seattle employers who have employees regularly working in Seattle? Are those employees entitled to paid sick leave? Yes, employees who work in Seattle at least 240 hours in a calendar year must accrue sick leave. Examples may include employees who cover shifts at multiple employer locations (including shifts at Seattle-based facilities), or who make deliveries or route-based stops in the city limits. This may also include employees who regularly telecommute from their Seattle residences.

Can employees waive coverage? No, individual employees may not waive coverage. Union employees may waive coverage, but only through collective bargaining agreements with clear and unambiguous terms.

Waiting Period

My business has a leave policy that limits an employee's right to take paid leave during the initial months employment. Are waiting periods permitted under the ordinance? Yes. Leave must begin to accrue from the date of hire, but employers may require employees to wait up to 180 days after hire to take the paid leave.

Leave Requirements

How much paid leave must my business provide? The amount of leave depends on the number of full-time equivalent employees:

  • Tier One:  5-49 FTE employees.  Employees accrue at least one hour of paid leave time for each 40 hours worked. Employees may use 40 hours per year and carry over up to 40 hours of unused time per calendar year.
  • Tier Two: 50-249 FTE employees. Employees accrue at least one hour of paid leave time for each 40 hours worked. Employees may use 56 hours per year and carry over up to 56 hours of unused time per calendar year.
  • Tier Three: 250 or more FTE employees.  Employees accrue at least one hour of paid leave time for each 30 hours worked. Employees may use 72 hours per year and carry over up to 72 hours of unused time per calendar year.

Can employers continue to offer PTO? Employers may provide paid time off (PTO), alternate methods of accrual, or more generous benefits than the ordinance, so long as the minimum number of hours are available for paid sick/safe time. Tier Three employers with PTO policies must provide at least 108 hours of paid leave use per year, and must allow up to 108 hours of unused paid leave to carry over into the next year.

How is accrued leave calculated? Exempt employees may accrue up to 40 hours per week based on their regularly weekly schedule. Non-exempt hourly employees accrue leave time on hours actually worked.

Are employers required to carry over leave from year to year? Yes. Accrued leave up to the cap carries over into the next year, but employees cannot use more leave in a year than their capped amount.

Must accrued leave be paid upon termination? Leave payouts are not required by the ordinance, but employers should review their existing policies to determine if they provide for payment of accrued leave upon termination.

Permitted Uses of Leave

What types of leave are covered by the ordinance? Under the ordinance, paid leave may be used when an employee must be absent from work for any of the following reasons:

  • Due to the employee's own illness, injury, diagnosis, treatment or preventative care;
  • For the health needs of employee's child, spouse, domestic partner, parent, parent-in-law or grandparent;
  • To cope with the consequences of domestic abuse, sexual assault or stalking that may affect the employee or a family member;
  • If the employee's place of business, or employee's child's school or place of care, is closed for a public health emergency.

How do employees notify the employer they wish to use paid sick/safe time? Employees must provide at least 10 days' advance notice of foreseeable leave requests. Employers may establish notice policies. Employers may require documentation for absences longer than three consecutive days (although employers must split the cost of obtaining any such documentation if the employer does not offer health insurance).

Recordkeeping Requirements

Do employers need to keep special records related to sick/safe time requirements? No, although employers should review their current recordkeeping practices to make sure that they accurately track hours worked in Seattle, accrued sick/safe leave, and sick/safe leave taken.

Do employers need to change payroll practices? Yes. Employers must notify employees of available sick/safe time balances each time wages are paid.

Notice and Posting Requirements

Do employers have to notify employees of their rights under this ordinance? Yes. Employers are required to give employees notice of their entitlement of paid sick/safe time, in either physical or electronic form. Notice posters are available for download.

In addition to our August 8, 2012 seminar, we will continue to provide information and analysis of the ordinance in future blog posts. If you have questions about the impact of the ordinance on your organization, please contact the Foster Pepper Employment and Labor Relations group.

Employee or Independent Contractor? Washington Supreme Court Changes the Rules - Part Two

In an article posted earlier this week, we wrote about the Washington Supreme Court’s new test for determining whether a worker is an employee entitled to minimum wage and overtime, or an independent contractor entitled only to compensation set by the parties. The article described the "economic-dependence test" in general terms: the worker is an employee if "as a matter of economic reality," the individual "is economically dependent upon the alleged employer or is instead in business for himself." Anfinson v. FedEx Ground Package Sys., Inc.

The article noted that the Court did not list the factors it would apply to the economic-dependence test, or suggest how to flesh out the general outlines of the test, but merely referred in passing to "competing lists of nonexclusive factors" that some federal courts use. Finally, the article warned that other courts and agencies have different factors for determining whether a worker is an employee or independent contractor.

In this post we will detail the factors used by the federal courts cited in the Anfinson decision, as well as the factors applied under other laws.

Cases cited in Anfinson

In supporting its economic-dependence test, the Supreme Court mentioned "competing lists of nonexclusive factors" that some federal courts use, citing Hopkins v. Cornerstone Am., 545 F.3d 338, 343 (5th Cir. 2008) and Real v. Driscoll Strawberry Assocs., 603 F.2d 748, 754 (9th Cir. 1979).

Hopkins applied these "non-exhaustive" factors:

(1) the degree of control exercised by the alleged employer;

(2) the extent of the relative investments of the worker and the alleged employer;

(3) the degree to which the worker's opportunity for profit or loss is determined by the alleged employer;

(4) the skill and initiative required in performing the job; and

(5) the permanency of the relationship.

Real applied these factors:

(1) the degree of the alleged employer's right to control the manner in which the work is to be performed;

(2) the alleged employee's opportunity for profit or loss depending upon his managerial skill;

(3) the alleged employee's investment in equipment or materials required for his task, or his employment of helpers;

(4) whether the service rendered requires a special skill;

(5) the degree of permanence of the working relationship; and

(6) whether the service rendered is an integral part of the alleged employer's business.

Other formulations

The Anfinson case applies only to the Washington Minimum Wage Act. Courts and agencies apply different formulations for different laws. Therefore, a worker could be considered either an employee or an independent contractor depending on the law or agency. For example, a worker who qualifies as an independent contractor for federal income tax purposes may be entitled to overtime pay as an employee under the Washington Minimum Wage Act.

A few of those formulations, along with links to source materials, follow below:

United States Department of Labor (applying the federal Fair Labor Standards Act, governing minimum wage and overtime):

(1) The extent to which the services rendered are an integral part of the principal's business.

(2) The permanency of the relationship.

(3) The amount of the alleged contractor's investment in facilities and equipment.

(4) The nature and degree of control by the principal.

(5) The alleged contractor's opportunities for profit and loss.

(6) The amount of initiative, judgment, or foresight in open market competition with others required for the success of the claimed independent contractor.

(7) The degree of independent business organization and operation.

Washington Department of Labor and Industries (covering workers compensation and safety requirements):

(1) Are you hiring someone for more than personal labor? ["Yes" answers tend to favor an independent contractor relationship.]

• Are they bringing employees?

• Are they bringing heavy equipment?

(2) Are you supervising?

• You ARE NOT supervising if you are only scheduling and inspecting the work.

• You ARE supervising if you are telling your worker or a subcontractor’s workers how to do the job, assigning tasks, training, keeping time sheets, paying a wage or setting regular hours.

(3) Do they have an established business of their own? ["Yes" answers tend to favor an independent contractor relationship.]

• Supervision: Does the worker perform work free of your direction and control?

• Separate business: Does worker offer services that are different from what you provide? Or, does the worker maintain and pay for a place of business that is separate from yours? Or, does the worker perform service in a location that is separate from your business or job sites?

• Previously established business: Does the worker have an established, independent business that existed before you hired?

• IRS taxes: When you entered into the contract, was this person responsible for filing a tax return with the IRS for his or her business?

• Required registrations: Is the worker up-to-date on required Washington State business registrations?

• Maintains books: Does the worker maintain his or her own set of books dedicated to the expenses and earnings of the business?

• Construction trades: If the work performed is in the construction trades, does the worker have an active contractor registration or electrical contractor’s license?

Internal Revenue Service (covering federal income tax responsibilities):

The IRS traditionally applied a 20 factor test enunciated in a 1987 revenue ruling. The IRS since has modified its analysis to cover three factors and a number of sub-factors. They are:

(1) Behavioral: Does the company control or have the right to control what the worker does and how the worker does the job? [These factors tend to favor an employment relationship]

• Type of instructions given (when and where to do the work; what tools or equipment to use; what workers to hire or to assist with the work; where to purchase supplies and services; what work must be performed by a specified individual; what order or sequence to follow when performing the work)

• Degree of instruction (the more detailed the instructions, the more control the business exercises over the worker)

• Evaluation system (measures the details of how the work is performed)

• Training (training on how to do the job, and periodic or on-going training about procedures and methods)

(2) Financial: Are the business aspects of the worker’s job controlled by the payer (such as how the worker is paid, whether expenses are reimbursed, and who provides tools/supplies)? [These factors tend to favor an independent contractor relationship.]

• Worker’s significant investment in equipment

• Unreimbursed expenses

• Opportunity for profit or loss

• Services available to the market (rather than just to one enterprise)

• Method of payment (e.g., flat fee)

(3) Type of Relationship: Are there written contracts or employee type benefits (such as pension plan, insurance, or vacation pay)? Will the relationship continue, and is the work performed a key aspect of the business?

• Written contracts (not controlling)

• Employee benefits (tend to show employee status)

• Permanency of the relationship (indefinite engagement tends to show employer-employee relationship)

• Services provided as key activity of the business (if worker’s services are a key aspect of the business, it’s more likely an employment relationship)

The IRS uses Form SS-8 in determining whether the worker is an employee or independent contractor for federal income tax purposes.

Equal Employment Opportunity Commission (covering federal anti-discrimination law, including Title VII of the Civil Rights Act of 1964, list below found at note 67):

(1) The employer has the right to control when, where, and how the worker performs the job.

(2) The work does not require a high level of skill or expertise.

(3) The employer furnishes the tools, materials, and equipment.

(4) The work is performed on the employer's premises.

(5) There is a continuing relationship between the worker and the employer.

(6) The employer has the right to assign additional projects to the worker.

(7) The employer sets the hours of work and the duration of the job.

(8) The worker is paid by the hour, week, or month rather than the agreed cost of performing a particular job.

(9) The worker does not hire and pay assistants.

(10) The work performed by the worker is part of the regular business of the employer.

(11) The employer is in business.

(12) The worker is not engaged in his/her own distinct occupation or business.

(13) The employer provides the worker with benefits such as insurance, leave, or workers' compensation.

(14) The worker is considered an employee of the employer for tax purposes (i.e., the employer withholds federal, state, and Social Security taxes).

(15) The employer can discharge the worker.

(16) The worker and the employer believe that they are creating an employer- employee relationship.

This list is not exhaustive. Other aspects of the relationship between the parties may affect the determination of whether an employer-employee relationship exists. Furthermore, not all or even a majority of the listed criteria need be met. Rather, the determination must be based on all of the circumstances in the relationship between the parties, regardless of whether the parties refer to it as an employee or as an independent contractor relationship.

Washington Common Law (covering the responsibility of the principal for the negligence of agents):

(1) the extent of control which, by the agreement, the principal may exercise over the details of the work;

(2) whether or not the worker is engaged in a distinct occupation or business;

(3) the kind of occupation, with reference to whether, in the locality, the work is usually done under the direction of an employer or by a specialist without supervision;

(4) the skill required in the particular occupation;

(5) whether the principal or the worker supplies the instrumentalities, tools, and the place of work:

(6) the length of time for which the worker is engaged;

(7) the method of payment, whether by the time or by the job;

(8) whether or not the work is a part of the regular business of the principal;

(9) whether or not the parties believe they are creating the relation of principal and agent; and

(10) whether the principal is or is not in business.

Hollingbery v. Dunn, 68 Wash.2d 75, 79-80 (1966).

Conclusion

The conflicting standards imposed by various courts and agencies make it difficult for businesses, non-profits and government entities to determine whether the people engaged to provide services are employees or independent contractors.  Foster Pepper’s Employment and Labor Relations attorneys can assist.

Seattle Paid Sick And Safe Time: Practical Guidance Employers Need To Know

The Seattle Paid Sick and Safe Time ordinance takes effect on September 1, 2012. Employers must provide Seattle workers with paid "sick and safe" time off – i.e., accrued, job-protected leave. Is your organization prepared?

Joint Foster Pepper attorneys and special guests on August 8, 2012 for a complimentary seminar covering the new ordinance. This presentation will provide practical guidance to Washington employers on compliance with the new leave requirements, including:

  • Legal requirements of the ordinance
  • Coverage and scope of the ordinance, including application to occasional Seattle employees
  • Hours tracking and leave requests
  • Accrual and use of paid time off
  • Modifications to existing paid leave programs
  • Notice and posting requirements
  • Practical guidance for employer implementation

In addition to experienced Foster Pepper attorneys, our presenters will include a special guest speaker from the City of Seattle to answer your questions.

Seating is limited, so please register early.

Another Dose Of Strong Medicine: Hospital Settles HIPAA Data Breach Suit For $750,000

A recent Massachusetts case highlights the continued responsibility on all health care organizations to protect confidential health information. The Massachusetts Attorney General announced that South Shore Hospital agreed to a $750,000 settlement after the hospital failed to protect confidential patient health information.

The data breach occurred when the hospital shipped several boxes of unencrypted backup tapes to a third party vendor to be erased. The backup tapes contained the protected health information (PHI) of approximately 800,000 individuals, including names, Social Security numbers, financial account numbers, and medical diagnoses. Unfortunately, only one of the boxes arrived at the Texas-based vendor. The other boxes were never recovered.

As a result of the breach, the Massachusetts Attorney General sued the hospital under authority granted by Congress in the “HITECH Act” of 2009, alleging violations of both the Health Insurance Portability and Accountability Act (HIPAA) and a state consumer protection statute. The suit claimed the hospital (1) failed to implement appropriate safeguards, policies, and procedures to protect consumers’ information, (2) failed to have a “business associate agreement” with the vendor, and (3) failed to properly train its workforce to protect the privacy of health data.

As we previously discussed, health care employers can expect continued enforcement efforts from both federal and state agencies for violations of the HIPAA Privacy Rule and state consumer protection and privacy laws. In light of the high price tag for mistakes, health care organizations should review existing policies and procedures and implement the following suggestions:

  • Health care organizations should implement policies and procedures to address removal of PHI from hospital premises.
  • Removal of PHI should only occur when absolutely necessary, and all information taken offsite should be rigorously safeguarded and encrypted.
  • Covered organizations should implement a comprehensive and well-documented HIPAA training program for all employees.
  • Covered organizations should consider on-site destruction of PHI whenever possible, consistent with document retention and destruction policies, and should select vendors that will comply with HIPAA privacy and security standards.
  • Obtain a business associate agreement with all vendors who handle PHI.

If you have questions about your organization’s HIPAA compliance efforts, please contact the Foster Pepper Health Care Practice Group or the Foster Pepper Employment and Labor Relations Practice Group.

Are You "Hiring" Unpaid Interns This Summer? Proceed With Caution.

Welcome to the first day of summer!

In many workplaces, summer marks the return of student interns, clerks and volunteers. As employment opportunities remain scarce, students are eager to find meaningful experience and credentials, even without pay.

Unfortunately for employers, scrutiny of unpaid internships is increasing. Groups of interns have sued various companies seeking minimum wage, overtime and expense reimbursements, leading Time magazine to forecast "The Beginning of the End of the Unpaid Internship."

Cautious employers should scrutinize their internship and volunteer programs to avoid problems. Failure to properly classify unpaid interns can have a substantial cost. Employers may be liable for unpaid wages for all hours worked (both straight time and overtime), unpaid employment taxes, and attorneys’ fees. Take a moment to review our comprehensive post on the subject, "Interns & Volunteers: Do We Really Have To Pay Them?" and consider whether your internship pay practices are legally compliant.

If you have questions about paying interns or volunteers, please contact our Employment and Labor Relations attorneys.

Railroads Challenge Seattle Sick Leave Ordinance

On May 9, BNSF and Union Pacific Railroads filed a lawsuit against the City of Seattle, seeking to invalidate Seattle’s sick and safe leave ordinance.  As we discussed in this blog here and here, in presentations, and in business publications, the ordinance requires most employers to provide paid sick and “safe” time for employees who work at least 120 days in Seattle each year.  

The two railroad plaintiffs argue that the ordinance is invalid for several reasons. 

  • Railroads are covered by federal laws that govern employment rights and benefits.  One such law already requires compensation for employees who are unable to work due to illness, injury or pregnancy.  Plaintiffs assert that because federal law ordinarily preempts or trumps state or local law, Seattle cannot enforce the part of the ordinance that requires sick leave.
  • Another federal law governs labor relations in the railroad industry.  That law requires collective bargaining over issues of pay and benefits, including paid leave.  According to plaintiffs, Seattle is not permitted to impose requirements that interfere with the exclusive method for establishing paid leave – collective bargaining.
  • Railroad health insurance plans and certain sickness benefit plans are governed by ERISA, the federal law that regulates employee benefit plans.  Because of ERISA, plaintiffs contend, Seattle cannot enforce an ordinance that conflicts with the terms of their employee benefits plans.
  • Finally, plaintiffs claim that the “safe” time provisions in the ordinance are invalid in light of Washington state law on the same topic.

Plaintiffs ask for an order prohibiting the city from enforcing the ordinance. 

For more information on the ordinance, the lawsuit, or other leave of absence requirements, please contact Foster Pepper's Employment and Labor Relations Practice Group.

EEOC Clarifies That Federal Prohibition Against Sex Discrimination Extends To Transgender Employees

In an April 23, 2012 decision, the Equal Employment Opportunity Commission (EEOC) declared that discrimination against transgender people is impermissible under Title VII of the Civil Rights of 1964.  Title VII prohibits discrimination on the basis of sex, race and other characteristics.  Until now, the EEOC and federal courts had not specifically determined that bias against transgender individuals constitutes sex discrimination under Title VII. 

Mia Macy, a transgender woman, brought a discrimination claim against the federal Bureau of Alcohol, Tobacco, Firearms, and Explosives.  She alleges the agency virtually assured her it would hire her as a ballistics expert, but chose another candidate when the background check revealed her gender transition.  In refusing to dismiss Macy’s claim, the EEOC reasoned that because both biological and gender sex characteristics are protected against discrimination, transgender individuals are covered by Title VII. 

The decision means that employees and job applicants can now file claims with the EEOC under Title VII when they experience discrimination based on transgender status.  Although the Macy decision arose from a claim against a federal agency, private employers are also subject to the EEOC’s interpretation of Title VII.  

The Macy decision is less significant in Washington and other states that already prohibit transgender discrimination.  Under the Washington Law Against Discrimination, employers are prohibited from discriminating on the basis of sexual orientation, which is defined broadly to include transgender status: 

"Sexual orientation" means heterosexuality, homosexuality, bisexuality, and gender expression or identity. As used in this definition, "gender expression or identity" means having or being perceived as having a gender identity, self-image, appearance, behavior, or expression, whether or not that gender identity, self-image, appearance, behavior, or expression is different from that traditionally associated with the sex assigned to that person at birth.   

If you have any questions regarding compliance with federal or state law, please contact the Foster Pepper Employment and Labor Relations Practice Group.

Not So Fast III: NLRB Employer Posting Requirement Again Delayed

As we wrote in February and October of last year and January of this year, the National Labor Relations Board (NLRB) has been trying to require employers to post a notice informing employees of their rights under the National Labor Relations Act (NLRA).  Until today, the deadline for compliance was April 30, 2012.  

The United States Court of Appeals in Washington, DC is considering a legal challenge to the posting requirement brought by various business groups.  Today the Court temporarily prohibited the NLRB from requiring the posters, thus allowing time for briefing and argument (to be set for September).  We’ll provide updated information when it becomes available.

If you have any questions about compliance with NLRB requirements, please contact the Foster Pepper Employment and Labor Relations Practice Group. 

Access Denied: Legislation Prevents Employers from Demanding Employees' Social Media Passwords

Many employers use social media to screen prospective job applicants. We’ve written several posts identifying “best practices” for researching a job candidate’s online history. 

Recent bills introduced in several states, including California, Illinois, and now Washington, provide another reason for avoiding Facebook and other social media passwords. 

Maryland is the first state to pass a law prohibiting employers from requiring or seeking social media usernames and passwords.  Similar legislation has been introduced in the Washington State Senate.  Senate Bill 6637 would make it unlawful for public and private employers to seek access to an employee’s social media profile as part of a job application or as a condition of continued employment.  Employers who violate the law would be subject to a $500 penalty payable to the prevailing employee, as well as attorneys’ fees. 

Even absent these legislative requirements, employers should not require current or potential employees to provide social media usernames or passwords as a condition of employment. There are ways to screen or monitor employees without demanding direct access to non-public Facebook pages, and to thereby avoid financial penalties and infringing on employees’ privacy rights.  One option, discussed in one of our posts, is to engage an outside vendor to conduct social media searches on an employer’s behalf.

If you have any questions about these issues, please feel free to contact the Foster Pepper Employment and Labor Relations Group

Washington Passes Marriage Equality Act

On February 13, 2012, Governor Gregoire signed into law the Marriage Equality Act, which provides "equal protection for all families in Washington by creating equality in civil marriage and changing the domestic partnership laws."

Washington already provides equal rights to unmarried couples (whether gay, lesbian, or heterosexual) who enter into registered domestic partnerships.  The Act goes further by permitting gay and lesbian couples to enter into civil marriages.

The Act will go into effect on June 7, 2012, although opponents are expected to gather sufficient valid voter signatures to force a referendum in November and thus delay implementation of the Act.

Foster Pepper will monitor and provide updates on this breaking development, particularly the impact of the Act on Washington employers.

Major Changes to US Patent Law Create New Challenges for Washington Employers

The patent landscape is transforming.  An employer’s successful adjustment to the new patent regime will require it to take important steps to protect its potentially patentable products.

The Change

The United States was – and for now still is – a “first to invent” country.  A company or individual can invent a product, perfect it, sell it, and then pursue patent protection.  

By March 16, 2013, however, the patent process will be very different.  The United States will become a “first to file” country, and public sale of an invention even a day before filing a patent application can preclude ever getting a patent.  While the new law has some protections for an inventor’s pre-filing disclosure, they are untested and uncertain.

In the time before March 2013, employers that depend on innovation should behave as though the new system is in place already, and begin implementing new patent disclosure and filing systems. This transition will require the most significant changes at mid-sized organizations. Let’s face it: major multi-national companies adapted to the new regime years ago, because so many other countries already have a first-to-file structure.  And smaller, start-up companies simply have fewer people and systems to change.  For mature, mid-sized companies and other organizations that develop protectable IP assets, it’s time for three simple steps to safeguard patentable developments.

What Should Employers Do?

First, review and update employment agreements.  There’s no real change here.  Washington employers can require employees to assign patents to the company when (1) the invention is directly related to the business of the employer, or to the employer’s actual or demonstrably anticipated research or development; (2) it was created on company time, with company equipment, or with company trade secrets; or (3) the invention results from any work performed by the employee for the employer.  But the agreement needs to say that – or the inventor may own the invention.  Also, if the company needs to amend employment agreements to add assignment language, it may need to provide additional consideration, such as a salary increase or bonus. Finally, it’s vital that the agreement recite that current inventions are assigned, not merely that the employee has an obligation to assign in the future.

Second, develop a system for tracking inventions.  Now that the employer owns the invention, it better have a way to identify it.  Here’s where the major shifts need to happen.  Employee-inventors probably won’t notice when they invent something; after all, changing products and processes, fixing problems, improving efficiencies are just in a day’s work. That’s the job, not an invention, right?

Formerly, an employer could decide what to patent long after the product is released, and base its decisions on what had succeeded, not really needing to ask in advance. Now all potentially patentable improvements have to be captured before they are made public.

Every group of employees that works to contribute to the design or development of products or processes should hold periodic meetings to discuss developments. Make sure someone there also knows about product launches, pitches, white papers, and every other way the employer might disclose those developments.  The employer can determine when to involve patent counsel, holding developments secret until they are ready to be filed or disclosed.

Third, secure the necessary patent documents.  When a patent filing is in the works, the employer needs to ensure that employee-inventors – as required by the employment agreement – sign a form of assignment document that demonstrates to the Patent Office that ownership of the invention transfers to the employer.

At the same time, the Patent Office needs quite a lot of information from the employee – and not only relating to the invention.  The employee-inventor must promise to disclose to the Office everything that is material to the patentability of the invention. So if the employee knows of related technology (and who doesn’t?) it’s vital to secure that information and give it to patent counsel.

The alternative can result in years of wasted effort.  Imagine getting a patent, only to discover that the now-former employee-inventor knew of several products similar to the invention, but never disclosed them.  The non-disclosure could be enough to render the patent unenforceable. On the other hand, armed with complete information, the employer and patent counsel would have been ready for competitor claims or might have decided not to seek a patent at all.  

Conclusion

Any employer who hopes to develop something new and valuable should adopt the steps outlined above, while of course heeding all legal advice from patent counsel. 

If you have questions about questions about the patents or other intellectual property issues, please contact the Foster Pepper Intellectual Property Practice Group.  If you have questions about employment agreements, please contact the Foster Pepper Employment and Labor Relations Practice Group.

New Duties for Health Care Facilities to Protect Workers Against Hazardous Drugs

On January 3, 2012, the Washington Department of Labor and Industries (“L&I”) adopted the “Hazardous Drugs Rule” (the “Rule”), which is intended to protect workers from potentially harmful exposure to chemotherapy or other hazardous drugs. Washington is now the first state to require health care employers to take precautions such as installing proper ventilation or using protective equipment to prevent exposure. Without these measures, workers may be at risk for harmful effects such as cancer, reproductive and developmental problems, and allergic reactions. The Rule is consistent with recommendations from the National Institute of Occupational Safety and Health (“NIOSH”), OSHA, and The Joint Commission.

Who must comply with the Rule?

The Rule applies to all “health care facilities” that have employees with occupational exposure to hazardous drugs, including but not limited to hospitals, clinics, nursing homes, laboratories, and pharmacies.

What is a “hazardous drug”?

A “hazardous drug” is any drug that NIOSH identified as hazardous in its 2010 report. Some substances on the list are dangerous cancer-causing agents, while others cause different kinds of irreversible harm to health care workers – even at low exposure levels.

What does the Rule require?

The Rule requires affected employers to develop a hazardous drugs control program that addresses the following elements:

  • A written inventory of hazardous drugs in the workplace.
  • A current hazard assessment for the hazardous drugs.
  • Hazardous drugs policies and procedures that cover among other things:

    • Engineering controls (equipment use and maintenance);
    • Personal protective equipment;
    • Safe handling practices for receiving and storage, labeling, preparing, administering, and disposing of hazardous drugs;
    • Cleaning, housekeeping, and waste handling;
    • Spill control;
    • Personnel issues (such as exposure to pregnant workers); and
    • Employee training.

When does the Rule take effect?

The Rule will go into effect in three stages:

  • By January 1, 2014, employers must complete and implement a written hazardous drugs control program.
  • By July 1, 2014, employee training must be implemented.
  • By January 1, 2015, employers must complete installation of required ventilated cabinets.

What should the employer do now?

L&I has not yet provided much guidance regarding developing and implementing a hazardous drugs control program. It has announced a plan to form a Hazardous Drugs Advisory Committee to develop model programs. As described here, L&I will host a public meeting on January 29 for those interested in the formation of the Advisory Committee.

In the meantime, employers subject to the Rule should begin initial assessments of their hazardous drug inventory and policies.

If you have questions about the Rule, please contact the Foster Pepper Employment and Labor Relations Practice Group or the Foster Pepper Health Care Practice Group.

Not So Fast II: NLRB Again Delays Employer Posting Requirements

As we wrote before, the National Labor Relations Board (NLRB) is requiring employers to post a notice informing employees of their rights under the National Labor Relations Act (NLRA). Just before Christmas, the NLRB announced that it is delaying the posting deadline from January 31 until April 30, 2012. Various business groups have filed a lawsuit challenging the posting requirement, and the federal court that is hearing the case requested more time to consider pending motions.

The latest announcement follows an earlier delay. As we wrote in October, the NLRB unilaterally set back the earlier deadline for compliance from November 14, 2011 to January 31, 2012 “to allow for enhanced education and outreach to employers, particularly those who operate small and medium sized businesses.”

Assuming no further delay, the April 30 posting requirement will apply to all private-sector employers subject to the NLRA – including those that have no union. Agricultural, railroad and airline employers are not covered.

If you have any questions about compliance with NLRB requirements, please contact the Foster Pepper Employment and Labor Relations Practice Group.

I-1183: New Training Requirements For Spirits Retailers

Initiative Measure 1183, approved by voters, privatizes spirit sales in the State of Washington.  Spirits retailers will face more stringent training and supervision requirements than previously required for sales of beer and wine.

Training Requirements For Retail Spirits Vendors

Under the new law, businesses seeking or renewing a “retail spirits license” must provide specified training of retail clerks and supervisors before they are permitted to sell spirits. The training must be renewed every five years, and the employer must maintain training records for all retail sales staff.

Although no training program currently exists, the Liquor Control Board is required to develop a “responsible vendor program” and create guidelines for employee training. In addition to the new training requirements, licensees must accept only certain forms of identification for alcohol sales, adopt related policies, post signs in the business, and keep records verifying compliance with the new requirements. We will provide updates as the Board defines the training requirements.

State Liquor Stores to Close by June 1, 2012 -- Stay Tuned

I-1183 takes effect immediately upon certification of the 2011 General Election by the Secretary of State. But, holders of a new spirits distributor license or spirits retail license may not commence distribution earlier than March 1, 2012; or for retailers, June 1, 2012 (the date retail sales by State Liquor Stores cease). Over the next few months the Liquor Control Board will issue regulations to implement I-1183. Sign up here to receive Foster Pepper's e-alerts on this rapidly changing industry. If you have questions about the training requirements for spirit sales licensees, please feel free to contact Foster Pepper’s Wineries, Breweries and Distilleries Group.

Not So Fast: NLRB Delays Employer Posting Requirements

As we wrote in February and explained in our client briefing in September, the National Labor Relations Board (NLRB) issued a proposed rule that requires employers to post a notice informing employees of their rights under the National Labor Relations Act (NLRA). The posting requirement would apply only to private-sector employers subject to the NLRA, which excludes agricultural, railroad and airline employers.

On October 5, the NLRB delayed the deadline for compliance from November 14, 2011 to January 31, 2012 “in order to allow for enhanced education and outreach to employers, particularly those who operate small and medium sized businesses.”  The NLRB has not changed the text of the notice, the requirements for posting, or the consequences of failing to post (all topics we addressed in our February article).

If you have any questions about these posting requirements, please contact the Foster Pepper Employment and Labor Relations Practice Group.

Fired Because Of Facebook: NLRB General Counsel Addresses Offensive Facebook Posts In The Context Of Protected Activity

Three recent National Labor Relations Board (NLRB) memoranda concluded that employees posting complaints about their jobs on social media websites may not be protected from disciplinary action even if their complaints are job-related. In each of the three cases, the NLRB Division of Advice recommended dismissal of the claims that employers violated the NLRA when they disciplined or discharged employees for Facebook activity.

In the first case, an employee was disciplined for profanely criticizing local management on his Facebook page. The remarks were visible only to his Facebook friends, some of whom were co-workers. Although two co-workers posted notes of support, the Division of Advice found that no evidence of protected concerted activity, as the Facebook posts were essentially a personal gripe made only on his own behalf. The employee had not included any language suggesting that his co-workers initiate or participate in group action; instead, the employee expressed his frustration over a single incident with a particular manager.

Likewise, the Division of Advice found no evidence of protected concerted activity where an employee in a mental health institution engaged in a Facebook conversation with a set of friends about the facility's clients. Her employer learned of the Facebook conversation when it was reported by a former patient, and the employer fired the employee. None of the employee's co-workers were Facebook friends, and the employee admitted she had never discussed her Facebook posts with co-workers. Therefore the employee had not engaged in protected concerted activity because she was not seeking to "induce or prepare for group action," and because her Facebook posts did not mention any terms and conditions of employment.

In a third case, the Division of Advice concluded that a bartender had not engaged in protected concerted activity when he complained about his employer's tip pooling policy on Facebook. Even though the bartender's complaint centered on his terms of employment, he did not direct his Facebook post to co-workers or discuss the post with them. In short, he was simply complaining and was not seeking to induce collective action.

Finally, the General Counsel also released a report summarizing the outcomes and reasoning behind more than a dozen cases in the past year involving employees' use of social media and employer social media policies. In each of the three memoranda and the vast majority of the social media cases, the General Counsel used similar legal standards, including:

• When an employee "acting with or the authority of" coworkers (a) "seeks to initiate, induce or prepare for group action," or (b) "brings truly group complaints to the attention of management," that employee's action is protected.

• When the employee's activities are "the logical outgrowth of concerns expressed by the employees collectively," the employee's activities are protected.

• When the employee is engaged in activity "solely by and on behalf of the employee himself," the employee's activity is unprotected.

• When the employee's comments are "mere griping," as opposed to "group action," the employee's comments are unprotected.

While not comprehensive, these guidelines will assist employers considering disciplining or terminating employees for offensive social media posts. Employers should consult competent employment counsel for additional guidance during the disciplinary process.

For more information on social media guidelines, compliance, and resulting employee discipline, please contact Foster Pepper's Employment and Labor Relations Practice Group.

Seattle City Council To Vote On Revised Sick Leave Mandate On September 12th

The Seattle City Council's Housing, Human Services, Health and Culture Committee has spent much of the summer working on revisions to a proposed ordinance that would require Seattle businesses to provide employees with "paid sick and paid safe time." As we previously discussed, if the ordinance is adopted, Seattle would join San Francisco, Milwaukee, and Washington D.C. as one of the few cities to require "paid sick and paid safe time."

Since June, the Committee has made several revisions to the proposed ordinance to make it friendlier to Seattle's businesses, including:

• Exempting businesses with fewer than 4 full-time employees ("micro employers") from the ordinance's requirements;

• Excluding college students on work study, even if they would otherwise qualify for "paid sick and paid safe time";

• Increasing the minimum eligibility requirement for employees who occasionally work in Seattle from 80 to 120 days per year to qualify for "paid sick and paid safe time"; and

• Enlarging the probationary period for employees at the largest businesses (250+ employees) from 90 to 180 days worked before any paid sick time may be used.

Despite these and other revisions, the legislation continues to be controversial with the Seattle business community. While some businesses have supported the measure, the Seattle Chamber of Commerce is urging its members to tell Seattle City Councilmembers to "slow down," "take more time" and "don't rush to mandate." The Chamber suggests that the City Council should more fully consider the impact of the leave ordinance on collective bargaining agreements, the impact on seasonal employment, and whether alternatives exist that wouldn't cause financial hardship for employers.

Despite this opposition, the ordinance is expected to be enacted in its current form on September 12.

For more information on the proposed ordinance and how it might affect your business, please contact Foster Pepper's Employment and Labor Relations Practice Group. We'll also discuss the outcome of the vote at our September 13th briefing.

Sixteen, Going On Seventeen: An Overview Of Washington Child Labor Laws

Many Washington employers hire workers under the age of 18 to work in a variety of jobs, but they need to follow special rules. Employment of children between 14 and 17 is governed by the Washington State Department of Labor and Industries (L&I) and the U.S. Department of Labor (DOL). Absent limited exceptions, such as for agricultural or theatrical jobs, children younger than 14 ordinarily cannot be employed at all.

Federal and state regulations regarding the employment of 14- to 17-year olds are found on the DOL and L&I sites. The regulations include specific requirements and limitations unique to minor employees in areas such as hours of work, meal and rest breaks, and prohibited job duties.

In Washington, employers must also obtain a minor work permit through L&I on their Master Business License for each work location with employees under the age of 18, and renew the permit annually. The minor work permit application may be completed online.

In addition to posting the minor work permit, Washington employers must also maintain the following information about each minor worker in a file at the minor’s work site:

1. Personal data: Name, address, and a copy of the minor’s Social Security card and other appropriate employment documents including an I-9.

2. Proof of age: Copy of birth certificate, driver's license, baptismal record, etc.

3. Job description: Must include equipment used, such as copiers, computers, power equipment, or vehicles.

4. Work schedule: Must show earliest and latest work hours (download chart showing work hour limits, PDF).

5. Parent/School Authorization Form: signed by parent/guardian and high school (if in session).

6. Special Variance Form: For a 16- or 17-year old high school student who wants or needs to work more than four hours a day or 20 hours per week (up to maximum 28 hours per week), a special variance form is available from the student's high school.

7. Position funding: Must pay at least minimum wage, currently $8.67/hour (effective January 1, 2010).

Employers must maintain employment records for three years after hiring a minor employee.

Civil and criminal penalties may be assessed for violations of state or federal child labor regulations. Under federal law, child labor violations by employers may be subject to a civil penalty up to $11,000 per minor worker.

If you have questions about employment of minor workers, please contact the Foster Pepper Employment and Labor Relations Practice Group.

Interns & Volunteers: Do We Really Have to Pay Them?

Now that summer is here, many workplaces find new faces in the hallways: students eager for work experience. Some are willing to donate their time to gain practical experience, others wish to support a worthy organization, and still others are focused on adding to their resume. But can the organization accept the efforts of these students without paying them?

Do we have to pay our summer interns?

As a general rule, the organization must pay all persons it “employs,” which is broadly defined to mean “suffer or permit to work.”

Nonprofits and public sector organizations usually are permitted to offer unpaid internships, even if the intern provides services of value to the organization.

The situation with for-profit entities is different. The company first must determine whether the intern is participating in a training program (and therefore not entitled to compensation) or is simply “employed.” Before permitting unpaid interns or trainees, the US Department of Labor requires the company to meet the following criteria:

1. The internship, even though it includes actual operation of the facilities of the employer, is similar to training which would be given in an educational environment;

2. The internship experience is for the benefit of the intern;

3. The intern does not displace regular employees, but works under close supervision of existing staff;

4. The employer that provides the training derives no immediate advantage from the activities of the intern, and on occasion its operations may actually be impeded;

5. The intern is not necessarily entitled to a job at the conclusion of the internship; and

6. The employer and the intern understand that the intern is not entitled to wages for the time spent in the internship.

If the company fails to satisfy any one of these requirements, the worker is considered an employee and must be paid at least minimum wage.

Do we have to pay our volunteers?

Nonprofit and public sector organizations may have volunteers as long as the volunteers are not employees of the organization and give time and services gratuitously. There can’t be any pressure or coercion to donate time, and all services must be free and voluntary.

For-profit companies cannot have volunteers. Companies must pay at least minimum wage to anyone who is permitted to work.

The US Department of Labor has offered guidance on volunteers, and the Washington Department of Labor & Industries has even more complete information.

Can we encourage our employees to volunteer their time, either to our organization or to other organizations?

It depends. Of course all volunteers must give their time freely, and they can’t be coerced or forced to participate.

A non-profit employer need not pay employees for volunteer activities so long as the volunteers perform duties that are not similar to their paid job and the employer doesn’t control the activity. However, if the employer requires or controls the volunteer work, and the activities benefit the employer, the employer may need to pay for time spent on the activities. Also, if employees on their own volition perform volunteer activities that are related to their job, and the employer knew or should have known that the employees would be participating, the employer may be required to pay for the time. For example, a charity can’t require or allow a bookkeeper to voluntarily process payroll, if that is the kind of work that he completes in his paid position. However, if the bookkeeper decides on his own to hand out t-shirts at the annual 5K race, he probably would not have to be paid.

According to the Department of Labor, public sector employees can’t volunteer to do work that is similar to their paid job within the same jurisdiction where they work, although they may volunteer to do similar work in different jurisdictions or different kinds of work in the same jurisdiction.  For example, a bus driver for the Auburn public schools could not volunteer to drive an extra shift at her elementary school for no pay. However, she could donate her time to drive for a class trip in the SeaTac schools. Or, if the driver prefers to spend her free time closer to home, the Auburn schools would not be obligated to pay her for volunteering to help restore a playground.

Private sector employees can volunteer in nonprofit and public sector in jobs that are similar to the work that they are paid to do in the business world. For-profit companies can never have volunteers doing company work without pay.

Can we give our unpaid interns and volunteers gift cards or stipends?

Yes. Volunteers and unpaid interns for nonprofit or public sector organizations can receive stipends or other nominal fees or gifts, as long as the gifts are not tied to productivity. Monthly or yearly stipends are fine, too, as are reimbursements for expenses.

However there is a limit.  If volunteers are paid more than a reimbursement for expenses, reasonable benefits or a nominal fee, the nonprofit might start to establish an employment relationship with the volunteer that would be subject to minimum wage requirements. The Department of Labor has defined “nominal fee” as 20% or less of what an employee doing the same work would make. For example, a custodian who serves as a coach for the varsity track team can receive a stipend for his work without losing volunteer status, as long as the stipend is 20% or less of what the school would have to pay an employee to do the same work.  Note also that employers also may need to withhold taxes for stipends that exceed $600.

If you have questions about paying interns or volunteers, please contact our Employment and Labor Relations attorneys.

Letting Someone Else Dig for the Dirt: Hiring Vendors to Assist in Social Media Searches

In our post on May 10 covering best practices for using social media in the recruiting process, we shared guidelines for using social media in screening applicants as part of the hiring process. Among other tips, we suggested that each organization designate an employee or group of employees who would conduct the Internet search for additional information about the applicant’s work qualifications, interests and negative work history or behavior. That employee would cull through the publically-available information and then share only the relevant data with the hiring managers. We also noted that the employer could engage a third party service provider to perform the work.

One prominent vendor, Social Intelligence, searches social media sites such as Facebook and Twitter for negative information about candidates. The company is particularly keen to locate racist remarks or activities, sexually explicit photos or video, potentially violent tendencies, and demonstrations of illegal activity.

The US Federal Trade Commission has dropped its investigation into Social Intelligence’s business practices.  The FTC found no evidence that Social Intelligence violated the Fair Credit Reporting Act, the federal law that regulates third-party investigations.

Thus, despite blog criticisms of Social Intelligence’s activities as “scary” and “creepy,” employers may decide that third-party social media searches are preferable to asking HR employees to scour the net in search of disqualifying behavior.

NOTE: Foster Pepper does not endorse Social Intelligence or any other vendor. Employers should carefully investigate before engaging any third party to assist in the hiring process.

What We're Reading: Long Weekend Edition

Warm weather warnings for workers and employers. The Washington Department of Labor & Industries reminds us that employees need to take precautions while working in hot weather conditions. For those of us who have suffered through a cold and rainy June in the Puget Sound region, such advice seems unnecessary and maybe even a bit cruel. But we’ll be ready if summer comes in July.

DOL has an app for that. The US Department of Labor has unveiled a free timesheet application that allows employees to track their work hours, breaks and overtime and use that information to challenge their employers’ records. The new program is available now for iPhone; Android and Blackberry likely coming soon.

Suffragists gather in Seattle a century ago. From HistoryLink.org, we found this article describing a train (dubbed the “Suffrage Special”) arriving in Seattle in late June 1909, filled with more than 250 leaders of the American Woman Suffrage movement. The group was here to hold the 41st annual convention of the National American Woman Suffrage Association, timed to coincide with Washington's first world's fair, the Alaska-Yukon-Pacific Exposition.  On July 5 of this year, Seattle will see a gathering of a different nature.

Seattle Considers Paid Sick Leave Mandate

Seattle may join San Francisco, Milwaukee, and Washington D.C. as one of the few cities to require “paid sick and paid safe time” for all employees if a proposed ordinance passes later this summer.

The legislation, introduced by City Councilman Nick Licata, would require businesses to provide employees with “paid sick and safe time.” The ordinance would mandate paid leave “to take care of their own or their family members’ health needs or their own or family members’ safety or other needs resulting from domestic violence, sexual assault, or stalking.”

In its current form, the ordinance mandates the amount of leave based on the size of the business:

• Businesses with 1 – 49 full-time employees: Each employee must accrue at least 1 hour of paid time off for every 50 hours worked, for a maximum of 5 days (40 hours) off in a year;

• Businesses with 50 – 249 full-time employees: Each employee must accrue at least 1 hour of paid time off for every 35 hours worked, for a maximum of 7 days (56 hours) off in a year;

• Businesses with 250 or more full-time employees: Each employee must accrue at least 1 hour of paid time off for every 30 hours worked, for a maximum of 9 days (72 hours) off in a year;

• Businesses with 1,000 or more employees using paid time off (PTO), such as a plan that combines vacation and sick time: Employees must receive the equivalent of at least 1 hour for every 15 hours worked, with at least half the time available for paid sick time.

Any unused “paid sick and paid safe time” must be carried over to the following calendar year, but the carryover may not exceed the limits outlined above (5 days, 7 days, or 9 days).

Employers that already have a paid leave policy, such as a PTO policy, will not be required to provide additional paid sick and safe time leave, provided that the PTO policy may be used for the same purposes.

The accrual rates discussed above reflect changes made to the proposal after conferences with business owners around Seattle. The ordinance drafters also included other provisions intended to allow small business owners more flexibility, including:

• Allowing workers to swap shifts rather than take paid sick leave; and

• Implementing a waiting period before workers could start using their accrued paid time off. Employees would have to wait 180 days before using their paid leave if employed by a business with fewer than 250 employees. For larger businesses, employees would have only a 90 day waiting period before paid leave is available.

If the ordinance is implemented, businesses with fewer than 250 full-time employees would have one year to implement a compliant paid leave policy, while employers with 250 or more full-time employees would have only 180 days. Businesses opening or relocating to Seattle with fewer than 250 full-time employees would have two years to implement a compliant paid leave policy.

The measure remains controversial. As the Seattle Times reported, advocates of the ordinance say that it will improve public health by keeping sick employees and their children at home. Small business owners argue that the costs of the program could be staggering to businesses with a small profit margin and a large number of part-time workers.  The Seattle Chamber of Commerce is concerned that the legislative timeline is too short for the level of discussion needed to accurately assess the impact of the legislation.

For more information on the proposed ordinance and how it might affect your business, please contact Foster Pepper’s Employment and Labor Relations Practice Group.

Back To Basics: The Washington Workers' Compensation System

Workers’ compensation is a form of no-fault insurance that provides wage replacement and medical benefits to employees who suffer injury or illness in the course of employment. Each state maintains a separate workers’ compensation system. The US Department of Labor has put together a quick reference guide to workers’ compensation offices across the nation.

The workers’ compensation system is designed to cover approved medical, hospital and related services due to workplace injuries or illnesses, as well as compensate employees who are temporarily unable to work full-time. Employers must provide coverage for their employees, and in return employers normally cannot be sued for damages when a work-related injury or illness occurs.

The Washington state workers’ compensation system is unusual. Washington was one of the first states to implement a workers’ compensation system, and is currently one of only four states that has a monopoly state fund to provide workers' compensation insurance.

Unlike non-monopoly states, where employers can purchase private insurance, Washington employers must obtain coverage through the Department of Labor & Industries. The agency manages and pays benefits out of an insurance pool called the Washington State Fund. The Fund is financed by premiums paid by employers and employees through payroll deduction. The Department sets premium rates each year; rates increased by 12% in 2011. Increases in 2012 and beyond are expected to be higher, as underlying medical care, pension and claim costs continue to rise.

The Department also requires employers to report serious workplace accidents or injuries. In cases of death, probable death or in-patient hospitalizations, employers have only eight hours to report the injury.

Employers seeking additional information on the workers' compensation system should consult the Department of Labor & Industries information page.

For more information on compliance with the Washington workers' compensation system, please contact Foster Pepper's Employment and Labor Relations Practice Group.

Book 'Em Dan-O - Seattle Criminalizes Wage Theft

Effective June 4, Seattle employers who intentionally fail to pay employees can face criminal charges. Ordinance No. 123596 added "wage theft" to the list of acts punishable as theft under the Seattle Municipal Code, and made wage theft a basis for revoking or denying a business license. In passing the Ordinance, the Seattle City Council found that "wage theft" is a growing national problem, particularly in low-wage industries, and that enforcement measures available under state law are often ineffective.

Under the revised Municipal Code, a person is guilty of theft if "he or she knowingly secures the performance of services by agreeing to provide compensation and, after the services are rendered, fails to make full and complete payment, with intent to avoid payment for services." The Code lists circumstances for a judge to consider in determining whether the employer had "intent to avoid payment for services." Evidence of an employer’s intent to avoid wage obligations may include failing to pay wages at an agreed-upon time, paying less than an agreed-upon amount, and paying wages with a bad check. A person convicted of wage theft faces a maximum fine of $5,000 and up to one year in jail.

The Ordinance also affected the availability of a business license. The Code now allows the City of Seattle to revoke or deny a business license based on a wage theft conviction within the last 10 years. The City may also revoke or deny a business license based on, within the last 10 years, a final judgment, or a final citation and notice of assessment from the Washington State Department of Labor and Industries, for violations of state wage laws if the employer did not timely satisfy the judgment or assessment. A revocation or denial on any of these grounds lasts at least one year. Thus a wage theft conviction, or failure to comply with state wage laws, may preclude a business from operating in Seattle for an extended period of time.

While the Ordinance imposes significant risks to Seattle employers, it does not create a direct remedy for employees. Employees seeking to recover wages (whether in or out of Seattle) remain confined to state law remedies. Washington employees with wage claims may seek relief in one of two ways:

  • Employees may file a wage claim with the Washington State Department of Labor and Industries. Many wage claims are resolved each year through this "Workplace Rights Complaint" system, which allows for prompt and informal proceedings.
  • Employees may file a lawsuit in court. In such cases, the employees often rely on RCW 49.52, which allows them to seek double damages, attorney fees and personal liability of responsible company officials. While the prospect of greater damages and fee awards may be attractive to some, the time for resolution can be long and the investment in time and attorneys’ fees can be considerable.

As a best practice, Washington employers (not just those located in Seattle) should carefully review their wage payment practices on a regular basis to ensure they are complying with federal, state and local wage payment laws. If you have any questions about this information, please contact the Foster Pepper Employment and Labor Relations Practice Group.

What Happens in Vegas Doesn't Stay in Vegas: Best Practices For Using Social Media in The Recruiting Process

Several attendees at the May 10 Social Media Breakfast Briefing asked about best practices for use of social media in the recruiting process. A candidate’s publicly-available social media profile may provide valuable information related to his or her work qualifications, interests and negative work history or behavior.

Social media searches used during the recruiting process must be consistent and carefully crafted. Failure to establish a consistent search methodology may yield too much information (e.g., information on protected status such as ethnicity, disability, pregnancy, or union affiliation) and therefore may generate a claim for failure to hire or for post-hire discrimination.

So, what are some guidelines for social media checkups during the hiring process?

1. Consistency: All applicants should be processed consistently. Any searches should be conducted at the same phase of the interview process (e.g., before the initial interview or after the first phone screen). The process should be followed for each candidate without regard to age, appearance, or perceived lifestyle choices. If you decide that not every position merits investigation using social media checks, designate particular job categories or departments that are included and consistently follow those guidelines.

2. Designated searcher: The organization should designate one employee (or small group of employees) to conduct the search. As an alternative, the organization may want to engage a third party service provider to perform the work. The employee conducting the search should not be the hiring manager.

3. Screen the hiring manager: The goal of naming a designated searcher is to avoid revealing protected information to the hiring manager. Protected information includes, for example, data about the age, race, religion, disability, genetic information, and political association of the candidate.

4. Limited scope: Before incorporating social media searches in recruiting, the organization should identify the social media sites they wish to search, focusing on securing relevant, work-related information. The search should seek publicly available information; do not allow the searcher or others in the recruiting department to “friend” an applicant in order to see private profile information.

5. Disclosure to applicant: Follow the same notice and disclosure policies the organization already has in place. Include a proviso regarding social media on the organization’s application for employment or in a separate disclosure.

6. Document results: Those conducting the review should consistently document the results of the social media search, removing any protected information that was inadvertently obtained. Search results should be maintained consistently with the organization’s recordkeeping policies.

7. Document the basis for hiring decisions: If you use social media search results to reject an applicant, such decisions should be based on legitimate, job-related reasons (e.g., work history was inconsistent with resume). The decision should be documented consistent with existing recruiting policies and procedures.

8. Communicate the policy to hiring managers: Hiring managers should be informed of the organization’s policy, and should be specifically advised not to perform their own social media searches.

If you have any questions about this information, please feel free to contact the Foster Pepper Employment and Labor Relations Group.  Materials from the May 10 Breakfast Briefing, including a sample social media policy, are available under the "News/Pubs" link on the ELR Group page.

Cleaning Up The Mortgage Meltdown: New SAFE Act Requirements For Employees In The Financial Industry

In response to the careless lending practices that led to the U.S. mortgage meltdown, Congress enacted the Secure and Fair Enforcement for Mortgage Licensing Act (the “SAFE Act”) on July 30, 2008. By mandating a nationwide registration system for residential “Mortgage Loan Originators,” the SAFE Act is intended to protect consumers and prevent fraud in the residential mortgage loan business. In August 2010, the federal agencies charged with implementing the SAFE Act released final regulations, and the initial registration period is currently under way. As of July 29, 2011, all Mortgage Loan Originators at federally-regulated financial institutions will be prohibited from originating residential mortgage loans without meeting the requirements of the SAFE Act.

Does the SAFE Act apply to your organization?

The SAFE Act applies if your company is a federally-regulated financial institution, and if you employ individuals working as residential Mortgage Loan Originators (“MLOs”).

What does the SAFE Act require?

The SAFE Act requires any employee of a federally-regulated financial institution who acts as a MLO to register with the Nationwide Mortgage Licensing System and Registry (the “Registry”), obtain a unique identification number from the Registry, and maintain such registration. MLOs who are not employed at federally-regulated financial institutions are subject to different requirements, but must also register with the Registry.

What is a Mortgage Loan Originator?

An MLO is an individual who both (1) takes a residential mortgage loan application, and (2) offers or negotiates the terms of a residential mortgage loan for compensation or gain. This definition does not include individuals who perform purely administrative tasks on behalf of a MLO, real estate brokers who are licensed under state law, or individuals involved in extensions of credit relating to timeshare plans.

What information must be supplied to the Registry?

The Registry requires MLOs to provide particular information and undergo a criminal background check. An MLO must provide his or her name, home address, work address, social security number, date and place of birth, and financial services-related employment history. An MLO’s fingerprints are also required. After all required information is verified and submitted, the Registry coordinates a criminal background check and notifies the employing financial institution of any adverse findings. The MLO will then be registered and will receive a unique identification number. Importantly, the Registry does not screen or approve registration applicants; that is the responsibility of the financial institution.

What are the obligations of the financial institution?

In addition to requiring MLOs to register in the Registry, the SAFE Act places certain obligations on the financial institutions themselves. The employing institutions must require MLOs to comply with the SAFE Act’s requirements of registering, obtaining a unique identification number, and maintaining registration. The institutions must also adopt and follow written policies and procedures designed to ensure compliance with the SAFE Act.

Conclusion

The SAFE Act imposes new requirements on financial institutions that employ MLOs. Such institutions must ensure that all MLOs are registered by July 29, 2011, and adopt procedures to maintain compliance with the SAFE Act. Financial institutions should familiarize themselves with the SAFE Act and applicable regulations to develop an implementation plan and ensure compliance.

If you have questions about the information in this posting please contact the Foster Pepper Employment and Labor Relations Practice Group or Financial Institutions Practice Group.

Back To Basics: What Is The ADEA And How Does It Apply To Washington Employers?

The Age Discrimination in Employment Act of 1967 (ADEA) protects individuals who are 40 years of age or older from employment discrimination based on age. It applies to employers with 20 or more employees, including state and local government. The Equal Employment Opportunity Commission (EEOC) enforces the ADEA.

ADEA applies to both employees and job applicants. The ADEA prohibits discrimination against a person because of age with respect to any term, condition, or privilege of employment, including hiring, firing, promotion, layoff, compensation, benefits, job assignments, and training.

A brief summary of ADEA protections:

• Job Notices and Advertisements: It is generally unlawful to include age preferences, limitations, or specifications in job notices or advertisements. Employers may specify an age limit only in the rare circumstance where age is a “bona fide occupational qualification” reasonably necessary to the normal operation of the business. Prohibited language includes words that the EEOC considers age-related, such as preferences for “energetic” candidates.

• Pre-Employment Inquiries: While the ADEA does not specifically prohibit an employer from asking an applicant’s age or date of birth, requests for age information must be necessary for a lawful purpose.

• Benefits: Employers may not deny benefits to older employees. Employers may be able to reduce benefits based on age under very limited circumstances where the cost of providing reduced benefits to older workers is the same as the cost of providing benefits to younger workers.

• Waivers of ADEA Rights: An employer may ask an employee to waive rights under the ADEA in settlement of a claim or an employment termination. The ADEA, as amended by the Older Workers Benefit Protection Act of 1990 (OWBPA) sets specific minimum standards that must be met in order for a waiver to be considered knowing and voluntary. Particularly in the context of group terminations, these requirements can be complex.

Washington employers covered by ADEA also are responsible for complying with the Washington Law Against Discrimination (WLAD). WLAD similarly prohibits age discrimination, and covers employers with as few as 8 employees. County and city ordinances also may prohibit age discrimination, and these local measures may cover even smaller employers.

For more information on compliance with the ADEA as well as state and local laws, please contact Foster Pepper’s Employment and Labor Relations Practice Group.

Some Things Don't Have to Be In Writing: Supreme Court Protects Employees Against Retaliation After Making Verbal Complaints of Wage and Hour Violations

The federal Fair Labor Standards Act (FLSA) establishes complex regulations governing minimum wage and overtime pay. Like many other employment laws, FLSA has an anti-retaliation provision that forbids employers “to discharge or in any other manner discriminate against any employee because such employee has filed any complaint or instituted or caused to be instituted any proceeding under or related to [FLSA].”

In a recent decision, Kasten v. Saint-Gobain Performance Plastics Corp., the Supreme Court found that the term “filed any complaint” includes oral as well as written complaints, and thus clarifying that employees who make verbal complaints of federal wage and hour violations are protected against retaliation.

Kasten repeatedly complained that the company was violating FLSA through its placement of time clocks. According to Kasten, the location prevented workers from receiving pay for time spent putting on and taking off work clothes – in FLSA parlance, “donning and doffing.” Kasten was persistent, reporting his concerns to his lead operator, shift supervisor, and two HR employees. In each case, however, the complaints were verbal.

Kasten later was fired. In his lawsuit, he alleged that the company discharged him because of his complaints. The company disagreed. It explained that Kasten made no significant complaint about the time clock location and that it discharged him because he failed to punch in and out.

The lower courts did not try to reconcile the two accounts, ruling simply that FLSA does not protect oral complainants against retaliation. The Supreme Court disagreed, sending the case back to the trial court to determine whether the company had adequate notice of the complaints and whether the discharge was retaliatory or justified.

The Kasten decision offers two reminders for employers.

First, employers should not ignore or minimize complaints of alleged illegal or improper treatment of employees, whether based on FLSA or other laws. Instead, each complaint – written or oral, formal or informal – should be reported to HR, reduced to writing, and given careful consideration. Depending upon the circumstances, an internal investigation might be prudent. Naturally, the employer should create documentation showing its thoughtful and respectful consideration of the complaint.

Second, once it receives a complaint, the employer should carefully consider any discipline of the complainant in light of a possible retaliation lawsuit. If possible, the employer should have full documentation of the facts and of its justification for the decision, justification that is independent of the complaint.

The treatment of workplace complaints and the discipline of complaining employees present complex issues. Sound advice from an employment lawyer can help to lower the risk of a lawsuit.  If you have any questions about the information in this posting please contact the Foster Pepper Employment and Labor Relations Practice Group.

Recent HIPAA Enforcement Actions: Strong Medicine for Health Care Employers

The United States Department of Health & Human Services (HHS) recently announced its first-ever civil monetary penalty for violations of the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule. On February 22, HHS reported that it assessed $4.3 million against Cignet Health of Prince George’s County, Md. Two days later, HHS disclosed a $1 million settlement with Massachusetts General Hospital to resolve a HIPAA privacy complaint.

Background on HIPAA and the HITECH Act

The HIPAA Privacy Rule protects personal health information held by covered entities such as hospitals, clinics, laboratories, pharmacies, dentists, and many others that provide medical, dental or mental health care or treatment. Although the Privacy Rule gives patients an array of rights with respect to that information, the rule is intended to permit disclosure of personal health information needed for patient care and other important purposes. HHS enforces HIPAA.

In 2009, Congress authorized increased penalties and outlawed additional behavior in the Health Information Technology for Economic and Clinical Health (HITECH) Act. The HITECH Act established four categories of violations to address increasing levels of culpability on the part of covered entities, by increasing civil monetary penalties, and by requiring that HHS base penalties on the nature and extent of the violation and of the resulting harm. The HITECH Act’s tiered penalty structure significantly increased the potential liability of covered entities. The new law also eliminated certain defenses that were previously available to covered entities.

Cignet Penalized for Violating HIPAA and Refusing to Cooperate

According to HHS, Cignet violated HIPAA by improperly denying 41 patients access to their medical records requested between September 2008 and October 2009. Many of these patients filed individual complaints with HHS, which initiated investigations. Cignet refused to cooperate with HHS’s investigations or to produce records in response to a subpoena. After HHS enforced the subpoena in federal court, Cignet produced the medical records, but made no further efforts to resolve the complaints.

HHS calculated the $4.3 million penalty based on the new violation categories and increased penalties authorized under the HITECH Act. Accordingly, HHS imposed a $1.3 million penalty for violation of the HIPAA rule that requires a covered entity to provide patients with their medical records within 30 (and no later than 60) days, and $3 million for failing to cooperate HHS in its investigations.

Mass General Settles HIPAA Claims

On the heels of the Cignet penalty, HHS announced that Mass General had agreed to pay a $1 million dollar settlement for HIPAA violations. In March 2009, a Mass General employee accidentally left documents on a subway train, including documents that contained the protected health information (PHI) of 192 patients, some of whom were diagnosed with HIV/AIDS. The documents contained the name, date of birth, medical record number, health insurer and policy number, diagnosis, and name of providers for 66 patients as well as the names and medical record numbers of all 192 patients. The documents were never recovered.

In addition to paying the government $1 million, Mass General also entered into a corrective action plan, requiring the hospital to: (a) implement a comprehensive set of policies and procedures to protect PHI that is removed from hospital premises; (b) train employees on these policies and procedures; and (c) review and update the policies annually.

While details of the settlement negotiations were not made public, the enhanced penalty provisions enacted as part of the HITECH Act in 2009 likely played a prominent role in the settlement.

Lessons Learned

Health care employers can expect HHS to continue its HIPAA enforcement efforts and to use its authority under HITECH to impose penalties or negotiate high dollar settlements with covered entities that violate HIPAA’s Privacy Rule. Covered entities will be held strictly liable for HIPAA violations; as seen in the Mass General case, even accidental violations are punishable.

Upon discovery of a potential HIPAA violation, health care organizations should take immediate steps to mitigate or correct the violation. Furthermore, covered entities should cooperate with HHS investigations to limit penalties of up to $50,000 per violation. The Cignet example demonstrates that HHS can and will impose penalties on covered entities that commit egregious violations of HIPAA and refuse to cooperate with investigations.

Additionally, the Mass General settlement shows that HHS expects all covered entities to implement policies and procedures addressing removal of PHI from hospital premises. Such removal should occur only when absolutely necessary, and the PHI should be rigorously safeguarded, including by encryption. Health care organizations should implement a comprehensive HIPAA training program for all employees that is well-documented and consistent with organizational policies and current legal requirements.

If you have any questions about the information in this posting please contact the Foster Pepper Employment and Labor Relations Practice Group or the Foster Pepper Health Care Practice Group.

Check Your Files: U.S. Supreme Court Narrows FOIA Exemption for Internal Personnel Rules

The U.S. Supreme Court recently issued a decision that will have a significant impact on public employers' compliance with the Freedom of Information Act ("FOIA"). In Milner v. Department of the Navy, the Court ruled that Navy maps showing ammunition stockpiles at Indian Island (near Port Townsend, Washington) could not be withheld from disclosure under Exemption 2 of FOIA, which allows a government entity to withhold records related to the internal personnel rules and practices of an agency.

While the parties disputed whether the release of the maps would threaten public safety, the crux of the case was whether Exemption 2 could be used to block the release of the type of documents in question. Over the years, "High 2" (as the exemption had become known) was used as a catchall exemption to allow government agencies to withhold even documents that had no connection with an agency’s personnel rules and practices.

The Supreme Court has rejected that practice (established over 30 years of federal caselaw and administrative opinions) and turned instead to the plain language of the rule. Writing for the Court, Justice Kagan stated that the past tolerance of the expansive "High 2" reading of the statute posed "the risk that FOIA would become less a disclosure than a 'withholding statute.'" As noted in the Milner case, Navy maps obviously have nothing to do with personnel matters.

The lesson for government entities is that FOIA exemptions are now more narrowly construed. Public employers should carefully consider whether documents requested under FOIA actually fit a particular FOIA exemption.

Some documents still may be withheld from disclosure under Exemption 2 as "personnel rules and internal practices," including the following:

  • Hiring and firing records
  • Discipline records
  • Compensation and pension information
  • Benefits records
  • Vacations, hours of work and parking information
  • Internal office phone number lists

The key is whether the documents concern the conditions of employment. If so, Exemption 2 still applies.

If you have any questions about the information in this posting please contact the Foster Pepper Employment and Labor Relations Practice Group.

Have You Reached The GINA Safe Harbor? Medical Information Requests Must Comply With GINA Regulations

As we previously discussed, employers need to update policies, forms, and postings to comply with the Genetic Information Non-Discrimination Act of 2008 ("GINA"). Under the final EEOC regulations, effective January 10, 2011, employers must inform employees and medical providers in advance not to provide genetic information in response to a medical information request.

So, how can employers actively avoid receipt of genetic information? The EEOC recommends employers include the following "safe harbor" language in all requests for medical information:

The Genetic Information Nondiscrimination Act of 2008 (GINA) prohibits employers and other entities covered by GINA Title II from requesting or requiring genetic information of an individual or family member of the individual, except as specifically allowed by this law. To comply with this law, we are asking that you not provide any genetic information when responding to this request for medical information. "Genetic information," as defined by GINA, includes an individual's family medical history, the results of an individual’s or family member's genetic tests, the fact that an individual or an individual’s family member sought or received genetic services, and genetic information of a fetus carried by an individual or an individual's family member or an embryo lawfully held by an individual or family member receiving assistive reproductive services.

Without this "safe harbor" language, employers may violate GINA if they receive genetic information in response to otherwise valid medical information requests. Employers should immediately review and revise medical information request forms to comply with this obligation. Affected forms may include FMLA medical certification forms, DOL model forms, ADA-related accommodation request forms, and fitness for duty certifications.

It is important to note, however, that employer obligations do not end with the "safe harbor" language. Some additional basic GINA compliance recommendations are discussed here, but employers will likely also need fact-specific legal advice relating to balancing the GINA requirements with the need to obtain complete medical certifications under FMLA, ADA and other statutes and policies.

If you have questions about the information in this posting or your organization's GINA compliance obligations, please feel free to contact the Foster Pepper Employment and Labor Relations Practice Group.

Supreme Court Sharpens Litigation Claws of Former Employees -- "Cat's Paw Theory" Now Applies to Employment Discrimination Cases

The United States Supreme Court recently issued an opinion that may significantly increase employer liability for the actions of lower-level supervisors. In Staub v. Proctor Hospital, the Court upheld the “cat’s paw” theory of employer liability.  "Cat's paw" is a phrase derived from a La Fontaine fable, referring to a person used unwittingly by another to accomplish his own purposes.  Applied to employment law, the "cat's paw" theory holds employers liable for discrimination when managers with discriminatory motives influence – but do not make – the ultimate adverse employment decision. Although the case addressed rights under the Uniformed Services Employment and Reemployment Rights Act (USERRA), the Court’s validation of the “cat’s paw” theory is likely to extend to many types of discrimination cases.

Factual Background

By way of background, USERRA forbids employers from denying “employment, reemployment, retention in employment, promotion, or any benefit of employment” on the basis of a person’s membership or obligation to perform in a uniformed service. Employers violate USERRA if the person’s military service is a motivating factor in the employer’s action, unless the employer can prove the action would have been taken in the absence of such service.

Employee Victor Staub was a member of the United States Army Reserves while employed by the defendant, Proctor Hospital. According to Staub, his supervisors expressed hostility toward him based on his membership in the Army Reserves, telling co-workers covering for Staub’s shifts that his military service was a “strain on the department” and asking for help to “get rid of him.” In the midst of these alleged anti-military statements and actions attributed to his supervisors, Staub received a disciplinary warning for violating a supposedly non-existent company rule. Shortly thereafter, the supervisors requested that Human Resources terminate Staub.

The Vice President of HR reviewed Staub’s personnel file and decided to fire him. Although the Vice President had never expressed any anti-military animus, Staub alleged that the termination decision was unduly influenced by those who did harbor animosity about his military service. The employer claimed that HR’s review of the personnel file before discharge was enough to wipe away the effect of the prior discrimination.

The Supreme Court sided with the employee, holding that an employer can be held liable under USERRA for an adverse employment action even if the decision maker has no anti-military animus. The Court explained that an employer can be held liable for a lower-level supervisor’s antimilitary hostility, when a supervisor’s act is motivated by the hostility and where the supervisor’s act is intended to (and actually does) result in an adverse employment action.

The Court also rejected the hospital’s argument that its independent investigation eliminated the effects of the prior discrimination, noting that the views of the hostile supervisors remained a motivating factor in the termination. The Court noted, however, that if the investigation turned up reasons for termination or discipline that were unrelated to the supervisors’ original biased action, the employer would not be liable.

Open Questions

Staub left several open questions. First, it is still unsettled whether the cat’s paw theory will apply to discrimination cases under other statutes that prohibit discrimination based on sex, race, religion, national origin, age, disability or and other protected characteristics. The Court did compare USERRA to the anti-discrimination provisions of Title VII of the Civil Rights of 1964, suggesting that the cat’s paw theory would apply to other kinds of discrimination claims.

Second, Staub did not specify whether an employer would be liable if a co-worker, rather than a supervisor, committed a discriminatory act that was intended to and did cause an adverse employment action. Although the Court expressed no opinion, the case is likely to be broadly applied, even to co-workers who are not supervisors.

Third, it is also unclear whether an employee is required to first utilize the employer’s grievance process to recover under USERRA.

Practical Steps To Minimize Exposure

The Staub decision means that employers are not immunized from their supervisors’ acts, even when decisions are made by a non-biased decision-maker and carefully investigated. So how can employers take steps to minimize their potential exposure?

• Train all supervisors about how to avoid prohibited discrimination, including under USERRA.

• Coach ultimate decision-makers not to reply on the personnel file alone. Decision-makers should conduct an independent, thorough investigation into the facts, before endorsing discipline or discharge decisions requested by supervisors. Employers should examine Human Resources staffing ratios and workloads to ensure Human Resources officials have the ability to fully investigate facts prior to termination.

• Take steps to address bias in lower-level employees. Although it is unclear whether an employer is liable for discriminatory acts committed by a co-worker, employers should promptly investigate and address discriminatory behavior on the part of lower-level employees.

• Establish an adequate internal grievance process for investigation and resolution of claims. Employers should ensure that an internal complaint procedure exists to allow and require employees to inform the employer of allegedly illegal bias in employment decisions.

• Consult legal counsel before making personnel decisions that may be based on discriminatory animus.

If you have any questions about the information in this posting please contact the Foster Pepper Employment and Labor Relations Practice Group.

Give Moms a Break: Anticipating Final Regulations On Break Time for Nursing Mothers

Buried in last year's health care bill is a little-known amendment to the Fair Labor Standards Act ("FLSA") that requires employers of non-exempt hourly employees to provide rest breaks for nursing mothers.

Specifically, Section 7 of the FLSA now requires employers to provide reasonable break times when an employee needs to express breast milk for her nursing child – up to one year after the child's birth. Employers are also required to provide a private, dedicated space other than a bathroom, which may be used by the lactating mother. The break time requirement officially became effective on March 23, 2010, when the Patient Protection and Affordable Care Act was signed into law. However, the US Department of Labor’s Wage and Hour Division ("WHD") recently issued preliminary interpretations of the new law and has requested information and input from the public on several issues raised by the legislation. The WHD is currently developing a draft final rule.

At a Glance – Highlights of WHD's interpretation of the new law

Who Must Comply? The law must be implemented by all public and private employers subject to the FLSA who employ 50 or more workers. Under the law, only non-exempt employees are specifically entitled to take these breaks (although exempt employees already have the discretion to take breaks as needed). Employers with fewer than 50 employees are not subject to the FLSA break time requirement if compliance would impose an undue hardship (evaluated by looking at the difficulty and expense of compliance).

As-Needed Breaks: Employers must provide a reasonable amount of break time as frequently as needed by the nursing mother. While the frequency of the breaks needed as well a the duration of each break will likely vary, WHD suggests that lactating mothers typically will need to take breaks to express milk 2 to 3 times during an 8 hour shift, at 15-20 minutes per break.

Set Aside A Separate Space: A bathroom, even if private, is not a permissible location. An employer need not maintain a permanent, dedicated space, but the location must be appropriate for expressing milk. A temporary conversion of office or storage space, if shielded from view and free from intrusion, is acceptable.

Compensation Is Not Required: Employers are not required under the FLSA to compensate nursing mothers for breaks taken for the purpose of expressing milk. However, where employers already provide compensated breaks, an employee who uses the allotted break time to express milk must be compensated just like employees taking a break for any other reason.

The Most Employee-Protective Law Governs: The new law does not replace state laws that provide greater protections to employees. However, as Washington has no laws regulating break time for nursing mothers, the FLSA governs.

Feedback for the Feds: The interpretations described above are still preliminary. The public comment period has just concluded, and the WHD is now developing a final rule. In the meantime, WHD's current interpretation provides useful information for establishing policies for nursing employees.

The WHD "Break Time For Nursing Mothers" page contains additional information and guidance on this issue.   If you have questions about the information in this posting or your organization's likely compliance obligations, please contact the Foster Pepper Employment and Labor Relations Practice Group.

Don't Bet On It: Are Office March Madness Pools Legal In Washington?

March Madness is here. References to pools, brackets, and Cinderella are popping up during meetings and hallway conversations across the country. Chances are your employees are organizing co-worker NCAA Tournament pools, which typically involve predicting the outcome of tournament basketball games. Many office pools require a “buy in,” in which participants contribute a certain dollar amount to be divided among the victors at the end of the tournament.

As a savvy professional, you might wonder: are office pools legal in the Washington workplace?

The simple answer is no. Office pools with a monetary component are illegal. Gambling activities are illegal in Washington unless they are specifically authorized by state law. The state’s Gambling Act was passed in 1973 – several years before the rise of ESPN and extensive television coverage of the NCAA tournament. As a result, the only authorized sports pool in Washington is the 100 square sports pool board, which is limited to buy-in of $1 per square, must have 100 squares, must randomly assign game scores to each square, and may only be offered once per athletic event.

So will the vice squad be raiding the workplace if March Madness office pools continue? It’s not likely. Although NCAA pool participants could be subject to criminal charges, enforcement is unlikely if the monetary component is low. Unless your employees are high rollers, your workplace is unlikely to be featured as a crime scene in the local paper.

Successful pool participants should also remember that pool winnings are recognized as income for IRS reporting purposes. (Of course, the employer should not include prize money on the employee’s W-2.)

Putting aside the specter of prosecution, March Madness pools have been known to severely distract large portions of the employee population. With many games available via live webcast, corporate bandwidth capabilities may be strained as employees access streaming media.

At the same time, there are also benefits to the workplace. March Madness can increase worker morale, including positive interactions among employees as they discuss bracket selections and support their chosen teams. Some employers set up viewing parties in company break rooms to further engage employees.

So, as an employer, how do you balance the competing legal and employee relations issues? As a best practice, employers should not encourage or sponsor NCAA office pools where money changes hands. Office pools organized for bragging rights alone are the safest bet for Washington employers.

Airing Dirty Laundry: Addressing Repeated, Frivolous Public Records Requests By Public Employees

Public employers often struggle to balance the requirements of the Washington Public Records Act (“PRA”) with the reality of abusive and/or frivolous requestors. The issue takes on an added complexity when the frivolous requestor is an employee. The Washington State Court of Appeals recently shed some light on the issue in Phillips v. Valley Communications, Inc. The Court upheld the denial of a public employee’s repeated requests for his employer’s investigative records following the employee’s termination. The Court also found that the trial court correctly imposed sanctions on the employee for frivolous records requests.

The employee, Phillips, who worked at a 911 call distribution center, had complained about his supervisor, triggering several investigations by his employer, a local agency subject to the PRA. While the investigations were ongoing, Phillips sent a threatening email to his employer and was terminated after a psychiatric evaluation concluded he was not fit for duty.

In response to his requests for documents, Phillips received copies of his personnel and medical files and a copy of the psychiatrist’s report. However he was not given the agency’s complete investigative file, much of which the agency contended was exempt from the PRA under attorney-client and work product privileges. Phillips then filed a lawsuit in superior court challenging his employer’s compliance with the PRA. Meanwhile, during the court proceedings, Phillips continued to make repeated records requests to the agency for the very same documents.

Several months later, Phillips again sued, claiming that his employer failed to comply with the PRA. This time, the trial court denied Phillips’ requests and awarded sanctions against Phillips for his frivolous and repeated PRA requests. But, the court also denied the employer’s request for a court order to bar Phillips from making further public records requests. The Court of Appeals upheld the trial court’s rulings and award of sanctions.

This decision highlights some of the issues public employers may face when balancing the open-government goals of the PRA with the reality of abusive and/or frivolous employee-requestors. A PRA request can sometimes serve as an easy way for a disgruntled employee to burden a current or former employer.

To address these concerns, public employers should consider the following suggestions:

  • Ensure that your agency’s public records personnel are up to date on the latest PRA requirements (particularly the list of records exempt from disclosure) and properly comply with all of them.
  • Ensure that your agency’s public records personnel know the records actually maintained by the agency.
  • Don’t withhold records from a difficult employee requestor without first analyzing the list of potential PRA exemptions, identifying the reasons to withhold the records, and providing sufficient evidence to support your exemption claims.
  • Don’t rely on the courts to stop frivolous requestors; sanctions are not commonly imposed.
  • Keep abreast of the latest legislative efforts addressing frivolous records requests. Several bills are pending in the Washington State House and Senate that would curtail the activities of abusive requestors.
  • Maintain an open, positive dialogue with employees regarding the importance of government transparency, while explaining the financial drain imposed by repeated records requests.

GINA Spawns New Regulations

On November 9, 2010, the Equal Employment Opportunity Commission (“EEOC”) issued its final regulations implementing Title II of the Genetic Information Nondiscrimination Act of 2008 (“GINA”).  These regulations, which took effect on January 10, 2011, provide guidance on GINA’s relatively young and untested prohibitions on discrimination in the workplace based on genetic information.  This article provides a brief overview of GINA and offers practical tips for employers to ensure compliance with its provisions. 

GINA Prohibits Discrimination on the Basis of Genetic Information

Congress enacted GINA in response to advances in the field of genetics.  Genetic testing can now help individuals determine whether they are predisposed to certain diseases or disorders.  The growing use of this type of technology raised concerns that health coverage providers and employers would consider this information in coverage or employment decisions, discouraging individuals from taking advantage of genetic testing. 

GINA addresses these concerns by prohibiting health coverage providers (Title I) and employers (Title II) from discriminating against individuals on the basis of genetic information.  In addition to generally prohibiting discrimination on this basis, Title II prohibits employers from requesting, requiring or purchasing genetic information, and places safeguards on an employer’s handling and disclosure of genetic information.  

 GINA Broadly Defines “Genetic Information”

At first blush, employers may not think that GINA affects their day-to-day practices.  Few employers obtain or require what is commonly thought of as genetic information.  However, GINA’s broad definition of “genetic information” includes more than just an individual’s genetic test results.  GINA’s definition also includes genetic tests of an individual’s family members, an individual’s family medical history, and an individual’s request for, or receipt of, genetic services or participation in clinical research that includes genetic services.  Therefore, GINA’s protections extend far beyond the ordinary meaning of genetic information.

Employee Protection Falls Into Three Categories – Discrimination, Acquisition, and Confidentiality

GINA provides three basic protections for employees.  First, GINA prohibits discrimination on the basis of genetic information.  Employers may not consider an employee’s genetic information in hiring, firing, promotion, compensation or other similar decisions.  GINA also prohibits employers from segregating or classifying employees on the basis of genetic information, and precludes retaliation based on an employee’s assertion of his or her rights under the statute.  Interestingly, GINA only protects employees from disparate treatment; it does provide a cause of action for employer practices that result in a disparate impact.

Second, GINA prohibits employers from requesting, requiring, or purchasing genetic information from employees or their family members.  Under the EEOC regulations, “requesting” includes activities such as Internet searches likely to reveal genetic information, actively listening to third-party conversations, searching an individual’s belongings for the purpose of obtaining genetic information, and requesting information about an individual’s health in a manner that is likely to reveal genetic information.  GINA provides several exceptions where the acquisition of genetic information does not violate the statute, including, but not limited to:

1.   Inadvertent Discovery:  An employer who inadvertently discovers genetic information does not violate GINA.  For example, a manager or supervisor who obtains genetic information during a casual conversation does not violate GINA, so long as the manager or supervisor does not probe for such information. 

Genetic information that an employer receives in response to a lawful request for medical information will not fall under this exception (i.e. will not be “inadvertent”) unless the employer directs the individual and/or health care provider from whom the information is requested not to provide genetic information, or the employer establishes that the request was not likely to result in the disclosure of genetic information.  To ensure that a medical request meets this requirement, the EEOC recommends adding the following “safe harbor” language in all requests for medical information:

The Genetic Information Nondiscrimination Act of 2008 (GINA) prohibits employers and other entities covered by GINA Title II  from requesting or requiring genetic information of an individual or family member of the individual, except as specifically allowed by this law.  To comply with this law, we are asking that you not provide any genetic information when responding to this request for medical information.  “Genetic information,” as defined by GINA, includes an individual’s family medical history, the results of an individual’s or family member’s genetic tests, the fact that an individual or an individual’s family member sought or received  genetic services, and genetic information of a fetus carried by an individual or an individual’s family member or an embryo lawfully held by an individual or family member receiving assistive reproductive services.

The inclusion of this language in a lawful medical request ensures that any genetic information revealed in response to the request falls under the inadvertent discovery exception.

2.   Health or Wellness Programs:  Generally, genetic information that employees voluntarily provide in connection with a health or wellness program does not violate GINA.  To benefit from this exception, employers must follow specific procedures set out in the statute. 

3.   Family Medical Leave Act Leave Requests:  An employer’s request for family medical information to comply with the FMLA or equivalent state or local statutes does not violate GINA.

4.   Publicly Available Information:  An employer’s passive acquisition of genetic information from commercially and publicly available sources does not violate GINA.

Finally, GINA provides safeguards for the handling and disclosure of genetic information in an employer’s possession.  Employers must treat genetic information as confidential and keep written genetic information in medical files separate from personnel files.  Essentially, genetic information must be kept in the same way as other confidential medical records.  GINA also prohibits employers from disclosing genetic information to third parties except in limited circumstances, such as responding to court orders requiring the disclosure of genetic information.

Employers Should Take Proactive Steps to Comply with GINA

Employers should take the following steps to promote compliance with GINA:

1.   Train Managers and Supervisors:  Employers should provide supervisory employees with training on GINA’s provisions.  Managers and supervisors who do not understand the type of information protected by GINA or its limitations on acquiring genetic information may unknowingly inquire about or discover information protected by GINA, creating potential liability for the employer. 

2.   Update Policies and Procedures:  Employers should update their nondiscrimination policies to preclude discrimination on the basis of genetic information.  The policies should also specify that the employer will generally not require genetic information in connection with requests for medical information.

3.   Include “Safe Harbor” Language in Medical Forms:  Employers should include the EEOC’s “safe harbor” language in all medical requests to ensure that any genetic information revealed falls under the inadvertent discovery exception.    

4.  Update EEO Postings:  Employers should update their EEO postings to include GINA.  Employers may obtain a GINA supplement or complete posting with GINA here.

If you have questions about the information in this posting or your organization’s GINA compliance obligations, please feel free to contact the Foster Pepper Employment and Labor Relations Practice Group.

Unsafe at Any Speed: Unauthorized Passengers in Employer-Owned Vehicles May Sue Employer for Driver's Negligence

Do your employees drive on company business? If so, you should take note of an important Washington Supreme Court decision that imposes liability against an employer for injuries suffered by family member or friend who rides in an employer-owned vehicle without authorization.

The employer in this case, Rahman v. State, is the Washington Department of Ecology. That agency had a strict policy prohibiting employees who travel on business from transporting passengers, unless they were also on official state business. Mr. Rahman, an intern with the department, needed to travel from Olympia to Spokane for work. His wife was lonely and ill and wanted to spend the day with him. Mr. Rahman brought her along, and she was badly injured when he lost control of the vehicle.

Mrs. Rahman sued the state under the principle of "respondeat superior." That principle provides that persons injured by a negligent employee acting within the scope of his duties can recover against the employer. In a 6-3 decision, the Supreme Court applied respondeat superior and ruled that Mrs. Rahman could recover against the state. As Mr. Rahman was traveling on business -- within the scope of his job -- the state agency is vicariously liable for his negligent driving. This result followed even though he violated clear policy by letting his spouse ride in the car. The full text of the Rahman decision is available here. The dissent is available here.

The Rahman decision means that despite clear rules prohibiting family members and friends from riding in company vehicles, those interlopers can still sue the employer if the employee drives unsafely. Note, however, that if the accident occurs when the vehicle is used outside the scope of the employee's duties, respondeat superior probably would not apply.

What are Washington employers supposed to do? As a first step, employers should check insurance covering employees traveling on business and anyone who those employees could injure. Second, even though it obviously will not offer full protection against liability, employers still should announce and actively enforce rules against non-employee riders. Third, employers should ensure that employees are careful drivers, conducting background checks before permitting them to drive, and adopting and enforcing safe driving rules. Finally, given the broad scope of respondeat superior, employers must simply hope for the best.

Drive Time: FMCSA Issues Proposed Changes To Hours-Of-Service Rule

Does your organization have employees or independent contractor drivers subject to hours of service regulations?  If so, you should be aware of potential changes to the hours of service regulations.  The Federal Motor Carrier Safety Administration (FMCSA) has released a proposed rule amending the hours of service requirements for drivers of property-carrying commercial motor vehicles (CMVs).  

FMCSA’s proposed rule would make seven changes from current requirements:

  1. Limit drivers to either 10 or 11 hours of driving time following a period of at least 10 consecutive hours off duty.  FMCSA currently favors a 10-hour limit, but its ultimate decision will include consideration of comments and any additional data received.
  2. Limit the standard “driving window” to 14 hours, while allowing that number to be extended to 16 hours twice a week.
  3. Actual duty time within the driving window would be limited to 13 hours.
  4. Drivers would be permitted to drive only if 7 hours or less have passed since their last off-duty or sleeper-berth period of at least 30 minutes.
  5. The 34- hour restart would be retained, subject to certain limits. The restart would have to include two periods between midnight and 6 a.m. and could be started no sooner than 168 hours (7 days) after the beginning of the previously designated restart.
  6. The definition of “on duty” would be revised to allow some time spent in or on the CMV to be logged as off duty.
  7. The oilfield operations exception would be revised to clarify the language on waiting time and to state that waiting time would not be included in the calculation of the driving window.

The formal public comment period runs through March 4, 2011.  The full text of the proposed rule changes, as well as information on how to submit public commentary, is available on the Agency’s website

If you have questions about the proposed rule change, or any other employment-related question, please contact the Foster Pepper Employment and Labor Relations Practice Group.

Clear Space In The Kitchen: NLRB Proposes Rule Requiring Notice Of Employee Rights Under The NLRA

The National Labor Relations Board (“NLRB” or “the Board”) has published a proposed rule that would require all employers to post a notice informing employees of their rights under the National Labor Relations Act (“NLRA”).  The proposed rule would apply only to private-sector employers subject to the NLRA, which excludes agricultural, railroad and airline employers.  The notice would be similar in content and design to the notice of NLRA rights that must be posted by federal contractors under a recent Department of Labor rule.

The language of the proposed employee notice is available here.  According to the Board, the purpose of the proposed rule is “to increase knowledge of the NLRA among employees, to better enable the exercise of rights under the statute, and to promote statutory compliance by employers and unions.”  Instead of quoting the NLRA itself, however, the posting provides detailed illustrations of employee rights derived from various court and Board decisions.  The notice also includes examples of conduct that may violate the NLRA. 

The proposed rule requires that the notice be posted physically “in conspicuous places, including all places where notices to employees are customarily placed.”  Electronic distribution, such as by email, posting on an intranet or an internet site, would also be required if an employer customarily communicates with its employees that way.  The notice would be available at no charge at NLRB regional offices or could be downloaded from the Board’s website.

Failure to post the required notice may result in significant sanctions for employers.  Failure to post the notice may be considered an unfair labor practice charge, evidence of unlawful motive in unfair labor practice cases, or may toll the six-month statute of limitations period for filing unfair labor practice charges. 

Although the public comments period for the proposed rule is now closed, we will continue to monitor and post updates on the ongoing rulemaking process.

If you would like to discuss the potential impact of the NLRB’s proposed rule on your business, please contact the Foster Pepper Employment and Labor Relations Practice Group.