Compliance Update — Insights and Highlights January 2024

On December 7, 2023, the Consumer Financial Protection Bureau (CFPB) ordered Atlantic Union Bank, an approximately $20 billion bank headquartered in Richmond, Virginia, to pay $6.2 million for “illegal overdraft fee harvesting” and “illegally enrolling thousands of customers in checking account overdraft programs.” The bank was ordered to pay $5 million in refunds and $1.2 million to a victims’ relief fund.

Regulation E provides that a bank may not charge a fee for an ATM or one-time debit card transaction unless it completes four steps. First, the bank must provide the customer with a notice describing the bank’s overdraft services in writing. Then, the bank must provide the customer with a “reasonable opportunity” for that customer to “affirmatively consent” to the payment of the ATM or one-time debit card transaction fee. Third, the customer must provide that “affirmative consent” or opt-in to the bank. And finally, the bank must provide the customer with written confirmation of their consent, including a statement of the right to revoke the consent at any time.

The CFPB alleged that Atlantic Union Bank failed to obtain proper consent when an account was opened in person at a branch. Bank employees orally provided customers with options for opting in to the payment of one-time debit card and ATM transaction fees pursuant to Regulation E. Bank employees asked customers to opt in orallyand then input the option into the bank’s account-opening computer system before printing the written consent form. The consent form was printed at the end of the account-opening process and was pre-populated with the customer’s oral opt-in choice.

In instances in which a customer was given options for opting in to the payment of one-time debit card and ATM transaction fees over the phone, bank employees did not have a script and allegedly provided misinformation and misleading statements about the benefits, costs, and other aspects of opting in to the payment of one-time debit card and ATM transaction fees pursuant to Regulation E.

The CFPB has taken the logical approach that a bank must provide the customer with a written disclosure of its overdraft practices prior to having them opt in. Additionally, without providing the customer with a prior written disclosure, a bank should not pre-populate its Regulation E opt-in form. Now is the time to review the consent order and your bank’s Regulation E opt-in processes and procedures.

For more news on CFPB Compliance, visit the NLR Financial Institutions & Banking section.

Minimizing National Labor Relations Act Liability for Employers with Non-Unionized Workforces

This post continues our consideration of comments submitted in response to proposed regulations under the Mental Health Parity and Addiction Equity Act (MHPAEA).

Under current law, if a plan provides any mental health or substance use disorder (MH/SUD) benefits in any classification of benefits, benefits for that condition or use disorder must be provided in every classification in which medical/surgical (M/S) benefits are provided. Classifications for this purpose include inpatient, in-network; inpatient, out-of-network; outpatient, in-network; outpatient, out-of-network; emergency care; and prescription drugs. The proposed regulations modify this standard by providing that a plan does not provide benefits for MH/SUD benefits in every classification in which M/S benefits are provided unless the plan provides meaningful benefits for treatment for the condition or disorder in each such classification “as determined in comparison to the benefits provided for medical/surgical conditions in the classification.”

The term “meaningful benefits” is nowhere defined. The regulators nevertheless “recognize that the proposal to require meaningful benefits [ ] is related to scope of services.” “Scope of services” for this purpose generally refers to the types of treatments and treatment settings that are covered by a group health plan or health insurance issuer. The preamble to the proposed regulation invites comments on how the meaningful benefits requirement “would interact with the approach related to scope of services adopted under the 2013 final regulations.” The preamble of the 2013 final regulations addressed an issue characterized as ‘‘scope of services’’ or ‘‘continuum of care’’ but otherwise failed to provide any substance. Two examples from the proposed regulations do, however, give us a sense of what the regulators have in mind.

  • A plan that generally covers treatment for autism spectrum disorder (ASD), a mental health condition, and covers outpatient, out-of-network developmental evaluations for ASD but excludes all other benefits for outpatient treatment for ASD, including applied behavior analysis (ABA) therapy, when provided on an out-of-network basis. (ABA therapy is one of the primary treatments for ASD in children.) The plan generally covers the full range of outpatient treatments and treatment settings for M/S conditions and procedures when provided on an out-of-network basis. The plan in this example violates the applicable parity standards.
  • In another example, a plan generally covers diagnosis and treatment for eating disorders, a mental health condition, but specifically excludes coverage for nutrition counseling to treat eating disorders, including in the outpatient, in-network classification. Nutrition counseling is one of the primary treatments for eating disorders. The plan generally provides benefits for the primary treatments for medical conditions and surgical procedures in the outpatient, in-network classification. The exclusion of coverage for nutrition counseling for eating disorders results in the plan failing to provide meaningful benefits for the treatment of eating disorders in the outpatient, in-network classification, as determined in comparison to the benefits provided for M/S conditions in the classification. Therefore, the plan violates the proposed rules.

Notably, the newly proposed meaningful benefits requirement is separate from, and in addition to, the newly prescribed nonquantitative treatment limitation (NQTL) testing standards. These latter standards include a “no more restrictive” requirement, a “design and application” requirement and an “outcomes data and network composition” requirement. A handful of comments nevertheless urge the regulators to add scope of services to its non-exhaustive list of NQTLs. As a result, a plan’s scope of services would be subject to comprehensive NQTL testing. Or, put another way, they would be fed back into the NQTL testing loop. Using the first of the examples above, this would require that ABA therapy to be first compared to the treatment limitations imposed on some M/S benefits in each classification. But what benefits, exactly? The problem is that a plan’s scope of services – what types of treatments a plan will pay for and in what settings – is a high-level plan design feature and not an NQTL.

While reasonable minds can and do differ on much of the substance of the proposed regulations, we doubt that anyone would claim that they streamline or simplify compliance. Compliance with these rules is already complicated and expensive; if the final rule looks anything like the proposed regulations, compliance will only get more complicated and more expensive. The proposed meaningful benefits requirement is intended to prevent plans, as a matter of plan design, from satisfying the parity rules by offering nominal or insubstantial MH/SUD benefits when compared to similar M/S benefits in each classification. Treating a plan’s scope of services as itself a separate NQTL does not advance this goal.

Third Time’s a Charm? SEC & CFTC Finalize Amendments to Form PF

On February 8, the Securities and Exchange Commission (SEC) and Commodity Futures Trading Commission (CFTC) jointly adopted amendments to Form PF, the confidential reporting form for certain registered investment advisers to private funds. Form PF’s dual purpose is to assist the SEC’s and CFTC’s regulatory oversight of private fund advisers (who may be both SEC-registered investment advisers and also registered with the CFTC as commodity pool operators or commodity trading advisers) and investor protection efforts, as well as help the Financial Stability Oversight Council monitor systemic risk. In addition, the SEC entered into a memorandum of understanding with the CFTC to facilitate data sharing between the two agencies regarding information submitted on Form PF.

Continued Spotlight on Private Funds

The continued focus on private funds and private fund advisers is a recurring theme. The SEC recently adopted controversial and sweeping new rules governing many activities of private funds and private fund advisers. The SEC’s Division of Examinations also continues to highlight private funds in its annual examination priorities. Form PF is similarly no stranger to recent revisions and expansions in its scope. First, in May 2023, the SEC adopted requirements for certain advisers to hedge funds and private equity funds to provide current reporting of key events (within 72 hours). Second, in July 2023, the SEC finalized amendments to Form PF for large liquidity fund advisers to align their reporting requirements with those of money market funds. And last week, this third set of amendments to Form PF, briefly discussed below.

SEC Commissioner Peirce, in dissent:

“Boundless curiosity is wonderful in a small child; it is a less attractive trait in regulatory agencies…. Systemic risk involves the forest — trying to monitor the state of every individual tree at every given moment in time is a distraction and trades off the mistaken belief that we have the capacity to draw meaning from limitless amounts of discrete and often disparate information. Unbridled curiosity seems to be driving this decision rather than demonstrated need.”

Additional Reporting by Large Hedge Fund Advisers on Qualifying Hedge Funds

These amendments will, among other things, expand the reporting requirements for large hedge fund advisers with regard to “qualifying hedge funds” (i.e., hedge funds with a net asset value of at least $500 million). The amendments will require additional disclosures in the following categories:

  • Investment exposures, borrowing and counterparty exposures, currency exposures, country and industry exposures;
  • Market factor effects;
  • Central clearing counterparty reporting;
  • Risk metrics;
  • Investment performance by strategy;
  • Portfolio, financing, and investor liquidity; and
  • Turnover.

While the final amendments increase the amount of fund-level information the Commission will receive with regard to individual qualifying hedge funds, at the same time, the Commission has eliminated the aggregate reporting requirements in Section 2a of Form PF (noting, in its view, that such aggregate information can be misleading).

Enhanced Reporting by All Hedge Funds

