.

Dorsey’s clients take compliance seriously, and Ryan helps them achieve that objective. If litigation is necessary despite our clients’ best efforts, Ryan is honored to defend them.

For more than two decades, Ryan has counseled corporate clients and HR professionals on non-competition, non-solicitation and other restrictive covenants; employee and independent contractor classification issues; hiring, discipline and termination matters; wage & hour issues; executive employment agreements; compensation plans; reductions in force; employee investigations; and human resources policies and practices.

Known for combining practical wisdom and an emphasis on efficiency with a vigorous approach to litigation, Ryan also has a successful track record of defending employers in complex and single plaintiff cases in federal and state courts, and arbitration. His litigation practice involves defense of high-stakes individual discrimination and retaliation claims; claims involving non-competition, non-solicitation, and confidentiality agreements; federal and state wage and hour actions; and cases involving claims for breach of employment contracts and fiduciary duties. He has extensive experience representing clients in class and collective actions, as well as in appellate proceedings.

Ryan brings his expertise to bear for clients in many industries, including banks, food and agribusiness companies, technology companies, telecommunications companies, financial service firms, medical providers, manufacturers, distributors and retailers. Ryan also serves as a lobbyist for Minnesota employers through the Minnesota Employment Law Council.

Select Experience

  • Successfully defended Abbott in lawsuit by former sales executive alleging age and gender discrimination and retaliation. (Ramsey County, Minnesota, 2023)
  • Defended Radisson Hotels in lawsuit by former human resources executive alleging violation of the Minnesota Whistleblower Act and constructive discharge.(Hennepin County, Minnesota, 2022)
  • Represented international logistics company in U.S. Department of Labor investigation involving class-based regular rate, unpaid overtime and joint employer allegations. (U.S. Department of Labor, 2022)
  • Defended Ameriprise Financial Services in California PAGA lawsuit claiming franchisee Financial Advisors were misclassified as independent contractors under the California Labor Code.Plaintiff challenged the constitutionality of the “investment advisor” exemption to the “ABC test” under AB-5, raising multiple novel questions under California law, including whether Ameriprise had constitutional standing to defend the constitutional validity of Labor Code provisions, whether Plaintiff had authority to maintain a constitutional challenge to the Labor Code in his capacity as a PAGA plaintiff, and whether the legislature’s exemptions to the ABC test, and the retroactivity of those exemptions under AB-5, withstood rational basis scrutiny.Motion for summary adjudication granted, after which Plaintiff dismissed the case.Quinn v. Ameriprise Financial Services, Inc., (Alameda County Superior Court, 2021)

Education

  • University of Iowa College of Law (J.D., 2001)
    • With Highest Distinction; Order of the Coif; Executive Editor, Iowa Law Review, Vol. 86
  • Luther College (B.A., Major: Political Science; Minors: Economics, Communication, 1998)
    • summa cum laude, Phi Beta Kappa

Professional Affiliations

  • Member, Minnesota State Bar Association and MSBA Labor & Employment Law section
  • Member, Hennepin County Bar Association and the HCBA Labor & Employment section
  • Member, Iowa State Bar Association
  • Board of Directors, Feed My Starving Children

Court Admissions

  • U.S. Court of Appeals for the Eighth Circuit
  • U.S. District Court for the District of Minnesota
  • U.S. District Court for the Northern District of Illinois
  • U.S. District Court for the District of Colorado

Bar Admissions

  • Minnesota
  • Iowa

Clerkships

  • U.S. Court of Appeals for the Eighth Circuit, Honorable Donald P. Lay, 2001-2002

Accolades

  • Chambers USA, Labor & Employment, Minnesota, 2018-2026
  • Best Lawyers in America®, 2018-2026
  • Minnesota Super Lawyers®, 2020-2026
  • Minnesota Monthly, "Top Lawyers in Minnesota," 2024, 2026
  • Consistently providing pro bono legal assistance to those in need through Dorsey’s Pro Bono program
  • MSBA, North Star Lawyer, 2013, 2020-2025
  • Benchmark Litigation, "Labor & Employment Star – Minnesota", 2021-2022
  • Best Lawyers in America Employment Law Issue, 2021
  • Chambers USA, "Up and Coming," Labor & Employment, 2015-2017
  • Minnesota Super Lawyers, "Rising Star", 2011-2016

