The Way to Protect Your Business? What You Need to Know About Trade Secrets

What do Coca-Cola’s secret formula, McDonalds’ special sauce, and Google’s search algorithm have in common? Each is a protected trade secret. In other words, they are proprietary information vital to these companies’ survival and are among their most valuable corporate secrets.

A trade secret can be anything of value to your company that is unique and not known to persons outside the company. For example, a trade secret can be a recipe, process, formula, strategy, technique, or device that your competitors do not know, do not have, and cannot use.

Trade secret law can be less risky in some respects than other forms of intellectual property like patents, copyrights, and trademarks. The application process for a patent requires that a company disclose the secret itself. With that comes an inherent risk—should the application be denied, the secret is no longer a secret. While the protection afforded by trade secret law may be considered fragile, meaning constant vigilance is required to maintain secrecy, the secret remains a secret; while a patent, even after issuance, carries some risk of post-grant invalidation. By contrast, a trade secret owner may ultimately enjoy greater certainty by maintaining protection, potentially forever. However, a trade secret is entitled to protection only for as long as it is kept a secret. If the information is lawfully disclosed to the public, it is no longer confidential and loses its trade secret protection forever.

Governing Law: Both federal and state law recognize the time and money invested to gain competitive advantages like trade secrets and protect those advantages. Federal Law: Under the controlling federal legislation passed by Congress in 2016, the Defend Trade Secrets Act (“DTSA”) defines a trade secret as something used in a company’s business that (a) is not known or readily accessible by competitors, (b) has commercial value or that provides a competitive advantage in the marketplace, and (c) the owner of the information protects from disclosure through reasonable efforts to maintain its secrecy. Prior to the DTSA’s enactment in 2016, no federal statute promulgated a federal trade secret private right of action.

In addition to the DTSA’s rules regarding trade secrets, additional federal rules apply. The Economic Espionage Act of 1996 makes the theft of trade secrets a federal crime. The Act prohibits the theft of a trade secret by a person intending or knowing that the offense will injure a trade secret owner. The Act also makes it a federal crime to receive, buy, or possess trade secret information knowing it to have been stolen. The Act allows the government to punish thefts of trade secrets by imprisonment up to 15 years and/or fines up to $5 million, depending on whether the defendant is an individual or a corporation. A private party can still sue for trade secret theft even if the federal government files a criminal case under the Economic Espionage Act.

New York State Law: Prior to federal law, most states had some form of trade secret law that varied state to state. The Uniform Trade Secrets Act (“UTSA”) was published in 1979 and amended in 1985 to provide a uniform trade secret law. Many states, including Pennsylvania in 2004 and New Jersey in 2012, adopted the UTSA. Notably, New York did not adopt the UTSA and does not have its own state trade secret statute, and thus relies on the common law.

Under New York common law, “misappropriation” refers to the acquisition of a trade secret by someone who knows that the trade secret was acquired by improper means—theft, bribery, misrepresentation, breach, or inducement of a breach of duty to maintain secrecy. The New York statute of limitations requires that any action for misappropriation be filed three years from the date the misappropriation is discovered. Further, New York law requires that the use of the trade secret be continuous in the operation of a business, rather than one-time use.

Cartier v. Tiffany: Cartier recently filed suit against its luxury rival Tiffany & Co. in New York state court. Cartier v. Tiffany & Co., et al.,650925/2022 (N.Y. Sup.). Richemont-owned Cartier sets out claims against LVMH’s Tiffany & Co. for various contractual and tort claims and trade secret misappropriation against both defendants [Who is the other defendant?]. Cartier seeks preliminary and permanent injunctive relief to require defendants to refrain from using the allegedly misappropriated information and return it to Cartier, as well as a judgment for any “compensatory damages that may be caused by [Tiffany’s] wrongful conduct.”

The complaint states that Tiffany & Co. lured former Cartier employee Megan Marino away from her role as its Assistant Manager for Jewelry Merchandising to learn more about Cartier’s “High Jewelry” collection, where pieces typically cost $50,000 to $10 million.

Cartier claims Marino was bound by non-disclosure and non-solicitation agreements she had signed as part of her role at Cartier and that she breached those agreements by using Cartier’s confidential business information to benefit Tiffany. This information includes Cartier’s “very sensitive and valuable” internal company documents that Marino forwarded to her personal email. Specifically, Marino “referenced a [Cartier] Excel spreadsheet” that “detailed Cartier’s confidential, High Jewelry assortment information.” Based on that spreadsheet, Cartier alleges, Marino “created a new Excel document, derived entirely from Cartier’s confidential information,” including “the total number of High Jewelry pieces at various Cartier locations in the U.S.” Cartier maintains this information is “only accessible by a limited number of Cartier employees [and] not known outside of Cartier” and “allow[s] a sophisticated competitor to replicate key strategies and, with relative ease, to reverse engineer how Cartier allocates, merchandises, and prices its High Jewelry stock.” Cartier claims the proprietary and confidential nature of this information amounts to a trade secret-protected asset.