The amendments will require more detailed reporting on Form PF regarding:

  • Hedge fund investment strategies (while digital assets are now an available strategy to select from, the SEC opted not to adopt its proposed definition of digital assets, instead noting that if a strategy can be classified as both a digital asset strategy and another strategy, the adviser should report the strategy as the non-digital asset strategy);
  • Counterparty exposures (including borrowing and financing arrangements); and
  • Trading and clearing mechanisms.

Other Amendments That Apply to All Form PF Filers

  • General Instructions. Form PF filers will be required to report separately each component fund of a master-feeder arrangement and parallel fund structure (rather than in the aggregate as permitted under the existing Form PF), other than a disregarded feeder fund (e.g., where a feeder fund invests all its assets in a single master fund, US treasury bills, and/or “cash and cash equivalents”). In addition, the amendments revise how filers will report private fund investments in other private funds, “trading vehicles” (a newly defined term), and other funds that are not private funds. For example, Form PF will now require an adviser to include the value of a reporting fund’s investments in other private funds when responding to questions on Form PF, including determining filing obligations and reporting thresholds (unless otherwise directed by the Form).
  • All Private Funds. Form PF filers reporting information about their private funds will report additional and/or new information regarding, for example: type of private fund; identifying information about master-feeder arrangements, internal and external private funds, and parallel fund structures; withdrawal/redemption rights; reporting of gross and net asset values; inflows/outflows; base currency; borrowings and types of creditors; fair value hierarchy; beneficial ownership; and fund performance.

Final Thoughts

With the recent and significant regulatory spotlight on investment advisers to private funds and private funds themselves, we encourage advisers to consider the interrelationships between new data reporting requirements on Form PF and the myriad of new regulations and disclosure obligations being imposed on investment advisers more generally (including private fund advisers).

The effective date and compliance date for new final amendments to Form PF is 12 months following the date of publication in the Federal Register.

Robert Bourret also contributed to this article.

OECD Tour de Table Includes Information on U.S. Developments on the Safety of Manufactured Nanomaterials

The Organization for Economic Cooperation and Development (OECD) has published the latest edition of the Developments in Delegations on the Safety of Manufactured Nanomaterials and Advanced Materials — Tour de Table. The Tour de Table compiles information provided by delegations on the occasion of the 23rd meeting of the OECD Working Party on Manufactured Nanomaterials (WPMN) in June 2023. The Tour de Table lists U.S. developments on the human health and environmental safety of nanomaterials. Risk assessment decisions, including the type of nanomaterials assessed, testing recommended, and outcomes of the assessment include:

  • The U.S. Environmental Protection Agency (EPA) completed review of four low volume exemptions (LVE) that included a graphene material, a titanium dioxide material, and two graphene oxide materials, one of which was a modification to an existing exemption. EPA denied two of the LVEs and granted two under conditions that limited human and environmental exposures to prevent unreasonable risks.
  • According to the Tour de Table, EPA has under review 17 premanufacture notices (PMN), 16 of which are for multi-walled carbon nanotube chemical substances and one of which is for a graphene material. The Tour de Table states that EPA is still reviewing these 17 chemical substances for potential risks to human health and the environment. EPA completed its review of one significant new use notice (SNUN) for a single-walled carbon nanotube, regulating it with a consent order due to limited available data on nanomaterials. The consent order limits uses and human and environmental exposures to prevent unreasonable risks.

The Tour de Table includes the following information regarding risk management approaches in the United States:

  • Between June 2022 and June 2023, EPA received notification of two nanoscale substances based on metal oxides that met reporting criteria pursuant to its authority under the Toxic Substances Control Act (TSCA) Section 8(a), bringing the total number of notifications to 87. Reporting criteria exempted nanoscale chemical substances already reported as new chemicals under TSCA and those nanoscale chemical substances that did not have unique or novel properties. According to the Tour de Table, most reporting was for metals or metal oxides.
  • Since January 2005, EPA has received and reviewed more than 275 new chemical notices for nanoscale materials under TSCA, including fullerenes and carbon nano-onions, quantum dots, semiconducting nanoparticles, and carbon nanotubes. EPA has issued consent orders and significant new use rules (SNUR) permitting manufacture under limited conditions. A manufacturer or processor wishing to engage in a designated significant new use identified in a SNUR must submit a SNUN to EPA at least 90 days before engaging in the new use. The Tour de Table notes that because of confidential business information (CBI) claims by submitters, EPA may not be allowed to reveal to the public the chemical substance as a nanoscale material in every new chemical SNUR it issues for nanoscale materials. EPA will continue to issue SNURs and consent orders for new chemical nanoscale materials in the coming year.
  • Because of limited data to assess nanomaterials, the consent orders and SNURS contain requirements to limit exposure to workers through the use of personal protective equipment (PPE), limit environmental exposure by not allowing releases to surface waters or direct releases to air, and limit the specific applications/uses to those described in the new chemical notification.

Regarding updates, including proposals, or modifications to previous regulatory decisions, the Tour de Table states that “[t]he approaches used, given the level of available information, are consistent with previous regulatory decisions. EPA’s assessments now assume that the environmental hazard of a nanomaterial is unknown unless acceptable hazard data is submitted with nanomaterial submission.”

The Tour de Table lists the following new regulatory challenge(s) with respect to any action for nanomaterials:

  • Standards/methods for differentiating between different forms of the same chemical substance that is a nanomaterial;
  • Standardized testing for the physical properties that could be used to characterize/identify nanomaterials; and
  • Differentiation between genuinely new nanoscale materials introduced in commerce and existing products that have been in commerce for decades or centuries.

Commerce Department Launches Cross-Sector Consortium on AI Safety — AI: The Washington Report

  1. The Department of Commerce has launched the US AI Safety Institute Consortium (AISIC), a multistakeholder body tasked with developing AI safety standards and practices.
  2. The AISIC is currently composed of over 200 members representing industry, academia, labor, and civil society.
  3. The consortium may play an important role in implementing key provisions of President Joe Biden’s executive order on AI, including the development of guidelines on red-team testing[1] for AI and the creation of a companion resource to the AI Risk Management Framework.

Introduction: “First-Ever Consortium Dedicated to AI Safety” Launches

On February 8, 2024, the Department of Commerce announced the creation of the US AI Safety Institute Consortium (AISIC), a multistakeholder body housed within the National Institute of Standards and Technology (NIST). The purpose of the AISIC is to facilitate the development and adoption of AI safety standards and practices.

The AISIC has brought together over 200 organizations from industry, labor, academia, and civil society, with more members likely to join in the coming months.

Biden AI Executive Order Tasks Commerce Department with AI Safety Efforts

On October 30, 2023, President Joe Biden signed a wide-ranging executive order on AI (“AI EO”). This executive order has mobilized agencies across the federal bureaucracy to implement policies, convene consortiums, and issue reports on AI. Among other provisions, the AI EO directs the Department of Commerce (DOC) to establish “guidelines and best practices, with the aim of promoting consensus…[and] for developing and deploying safe, secure, and trustworthy AI systems.”

Responding to this mandate, the DOC established the US Artificial Intelligence Safety Institute (AISI) in November 2023. The role of the AISI is to “lead the U.S. government’s efforts on AI safety and trust, particularly for evaluating the most advanced AI models.” Concretely, the AISI is tasked with developing AI safety guidelines and standards and liaising with the AI safety bodies of partner nations.

The AISI is also responsible for convening multistakeholder fora on AI safety. It is in pursuance of this responsibility that the DOC has convened the AISIC.

The Responsibilities of the AISIC

“The U.S. government has a significant role to play in setting the standards and developing the tools we need to mitigate the risks and harness the immense potential of artificial intelligence,” said DOC Secretary Gina Raimondo in a statement announcing the launch of the AISIC. “President Biden directed us to pull every lever to accomplish two key goals: set safety standards and protect our innovation ecosystem. That’s precisely what the U.S. AI Safety Institute Consortium is set up to help us do.”

To achieve the objectives set out by the AI EO, the AISIC has convened leading AI developers, research institutions, and civil society groups. At launch, the AISIC has over 200 members, and that number will likely grow in the coming months.

According to NIST, members of the AISIC will engage in the following objectives:

  1. Guide the evolution of industry standards on the development and deployment of safe, secure, and trustworthy AI.
  2. Develop methods for evaluating AI capabilities, especially those that are potentially harmful.
  3. Encourage secure development practices for generative AI.
  4. Ensure the availability of testing environments for AI tools.
  5. Develop guidance and practices for red-team testing and privacy-preserving machine learning.
  6. Create guidance and tools for digital content authentication.
  7. Encourage the development of AI-related workforce skills.
  8. Conduct research on human-AI system interactions and other social implications of AI.
  9. Facilitate understanding among actors operating across the AI ecosystem.

To join the AISIC, organizations were instructed to submit a letter of intent via an online webform. If selected for participation, applicants were asked to sign a Cooperative Research and Development Agreement (CRADA)[2] with NIST. Entities that could not participate in a CRADA were, in some cases, given the option to “participate in the Consortium pursuant to separate non-CRADA agreement.”