Select Presentations

  • “Compensable Work Time Under the FLSA and State Wage and Hour Laws,” Federal and Minnesota Wage and Hour Law, Minnesota CLE, August 15, 2023 
  • "2018 Wage and Hour Update: Trending Topics and Challenges," Labor and Employment Symposium, Dorsey & Whitney, May 7, 2018
  • "Annual Construction Symposium," Dorsey & Whitney, May 2018
  • #youtoo: Why the Construction Industry Needs to Focus on Sexual Harassment
  • "The First Year: Answering Client Questions About the Impact of the New Administration – Employment Law," Minnesota CLE, January 23, 2018
  • "The First 100 Days: Answering Client Questions about the Impact of the New Administration," Minnesota CLE, May 3, 2017
  • “Independent Contractors – Risks, Benefits & Best Practices,” Minnesota CLE, February 2017
  • “Labor & Employment Challenges for Farmer Cooperatives,” NCFC Annual Conference, February 2017  
  • "The Evolving World of Employee Leave: How States and Cities are Filling the Gaps Left by the FMLA," MinnCLE webinar, July 8, 2016
  • "Who Is the Employer?: Dealing With Misclassification and Co-Employment Risks In the Modern Workplace," Crossroads HR Conference, Salt Lake City, UT, September 22, 2015
  • "Hiring Processes and Employment Polices," Best Practices for Protecting Our Children Conference, Shattuck St. Mary’s School, Faribault, MN, September 15, 2015
  • “The Perils of Multistate Employment: Avoiding State Law Wage & Hour Traps In California and Beyond,” 2015 Upper Midwest Employment Law Institute, May 2015
  • “Independent Contractor or Employee? Warning Signs and Best Practices to Avoid Misclassification,” MinnCLE Representing the Ongoing Business CLE, January 2015
  • “Employment Law Series: How to Respond to the New Minnesota Women’s Economic Security Act,” MinnCLE webinar, October 2014
  • “FLSA Emerging Trends, Cases and Analysis,” panel participant, 2014 Upper Midwest Employment Law Institute, May 2014
  • “Independent Contractor or Employee? Warning Signs and Best Practices to Avoid Misclassification,” MinnCLE Closely Held Business CLE, October 2013
  • “Case Studies – The Jokester, the Gossip, the Bad Attitude: How To Move A Difficult Employee From Problematic To Productive,” panel moderator, MinnCLE, August 2013
  • “Employment Law Series: FLSA Claims – Settlement and Release Considerations,” MinnCLE webinar, October 2012
  • “Independent Contractor or Employee? Warning Signs and Best Practices to Avoid Misclassification,” MinnCLE Representing the Ongoing Business CLE, October 2012
  • “The Contingent Workforce and Alternate Staffing Models – In House Counsel Perspectives,” panel moderator, 2012 Upper Midwest Employment Law Institute, May 2012
  • “Are They Really Independent Contractors? Enforcement Trends and Best Practices to Avoid Misclassification,” 2012 Upper Midwest Employment Law Institute, May 2012
  • “To Pay Or Not To Pay: Identifying and Counting Compensable Work Time Under Wage & Hour Laws,” MinnCLE Wage & Hour program, March 2012

Insights

Client Alert

FTC Prohibits Noncompete Agreements; Business Groups Sue

April 25, 2024

The Federal Trade Commission (“FTC”) just approved a rule that would largely prohibit making or enforcing employee noncompete agreements. The U.S. Chamber of Commerce and others have already sued to block the new rule. What should businesses and employees know? Timing. The earliest possible effective date for the rule is four months from now—120 days after publication in the Federal Register. The date will be even later (if ever) if a court delays or blocks the rule’s implementation. If the rule goes into effect as written, however, it will prohibit making new agreements and enforcing most existing agreements (unless the agreement was breached before the effective date). Prohibition. The rule is broad. It prohibits every “term or condition of employment that prohibits a worker from, or penalizes a worker for, or functions to prevent a worker from… seeking or accepting work in the United States with a different person where such work would begin after the conclusion of the employment that includes the term or condition,” or “operating a business in the United States after the conclusion of the employment that includes the term or condition.”   Limited Exemption for Noncompetes with Senior Executives. The rule prohibits new noncompete agreements across the board, but permits enforcement of noncompete agreements with certain “senior executives” that exist as of the effective date. “Senior executive” means that the employee must earn at least $151,164 in annualized compensation (including salary, commissions, and nondiscretionary bonuses, but excluding payments for medical insurance, payments for life insurance, contributions to retirement plans. and the cost of other similar fringe benefits). The “senior executive” must also hold a “policy-making position,” such as president or CEO. An officer of a subsidiary, however, will probably not be considered a senior executive.  The meaning of “policy-making position” is not at all clear. Notice Requirement. The rule also requires employers to provide workers who are subject to covered noncompete clauses “with clear and conspicuous notice … that the worker’s non-compete clause is no longer in effect and will not be, and cannot legally be, enforced against the worker.”  Sale-of-Business Exception. The rule exempts noncompete clauses that are “entered into by a person pursuant to a bona fide sale of a business entity, of the person’s ownership interest in a business entity, or of all or substantially all of a business entity’s operating assets.” Whether the exception applies to executives that have rights to shares in a corporation as part of their equity awards will likely be a topic of future litigation.   State Laws. The FTC rule sets a floor but not a ceiling for state law. A state can continue to prohibit noncompetes altogether, or it can set a lower compensation level than the $151,164 at which the FTC rule would render existing noncompetes with “senior executives” unenforceable. Enforcement. The rule does not directly create any cause of action for employees. It is possible that the FTC will bring enforcement actions. It is also possible that state attorneys general will enforce their states “little FTC Acts” and use the FTC’s rule as an indicator of what constitutes “unfair methods of competition” under state law. Finally, an employee might argue that a state should update its own common law principles in light of the rule or (where state law permits it) bring a private action under the state’s statutory law. Legal Challenges. The U.S. Chamber of Commerce, joined by several other business groups, has filed a lawsuit in Texas federal court seeking to prevent implementation of the rule. Private employers have also started lawsuits. The Chamber claims that the FTC lacks statutory authority for this rulemaking, that not all noncompetes can be considered anticompetitive, that the rule is impermissibly retroactive (applying to agreements that were already negotiated), and that the rule is arbitrary and capricious.   Actions for Employers Use the Time. This rule has been in the works for more than a year, so many employers have already prepared for this day. But if your company has not developed a contingency plan, use the next several months wisely. As employers in states that have already banned noncompetes know, there are many ways to protect legitimate business interests, even if noncompetes are prohibited. Review Key Non-Disclosure, Non-Solicitation, and Confidentiality Provisions and Agreements. Employers should evaluate how to protect their highly sensitive information through means other than a noncompete, such as strengthening confidentiality and nondisclosure provisions. Employers should consider limiting the number of employees who have access to highly sensitive information—and ensure that those who do have access also have strong confidentiality agreements and receive training on their obligations to maintain confidentiality during and after employment. Employers should carefully review provisions prohibiting the solicitation of customers and clients to determine whether they come within the rule’s prohibition. Employers should also put measures in place to prohibit new hires from breaching confidentiality provisions entered into with previous employers.  Identify “Senior Executives.” Employers should do their best to identify which of their employees might qualify as “senior executives.” That includes ensuring they meet the compensation requirement, and developing the employer’s rationale for why those employees have “policy-making” authority.    Review Template Noncompete Agreements. Employers should also revisit template agreements for lower-level employees to identify provisions that might violate the rule and consider alternative provisions to protect the company’s legitimate business interests.   Be Mindful of State Laws. Even if a court prohibits implementation of the FTC’s rule, remember that relevant state laws will remain in effect. California, Minnesota, North Dakota, and Oklahoma have banned most noncompete agreements entirely. Several states prohibit noncompete agreements with employees whose compensation is below a statutory amount. These states include Colorado, Illinois, Maine, Maryland, Massachusetts, Nevada, New Hampshire, Oregon, Rhode Island, Virginia, Washington, and Washington D.C. Prepare for Notifications. Employers should develop plans for complying with the rule’s notice provisions—and make sure that they comply with any applicable notice requirements under state law. For example, California recently implemented a notice requirement with a deadline of February 14, 2024 for employers to provide the notice. Consider Alternative Retention Strategies. The rule prohibits the stick, but not the carrot. Employers should consider whether alternative retention strategies will now become more necessary if the rule goes into effect. For example, an employer might offer hiring bonuses in their compensation packages, payable after a satisfactory employment period (one year, for example) but advanced to the employee upon hire. Employees who leave before the period can then be on the hook to repay the bonus if they leave early, which protects a company’s investment in an employee by incentivizing a certain minimum tenure.   Think About the Opportunities. If the rule goes into effect, your noncompete agreements will become largely unenforceable—but so will those of your competitors. Consider whether the rule might create hiring opportunities. Comply with Antitrust Laws. The rule deals only with agreements between employers and their workers.  Making those agreements unenforceable might increase the incentive to work out informal agreements with competing employers not to hire each other’s workers. Don’t succumb to that temptation!  In 2016 the FTC and the U.S. Department of Justice (“DOJ”) announced their position that “no poaching” agreements between employers were not only per se illegal, but also criminal violations. It took DOJ several years to bring a criminal enforcement action, and it has yet to win a conviction from judge or jury, but that is cold comfort to anyone who has to endure a criminal prosecution. Moreover, civil private class-action litigation against no-poaching agreements continues apace.