Cartier further claims Tiffany has a history of poaching employees and maintains a “disturbing culture of misappropriating competitive information.” Given the alleged pattern, Cartier asserts that Tiffany now possesses “a substantial amount of [its] confidential and trade secret information that it obtained from Marino and other former Cartier employees” as a result of their “unlawful taking of Cartier’s valuable confidential information and trade secrets.”

Even if Cartier successfully establishes that it maintains trade secret information that Tiffany misappropriated, the case is hardly straightforward. Establishing damages in cases like this is particularly challenging, as it is difficult to assign a dollar value to trade secret information that will compensate the plaintiff for the economic loss caused by the defendant’s misappropriation. As a result, courts generally have quite a bit of discretion in fashioning damages awards.

©2022 Norris McLaughlin P.A., All Rights Reserved

3 Benefits of Cloud-Based Law Firms

Any law firm that’s evaluating practice management software has seen “cloud-based” options. Cloud technology has been around for a while, but some law firms are hesitant to switch to the cloud due to security concerns, lack of control, or downtime. The cloud has numerous benefits for a law firm, however. Instead of relying on filing cabinets and in-office servers, law firms can embrace the cloud and maximize their time and profits.

Why Should My Firm Use Cloud-Based Software?

Traditionally, law firms have relied on in-office software that is installed on a local computer or server within the office space. These servers are only accessible from computers in the same space but limit any remote access or capability. This setup quickly became an issue for law firms looking to sustain business continuity during the pandemic.

A cloud-based solution isn’t installed locally on the office server but is fully hosted on the internet. It uses a remote server maintained by the software provider, and access occurs through the internet. More recently, cloud-based legal practice management software has become the gold standard for law firms to manage and operate their business from anywhere. LPMs have slowly started to replace traditional servers and become the backbone for law firms to handle client management, calendaring, tasks, billing, and document storage.

Even post-pandemic, law firms are still learning to embrace legal technology and leverage the advantages of shifting their practice to the cloud. When done correctly and with the right resources, cloud-based law firms can improve aspects of their business from accessibility, security, client support, and even hiring and retention.

If you’re still on the fence about moving your firm to the cloud, here are 5 benefits that may change your mind:

Person checking phone for security code

1. Improved Security

Legal technology has come a long way in recent years with a strong emphasis on compliance and security. Law firms may be concerned about security, but some are realizing the cloud is more secure and cost-efficient than an on-premise solution. This is mostly because on-premise solutions typically require specialized support staff to perform lucrative updates to the system. These updates can cause severe downtime and even cost money calling in support.

With a cloud-based legal practice management software like PracticePanther, the all-in-one platform automatically updates and comes with the security and support your firm needs. The platform comes equipped with ABA and IOLTA compliant features and 256-bit military-grade encryption to ensure confidential information is safeguarded. It also offers two-factor authentication and customized security settings, which allow law firms to limit access to certain aspects of the software for some staff members.

Person communicating via video call

2. Supports Remote and Hybrid Work

Though many law firms are still working out the kinks — remote and hybrid working environments are a mainstay in the legal industry. Many lawyers are enjoying the productivity benefits and work-life balance of remote or hybrid schedules, allowing them to put in the hours they need for casework while also balancing their responsibilities at home.

On-premise legal software limits lawyers with remote work in many ways. Cloud-based legal software enables law firms to work securely within a centralized platform from anywhere. This allows staff to continue their responsibilities without risking accessibility or tasks falling through the cracks when staff are in different locations. For example, PracticePanther can create workflows with triggered tasks for staff to complete a new client onboarding, send documents for electronic signature, and even process payments. This process can be done from anywhere and lives in one system where the appropriate staff can easily access the case or client matter.

3. Streamlined Billing and Online Payments

Clients’ expectations have shifted and they want more convenient processes, especially with legal billing and how they conduct business with law firms. These clients are already using online services for virtually everything, from grocery shopping to accessing medical bills, and they want the same digital experience from their lawyers.