While the initial deadline to submit a letter of intent has passed, NIST has provided that there “may be continuing opportunity to participate even after initial activity commences for participants who were not selected initially or have submitted the letter of interest after the selection process.” Inquiries regarding AISIC membership may be directed to this email address.

Conclusion: The AISIC as a Key Implementer of the AI EO?

While at the time of writing NIST has not announced concrete initiatives that the AISIC will undertake, it is likely that the body will come to play an important role in implementing key provisions of Biden’s AI EO. As discussed earlier, NIST created the AISI and the AISIC in response to the AI EO’s requirement that DOC establish “guidelines and best practices…for developing and deploying safe, secure, and trustworthy AI systems.” Under this general heading, the AI EO lists specific resources and frameworks that the DOC must establish, including:

It is premature to assert that either the AISI or the AISIC will exclusively carry out these goals, as other bodies within the DOC (such as the National AI Research Resource) may also contribute to the satisfaction of these requirements. That being said, given the correspondence between these mandates and the goals of the AISIC, along with the multistakeholder and multisectoral structure of the consortium, it is likely that the AISIC will play a significant role in carrying out these tasks.

We will continue to provide updates on the AISIC and related DOC AI initiatives. Please feel free to contact us if you have questions as to current practices or how to proceed.

Endnotes

[1] As explained in our July 2023 newsletter on Biden’s voluntary framework on AI, “red-teaming” is “a strategy whereby an entity designates a team to emulate the behavior of an adversary attempting to break or exploit the entity’s technological systems. As the red team discovers vulnerabilities, the entity patches them, making their technological systems resilient to actual adversaries.”

[2] See “CRADAs – Cooperative Research & Development Agreements” for an explanation of CRADAs. https://www.doi.gov/techtransfer/crada.

Raj Gambhir contributed to this article.

Form I-9 Software: Avoiding Unlawful Discrimination When Selecting and Using I-9 and E-Verify Software Systems

A recent employer fact sheet from the U.S. Department of Justice (DOJ) and U.S. Department of Homeland Security (DHS) provides guidance for avoiding unlawful discrimination and other violations when using private software products to complete Forms I-9 and E-Verify cases.

Quick Hits

  • Employers are responsible for selecting and using software products that avoid unlawful discrimination and comply with Form I-9 and E-Verify requirements.
  • Employers must not use software products that violate Form I-9 and E-Verify requirements or involve system limitations that unlawfully discriminate among workers.
  • DOJ and DHS advise employers to train staff on Form I-9 and E-Verify requirements, and to provide access to published government guidance on Form I-9 and E-Verify requirements.

Employer Compliance With Form I-9 Software Products

The fact sheet reminds employers to use the current Form I-9 and properly complete the Form I-9 for each new hire after November 6, 1986, with any acceptable employee documents. Form I-9 systems must comply with requirements for electronic signatures and document storage including the ability to provide Form I-9 summary files containing all information fields on electronically stored Forms I-9. The fact sheet confirms required software capabilities and employer practices to properly complete the Form I-9 and avoid unlawful discrimination.

Employers must ensure that any software:

  • allows employees to leave form fields blank, if they’re not required fields (such as Social Security numbers, if not required on E-Verify cases);
  • allows workers with only one name to record “Unknown” in the first name field and to enter their names in the last name field on the Form I-9;
  • uniquely identifies “each person accessing, correcting, or changing a Form I-9”;
  • permits Form I-9 corrections in Section 1 and does not complete Section 1 corrections for workers, unless completing preparer/translator certifications in Supplement A;
  • retains all employee information and documents presented for form completion; and
  • permits Form I-9 corrections in Section 2 and allows completion of Supplement B reverifications with any acceptable employee documents.

Employer Compliance With E-Verify Software Products

The fact sheet reminds employers to comply with E-Verify program requirements when using software interfaces for E-Verify case completion. The fact sheet confirms required software capabilities and employer practices for completing E-Verify cases. Employers must still:

  • provide employees with current versions of Further Action Notices and Referral Date Confirmation letters in resolving Tentative Nonconfirmations (mismatches) in the E-Verify system;
  • provide English and non-English Further Action Notices and Referral Date Confirmation letters to employees with limited English proficiency;
  • display E-Verify notices confirming employer use of E-Verify;
  • “promptly notify employees in private” of E-Verify mismatches and provide Further Action Notices. If an employee who has been notified of a mismatch takes action to resolve the mismatch, provide the Referral Date Confirmation letter with case-specific information;
  • delay E-Verify case creation, when required. For example, when workers are awaiting Social Security numbers or have presented acceptable receipts for Form I-9 completion, employers must be able to delay E-Verify case creation; and
  • allow employees to resolve E-Verify mismatches prior to taking any adverse action, including suspensions or withholding pay.

Prohibited Employer Activity When Using Form I-9 Software

The fact sheet notes that an employer that uses private software products for Form I-9 or E-Verify compliance is prohibited from:

  • completing the Form I-9 on an employee’s behalf unless the employer is helping an employee complete Section 1 as a preparer or translator;
  • prepopulating employee information from other sources, providing auto-correct on employee inputs, or using predictive language for form completion;
  • requiring more or less information from employees for Form I-9 completion or preventing workers from using preparers/translators for form completion;
  • improperly correcting the Form I-9, improperly creating E-Verify cases, or failing to report corrections in the Form I-9 audit trail;
  • requesting more or different documentation than needed for Form I-9 completion, or failing to complete reverification in Supplement B of the Form I-9; and
  • imposing “unnecessary obstacles” in starting work or receiving pay, “such as by requiring a Social Security number to onboard or by not paying an employee who can complete the Form I-9 and is waiting for a Social Security number.” (Emphasis in the original.)

Staff Training and Technical Support

The fact sheet warns employers against using software products that do not provide technical support to workers, and it notes that employers are required to provide training to staff on Form I-9 and E-Verify compliance. Resources for staff members using software products for Form I-9 and E-Verify case completion include I-9 Central, the Handbook for Employers M-274, the M-775, E-Verify User Manual, and DOJ publications.

Three Ways to Get Lawyers to Fall In Love with Marketing Technology

While it may (or may not) be shocking that 50% of marriages end in divorce, what may be a more jarring statistic is how 77% of lawyers have experienced a failed technology implementation. And while some may take a second or even third chance at marriage, you rarely get a second chance at a marketing technology implementation, especially at a law firm.

Today’s legal industry is hyper-competitive, firms are asking attorneys to learn new skills and adopt new technology like artificial intelligence, eMarketing, or experience management systems. So, lawyers should be eager to embrace any MarTech that could help them gain an advantage, right? Unfortunately, fewer than 40% of lawyers use a CRM, and only slightly more than a quarter of them use it for sales pipeline management.

When considering lawyers’ love/hate relationship with their firm’s marketing technology infrastructure, it is important to consider the lawyer’s perspective when it comes to change management and technology adoption. By nature, lawyers are skeptical, hypercritical, risk-averse, and reluctant to change. These attributes are certainly beneficial for practicing law, but not so much for encouraging marketing technology adoption. This is why it can sometimes feel like you are herding cats, except these cats are extremely smart, have opposable thumbs, and argue for sport.

While lawyers and technology might not seem like a match made in heaven, you can follow these steps to ensure greater adoption and utilization of your marketing technology:

1. Needs Assessment

The beauty of technology is that it can do so many things, the problem with technology is… it can do so many things. For technology to succeed it has to adequately satisfy the end users’ needs. Because each firm has its own set of unique needs, technology selection should start with a needs assessment. Interviews should be conducted with key stakeholders to determine your organization’s specific needs and requirements.

As a follow-up to the needs assessment, interview user groups like attorneys, partners and even their assistants, to understand their needs and requirements, and understand their day-to-day processes and problems. These groups each define value differently, meaning that each group will have its own unique needs or set of requirements. Making these users part of the process upfront will increase the likelihood they’ll adopt the technology later on.

2. Communicate

Like any good love affair, a successful technology deployment requires extensive communication. Attorneys must be convinced that the technology will not only benefit the firm, but them individually. It can be helpful to take the time to craft a formal communication plan -starting with an announcement coming from firm leadership outlining the system’s benefits. Realistic expectations should be set, not only for the system but also for user requirements.

Next, establish, document, and distribute any processes and procedures necessary to support the implementation. Most importantly, sharing is caring, so always communicate when goals have been reached or solicit feedback from the end users.

3. Resources

All good relationships require attention. Oftentimes, firms forget to account for the long-term costs associated with a technology deployment. For a successful technology deployment, firms must dedicate necessary resources including time, money, and people. It also takes the coordinated efforts of everyone in the firm, so be sure to invite everyone who may need to be involved, such as:

  • Technical support to assist with implementation and integrations
  • Training programs with outlined criteria for different user groups
  • Data stewards (internal or outsourced) to make sure data is clean, correct and complete
  • The marketing and business development departments that will be tasked with developing and executing a communication strategy
  • Firm leadership and key attorneys whose support can be used to drive adoption