Client Alert

A New World For Minnesota Employers: Minnesota Concludes Legislative Session and New Requirements for Employers Abound

June 1, 2023

The Minnesota Legislature recently concluded its 2023 session with the passage of a comprehensive paid family medical leave bill Mn Chapter 59  and an omnibus labor bill Mn Chapter 53  that will impose significant new obligations on Minnesota employers. Governor Walz promptly signed all bills. Dorsey’s prior e-update focused on Minnesota’s impending ban on new non-competition agreements between employers and employees. The legislature also passed a statewide sick and safe leave requirement, a paid family and medical leave program that includes new protected leave rights for Minnesota employees, and expanded protections for pregnant and nursing employees, among other new provisions targeting certain industries (such as meat packers and the construction industry). The legislature also passed a recreational marijuana bill, which will further complicate drug testing and discipline for Minnesota employers. Expanded Pregnancy and Nursing Protections Effective July 1, 2023 (included in Mn Chapter 53) Under existing law, employers that employ over 21 employees must provide reasonable break times each day to an employee who needs to express breast milk. Effective July 1, 2023, all employers with more than one employee must comply with the statute. In addition, an employer’s right to require nursing breaks to run concurrent with scheduled break times has been curtailed, and the former exception for breaks that would unduly disrupt the employer’s operations has been revoked. An employee’s right to breaks to express breast milk is no longer limited to the 12 month period following birth of a child. The new law also expands the statutory list of potential reasonable accommodations for pregnant employees to expressly include temporary leave of absence, modification of work schedule or job assignments, and more frequent or longer breaks, in addition to transfer to a less strenuous or hazardous position, seating accommodations, or limits to heavy lifting. Employers must give notice of these provisions upon an employee’s request and must provide information regarding employee rights and remedies in any employee handbook. The Minnesota Department of Labor and Industry is required to provide uniform notice language. All Minnesota Employers Must Provide Paid Sick and Safe Leave Effective January 1, 2024 (included in Mn Chapter 53) While employers in Minneapolis and St. Paul (and some other localities) have been subject to paid sick and safe leave requirements for some time, effective January 1, 2024, all Minnesota employers will be required to provide that benefit. Under the new law, full-time, part-time and temporary employees are entitled to earned sick and safe leave, provided the employee works at least 80 hours in a year for that employer in Minnesota.  Employees will be entitled to accrue at least one hour of earned sick and safe time for every 30 hours worked, up to a legally required 48 hours of earned sick and safe time per year. Employees must be permitted to carry over unused sick and safe time year to year, up to 80 total hours. There is a limited front-loading option as an alternative to accrual based on hours worked.  Employers must keep accurate records of accrued sick and safe time for each employee. Accrual commences on the first day of employment and earned sick and safe time may be used as it accrues. Employees must be permitted to use earned sick and safe time broadly, including for the employee’s own physical or mental illness or injury; to care for a family member; absences due to domestic abuse, sexual assault or stalking of the employee or a family member; seeking legal advice or participating in any criminal or civil legal proceeding related to domestic abuse, sexual assault or stalking; the closure of employee’s place of business due to weather or public emergency; absences due to providing care for family members whose school or place of business has been closed due to weather or public emergency; or an inability to work caused by circumstances analogous to the COVID pandemic. For purposes of the law, “family member” is defined broadly to include an employee’s child (including foster child, adult child, or child to whom the employee stands in loco parentis), spouse or domestic partner, siblings (including foster or stepsiblings), parents (including foster parents, stepparents, or any person who stood in loco parentis to the employee), grandparents or grandchildren, aunts, uncles, nieces, nephews, “any other individual related by blood or whose close association with the employee is the equivalent of a family relationship,” and “up to one individual annually designated by the employee.” An employer may require reasonable notice (up to 7 days) of the need to use earned sick and safe leave time, but only pursuant to a written policy containing reasonable procedures for employees to provide such notice. Notably, if the need for leave is unforeseeable, employers may not require more notice than is “practicable” for the employee. Employers may not retaliate against an employee for exercising rights under the statute and must maintain the employee’s insurance coverage during any period of sick and safe leave. Employees must be returned to a position at the same rate of pay, and with all pre-leave benefits and seniority, upon conclusion of sick and safe leave. Employers must give notice of sick and safe leave rights to current and new employees, either by a posting in the workplace or by providing notice directly to employees in hard-copy or electronic form. The Minnesota Department of Labor and Industry is required to provide a uniform employee notice form. The law also imposes confidentiality obligations on employers who learn private information associated with an employee’s need for protected leave. Employers need not pay out accrued but unused sick and safe time upon termination, but must reinstate an employee’s sick and safe time bank upon rehire within 180 days. Successor employers, including business purchasers, must honor employees’ sick and safe time banks. The law also provides for either the Commissioner of Labor and Industry or the individual employee to bring a claim within 3 years of the alleged violation. An employer’s existing PTO practices likely will suffice to provide the required sick and safe leave benefit, provided the policy or practice satisfies the requirements of the new law (i.e., number of hours, carry over, notice limits, use of leave).Significantly, the new sick and safe leave entitlement is in addition to the paid family medical leave benefit described below. All Minnesota Employers Must Provide Protected Family and Medical Leave Effective January 1, 20261 The vast majority of Minnesota employees (including those employees who may work outside of Minnesota for the majority of their time but whose work is “controlled and directed” from Minnesota) will be entitled to paid family and medical leave (“PFML”) benefits under a state-run insurance program administered by the Department of Economic Development. The program will be funded by a new payroll tax currently set at 0.7%. In the event that an employer chooses to participate in the state-run PFML program, the law allows employers to deduct 50% percent of the payroll tax from their employee’s wages. Employers may be able to substitute a private plan for the state-run benefit, but all employers will be required to provide protected leave for employees concurrent with their entitlement to benefits. The Department of Commerce is granted the authority to certify any substitutions of private plans. Effective January 1, 2026, Minnesota employees will be entitled to protected leave for up to 12 weeks for an employee’s own serious health condition and 12 weeks for bonding, safety leave, family care or qualifying exigency leave (military service and related leave), up to a total of 20 weeks of protected leave in any benefit year. Employees are protected by the statute’s reinstatement rights ninety days from the date of hire. Employees may use PFML leave on an intermittent basis, for up to 480 hours in any 12-month period. There is no undue hardship exception, but an employee must provide a schedule of days off as soon as practicable and must make a reasonable effort to schedule intermittent leave to avoid disruption to an employer’s operations. (However, an employer’s ability to enforce this requirement is virtually nonexistent.) In determining an employee’s eligibility for benefits: “Serious health condition” for purposes of an employee’s self-care or care of a family member is similar to the FMLA; “Safety leave” means leave from work because of domestic abuse, sexual assault or stalking of an employee or the employee’s family member, including seeking medical attention or victim services, seeking relocation, or participating in legal proceedings. “Family members” are defined broadly to include an employee’s spouse or domestic partner, child (including foster child, child to whom the employee stands in loco parentis or “de facto parent”), siblings, parents or a spouse’s parents (including foster parents, stepparents, or any person who stood in loco parentis), grandparents or a spouse’s grandparents, grandchildren, son-in-law or daughter-in-law, or any individual “who has a relationship with the applicant that creates an expectation and reliance that the applicant care for the individual, whether or not the applicant and the individual reside together.” As a general rule, eligibility for leave requires a seven-day qualifying event. An employer may require reasonable notice, including at least 30 days’ notice for foreseeable leave, or as much notice as practicable if 30 days is not possible.  Employees are entitled to protected leave for any day for which they have been deemed eligible for PFML benefits, as well as any day for which the employee cannot work and has applied for benefits in “good faith.” Good faith is defined as “anything that is not knowingly false or in reckless disregard of the truth.” (It is unclear what rights an employee may have if they fail to provide reasonable notice but have applied for benefits other than based on a knowing falsehood.) Thus, employers likely will be required to determine an employee’s eligibility for protected leave in the absence of a benefits eligibility determination from the state, given the potential for significant lags between an employee’s need for leave and their application for benefits (or the determination thereof). It also is unclear what obligations an employer will have to provide protected leave in the event of an appeal from an initial benefits determination. Employers may not interfere with an employee’s use of leave or application for benefits or retaliate against an employee for exercising rights under the statute. Employers are subject to rigorous requirements to return the employee to the same or virtually identical position at the conclusion of protected leave, subject to limited exceptions if the employee’s employment would have terminated regardless of leave status. Employers must maintain the employee’s insurance coverage during any period of protected PFML leave. Although employers may require the employee to pay their share of premiums, an employer’s obligations if an employee fails to do so are unclear. An employer may require that state-mandated PFML run concurrently with federal FMLA leave, to the extent possible, but employers should note that if an employee’s PFML leave is not FMLA-qualifying, the employee would have additional FMLA rights in the event of a later FMLA-qualifying leave. Further, unlike the federal FMLA benefit, there is no threshold minimum number of employees before an employer is covered. Employees can chose to use other available benefits (PTO or vacation) in lieu of PFML benefits, but an employer may not require an employee to do so. An employee’s PFML leave benefits are in addition to sick and safe leave benefits available under state law or local ordinances. Thus the actual duration of protected leave may be substantially more than 12/20 weeks. Employers must post notice of benefits under the new statute in the workplace and must provide written notice (in the employee’s primary language) of benefit and leave eligibility, as well as premium deductions to be made by the employer. Employers have new wage detail reporting obligations and are required to maintain statutorily required employee earnings statements, including tax deductions for PFML benefits premiums, for at least 3 years. For employment practitioners, release of claims under the PFML statute are subject to the MHRA’s 15-day rescission period. Minnesota employers face fundamental changes as a result of the new laws passed in the 2023 Legislative Session. Employers can implement necessary changes thoughtfully, so some of the more onerous obligations have extended effective dates and will requires administrative rulemaking to implement. Executives and HR professionals should thoroughly analyze these new significant requirements and consult with their legal advisors to ensure they take the steps necessary to come into compliance. Dorsey’s Labor and Employment team will discuss these new laws (and others) at our annual symposium in August. 1This is a complex bill with various effective dates applicable to the Department of Economic Development and other government agencies but the Employer’s obligation to provide leave and to commence withholding is January 1, 2026. 