Cloud-based software makes this simple, especially when billing and online payments are built natively. This means firms can track time, create invoices, and send them for payment with easy-to-use payment links embedded. Platforms like PracticePanther also include exclusive reporting functions so firms can gain better insight into where and how their cash flow is generated to make more informed business decisions.

Outlook on Cloud-Based Firms

Cloud-based software offers law firms a unique opportunity to manage their practice and staff while growing their business from virtually anywhere. This structure has proved sustainable for many law firms and will continue to be the standard in the legal industry for firms that want to remain competitive and most importantly, profitable.

© Copyright 2022 PracticePanther

Throwing Out the Privacy Policy is a Bad Idea

The public internet has been around for about thirty years and consumers’ browser-based graphic-heavy experience has existed for about twenty-five years. In the early days, commercial websites operated without privacy policies.

Eventually, people started to realize that they were leaving trails of information online, and in the early ‘aughts the methods for business capturing and profiting from these trails became clear, although the actual uses of the data on individual sites was not clear. People asked for greater transparency from the sites they visited online, and in response received the privacy policy.

A deeply-flawed instrument, the website privacy policy purports to explain how information is gathered and used by a website owner, but most such policies are strangely both imprecise and too long, losing the average reader in a fog of legalese language and marginally relevant facts. Some privacy policies are intentionally obtuse because it doesn’t profit the website operator to make its methods obvious. Many are overly general, in part because the website company doesn’t want to change its policy every time it shifts business practices or vendor alliances. Many are just messy and poorly written.

Part of the reason that privacy policies are confusing is that data privacy is not a precise concept. The definition of data is context dependent. Data can mean the information about a transaction, information gathered from your browser visit (include where you were before and after the visit), information about you or your equipment, or even information derived by analysis of the other information. And we know that de-identified data can be re-identified in many cases, and that even a collection a generic data can lead to one of many ways to identify a person.

The definition of data is context dependent.

The definition of privacy is also untidy. An ecommerce company must capture certain information to fulfill an online order. In this era of connected objects, the company may continue to take information from the item while the consumer is using it. This is true for equipment from televisions to dishwashers to sex toys. The company likely uses this information internally to develop its products. It may use the data to market more goods or services to the consumer. It may transfer the information to other companies so they can market their products more effectively. The company may provide the information to the government. This week’s New Yorker devotes several pages to how the word “privacy” conflates major concepts in US law, including secrecy and autonomy,1 and is thus confusing to courts and public alike.

All of this is difficult to reflect in a privacy policy, even if the company has incentive to provide useful information to its customers.

Last month the Washington Post ran an article by Geoffrey Fowler that was subtitled “Let’s abolish reading privacy policies.” The article notes a 2019 Pew survey claiming that only 9 percent of Americans say they always read privacy policies. I would suggest that more than half of those Americans are lying. Almost no one always reads privacy policies upon first entering a website or downloading an app. That’s not even really what privacy policies are for.

Fowler shows why people do not read these policies. He writes, “As an experiment, I tallied up all of the privacy policies just for the apps on my phone. It totaled nearly 1 million words. “War and Peace” is about half as long. And that’s just my phone. Back in 2008, Lorrie Cranor, a professor of engineering and public policy at Carnegie Mellon University, and a colleague estimated that reading and consenting to all the privacy policies on websites Americans visit would take 244 hours per year.”

The length, complexity and opacity of online privacy policies are concerning. The best alleviation for this concern would not be to eliminate privacy policies, but to make them less instrumental in the most important decisions about descriptive data.

Limit companies’ use of data and we won’t need to fight through their privacy options.

Website owners should not be expected to write out privacy policies that are both sufficiently detailed and succinctly readable so that consumers can make meaningful choices about use of the data that describes them. This type of system forces a person to be responsible for her own data protection and takes the onus off of the company to limit its use of the data. It is like our current system of waste recycling – both ineffective and supported by polluters, because rather than forcing manufacturers to use more environmentally friendly packaging, it pushes consumers to deal with the problem at home, shifting the burden from industry to us.  Similarly, if the legislatures provided a set of simple rules for website operators – here is what you are allowed to do with personal data, and here is what you are not allowed to do with it – then no one would read privacy policies to make sure data about our transactions was spared the worst treatment. The worst treatment would be illegal.

State laws are moving in this direction, providing simpler rules restricting certain uses and transfers of personal data and sensitive data. We are early in the process, but if the trend continues regarding omnibus state privacy laws in the same manner that all states eventually passed data breach disclosure laws, then we can be optimistic and expect full coverage of online privacy rules for all Americans within a decade or so. But we shouldn’t need to wait for all states to comply.