© Copyright 2024 CLIENTSFirst Consulting

by: Christina R. Fritsch JD of CLIENTSFirst Consulting

For more news on Legal Marketing, visit the NLR Law Office Management section.

Striking a Balance: The Supreme Court and the Future of Chevron Deference

In its frequent attempts to enforce the separation of powers that the Constitution’s framers devised as a system of checks and balances among the executive, legislative, and judicial branches of the federal government, it is often the so-called “Fourth Branch”—that includes the varied administrative agencies—that is at the heart of things.[1]

These agencies possess a level of technical and scientific expertise that the federal courts generally lack. And, without reference to expertise, Congress often leaves it to agencies and the courts to interpret and apply statutes left intentionally vague or ambiguous as the product of the legislative compromise required to gain passage. This phenomenon begs the question of the extent to which the federal courts may defer to administrative agencies in interpreting such statutes, or whether such deference abnegates the judicial prerogative of saying what the law is. Having passed on several opportunities to revisit this question, the Supreme Court of the United States has finally done so.

In what potentially will lead to a decision that might substantially change the face of federal administrative law generally while voiding an untold number of agency regulations, the Supreme Court, on January 17, 2024, heard oral argument in a pair of appeals, Loper Bright Enterprises, et al., v. Raimondo, No. 22-451, and Relentless, Inc., et al. v. Department of Commerce, No. 22-1219, focusing on whether the Court should overrule or limit its seminal decision in Chevron U.S.A., Inc. v. Natural Resources Defense CouncilInc., 467 U.S. 837 (1984).

Almost 40 years ago, the Chevron decision articulated the doctrine commonly known as “Chevron deference,” which involves a two-part test for determining when a judicial determination must be deferential to the interpretation of a statute. The first element requires determining what Congress has spoken directly to the specific issue in question, and the second is “whether the agency’s answer is based on a permissible construction of the statute.”

Among the most cited Supreme Court cases, Chevron has become increasingly controversial, especially within the conservative wing of the Court, with several Justices having suggested that the doctrine has led to the usurpation of the essential function of the judiciary.

Chevron deference affects a wide range of federal regulations, and the Court’s ruling, whether or not Chevron is retained in some form, is likely to result in significant changes to how agencies may implement statutes and how parties affected by regulations may seek relief from the impact of those regulations. Interestingly, commentators on the recent oral argument in the case are widely divided in their predictions as to the outcome—some suggesting that the conservative majority of the Court will overrule Chevron outright, others suggesting that the Court has no intention at all to do so.

Based on remarks made during the oral arguments by Justice Gorsuch, and by Justices Amy Coney Barrett and Elena Kagan, as well as Justice Kagan’s fashioning of a majority that clarified a related interpretive rule in an earlier case focusing on agencies’ authority to interpret their own regulations, we suggest that there is a substantial possibility that the Court will take a moderate path by strengthening judicial scrutiny at the “Step One” level while recognizing that there are technical and scientific matters as to which courts have no expertise. At the same time, the Court may make it clear that, essentially, legal issues are within its prerogatives and are not subject to agency interpretation.

We examine how the Court might find a path to a better balancing of agency and judicial functions that is consistent with and builds upon other recent rulings involving the review of actions taken by administrative agencies. Whatever the outcome, the Court’s ruling in these cases will have a profound impact on individuals and entities that are regulated by federal agencies or that depend on participation in government programs, such as Medicare and Social Security.

Chevron Refresher

Most law students and lawyers have some familiarity with the touchstone for judicial review of agency rules that was articulated in Chevron, a case that dealt with regulations published by the Environmental Protection Agency to implement a part of the Clean Air Act.[2] The Supreme Court explained that judicial review of an agency’s final rule should be based on the two-part inquiry that we mentioned earlier. First, the reviewing court should determine whether Congress made its intent unambiguously clear in the text of the statute; if so, the inquiry ends, and both the agency and the reviewing court must give effect to Congress’s intent. This has become known by the shorthand phrase “Step One.”

If Congress’s intent is not clear, either because it did not address a specific point or used ambiguous language, then the court should defer to the agency’s construction if it is based on a permissible reading of the underlying statute. This has become known as “Step Two.”

In applying Step Two, a reviewing court should determine if the gap left by Congress was explicit or implicit. If the ambiguity is explicit, then the agency’s regulations should be upheld unless they are arbitrary, capricious, or contrary to the statute.[3] If the ambiguity is implicit, then the “court may not substitute its own construction of a statutory provision for a reasonable interpretation made by the administrator of an agency.”[4]

Chevron deference is not a blank slate for courts to find ambiguity. It recognized that the judiciary “is the final authority on issues of statutory construction” and instructed that in applying Step One, judges are expected to apply the “traditional tools of statutory construction.”[5] It also recognized that any deference analysis should fit within the balance among the branches of government. The Supreme Court explained that while Congress sets an overall policy, it may not reach specific details in explaining how that policy is to be executed in particular contexts. In these situations, the executive branch may have the necessary technical expertise to fill in the details, as it is charged with administering the policy enacted into law. The Court noted that the judiciary was not the ideal entity to fill in any gaps left in legislation because “[j]udges are not experts in the field” and that courts are not political entities. As a result, agencies with expertise are better suited to carry out those policies. Moreover, even if agencies are not accountable to the public, they are part of the executive branch headed by the President, who (unlike judges with life tenure) is directly accountable to the electorate.[6]

Nevertheless, during the recent oral arguments, the Chief Justice stated that the Court had not in recent years employed Chevron itself in its analysis of agency action. The reason why the issue of whether Chevron unduly intrudes upon the judicial function, and whether it should be overruled or modified, relates to the fact that it is widely used in lower court review of administrative actions. Its reconsideration also relates to increasing jurisprudential conservatism on the Supreme Court and the application of originalism and, more widely, textualism.

The Chevron concept of deference to agency regulations exists alongside a line of cases in which courts have deferred to an agency’s interpretations of its own regulations. In both Bowles v. Seminole Rock & Sand Co.[7] and Auer v. Robbins,[8] the Supreme Court developed the principle that courts are not supposed to substitute their preference for how a regulation should be interpreted; instead, a court should give “controlling weight” to that interpretation unless it is “plainly erroneous or inconsistent with the regulation.”[9] Nevertheless, the Court has refused to extend that form of deference to subregulatory guidelines and manuals where there is little or no evidence of a formal process intended to implement Congress’s expressed intent.[10]

The Chevron framework has generated criticism, including statements by several current Justices. Their position relies on an argument that Chevron distorts the balance of authority in favor of the executive and strips courts of their proper role. In a recent dissent from a denial of certiorari, Justice Gorsuch complained that Chevron creates a bias in favor of the federal government and that instead of having a neutral judge determine rights and responsibilities, “we outsource our interpretive responsibilities. Rather than say what the law is, we tell those who come before us to go ask a bureaucrat.”[11] Justice Thomas has written that the Administrative Procedure Act does not require deference to agency determinations and raises constitutional concerns because it undercuts the “obligation to provide a judicial check on the other branches, and it subjects regulated parties to precisely the abuses that the Framers sought to prevent.”[12]

Chevron and the Herring Fishermen

The dispute that has brought Chevron deference to the Supreme Court in 2024 starts with the business of commercial fishing for herring. The National Marine Fisheries Service (NMFS) published a regulation in 2020 that requires operators of certain fishing vessels to pay the cost of observers who work on board those vessels to ensure compliance with that agency’s rules under the Magnuson-Stevens Fishery Conservation and Management Act of 1976 (“Act”). Several commercial fishing operators challenged the regulations, which led to two decisions by the U.S. Courts of Appeals for the District of Columbia Circuit and the First Circuit. Both courts upheld the regulations, but on slightly different grounds. In the first decision, Loper Bright Enterprises, Inc. v. Raimondo,[13] the District of Columbia Circuit followed the traditional Chevron analysis and concluded that the Act did not expressly address who would bear the cost of the monitors. The NMFS’s interpretation of the statute in the regulation was found to be reasonable under Step Two of Chevron based on the finding that the agency was acting within the scope of a broad delegation of authority to the agency to further the Act’s conservation and management goals, and on the established precedent concluding that the cost of compliance with a regulation is typically borne by the regulated party.

The second decision by the First Circuit, Relentless, Inc. v. United States Department of Commerce,[14] took a slightly different approach. That court focused on the text of the Act and concluded that the agency’s interpretation was permissible. It did not anchor its decision in a Chevron analysis and stated that “[w]e need not decide whether we classify this conclusion as a product of Chevron step one or step two.”[15] The First Circuit also emphasized that the operators’ arguments did not overcome the presumption that regulated entities must bear the cost of compliance with a relevant statute or regulation.