Select Book Chapters

  • Contacting References, MinnCLE Job Applicant Screening: A Practice Guide (2014)
  • Independent Contractors, MinnCLE The Ongoing Business Deskbook (2012)
  • To Pay Or Not To Pay: Identifying and Counting Compensable Work Time Under Wage & Hour Laws, MinnCLE Wage and Hour Handbook: Federal and Minnesota (2011)

Firm Highlights

Insights

EPA Limits Title V Re-Litigation of NSR Permits

Overview On September 25, 2026, the U.S. Environmental Protection Agency (“EPA”) published a final rule that significantly limits the ability of third parties to use the Clean Air Act (“CAA”) Title V permitting process to revisit New Source Review (“NSR”) permitting decisions years after those decisions were made. The rule establishes that NSR permitting determinations generally must be challenged during the original permitting proceeding, thereby providing regulated sources with greater permitting certainty and finality for major capital projects. Published in the Federal Register titled Clarifying the Scope of “Applicable Requirements” Under State Operating Permit Programs and the Federal Operating Permit Program (Docket ID No. EPA-HQ-OAR-2023-0401), the rule amends 40 C.F.R. Parts 70 and 71 to codify EPA’s interpretation regarding when requirements established under other CAA programs may be reviewed, modified, or implemented through the Title V operating permit program. The rule becomes effective 30 days after publication. The rule addresses two principal issues: (1) the relationship between NSR preconstruction permitting and Title V operating permits, and (2) the treatment of the General Duty Clause under CAA section 112(r)(1). Most significantly, the rule provides greater certainty for sources navigating the NSR permitting process. EPA’s amendments are intended to ensure that NSR permitting decisions made through an approved public process are generally not revisited later through Title V permit proceedings. The rule responds to a circuit split between the U.S. Courts of Appeals for the Fifth and Tenth Circuits. In Environmental Integrity Project v. EPA, 969 F.3d 529 (5th Cir. 2020), the Fifth Circuit upheld EPA’s interpretation, concluding that it was consistent with the text, structure, and purpose of Title V. In contrast, the Tenth Circuit reached the opposite conclusion in Sierra Club v. EPA, 964 F.3d 882 (10th Cir. 2020), finding that the then-existing regulatory definition of “applicable requirement” did not support EPA’s position. By amending the regulatory language on which the Tenth Circuit relied and codifying the interpretation approved by the Fifth Circuit, EPA has established a nationwide framework governing the interaction between NSR and Title V. NSR and Title V: EPA Establishes a Uniform Nationwide Framework At the core of the rule is EPA’s effort to define the respective roles of NSR and Title V. The rule codifies the approach EPA has applied since 2017: once a source obtains an NSR permit under an EPA-approved permitting program, and that permit was issued following public notice with an opportunity for comment and judicial review, the permit establishes the NSR-related “applicable requirements” of the State Implementation Plan (“SIP”) or Federal Implementation Plan (“FIP”) for Title V purposes. Under this framework, Title V is not a vehicle for re-examining underlying NSR permitting decisions. EPA does not intend to use the Title V process to revisit applicability determinations, emissions calculations, control technology determinations, permit conditions, or other issues resolved through the NSR permitting process. This principle applies regardless of the stage of the Title V proceeding; whether the NSR permit was issued pursuant to a SIP or FIP; the type of NSR issue involved; or whether the NSR permit is incorporated into Title V sequentially or concurrently. Limited Exceptions EPA recognizes several circumstances in which NSR issues may still be reviewed through the Title V program: No NSR permit was issued at all; The permit was issued without public notice and an opportunity for comment and judicial review; or The issue involves substantive overlap between Title V and NSR requirements, such as the adequacy of monitoring provisions. As a result, the rule does not insulate unpermitted projects or foreclose review of matters that independently arise under Title V. Key Regulatory Amendments The rule revises the definition of “applicable requirement” in 40 C.F.R. §§ 70.2 and 71.2. Paragraph (1): Where an NSR permit is issued with public notice and an opportunity for comment and judicial review, the permit establishes and defines the applicable SIP or FIP requirements for Title V purposes. Paragraph (2): All NSR permit terms, including terms contained in minor NSR permits, constitute applicable requirements that must be incorporated into Title V permits. Paragraph (4): CAA section 112(r)(1) (the General Duty Clause) is expressly excluded from the definition of “applicable requirement,” while section 112(r)(7) Risk Management Program requirements remain included. EPA also amended 40 C.F.R. §§ 70.8 and 70.12 to clarify that alleged defects in requirements established outside the Title V process generally do not provide a basis for EPA objection to a Title V permit or for a Title V citizen petition. General Duty Clause Exclusion The rule also codifies EPA’s longstanding position that the General Duty Clause in CAA section 112(r)(1) is not an “applicable requirement” for Title V purposes. EPA points to several considerations supporting that conclusion, including the distinction between the General Duty Clause and Title V permit terms, the provision’s origins in the Occupational Safety and Health Act’s general duty clause, and the different enforcement structures applicable to the General Duty Clause and Title V permit requirements. Importantly, excluding section 112(r)(1) from the definition of “applicable requirement” does not eliminate EPA’s authority to enforce the General Duty Clause independently of the Title V program. The final rule instead clarifies that the General Duty Clause need not—and should not—be incorporated into Title V permits as an applicable requirement. Practical Implications for Regulated Sources Greater Finality for NSR Permits  For projects requiring PSD, nonattainment NSR, or minor NSR permits, the permitting process becomes the primary forum for resolving disputes regarding applicability determinations, emissions calculations, control technology requirements, offsets, and permit conditions. Once an NSR permit is issued through a qualifying public process, regulated sources should face substantially reduced risk that those same issues will be challenged years later through Title V permit proceedings. Reduced Risk of Collateral Permit Challenges Stakeholders have sometimes sought to use Title V permit issuance, renewal, revision, or citizen-petition proceedings to challenge underlying NSR determinations. The final rule makes clear that Title V is not the appropriate vehicle for challenging whether an applicable requirement was correctly established in the first instance. This should reduce the risk of permit delays and uncertainty associated with collateral challenges to previously issued NSR permits. The rule does not, however, eliminate all Title V challenges relating to an NSR permit. Challenges concerning the Title V permit itself—including whether it appropriately incorporates applicable requirements or contains adequate compliance provisions—remain possible. Increased Importance of the Initial NSR Proceeding Because Title V generally will not provide a second opportunity to challenge the substantive validity of an NSR determination, the administrative record developed during the NSR process becomes increasingly important. Permit applicants should ensure that applicability analyses, emissions calculations, control technology evaluations, modeling demonstrations, and supporting technical documentation are thoroughly developed during the original permitting proceeding. For significant projects, applicants may therefore have an additional incentive to identify and resolve potential permitting issues before the NSR permit is issued rather than assuming that unresolved issues can be addressed during a subsequent Title V proceeding. Potential Incentive for Broader Public Participation EPA also notes that permitting authorities may choose to provide public notice and an opportunity for comment for a broader range of NSR permits because permits issued through a qualifying public process receive the benefit of the finality framework established by the rule. Some permitting authorities may conclude that greater public participation at the NSR stage is preferable to uncertainty during subsequent Title V proceedings. Conclusion The final rule is principally a permitting-certainty measure. For sources that obtain NSR permits through a public process, EPA has substantially limited the ability of third parties to revisit underlying NSR determinations through the Title V program. As a result, regulated entities should benefit from greater finality regarding key permitting decisions, reduced risk of collateral permit challenges, and increased certainty when planning and implementing capital projects.