Unlike the data breach disclosure laws which encourage companies to comply only with the laws relevant to their particular loss of data, omnibus privacy laws affect the way companies conduct the normal course of everyday business, so it will only take requirements in a few states before big companies start building their privacy rights recognition functions around the lowest common denominator. It will simply make economic sense for businesses to give every US customer the same rights as most protective state provides its residents. Why build 50 sets of rules when you don’t need to do so? The cost savings of maintaining only one privacy rights-recognition system will offset the cost of providing privacy rights to people in states who haven’t passed omnibus laws yet.

This won’t make privacy policies any easier to read, but it will become less important to read them. Then privacy policies can return to their core function, providing a record of how a company treats data. In other words, a reference document, rather than a set of choices inset into a pillow of legal terms.

We shouldn’t eliminate the privacy policy. We should reduce the importance of such polices, and limit their functions, reducing customer frustration with the privacy policy’s role in our current process. Limit companies’ use of data and we won’t need to fight through their privacy options.


ENDNOTES

1 Privacy law also conflates these meanings with obscurity in a crowd or in public.


Article By Theodore F. Claypoole of Womble Bond Dickinson (US) LLP

Copyright © 2022 Womble Bond Dickinson (US) LLP All Rights Reserved.

CMS Reduces COVID-19 Vaccine Mandate Surveys and Rescinds Surveyor Vaccination Requirements

In two recent memoranda, the Centers for Medicare and Medicaid Services (CMS) made changes to previously issued survey guidance related to COVID-19 vaccination issues.

In QSO-22-17-ALL, CMS modified the frequency by which State Agencies and Accreditation Organizations will survey for compliance with the federal staff vaccine mandate applicable to health care providers and suppliers (discussed in a prior post).  Noting that 95% of providers and suppliers surveyed have been found in substantial compliance with the rule, CMS is eliminating the previous requirement that State Agencies and Accreditation Organizations survey for compliance with the vaccine mandate during every survey.  Review of compliance with vaccine mandate is still required, however, during initial surveys, recertification surveys, and in response to specific complaint allegations that allege non-compliance with the staff vaccination requirement.  This means that a State Agency or Accreditation Organization is not required to review compliance with the staff vaccination requirement during, for example, a validation survey or a complaint survey unrelated to compliance with the staff vaccination requirement.  A State Agency or Accreditation Organization may still choose to expand any survey to include review of vaccine mandate compliance; however, the new guidance should result in a reduction in survey frequency of this issue for providers and suppliers.

In QSO-22-18-ALL, CMS rescinded, in its entirety, the previously issued QSO-22-10-ALL memorandum, which had mandated that surveyors of State Agencies and Accreditation Organizations be vaccinated for COVID-19.  However, CMS noted that the State Agencies and Accreditation Organizations were responsible for compliance and prohibited providers and suppliers from asking surveyors for proof of vaccination.  While CMS is now encouraging vaccination of surveyors performing federal oversight surveys, the mandate for vaccination is no longer in effect.

Article By Allen R. Killworth of Epstein Becker & Green, P.C.

For more coronavirus legal news, click here to visit the National Law Review.

©2022 Epstein Becker & Green, P.C. All rights reserved.

How to Write Better Client Alerts and Blog Posts

One of the most effective marketing strategies for lawyers is writing client alerts and blog posts on a regular basis. Publishing content like this establishes you as a thought leader and helps to keep you top of mind with your clients, referrals, prospects and the media and bolsters your SEO results too.

So, what makes a good client alert or blog post? It’s not about writing the longest alert or publishing it before your competitors or including every detail about the court decision.

I see many law firms publish client alerts with good intentions – the whole idea is to get helpful information to your clients and prospects as quickly as possible with interesting insights.

A lot of law firms sometimes miss the mark because their client alerts are either just regurgitating facts, don’t have a lot of insight in them, are too long, are written in legalese and they’re not client-centric meaning they don’t put the client first and aren’t written for them and their needs, which completely defeats the point.

I also see alerts that are too cute or clever – with headlines based on movies, TV shows or music lyrics . What you really want to do is deliver a clear promise in the headline and provide value while engaging your reader.

A strong headline is often the determining factor on whether someone actually opens the content or not. You also must actually deliver on what you say you’re going to provide in the alert.

So if the alert says it is going to be on X topic and the first few sentences lead you to believe that, but then it goes down another path, that’s clickbait and frustrates the reader.

Almost as important as what you write is how you structure the alert. Dense, long paragraphs are not going to capture your reader’s attention today. Try using shorter paragraphs with subheadings. Make it easy for someone to follow along and find points of engagement. Bulleted or numbered lists also work well to engage your reader.