The parties have staked out starkly different views of Chevron’s legitimacy and whether it is compatible with the separation of powers in the U.S. Constitution. The fishermen petitioners argue that Chevron is not entitled to respect as precedent because the two-part test was only an interpretive methodology and not the holding construing the Clean Air Act. Their core argument is that Chevron improperly and unconstitutionally shifts power to the executive branch by giving more weight to the agencies in rulemaking and in resolving disputes where the agency is a party and shifts power away from the judiciary’s role under Article III to interpret laws and Congress’s legislative authority power under Article I. Taking this one step further, the petitioners argue that this shift violates the due process rights of regulated parties. They also argue that Chevron is unworkable in practice, citing instances where the Supreme Court itself has declined to apply the two-part test and the lack of a consensus as to when a statute is clear or ambiguous, making the application of Chevron inconsistent. Put another way, according to the petitioners, the problem with Chevron is that there is no clear rule spelling out how much ambiguity is needed to trigger deference to an agency’s rule. Next, they argue that Chevron cannot be applied when an underlying statute is silent because this allows agencies to legislate when there is a doubt as to whether Congress delegated that power to the agency at all and that it would run counter to accepted principles of construction that silence can be construed to be a grant of power to an agency. Finally, they contend that Chevron deference to agencies conflicts with Section 706 of the Administrative Procedure Act, where Congress authorized courts to “decide all relevant questions of law, interpret constitutional and statutory provisions, and determine the meaning or applicability of the terms of an agency action.”[16]

The Secretary of Commerce argues that there are multiple reasons to preserve Chevron deference. First, the Secretary argues that Chevron fits within the balance of power between the branches of the federal government. In the Secretary’s view, Chevron deference is consistent with the separation of powers doctrine, as it respects (1) Congress’s authority to legislate and to delegate authority to an administrative agency, (2) the agency’s application of its expertise in areas that may be complex, and (3) the judiciary’s authority to resolve disputed questions of law. Therefore, the Chevron framework avoids situations where courts may function like super-legislatures in deciding how a statute should be implemented or administered and second-guess policy decisions.

According to the Secretary, courts know how to apply the traditional tools of statutory interpretation, and if an ambiguity exists after that exercise is complete, it is appropriate to defer to an administrative agency that has technical or scientific experience with the subject matter being regulated. In addition, the Secretary contends that Chevron promotes consistency in the administration of statutes and avoids a patchwork of court rulings that may make it difficult or impossible to administer a nationwide program, such as Social Security or Medicare. Third, the Secretary notes that Chevron is a doctrine that has been workable for 40 years and that over those decades, Congress has not altered or overridden its holding, even as it has enacted thousands of statutes since 1984 that either require rulemaking or have gaps that have been filled by rulemaking. As a result, the Secretary argues that there are settled interpretations that agencies and regulated parties rely on, and overruling Chevron would lead to instability and relitigating settled cases. Finally, the Secretary argues that Chevron deference cannot be limited to interpretations of ambiguous language alone, as there are no accepted criteria for distinguishing ambiguous statutory language from statutory silence.

The Oral Argument

The Supreme Court heard arguments in both cases on January 17, 2024. Over more than three hours of argument, the Justices focused on several questions. Justices Kagan, Sotomayor, and Jackson expressed concerns that abandoning the Chevron framework would put courts in the position of making policy rather than just ruling on questions of law. In their view, courts lack the skills and expertise to craft policy and should not act as super-legislators. They also stressed that there are situations in which the tools of statutory construction do not yield a single answer or that Congress has not addressed the question either because it left some matters unresolved in the statute or through other subsequent changes not contemplated by Congress, such as the adoption of new technologies. In these cases, the Justices wanted to know why deference to an agency was not appropriate and did not see any clear indication that Congress intended that courts, not agencies, should make determinations when the statutory language is ambiguous or silent. They also questioned why the Supreme Court should overrule Chevron when Congress has been fully aware of the decision for 40 years and has not enacted legislation to eliminate the ability of a court to defer to an agency’s determinations.

The members of the more conservative wing of the Supreme Court questioned counsel about weaknesses in the Chevron framework. Justice Gorsuch returned to his earlier criticism of Chevron and asked the parties to define what constitutes enough ambiguity to allow a court to move from Step One to Step Two. He further questioned whether there was sufficient evidence that Congress ever intended to give the government the benefit of the doubt when an individual or regulated entity challenges agency action. Justice Gorsuch, along with Justices Thomas and Kavanaugh, asked whether Chevron actually resulted in greater instability and whether it was appropriate to abandon Chevron in favor of the lesser form of deference articulated in Skidmore v. Swift & Co., where deference is not a default outcome and a court is supposed to exercise its independent judgment to give weight to agency determinations based on factors including the thoroughness of the agency’s analysis, the consistency and validity of the agency’s position, and the agency’s “consistency with earlier and later pronouncements, and all those factors which give it power to persuade.”[17] The follow-up questions asked whether it was correct to accord deference to agency regulations when the agency’s policy can shift from administration to administration.

Where Is the Conservative Court Likely to Go?

The length of the argument and the alacrity of questioning do not mean that the Supreme Court is going to overrule the 40-year-old, highly influential Chevron doctrine. It is, however, quite likely that the doctrine will be narrowed and clarified. To say nothing of the recent oral argument, several recent decisions evidence a reluctance to abandon deference altogether. In a pair of decisions issued in 2022 involving Medicare reimbursement to hospitals, the Court resolved deference questions by relying on the statutory text alone.

Those decisions involved challenges to a Medicare regulation governing hospital reimbursement, and a published interpretation of a section of the Medicare statute governing reimbursement for outpatient drugs. Although the Court ruled in the government’s favor in the former case and against the government in the latter case, neither decision relies on Chevron—even though in one case, the petitioner’s counsel expressly asked the Court to overrule Chevron during the oral argument.[18] Yet, by relying on the text of each statute to resolve a regulatory dispute, the Court’s reasoning in both decisions is consistent with Step One of the Chevron test and demonstrates that it is workable in practice and need not result in a dilution of judicial review. In addition, the Court has developed another limit to agency action in its decisions, finding that when a regulatory issue presents a “major question,” deference is irrelevant unless the agency can show that Congress expressed a clear intent that the agency exercise its regulatory authority. This concept remains a work in progress because the Court has not defined criteria that make an issue a major question.[19]

These cases provide a useful background to an increasingly jurisprudentially conservative, textually oriented Court. Two cases that were specifically discussed during oral argument are particularly significant in plotting the Court’s landing place with regard to Chevron. Justice Gorsuch made multiple references to Skidmore, which sets forth the principle that a federal agency’s determination is entitled to judicial respect if the determination is authorized by statute and made based on the agency’s experience and informed judgment. Unlike the Chevron standard, the Skidmore standard considers an agency’s consistency in interpreting a law it administers.

The second, and more recent, precedent that is even more likely to guide the narrowing of Chevron is Kisor v. Wilkie.[20] There, a 5-4 divided Court adopted a multi-stage regime for reviewing an agency’s reliance upon arguably ambiguous regulations that is roughly analogous to Chevron’s two-stage analytical modality. In doing so, it modified, but did not overrule, Auer v. Robbins, 519 U.S. 452 (1997), and its doctrinal predecessor, Bowles v. Seminole Rock & Sand Co., 325 U.S. 410 (1945), which permit a court to defer to an agency’s interpretation of its own ambiguous regulation, so long as that interpretation is reasonable, even if the court believes another reasonable reading of the regulation is the better reading.

Kisor saw a mixed bag of Justices joining, or dissenting from, various parts of the Kagan opinion. What made the majority as to its operative section was the Chief Justice’s joining Justice Ginsburg, Breyer, and Sotomayor. With Justice Ginsburg having been succeeded by Justice Barrett, and Justice Breyer having been succeeded by Justice Jackson, one might hypothesize that there now would be a conservative 5-4 majority that would have overruled Auer. However, it was Justice Barrett who raised the possibility of “Kisorizing” Chevron, a suggestion quickly adopted by Justice Kagan. Justice Gorsuch, a longtime opponent of Chevron, is likely amenable to a Skidmore-oriented result.

The Kagan opinion cabins and arguably lowers the level of deference an agency’s interpretation of a rule should receive. Thus, with a strong nod to the Court’s jurisprudential drift to the right, Justice Kagan begins with the truism that whatever discretion an agency might claim, the Court’s analysis must proceed under the proposition that an unambiguous rule must be applied precisely as its text is written. It is not unlikely that, if the Court narrows Chevron (as we predict it shall), it also will begin with a more robust requirement to apply the statutory text in Step One and re-emphasize the need to exhaust all of the tools of statutory construction; in other words, there is no need for deference unless there is genuine ambiguity. If an agency’s determination is to become relevant, it only becomes so after ambiguity is established.[21]