Insights

Energy Law: Month in Review - September 2026

Welcome to Dorsey’s Energy Law: Month in Review. We provide this update to our clients to identify significant developments in the previous month. Please reach out to any of the authors, listed above, to discuss these issues. Regulatory Developments Massachusetts Ratchets Up State and Local Regulation of AI Data Centers In early September, Governor Maura Healey of Massachusetts signed an executive order requiring that artificial intelligence data centers secure the approval of local communities as a precondition to proceeding with a given project. According to the terms of the order, data center developers will need to secure a “community benefits agreement” as a precondition to receiving permits from numerous state agencies, including the Department of Environmental Protection, the Energy Facilities Siting Board, and the Massachusetts Environmental Policy Act Office. Beyond requiring community benefits agreements, the order also mandates that developers mitigate utility costs to consumers, prohibits the use of nondisclosure agreements, and requires various state agencies to develop measures to limit data center impacts on the environment. North Carolina Regulators Decline Approval of Duke Energy Gas Turbine On September 18, 2026, North Carolina Utilities Commission (NCUC) denied Duke Energy’s application for a certificate of public convenience and necessity required to construct a gas-fueled combustion turbine at its Smith Energy Complex in North Carolina. The NCUC objected strongly to the $584 million price tag and noted that Duke appeared to be constructing the facility “based on anticipated data center customer additions.” The NCUC rejected that anticipated growth as “insufficiently reliable for the Commission to act at this point.” In rejecting Duke’s application, the NCUC also noted that Duke had signed the White House Ratepayer Protection Pledge, in which it represented that it would not shift data center costs to consumers. The NCUC observed that the record did not demonstrate how Duke “intends to adhere to its commitments under the Ratepayer Protection Pledge with regard to the Proposed Facility.” Notably, commission staff had actually supported the construction of the turbine, citing concerns about Duke’s reserve margins. The NCUC noted that it “understands the Public Staff’s expressed concerns,” but those concerns were outweighed by the NCUC’s reservations, including questions of demand. Department of Energy Approves Funds for Grid Improvement The U.S. Department of Energy (DOE) recently announced that it would fund 31 grid-improvement projects in 26 states. The funding initiative is part of the DOE’s “SPARK” initiative. The funding will include $1.9 billion in federal funding from DOE and $3.35 billion in recipient cost-sharing funding. The funds will go to projects designed to improve grid reliability and lower electricity costs. Recipients plan to reconductor over 1,500 miles of transmission lines and will deploy grid-enhancing technologies across approximately 21,000 miles. DOE stated that this initiative will make available over 23 additional gigawatts of electricity. Texas Moderates Rules Governing Data Center Interconnection The Texas Public Utility Commission adopted new regulations governing large-load interconnections. The rules impose a flat study fee of $100,000 for all proposed interconnections, which departs from the initial proposal to impose study fees using a tiered system based on project size. Additionally, the final rule eliminates the PUC’s previous proposal to impose a non-refundable interconnection fee of $50,000 per MW of contracted peak demand. The final rule also moderates the initially proposed regulations governing Electric Reliability Council of Texas (ERCOT) notifications for large-load customers’ non-utilized capacity. The proposed rules would have required notifying ERCOT within 30 days of missing a scheduled energization milestone by six months. The final rules, however, do not require informing ERCOT unless a scheduled energization milestone is missed by 24 months. FERC Denies TransAlta 202(c) Cost-Recovery Plan The Federal Energy Regulatory Commission (FERC) recently rejected TransAlta’s plan to recover $19.9 million in expenses stemming from a DOE order in which DOE prohibited TransAlta from retiring its coal-powered Centralia power plant. TransAlta had previously intended to retire the facility at the end of 2025. TransAlta’s cost recovery plan proposed spending an additional $23 million on repairs to continue operating the unit. FERC’s main objection had to do with geographic scope. TransAlta’s recovery plan called for recovering costs from California Independent System Operator (CAISO) and the Southwest Power Pool (SPP), but the DOE’s order requiring operation of the plant was designed to ensure reliability in the Northwest assessment area (Montana, Oregon, Washington, and parts of northern California and northern Idaho). Accordingly, FERC was unwilling to allow cost recovery from CAISO and SPP when the order that precipitated the additional costs only related to the Northwest assessment area. FERC informed TransAlta that it would only approve cost recovery from load-serving entities in the Northwest assessment area. FERC’s decision comes amid a rush of DOE emergency orders requiring the continued operation of coal-fired generating units. Litigation Appeals Court Upholds Washington Hydropower Plant With Caveats In a September 21, 2026, opinion, the Washington Court of Appeals largely upheld a Clean Water Act water quality certification by the Washington Department of Ecology for the Goldendale Energy Storage Project, a proposed pumped-water storage hydropower system adjacent to, but off-stream from, the Columbia River. A nonprofit (Columbia Riverkeeper) and the Confederated Tribes and Bands of the Yakama Nation appealed the certification, contending that it failed to impose necessary conditions and monitoring requirements to protect the water quality of the Columbia River. Most saliently, the plaintiffs argued that the project had the potential to leak 100 acre-feet of water per year into tributaries of the Columbia River. The Court of Appeals broadly rejected plaintiffs’ challenge to the state’s conclusion that “the project was designed not to leak.” That said, the Court of Appeals did reverse on one narrow issue. Specifically, the court determined that the state’s conclusion that “leakage from the project’s tunnels would be monitored and reported” was not supported by the evidence because the certification “does not explicitly require monitoring and reporting to determine whether there is any leakage.” Accordingly, the court remanded the matter to the state to impose monitoring and reporting requirements but otherwise affirmed the certification. Legislative Developments California Legislates Restrictions on Data Center Energy Use and Grid Costs On September 21, 2026, California Governor Gavin Newsom signed seven bills broadly regulating data centers in the state. SB 1168 directed the California Public Utilities Commission to assess the energy used by data centers. It also requires the PUC to pass costs of transmission and distribution upgrades and load increases on to data centers, rather than customers. SB 886 and SB 887 compel data centers to pay for infrastructure upgrade and generation costs, and wildfire mitigation costs, in addition to imposing environmental review. The statutes additionally increase local oversight of data centers. AB 1577 imposes a monthly reporting requirement that requires data centers to supply energy consumption and efficiency data to the California Energy Commission. AB 2383 contains incentives for data centers to use onsite clean energy generation. Finally, AB 2469 and AB 2619 require data center developments to assess water supply and develop a water scarcity plan. The statutes also mandate statewide water reporting as a precondition to obtaining and renewing business licenses.