In addition, make sure your alert has a vantage point. Just regurgitating information that somebody can find on a public website about a major decision or case or update in the law is not very poignant, memorable, relevant or helpful.

What is helpful and useful is explaining what the decision or update means for your client’s business.  And of course, the hidden underlying message is “we can help you with this, we care about you and our insights can help solve your thorniest legal and business needs.” Just make sure that your content supports that too.

Writing client alerts and blog posts is one of the best ways to get back in touch with your clients, referrals and prospects in a way that showcases your subject-matter authority. Plus you’re not even thinking about all of the silent viewers and readers of your content and how that can actually lead to new business, greater visibility and brand recognition.

If writing a client alert or blog post seems too overwhelming to do alone, buddy up with a colleague or even better – a client. The summer is a great time to focus on drafting and publishing a piece of content like this, so what are you waiting for?

Watch this video for more tips on writing a better client alert or blog post.

Copyright © 2022, Stefanie M. Marrone. All Rights Reserved.

Governor Rolls Back California COVID-19 Executive Orders & Cal/OSHA Releases Draft Permanent COVID-19 Standard

On June 17, 2022, Governor Newsom issued an executive order terminating certain provisions of prior executive orders related to Cal/OSHA’s COVID-19 Emergency Temporary Standards (ETS). Some of the terminated orders were no longer necessary due to changes in the ETS. For example, previously the Governor had issued an executive order stating exclusion periods could not be longer than California Department of Public Health (CDPH) guidelines or local ordinances. However, since the ETS now defers to CDPH guidance on isolation and quarantine, the Governor has rescinded his prior executive order on this issue. Moreover, Cal/OSHA has issued guidance for employers on COVID-19 Isolation and Quarantine that aligns with CDPH requirements.

The current version of the ETS remains in effect until the end of 2022. However, Cal/OSHA won’t be done with COVID-19 regulations in 2023. The agency is currently working on a permanent COVID-19 Standard. Recently, the draft of the proposed regulation was released.

The draft regulation carries over many of the employer obligations from the current ETS. The following are some of the proposed requirements:

  • COVID-19 procedures, either included in their Injury and Illness Prevention Program (IIPP) or a separate document.
  • Exclusion and prevention requirements for positive employees and close contacts.
  • Employers would continue to be required to provide testing to employees who have a close contact in the workplace.
  • Employers would continue to have notice requirements for COVID-19 exposure.
  • Employers would continue to have to provide face coverings to employees.
  • Employers would continue to have reporting and recordkeeping requirements for COVID-19 cases and outbreaks in the workplace.

Currently, no public hearing has been set for the proposed permanent COVID-19 Standard, so it is uncertain how soon the regulations may be implemented.

Jackson Lewis P.C. © 2022

Uyghur Forced Labor Prevention Act Takes Effect: What Importers Need to Know

The Uyghur Forced Labor Prevention Act (UFLPA) is in effect as of June 21, 2022. Congress passed the Act in December 2021 to increase enforcement of longstanding U.S. policy prohibiting the importation of goods, or components thereof, made with forced labor and to create a “rebuttable presumption” that merchandise from the Xinjiang Uyghur Autonomous Region (XUAR) or by an entity on the UFLPA Entity List is made with forced labor and thereby prohibited from entry into the United States. The rebuttable presumption applies to downstream products that incorporate inputs from XUAR, regardless of where the finished products are manufactured, including goods from outside XUAR in the People’s Republic of China (PRC), or in third countries. There is no de minimis provision in the law – any prohibited content, no matter how small, will make a product subject to the rebuttable presumption made by the law. If an importer can demonstrate by “clear and convincing” evidence that the goods were not produced wholly or in part by forced labor, U.S. Customs and Border Protection (CBP) will grant an “exception” to the presumption. The UFLPA provides for increased detentions and seizures of merchandise and potential civil and criminal penalties. See prior GT Alerts on the UFLPA.