In short, if the law gives a definitive answer on its face, there is nothing to which a court should defer, even if the agency argues that there is an interpretation that produces a better, more reasonable result. This is a textual determination that addresses the criticism of the so-called Administrative State’s acting as a quasi-legislature to which the Court yields its own power to say what the law is.

However, even a reasonable agency interpretation, the Kagan opinion notes, might not be dispositive. The opinion must be the agency’s official position, not one ginned up for litigation purposes, and it must reflect the agency’s particular expertise.

­Conclusion

In its 40-year life, Chevron deference has been at the heart of the application of federal administrative law. No case among all of the many governmental functions that the Supreme Court considers has been more widely cited, and no administrative law case has been more controversial, especially among jurisprudential conservatives. While asked by various parties to do so, the Court has declined, and the Chevron structure has been applied, often inconsistently, by federal courts. Perhaps reflecting the increasingly conservative direction of the Court, we have reached a point where the Court will consider retiring this long-standing precedent or, alternatively, refreshing it based on the experience of courts and agencies since 1984.

Justice Kagan’s analytic method in Kisor v. Wilkie could also apply to tightening Chevron. In her decisions, she has exhibited great fidelity to reading text literally, avoiding the perils of legislation from the bench. As she wrote in Kisor:

[B]efore concluding that a rule is genuinely ambiguous, a court must exhaust all the traditional tools of construction. . . . For again, only when that legal toolkit is empty and the interpretive question still has no single right answer can a judge conclude that it is more one of policy than of law. That means a court cannot wave the ambiguity flag just because it found the regulation impenetrable on first read. Agency regulations can sometimes make the eyes glaze over. But hard interpretive conundrums, even relating to complex rules, can often be solved. A regulation is not ambiguous merely because discerning the only possible interpretation requires a taxing inquiry. To make that effort, a court must carefully consider the text, structure, history, and purpose of a regulation, in all the ways it would if it had no agency to fall back on. . . . Doing so will resolve many seeming ambiguities out of the box, without resort to . . . deference” (citations and internal punctuation omitted).[22]

Text alone might not provide the answer in every case, as Justice Kagan recognizes as she outlines four additional steps that might lead to judicial deference to agency statutory interpretations. However, to the extent that a majority of the Court elects to retain Chevron, though narrowing it, her approach in the analogous setting reflected in Kisor would be effective in resolving the two cases now at bar—recognizing agency expertise in technical and scientific matters beyond the competency of the judiciary while preserving the function of the courts to determine what the legislature actually wrote, not to write it themselves.

* * * *

ENDNOTES

[1] Besides the administrative bureaucracy, various jurists and commentators have, under this rubric, included the press, the people acting through grand juries, and interest or pressure groups. Those institutions represent the arguable influence of extra-governmental sources. We are focused here on the level of judicial deference afforded to federal administrative agencies.

[2] 467 U.S. at 842-43.

[3] 5 U.S.C. § 706(2)(A).

[4] Id. at 844.

[5] Id. at 843, fn.9.

[6] Id. at 865-66.

[7] 325 U.S. 410, 414 (1945).

[8] 519 U.S. 452, 461 (1997).

[9] Id.

[10] United States v. Mead Corp., 533 U.S. 218, 229 (2001); Christensen v. Harris County, 529 U.S. 576 (2000).

[11] Buffington v. McDonough, No. 21-972 (Gorsuch, J., dissenting at 9) (2022).

[12] Perez v. Mortgage Bankers Ass’n, 135 S.Ct. 1199,1213 (2015) (Thomas, J., concurring in the judgment).

[13] 45 F.4th 359 (D.C. Cir. 2022).

[14] 62 F.4th 621 (1st Cir. 2023).

[15] Id. at 634.

[16] 5 U.S.C. § 706.

[17] 323 U.S. 134, 140 (1944).

[18] Becerra v. Empire Health Foundation, 142 S.Ct. 2354 (2022), and American Hospital Ass’n v. Becerra, 142 S.Ct. 1896 (2022). The request to overrule Chevron appears in the transcript of the American Hospital Ass’n oral argument, at 30.

[19] West Virginia v. EPA, 142 S.Ct. 2587 (2022); Utility Air Regulatory Group v. EPA, 573 U.S. 302, 324 (2014).

[20] 139 S. Ct. 2400 (2019).

[21] Kisor predicated deference, if at all, upon five preliminary stages. First, as noted, the reviewing court should determine that a genuine ambiguity exists after applying all of the tools of statutory construction. This is consistent with Step One of Chevron, but Justice Kagan makes it clear that this is a heightened textual barrier. Second, the agency’s construction of the regulation must be “reasonable”; this is a restatement of Step Two of Chevron. The Court cautioned that an agency can fail at this step. Third, the agency’s construction must be “the agency’s ‘authoritative’ or ‘official position,’” which was explained as an interpretation that is authorized by the agency’s head or those in a position to formulate authoritative policy. Fourth, the regulatory interpretation must implicate the agency’s “substantive expertise.” Finally, the regulatory interpretation must reflect the agency’s “fair and considered judgment” and that a court should decline to defer to a merely “convenient litigating position” or “post hoc rationalizatio[n] advanced” to “defend past agency action against attack.”

[22] 139 S.Ct. at 2415.

SEC Enforcement Targets Anti-Whistleblower Practices in Financial Firm’s Settlement Agreements with Retail Clients by Imposing Highest Penalty in Standalone Enforcement Action Under Exchange Act Rule 21 F-17(a)

As the year gets underway, the Securities and Exchange Commission (SEC or Commission) is continuing its ongoing enforcement efforts to target anti-whistleblower practices by pursuing a broader range of entities and substantive agreements, including the terms of agreements between financial institutions and their retail clients. The most recent settlement with a financial firm signifies that the SEC is imposing increasingly steep penalties to settle these matters while focusing on confidentiality provisions that do not affirmatively permit voluntary disclosures to regulators. We discuss below the latest SEC enforcement actions in the name of whistleblower protection and offer some practical tips for what firms and companies may do to proactively mitigate exposure.

On 16 January 2024, the SEC announced a record $18 million civil penalty against a dual registered investment adviser and broker-dealer (the Firm), asserting that the use of release agreements with retail clients impeded the clients from reporting securities law violations to the SEC in violation of Rule 21F-17(a) of the Securities Exchange Act of 1934 (Exchange Act).1

The SEC found that from March 2020 through July 2023, the Firm regularly required its retail clients to sign confidential release agreements in order to receive a credit or settlement of more than $1,000. Under the terms of these releases, clients were required to keep confidential the existence of the credits or settlements, all related underlying facts, and all information relating to the accounts at issue, or risk legal action for breach of the agreement. The agreements “neither prohibited nor restricted” the clients from responding to any inquiries from the SEC, the Financial Industry Regulatory Authority (FINRA), other regulators or “as required by law.” However, the agreements did not expressly allow the clients to initiate voluntary reporting of potential securities law violations to the regulators. The SEC found that this violated Rule 21F-17(a) “which is intended to ‘encourag[e] individuals to report to the Commission.’”While the Firm did report a number of the underlying client disputes to FINRA, the SEC found this insufficient to mitigate the lack of language in the release agreements that expressly permitted the clients to report potential securities law violations to the SEC.

The SEC initiated a settled administrative proceeding against the Firm, which neither admitted nor denied the SEC’s findings. In addition to the $18 million civil monetary penalty, the settlement requires that the Firm cease and desist from further violations of Rule 21F-17(a). Notably, the SEC credited certain remedial measures promptly undertaken by the Firm, including revising the at-issue release language and affirmatively alerting affected clients that they are not prohibited from communicating with governmental and regulatory authorities.

This enforcement action is significant for several reasons. First, it signals a broader enforcement focus by the SEC with respect to Rule 21F-17(a) in that this is the first action involving the terms of agreements between a financial institution and its retail clients, which are prevalent throughout the financial services industry. Previously, enforcement had focused squarely on restrictive confidentiality provisions involving employees, such as those found in employment or severance agreements or in connection with internal investigation interviews.

Second, the unprecedented magnitude of the penalty in a standalone Rule 21F-17(a) case underscores the SEC’s emphasis on preventing practices that it views as obstructions of whistleblower rights. SEC Enforcement Director Gurbir Grewal’s statement announcing the settlement reflects this position, “Whether it’s in your employment contracts, settlement agreements or elsewhere, you simply cannot include provisions that prevent individuals from contacting the SEC with evidence of wrongdoing.” Companies (public and private), broker-dealers, investment advisers, and other market participants should expect to see continued enforcement investigations in connection with the SEC’s ongoing attention toward compliance with Rule 21F-17(a), as discussed further below.

The SEC’s Whistleblower Protection Program