Insights

The Supreme Court Update - October 8, 2026

On September 29, 2026, the Supreme Court granted certiorari in one case: Department of Homeland Security v. D.V.D., No. 26-426: This case concerns the Trump Administration’s “third-country removal” procedures, where immigrants are deported to countries not listed in the removal orders. In granting certiorari, the Court granted the Government’s application to stay a lower court decision halting the practice, which will allow third-country removals to continue pending resolution of the case. The issues presented are: (1) Whether the district court had jurisdiction over respondents’ claims; (2) whether the district court had authority to enter class-wide declaratory relief and APA vacatur under 8 U.S.C. § 1252(f)(1); (3) whether the Government’s guidance on third-country removals is unlawful under 8 U.S.C. § 1231(b), the due process clause, or FARRA/CAT and its implementing regulations; and (4) such other questions that the Government determines are appropriate for the proper disposition of the case. On October 1, 2026, the Court granted certiorari in three additional cases: Rhoney v. Barbosa da Cunha, No. 26-104: Immigration officials detained Ricardo Aparecido Barbosa da Cunha—a Brazilian citizen who had lived in the United States for approximately twenty years after entering without inspection—and denied him a bond hearing under 8 U.S.C. § 1225(b)(2)(A). The Second Circuit held that his detention was instead governed by § 1226(a), which permits release on bond, because § 1225(b)(2)(A)’s mandatory-detention requirement applies only to noncitizens apprehended while entering the country or shortly thereafter. The question presented is: Whether 8 U.S.C. § 1225(b)(2)(A) mandates the detention pending removal proceedings of aliens who, like Barbosa da Cunha, are present in the United States without having been admitted. Missionaries of St. John the Baptist, Inc. v. Frederic, No. 25-113: A Catholic religious organization sought to build a shrine to the Virgin Mary on land the organization owned adjacent to its church in Park Hills, Kentucky. Local zoning restrictions prohibited the proposed construction. The question presented is: Whether a land-use regulation that prohibits a religious institution from building a religious structure on its own property constitutes a “substantial burden” on religious exercise under the Substantial Burden Provision of the Religious Land Use and Institutionalized Persons Act, 42 U.S.C. § 2000cc(a). Marschner v. Marschner, No. 25-1349: Under the Uniformed Services Former Spouses’ Protection Act (“USFSPA”), a veteran’s longevity-based retirement pay can be divided in a divorce, but retirement pay based on disability and retirement pay that was waived to receive disability pay are indivisible. The question presented is: Does the USFSPA require state courts to refuse enforcement of indemnification provisions in a divorce settlement agreement?