Pursuant to the UFLPA, a multi-agency task force chaired by the Department of Homeland Security was mandated to develop a strategy for the Act’s implementation. On June 17, in anticipation of the June 21 effective date, DHS released the “Strategy to Prevent the Importation of Goods Mined, Produced, or Manufactured with Forced Labor in the People’s Republic of China” (Enforcement Strategy), which includes:

  • An assessment of risk of importing goods mined, produced, or manufactured, wholly or in part, in the PRC; according to the strategy, complex supply chains that touch XUAR are “highly susceptible to contamination by goods made using forced labor.”
  • list of entities affiliated with forced labor; therefore, their products are subject to the presumption that their goods are prohibited from entry. The Entity list will be updated multiple times per year and will be publicly available.
  • A list of high priority sectors and products including apparel and textiles, cotton and cotton products, polysilicon, and tomato products. Other products listed include footwear, nails, electronics, and toys.
  • Guidance to importers advising that companies need heightened due diligence to ensure compliance with UFLPA and to identify potential supply chain exposure to Xinjiang. Supply chain tracing is the general method to demonstrate that goods are free of inputs from Xinjiang, but CBP expects that barriers to supply chain tracing may make it difficult for importers to be compliant and has stated that third-party audits alone are insufficient to demonstrate due diligence.

Should CBP detain goods on suspicion of being made wholly or in part with forced labor, the importer has options. It can re-export the goods (up until CBP seizes them); it can abandon the goods; it can seek an “exception” for the goods, to get them released from CBP custody; it can also provide information to CBP demonstrating that the goods are not subject in any way to the Act. The evidence and documentation needed for the latter two must be “clear and convincing.”

It should be noted that in order to obtain an “exception” for goods that have been detained, an importer must meet all three of the following requirements:

  • Provide clear and convincing evidence that the detained goods were not made in whole or in part with forced labor, or were sourced from entities on the Entity List.
  • Fully and substantively respond to any questions from CBP.
  • Show that it has complied with all of the requirements set out in the Enforcement Strategy and CBP’s Operational Guidance (i.e., due diligence, supply chain tracing and management, etc.).

The Enforcement Strategy document provides importers with guidance in the following three areas:

  • Due diligence, effective supply chain tracing, and supply chain management measures to ensure that no goods violating the Act enter the importer’s supply chain.
  • The type, nature, and extent of evidence that demonstrates that goods originating in China were not mined (or grown), produced, or manufactured wholly or in part in Xinjiang.
  • The type, nature, and extent of evidence that demonstrates goods originating in China, including goods detained under Section 307 of the Tariff Act, were not mined (or grown), produced, or manufactured wholly or in part with forced labor.

CBP has made it clear that should there be a detention, participants in the Customs and Trade Partnership Against Terrorism program (C-TPAT) will be prioritized for review of submissions to rebut the presumption that the merchandise was made with forced labor.

Importers may wish to plan for contingencies should CBP detain imported merchandise, map complex supply chains and review purchase agreements and supplier codes of conduct.

©2022 Greenberg Traurig, LLP. All rights reserved.

Auto Industry Picks up Capitol Hill Advocacy on Reports of Resurgence of Biden’s Build Back Better (BBB) Proposal

Last week, General Motors Chair and CEO Marry Barra, Toyota Motor North America President and CEO Ted Ogawa, Ford Motor Company CEO James Farley, and Stellantis CEO Carlos Taveres sent a letter to Senate Democratic Leader Chuck Schumer, Senate Republican Leader Mitch McConnell, House Speaker Nancy Pelosi, and House Minority Leader Kevin McCarthy revamping the industry’s advocacy for the inclusion of certain production tax credits ahead of a possible budget reconciliation package.

This letter comes on the heels of recent reports on Capitol Hill that the lynchpin to the Senate passing a budget reconciliation package, Senator Joe Manchin (D-WV), has had multiple in person conversations with Senate Democrat Leader Chuck Schumer regarding a legislative path forward on the proposal.

The letter specifically advocated for the inclusion in any final BBB proposal of House-passed legislation, authored by Congressman Dan Kildee (D-MI-05) and Senator Debbie Stabenow (D-MI) which would extend and build on current tax credits for EVs. Specifically, the provision would make consumers eligible for a $7,500 credit for eligible EV purchases for the first five years and an additional $4,500 credit if the EV is manufactured by a unionized facility, and an additional $500 credit if the EV uses an American made battery. In addition, the proposal would amend the current credit authority to make the credits refundable and transferrable at the time of purchase rather than consumers having to claim the credit on their tax return. Finally, the proposal would bar consumers making over $400,000 from eligibility and creates EV price limits to preclude luxury EVs from eligibility.

While this provision enjoys broad Democrat support in the Senate, Senator Manchin, foreign automakers and Tesla have publicly criticized the $4,500 bonus for union made vehicles.