Established in 2011 pursuant to the Dodd-Frank Wall Street Reform and Consumer Protection Act of 2010, the SEC Whistleblower Program provides monetary awards to individuals who “tip” the SEC with original information that leads to an enforcement action resulting in monetary sanctions that exceed $1 million. Through the end of the SEC’s FY2023, the SEC has awarded almost $2 billion to 385 whistleblowers.In FY2023 alone, the SEC received over 18,000 whistleblower tips and awarded more than $600 million in whistleblower awards to 68 individuals.4

In furtherance of the Whistleblower Program, the SEC also issued Exchange Act Rule 21F-17(a), which provides that “no person may take any action to impede an individual from communicating directly with the Commission staff about a possible securities law violation, including enforcing, or threatening to enforce, a confidentiality agreement . . . with respect to such communications.”5

SEC Struck Several Blows in 2023 Against Companies that Failed to Carve out Whistleblower Protections in Their Confidentiality Agreements

The SEC has been aggressively enforcing Rule 21F-17(a) since its first enforcement action in 2015 with respect to that Rule,through several waves of enforcement actions. During 2023, the SEC was especially active with a number of settled enforcement actions asserting violations of Rule 21F-17(a) in which the respondents neither admitted nor denied the SEC’s findings:

  • In February 2023, the SEC fined a video game development and publishing company $35 million for violating federal securities laws through its inadequate disclosure controls and procedures. The settled action also included a finding that the company had violated Rule 21F-17(a) by executing separation agreements in the ordinary course of its business that required former employees to provide notice to the company if they received a request for information from the SEC’s staff.7
  • In May 2023, the SEC imposed a $2 million fine on an internet streaming company for: (i) retaliating against an employee who reported misconduct to the company’s management prior to and after filing a complaint with the SEC; and, (ii) impeding the reporting of potential securities law violations, by including provisions in employee severance agreements requiring that departing employees waive any potential right to receive a whistleblower award, in violation Rule 21F-17(a).8
  • In September 2023, in another standalone enforcement action for violations of Rule 21F-17(a), the SEC imposed a $10 million civil monetary penalty on a registered investment adviser (RIA) for requiring that its new employees sign employment agreements that prohibited the disclosure of “Confidential Information” to anyone outside of the company, without an exception for voluntary communications with the SEC concerning possible securities laws violations.Further, the RIA required many departing employees to sign a release in exchange for the receipt of certain deferred compensation and other benefits affirming that, among other things, the employee had not filed any complaints with any governmental agency. Although the RIA later revised its policies and issued clarifications to employees that they were not prevented from communicating with the SEC and other regulators, the RIA failed to amend its employment and release agreements to provide the carve out.
  • Also in September 2023, the SEC charged two additional firms with violations of Rule 21F-17(a). In one case imposing a $375,000 civil penalty, the SEC found that a commercial real estate services and investment firm impeded whistleblowers by requiring its employees, as a condition of receiving separation pay, to represent that they had not filed a complaint against the firm with any federal agency.10 In another case, the SEC imposed a $225,000 civil penalty against a privately-held energy and technology company for requiring certain departing employees to waive their rights to monetary whistleblower awards.11 This particular action underscores that Rule 21F-17 applies to all entities, and not only to public companies.

Mr. Grewal, in an October 2023 speech before the New York City Bar Association Compliance Institute, emphasized that potential impediments to the SEC’s Whistleblower Program would be a continued focus of the agency’s enforcement efforts, stating, “we take compliance with Rule 21F-17 very seriously, and so should each of you who work in a compliance function or advise companies. You need to look at these orders and the violative language cited by the Commission and think about how those actions may impact your firms. And if they do, then take the steps necessary to effect compliance.”12

Key Take-Aways

The SEC’s recent enforcement actions demonstrate that violations of Rule 21F-17(a) can carry significant fines and reach virtually any confidentiality agreement that does not carve out communications between a firm’s current or former employees or customers and the SEC or other regulators about potential securities violations. Moreover, although many of the enforcement actions relate to language in agreements, Rule 21F-17 is not so limited and can also apply to language in internal policies, procedures, guidance, manuals, or training materials. The message from the SEC is clear: it will continue to enforce Rule 21F-17 with respect to public companies, private companies, broker-dealers, investment advisers, and other financial services entities.

The SEC in its recent orders has provided credit to companies for cooperation as well as for instituting remedial actions.13 Being proactive in identifying and correcting potential violations in advance of any investigation by the SEC can result in mitigation of any action or penalties.

Legal and compliance officers may want to consider the following steps in order to evaluate and potentially mitigate any potential exposure to an enforcement action:

  • Conduct a review of all employee-facing and client-facing documents or contracts with confidentiality provisions and remove or revise any content that may be viewed as impeding (even unintentionally) a person’s ability to report potential securities law violations to the SEC. Depending on the circumstances, this may involve including a reference expressly permitting communications with the SEC and other government or regulatory entities without advance notice or disclosure to the company.
  • Remove any language from the templates that could be interpreted as hindering an employee’s or client’s ability to communicate with the SEC concerning potential securities law violations, including language threatening disciplinary action against employees for disclosing confidential information in their communications with government agencies when reporting potential violations.
  • Prepare addenda or updates to current employee- and client-facing agreements that reflect the revised confidentiality clauses.
  • Include reference in written anti-retaliation policies that employees’ communications and cooperation with the SEC and other government agencies will not result in retaliation from the company.
  • Conduct trainings for company managers and supervisors regarding appropriate communications to employees regarding their interactions with the government.
  • Implement policies that prevent any company personnel from taking steps to block or interfere with an employee’s use of company platforms or systems to communicate with the SEC and other government agencies.14

In the Matter of JP Morgan Securities LLC, Admin. Proc. No. 3-21829 (Jan. 16, 2024), https://www.sec.gov/files/litigation/admin/2024/34-99344.pdf.

Id. (quoting Securities Whistleblower Incentives and Protections Adopting Release, Release No. 34-63434 (June 13, 2011)).

SEC Office of the Whistleblower Annual Report to Congress for Fiscal Year 2023 (Nov. 14, 2023), https://www.sec.gov/files/2023_ow_ar.pdf; SEC Whistleblower Office Announces Results for FY 2022 (Nov. 15, 2022), https://www.sec.gov/files/2022_ow_ar.pdf; 2021 Annual Report to Congress Whistleblower Program (Nov. 15, 2021), https://www.sec.gov/files/owb-2021-annual-report.pdf; 2020 Annual Report to Congress Whistleblower Program (Nov. 16, 2020), https://www.sec.gov/files/2020_owb_annual_report.pdf.

SEC Office of the Whistleblower Annual Report to Congress for Fiscal Year 2023 (Nov. 14, 2023), https://www.sec.gov/files/2023_ow_ar.pdf.

17 C.F.R. § 240.21F-17.

In the Matter of KBR, Inc., Admin. Proc. No. 3-16466 (Apr. 1 2015), https://www.sec.gov/files/litigation/admin/2015/34-74619.pdf (imposing a US$130,000 fine on a company in a settled enforcement action for requiring that witnesses in certain internal investigations sign confidentiality agreements warning that they could be subject to discipline if they discussed the matters at issue outside the company without prior approval of the company’s legal department).

In the Matter of Activision Blizzard, Inc. Admin. Proc. No. 3-21294 (Feb. 3, 2023), https://www.sec.gov/files/litigation/admin/2023/34-96796.pdf.

In the Matter of Gaia, Inc. et. al., Admin. Proc. No. 3-21438 (May 23, 2023), https://www.sec.gov/files/litigation/admin/2023/33-11196.pdf.

In the Matter of D.E. Shaw & Co., L.P., Admin. Proc. No. 3-21775 (Sep. 29, 2023), https://www.sec.gov/files/litigation/admin/2023/34-98641.pdf.

10 In the Matter of CBRE Inc., Admin. Proc. No. 3-21675  (Sept. 19, 2023), https://www.sec.gov/files/litigation/admin/2023/34-98429.pdf.

11 In the Matter of Monolith Res., LLC, Admin. Proc. No. 3-21629 (Sept. 8, 2023), https://www.sec.gov/files/litigation/admin/2023/34-98322.pdf.

12 Gurbir S. Grewal, Remarks at New York City Bar Association Compliance Institute (Oct. 24, 2023), https://www.sec.gov/news/speech/grewal-remarks-nyc-bar-association-compliance-institute-102423.

13 See, e.g., In the Matter of CBRE Inc., Admin. Proc. No. 3-21675  (Sept. 19, 2023), https://www.sec.gov/files/litigation/admin/2023/34-98429.pdf (crediting respondent’s remediation program, which included, among other measures, an audit of relevant agreements, updates to policies with respect to Rule 21F-17, and mandatory trainings); In the Matter of Monolith Res., LLC, Admin. Proc. No. 3-21629 (Sept. 8, 2023), https://www.sec.gov/files/litigation/admin/2023/34-98322.pdf (crediting respondent’s prompt remedial acts including revisions to the at-issue release language and affirmatively alerting affected clients that they are not prohibited from communicating with governmental and regulatory authorities.)