Insights

SEC Proposes Expansion of Investment Adviser Performance-Based Compensation Rule

On September 30, 2026, the Securities and Exchange Commission (the “SEC”) proposed amendments to Rule 205-3 under the Investment Advisers Act of 1940, as amended (the “Advisers Act”), which provides an exemption from the general prohibition under Section 205(a)(1) of the Advisers Act on registered investment advisers receiving performance-based compensation (the “Proposal”) so long as performance-based compensation is limited to “qualified clients”.1 Most notably for private fund sponsors, the Proposal would expand the definition of “qualified client” to include any investors that satisfy the “accredited investor” definition under Regulation D. The Proposal may also have implications for private fund managers that rely on exemptions from investment adviser registration under state law because certain state-level investment adviser registration exemptions incorporate or otherwise reference the federal qualified client definition. Expansion of the Qualified Client Definition Under the current Rule 205-3, an investor generally may qualify as a qualified client if, among other alternatives, the investor has at least $1.4 million under management with the adviser or has a net worth exceeding $2.7 million. These thresholds are higher than the financial thresholds applicable to many accredited investors under Regulation D. As a result, an investor may currently qualify as an accredited investor for purposes of investing in a private offering without qualifying as a qualified client for purposes of paying performance-based compensation. The Proposal would expand the qualified client definition to include any natural person or legal entity investor that satisfies the accredited investor definition under Regulation D. The Proposal would also remove the assets under management and net worth thresholds under the current Rule 205-3 qualified client test. For private funds relying on Section 3(c)(1) of the Investment Company Act of 1940, this change could reduce the need to apply a separate qualified client standard to investors that already qualify as accredited investors. Dorsey Observations and Next Steps If adopted as proposed, the expanded qualified client definition could be particularly significant for private fund managers. Most private fund offerings are already limited to accredited investors under Regulation D. However, the Proposal could expand the pool of prospective investors available to emerging private fund managers while reducing the regulatory burden associated with complying with Rule 205-3. The Proposal could also benefit advisers operating below the SEC registration threshold that rely on a state private fund adviser exemption. A number of states have adopted exemptions modeled on the North American Securities Administrators Association (“NASAA”) private fund adviser exemption, which may condition relief for advisers to certain funds relying on Section 3(c)(1) on each beneficial owner satisfying the federal qualified client definition. However, state requirements vary, and any effect of the Proposal would depend on the text of the applicable state exemption and how it incorporates Rule 205-3. Many emerging private fund managers may have a larger network of accredited investor relationships than qualified client relationships during the early stages of their investment advisory business. Currently, under Rule 205-3, private fund managers may receive performance-based compensation from investors who do not satisfy the qualified client definition if those investors were admitted to their private funds prior to registration with the SEC. Following registration with the SEC, however, managers may continue to permit investors that are not qualified clients to invest in future private funds but may not receive performance-based compensation from those investors with respect to such investments. In addition, because the net worth and assets under management thresholds for qualified client status are adjusted for inflation every five years, the pool of qualified client investors may diminish over time as previously eligible investors no longer satisfy the applicable thresholds. The Proposal could provide the dual benefit of greater flexibility for private fund managers to establish and maintain relationships with accredited investors as their businesses scale and they become registered with the SEC, and greater flexibility for certain accredited investors to participate in investment strategies that historically have been restricted to much larger institutional investors. Unless and until the Proposal is adopted, investment advisers should continue to comply with the existing qualified client requirements. If the Proposal is adopted, private fund sponsors should consider whether corresponding changes are appropriate for their subscription documents, investor questionnaires, and other offering materials. Advisers that are state-registered or rely on a state-level exemption should also consult the laws and regulations of each relevant jurisdiction before changing investor eligibility standards or performance-based compensation practices, because adoption of the federal amendments may not automatically modify state requirements. Comments on the Proposal will be due 60 days after publication in the Federal Register. 1 Investment Adviser Performance-Based Compensation Modernization, Investment Advisers Act Release No. IA-7022 (Sept. 30, 2026), available at https://www.sec.gov/rules-regulations/2026/09/s7-2026-28#33-11443proposed.