Additional Electric Vehicle Infrastructure funding that could be included in the bill include:

  • Electric Vehicle Supply Equipment Rebate Program –$2 billion for eligible entities for covered expenses associated with EV supplies including grounding conductors, attachment plugs and other fittings, electrical equipment, batteries, among other things;
  • Electric Vehicle Charging Equity Program – $1 billion to provide technical assistance, education and outreach, or grants for projects that increase deployment and accessibility of EV supply equipment in underserved or disadvantaged communities;
  • General Services Administration Clean Vehicle Fleet program – $5 billion for GSA for the procurement of EVs and related infrastructure for the Federal Fleet (excluding USPS and DOD vehicles);
  • United States Postal Service Clean Vehicle Fleet and Facility Maintenance – $3 billion for the USPS to purchase electric delivery vehicles and $4 billion for the purchase of related infrastructure; and
  • District of Columbia Clean Vehicle Fleet – $10 million for the District of Columbia for the procurement of EVs and related infrastructure.

While it is unclear what would be in a final BBB deal or if it would have the votes to pass the House and the Senate, industry representatives are descending on Capitol Hill to push for critical funding and tax provisions that could have significant benefits to their respective industries, especially those provisions that could lower costs for producers and consumers in the current economic climate.

© 2022 Foley & Lardner LLP

You Have Mail (Better Read It): District Court Finds EEOC 90-Day Deadline Starts When Email Received

If a letter from the EEOC is in your virtual mailbox but you never open it, have you received it? Most of us are familiar with the requirement that a claimant who files an EEOC charge has 90 days to file a lawsuit after receiving what is usually required a “right-to-sue” letter from the agency. This is one of the deadlines that both plaintiff and defense counsel track on their calendars. But when is that notice officially “received” by the claimant — especially in these days of electronic correspondence? In Paniconi v. Abington Hospital-Jefferson Health, one Pennsylvania federal court decided to draw a hard line on when that date actually occurs.

A Cautionary Tale

Denise Paniconi worked for a hospital in Pennsylvania and filed a charge of discrimination with the EEOC alleging race and religious discrimination. The EEOC investigated and issued a right-to-sue letter dated September 8, 2021, which gave her 90 days to file her complaint. She filed her complaint 91 days after the EEOC issued the letter. The employer moved to dismiss the complaint for failing to comply with the 90-day deadline.

What ordinarily would just be a day counting exercise took a twist because of how the EEOC issued the notice. The EEOC sent both the plaintiff and her lawyer an email stating that there was an “important document” now available on the EEOC portal. Neither the plaintiff nor her lawyer opened the email or accessed the portal until sometime later. They argued that the 90-day filing deadline should run from the date that the claimant actually accesses the document, not from the date the EEOC notified them it was available.

The court dismissed the complaint for failing to meet the deadline. The opinion noted that although the 90-day period is not a “jurisdictional predicate,” it cannot be extended, even by one day, without some sort of recognized equitable consideration. Paniconi’s lawyer argued that the court should apply the old rule for snail mail  ̶  without proof otherwise, it should be assumed that the notice is received within three days after the issuance date. The court disagreed and pointed out that no one disputed the date that the email was sent  ̶   it was simply not opened and read by either Paniconi or her lawyer. The court said that there was no reason that those individuals did not open the email and meet the 90-day deadline.

Deadlines Are Important

This is another example of how electronic communication can complicate the legal world. The EEOC has leaned into its use of the portal, and the rest of the world needs to get used to it. The minute you receive an email or notice from the portal, you need to calendar that deadline. Some courts (at least this one) believe that electronic communication is immediate, and you may not get grace for not logging on and finding out what is happening with your charge. Yet another reason to stay on top of your emails.

© 2022 Bradley Arant Boult Cummings LLP

The Intersection of the Bipartisan Infrastructure Law and Davis-Bacon Act Requirements for Federal Contractors and Subcontractors

On November 15, 2021, President Joe Biden signed the $1.2 trillion Infrastructure Investment and Jobs Act into law, which is popularly known as the Bipartisan Infrastructure Law (“BIL”).

The BIL is estimated to create an additional 800,000 jobs.  The United States Department of Labor (“DOL”) contends that such new jobs will “expand the middle class, revitalize our nation’s transportation, communications and utility systems and build a more resilient, reliable, and environmentally sound future.”  The White House asserts that the BIL will provide protection to “critical labor standards on construction projects,” as a substantial portion of the construction projects included in the BIL will be subject to requirements of the Davis-Bacon Act (“DBA” or the “Act”).

While the BIL provides new revenue sources and opportunities for construction projects, federal contractors and subcontractors should ensure that their businesses comply with the DBA’s prevailing wage rates and labor standards requirements.

Scope and Coverage of DBA