14 Cf.  In the Matter of David Hansen, Admin Proc. 3-20820 (Apr. 12, 2022), https://www.sec.gov/enforce/34-94703-s (settled SEC enforcement action against former Chief Information Officer of a technology company for violating Rule 21F-17(a) by, among other things, removing an employee’s access to the company’s computer systems after the employee raised concerns regarding misrepresentations contained in the company’s public disclosures).

Premarital Agreements and the “Voluntary” Signature

Premarital agreements offer persons contemplating marriage the ability to plan for the distribution of their assets and liabilities in the event of separation and/or divorce.

While the concept of planning for divorce may seem counterintuitive for persons pledging promises of life-long fidelity and companionship, premarital agreements offer solutions for a variety of scenarios, including estate planning protection and the protection of interests in closely held businesses in the event of separation and/or divorce.

In many cases, the signed agreement will become a distant memory as the routines of married life evolve. Yet years later, the agreement will be retrieved from the file cabinet by the party seeking its protection when one or both spouses conclude that the marital contract should be dissolved. The agreement may then be challenged by the spouse, who concludes that enforcement of the bargain made decades earlier will produce egregiously “unfair” results.

As will be shown below, the burden to be met when challenging a premarital agreement is steep. It is, therefore, imperative that persons being asked to enter into such an agreement fully and completely understand its legal consequences before signing on “the dotted line.”

Legal Framework for Premarital Agreements in North Carolina

In North Carolina, premarital agreements are governed by the Uniform Premarital Agreement Act. See N.C. Gen. Stat. §§ 52B-1 through -11.

To avoid enforcement of a premarital agreement, the party challenging the agreement must prove either that (1) she did not execute the agreement “voluntarily” or (2) that the agreement was unconscionable when it was executed and before its execution she (a) was not provided, (b) did not waive the disclosure of, and (c) did not have, or reasonably could not have had, adequate knowledge of the property or financial obligations of the other party. N.C. Gen. Stat. § 52B-7(a).

In this article, we will review two North Carolina cases that shed light on what is meant by the term “voluntary” when it comes to the execution of a premarital agreement.

CASE STUDY 1: HOWELL V. LANDRY

In Howell v. Landry, Mary Landry challenged the enforcement of the couple’s premarital agreement. She challenged the agreement on the grounds that her execution of the agreement was not “voluntary.” She complained:

  • that her husband first presented her with a draft of a premarital agreement which had been prepared by his attorney without the wife’s knowledge at 8:00 pm on the day before they were to travel to Las Vegas, Nevada for their wedding;
  • that her husband told her that if the agreement was not signed, they would not get married;
  • that she had never seen a premarital agreement before, and she advised her husband that she wanted her own attorney to review the document;
  • that she advised her husband that she did not want to sign the agreement.

Ms. Landry argued that these facts support a conclusion that the agreement was the product of duress and was, therefore, unenforceable. The case came before Judge Russell Sherill in Wake County. Judge Sherill agreed with Ms. Landry and ruled in her favor, concluding that the Agreement was the product of duress and therefore invalid.

Mr. Howell appealed Judge Sherrill’s ruling to the North Carolina Court of Appeals. The Court of Appeals rejected wife’s argument that the agreement was the product of duress. The Court’s ruling is instructive. The Court observed that:

[d]uress is the result of coercion. It may exist even though the victim is fully aware of all facts material to his or her decision.

* * *

Duress exists where one, by the unlawful or wrongful act of another, is induced to make a contract or perform or forego some act under circumstances which deprive him of the exercise of freewill. An act is wrongful if made with the corrupt intent to coerce a transaction grossly unfair to the victim and not related to the subject of such proceedings.

* * *

The mere shortness of the time interval between the presentation of the premarital agreement and the date of the wedding is insufficient alone to permit a finding of duress or undue influence . . . . The shortness of the time interval when combined with the threat to call off the marriage if the agreement is not executed is likewise insufficient per se to invalidate the agreement.

* * *

Here, the threat to cancel the marriage and the execution of the premarital agreement were closely related to each other. The marriage would have redefined the respective property rights of the parties, and the premarital agreement would have avoided that re-definition to some extent. Indeed, the cancelation of a proposed marriage would be the natural result of failure of a party to execute a premarital agreement desired by the other party.

In summary, Ms. Landry’s decision to sign the agreement was deemed to have been a voluntary decision despite the fact that it was presented to her the night before the couple was to leave for their wedding and despite her request to have an attorney review it for her.

CASE STUDY 2: KORNEGAY V. ROBINSON

Our second real-life example contains facts that appear even more favorable to the complaining spouse than those presented in the Howell v. Landry matter. In Kornegay v. Robinson, the wife signed a premarital agreement that included a waiver of her spousal share of her husband’s estate.

When her husband passed away without providing for her in his will, she challenged the premarital agreement in an attempt to receive a share of the estate. Ms. Kornegay claimed that the premarital agreement had not been voluntarily executed because:

  • She had only a high school education;
  • She learned that her husband wanted her to execute a premarital agreement only after she had moved in with him and obtained a license to marry him;
  • She was presented with the agreement in her husband’s attorney’s office on the same day that she and her husband were to be married; and
  • She did not have the opportunity to review the agreement with independent counsel before signing it.

The trial judge who heard the case ruled against Ms. Kornegay. She appealed the matter to the North Carolina Court of Appeals. A majority of the panel who heard the case were persuaded that the trial court’s ruling was improper. However, one member of the panel filed a dissenting opinion and concluded that Ms. Kornegay’s claim to set aside the Agreement was properly denied. The husband’s estate appealed the matter to the North Carolina Supreme Court.

In a unanimous opinion, the Supreme Court adopted the dissenting opinion, which rejected Ms. Kornegay’s argument. The dissenting opinion adopted by the Court is informative.

Plaintiff (Ms. Kornegay) now contends she did not voluntarily sign the premarital agreement due to the totality of the circumstances existing at the time of execution of the Agreement. Plaintiff argues her lack of legal counsel and lack of an opportunity to obtain legal counsel are important elements in the circumstances surrounding her execution of the Agreement. Plaintiff acknowledged in her deposition she never requested “(1) additional time to read the Agreement; or (2) another attorney to be present to explain the Agreement before she signed it.” This case fits squarely within the facts and holding of Howell ….

This Court has held contract rules apply to premarital agreements.

Absent fraud or oppression . . . parties to a contract have an affirmative duty to read and understand a written contract before signing it.

Plaintiff’s argument that her execution was not voluntary because she did not read the agreement was without merit. Plaintiff had an affirmative duty to read and understand the premarital agreement before signing it. Plaintiff provided no evidence she was prevented from reading the agreement or that she sought separate counsel prior to signing the agreement. Plaintiff admitted both in the agreement and at her deposition that she voluntarily signed the agreement.

* * *

Plaintiff asserts no inequality in education or business experience between her and her husband. Plaintiff did not assert she made any disclosures to Defendant of her pre‑martial assets to any greater extent than her knowledge of Defendant’s assets on the date of the agreement.

* * *

Plaintiff’s chief complaint of unfair appears to be based upon the current value of her husband’s assets, from which she has received and enjoyed the income over the fifteen years of their marriage, and not her knowledge of the nature and extent of the decedent’s assets on the date of the agreement. The value of decedent’s assets on the date the contract was signed controls. Plaintiff’s bootstrapped claim that her execution of the agreement was not voluntary does not create any genuine issue of material fact to overcome the plain language in the agreement or her sworn admissions during her deposition. The trial court’s judgment should be affirmed in its entirety.

* * *

The fact that the decedent’s assets grew during the marriage does not make the agreement unconscionable or unfair.

The North Carolina Supreme Court rejected Ms. Kornegay’s claim the agreement should be set aside. Once again, not even the presentation of the agreement in the husband’s attorney’s office on the day of the wedding was sufficient fact from which to find that the Agreement had not been signed “voluntarily.”

Lessons Learned

The Howell v. Landry and the Kornegay v. Robinson decisions reveal the steep climb required to meet one’s burden of setting aside a premarital agreement on the grounds that it was not executed “voluntarily.”

Persons asked to sign a premarital agreement on the eve of the wedding should be aware that the “last minute” presentation will more than likely not be sufficient cause to set aside the agreement. When it comes to premarital agreements, the following advice is in order:

  1. Timely ask your prospective spouse whether he or she is considering the use of a premarital agreement;
  2. Advise your prospective spouse that you will need time to have an attorney of your choice review the agreement before you will be able to sign it;
  3. While inconvenient and potentially embarrassing, consider postponing the wedding ceremony if an agreement is presented at the last moment.