In its simplest form, the DBA, enacted in 1931, requires federal contractors and subcontractors to pay prevailing wage rates and fringe benefits to certain construction workers employed on certain federal contracts.  The DOL’s Wage and Hour Division (“WHD”) administers and enforces the Act’s requirements on federally funded and assisted construction projects.  The DBA applies to contracts:

  1. Which the Federal Government or the District of Columbia is a party;

  2. For the construction, alteration, or repair, such as painting and decorating, of public buildings and public works to which the Federal Government or the District of Columbia is a party;

  3. Involving the employment of mechanics, laborers, and other workers that engage in manual or physical labor (except for individuals performing administrative, clerical, professional, or management work such as superintendents, project managers, engineers, or office staff); and

  4. Which are in excess of $2,000.

With respect to the DBA applying to federal contracts above $2,000, this value threshold only applies to the initial federal contract.  If the threshold is met, however, then the DBA applies to any lower-tier subcontracts even if the value of the subcontract is less than $2,000.

Requirements for Contractors and Subcontractors

There are various requirements for federal contractors and subcontractors under the DBA, which the United States Supreme Court has described as “a minimum wage law designed for the benefit of construction workers.”  The Act was designed to protect construction workers’ wage standards from federal contractors who may base their contract bids on wage rates that are lower than the local wage level.  Under the DBA, federal contractors and subcontractors are required, among other things, to do the following:

  1. Pay covered workers who work on the work site the prevailing wage rates and fringe benefits that are listed in the applicable wage determinations, which are provided by the WHD (the prevailing wage rate consists of both the basic hourly rate of pay and any fringe benefits to bona fide third-party plans, which may include medical insurance; life and disability insurance; pensions on retirement or death; compensation for injuries or illness resulting from occupational activity; or other bona fide fringe benefits – bona fide fringe benefits, however, do not include payments made by employer contractors or subcontractors that are required by other federal, state, or local laws such as required contributions to unemployment insurance);

  2. Maintain accurate payroll records for employees that must be submitted to the contracting agency on a weekly basis (within seven days following the regular pay date for the particular workweek), which must include the following for covered employees: (i) name; (ii) classification; (iii) daily and weekly hours worked; and (iv) deductions made and actual wages paid (there are additional recordkeeping requirements for federal contractors who employ apprentices or trainees under approved DOL programs);

    • Federal contractors and subcontractors are also required to preserve the payroll records for three years following the completion of the covered work, provide accessibility to the records upon request by the DOL or its representatives, and allow the DOL or its representatives to interview employees during work hours.

    • Federal contractors and subcontractors can use the WHD’s Form WH-347 to satisfy the weekly reporting requirements.

  3. With respect to prime or general contractors, they must ensure that specific contract clauses and the applicable wage determinations are inserted into any lower-tier subcontracts (the contract clauses cover the following: (i) construction wage rate requirements; (ii) withholding of funds; (iii) payrolls and basic records; (iv) apprentices and trainees; (v) compliance with requirements under the Copeland Act; (vi) requirements for subcontracts; (vii) contract termination – debarment; (viii) compliance with construction wage rate requirements and related regulations; (ix) disputes concerning labor standards; and (x) certification of eligibility); and

  4. Post a notice of the prevailing wages as to every classification of worker and an “Employee Rights under the DBA” poster in a prominent location that is easily accessible to the covered workers at the work site.

Practical Consideration in Compliance with DBA

Federal contractors and subcontractors should ensure that covered workers are properly classified for the work such individuals perform and paid in accordance with the prevailing wage rate for their classification.

Employers will often face recordkeeping challenges when they have nonexempt employees who perform covered (manual) work and non-covered (administrative) work in the same workweek.

In such instances, the employer must determine whether the employee is salaried or paid hourly.  If the employee is salaried, the employer must determine whether the employee’s salary is greater than or equal to the prevailing wage rate for the employee’s classification.  If not, the employer contractor is required to increase the employee’s pay for the week the covered work is performed.

Likewise, if the employee is paid hourly, then the employer must ensure the employee’s hourly rate is greater than or equal to the prevailing wage rate for the employee’s classification.

Federal contractors and subcontractors could face various consequences due to their failure to comply with the DBA, ranging from termination of the federal contract and debarment to a contracting agency withholding money due to the contractor to cover back wages due to employees as well as criminal prosecution.  Accordingly, federal contractors and subcontractors should consult with legal counsel to ensure they comply with the various DBA requirements for any covered contracts.

© 2022 Ward and Smith, P.A.. All Rights Reserved.