.

Blog Post

AI Regulation Introduced in Europe – Setting the Way Forward for the Rest of the World or Slowing Down the Adoption of New Tech?

March 26, 2024 – The TMCA

by Ron Moscona and Tessa Adams

Download as a PDF

Share this page

The EU AI Act, which was passed by the European Parliament on 13 March and is set to become law later this year, will probably be the world’s first legislation to introduce a general regulatory framework for artificial intelligence systems. The European Union is known to pioneer the responsible regulation of emerging technology, and the AI Act is no exception: it intends to govern the development, deployment and use of AI systems in order to protect against risk and uphold health, safety and fundamental rights, while balancing technological development and competition. If successful in achieving that balance, it will likely inform legislative standards around the world. The framework comes at a time where artificial intelligence is increasingly becoming more easily and readily deployable in a range of sectors and products, presently with little or no limitations to its usages.

Overview

The Act will cover AI systems that are deployed anywhere in the European Union, defining an AI system broadly as: “a machine-based system designed to operate with varying levels of autonomy and that may exhibit adaptiveness after deployment and that, for explicit or implicit objectives, infers, from the input it receives, how to generate outputs such as predictions, content, recommendations, or decisions that can influence physical or virtual environments.”

The framework classifies AI systems according to the risk they present and sets out categories ranging from “unacceptable risk” to “minimal risk”, each subject to varying degrees of regulation. The majority of the Act focuses on requirements for developers of “high risk” systems, including regulatory oversight and conformity assessments, data quality and traceability, robustness and accuracy, human oversight, and transparency – but there are also obligations for commercial users, importers, distributors and product manufacturers. Further, the Act prohibits certain systems that are deemed to present unacceptable risk. Rules are also laid down for general-purpose AI models, being those systems that are widely integrated into a range of products without a specific purpose.

Prohibited Systems

The Act bans, with very limited exceptions, AI systems which pose unacceptable threats to the safety, livelihood and rights of EU citizens, including systems designed to:

  • Manipulate or influence people’s behaviour subconsciously;
  • Exploit vulnerabilities of specific groups in order to distort their behaviour;
  • Conduct social scoring (i.e. categorising people based on their behaviour, race, political opinions, sexual orientation, etc.);
  • Enable facial recognition using web-scraping;
  • Conduct real-time biometric identification, except in very limited law enforcement situations.

Additionally, systems designed to do anything else which is already against the law are prohibited.

High-risk Systems

Systems considered high-risk are those with significant potential to cause harm or affect safety or fundamental rights. Specifically, AI systems used in certain sectors are designated as high-risk, including systems used in medical devices, lifts, machinery, aviation, automotive and transportation, education, border control, and the management of critical infrastructure.

Of course, products within many of these sectors are already regulated products in the European Union and subject to safety standards and conformity assessment requirements. The Act designates as “high risk” any AI system used as part of a regulated product falling within any of the list of existing product regulations set out in Annex II of the Act.  In addition, Article 6(1) designates as “high risk” any system intended to be used as a safety component or as a safety product, if such product or system is subject to a legal requirement in the EU to undergo a third-party conformity assessment.

Further, under Article 6(2) of the Act, regardless of the particular product or system in which an AI model might be deployed, if the AI system is developed for use within certain sectors listed in Annex III of the Act it will be considered “high-risk”. These listed sectors include education and vocational training, biometrics, law enforcement, employment and critical infrastructure. Any use of an AI system in one of the listed areas is deemed “high-risk” regardless of whether the system is part of a regulated product subject to EU safety standards. For example, in the employment sector, AI systems might be used to filter out prospective applicants; in the education sector, a system might be deployed to assist with deciding on admissions. Such systems will be deemed “high-risk” under the Act.

Where a system is designated as high-risk, most obligations fall on the “provider”, i.e. the developer, of that system. Providers must conduct a Fundamental Rights Impact Assessment before placing their system on the market, and also must continuously assess risk after that. The assessment will evaluate the risks posed by the system and how these will be mitigated. If such a provider believes their system is not high-risk despite being designated as such by the Act, it must conduct and register an assessment to prove this before making the system available, in order to take advantage of the exemption for systems where there is no “significant risk of harm to the health, safety or fundamental rights of natural persons, including by not materially influencing the outcome of decision-marking” (Article 6(2a)).

Providers of high-risk systems, as part of their ongoing risk assessment obligations, will need to integrate processes and documentation to minimise risks, and must ensure that the data used to train and test the system are governed in accordance with that assessment and that cybersecurity is maintained. Further, providers must put together technical documentation to demonstrate a system’s compliance with the Act and must keep records and logs of safety incidents. Such records must be provided to deployers of the system, but also to competent authorities if requested as part of a provider’s co-operation obligations under Article 23. A key concept of the Act is human oversight: high-risk systems must be developed in such a way to allow them to be overseen by natural persons when deployed, allowing users to intervene and override decisions made by AI algorithms. Transparency obligations dictate that users be informed when interacting with AI systems.

Conformity Assessment Procedures and Regulatory Oversight

To guarantee compliance with the standards and requirements laid out in the Act, before putting a high-risk system on the market, the providers will have to issue a declaration of conformity and apply a CE mark to the system. To do so, they will have to follow conformity assessment procedures, either in accordance with existing regulations for Annex II or Article 6(1) regulated products (such as medical devices, machinery, or automotives) or in accordance with the conformity assessment procedures laid out in the Act for AI systems used in non-regulated products within the designated high-risk sectors (as listed in Annex III).

The conformity assessment procedure will in many cases involve notified bodies which will have the role of assessing the high-risk system’s conformity with the rules and standards laid out in the legislation. Notified bodies have a key role in product safety conformity assessment and certification in the EU and are designated to perform that role by the member states. However, the providers, as well as importers, distributors and deployers, of the AI systems will have the ultimate legal responsibility to ensure compliance with the regulatory requirements.

Compliance obligations do not fall upon the heads of providers alone. Further down the supply chain, deployers of the AI system (being commercial users who exploit a system in their own product, rather than end-users who interact with the system) need to take measures to ensure that they use a high-risk system in accordance with the instructions from the provider. Importers of high-risk systems are also responsible for ensuring that a system conforms with the Act, and distributors must verify that a system bears the CE conformity marking before distributing it.

Consequences for non-compliance can be serious: for example, breaches of certain high-risk system obligations can result in a fine of the higher of €35M and 7% of turnover, with small and medium size enterprises ("SMEs") and start-ups being subject to a fine which is the lower of the two figures.

General Purpose Systems

General-purpose AI (GPAI) models are those with no specific purpose and which instead generate output or content in response to a prompt from the user. Such models are frequently integrated into downstream apps and systems due to their range of uses and operate via extensive training using a huge amount of data (e.g. images or text). The obvious examples that spring to mind are tools like ChatGPT, or models used to create AI images or deep-fakes.

Such models, regardless of whether they form high-risk systems or are subject to other requirements under the Act, have separate obligations. Given the models do not have specific intended purposes, risk assessments are difficult due to the huge range of potential uses. Providers of such models instead need to evaluate generic “systemic risks” that might apply in most usages, such as the generation of hate speech or misinformation, assisting or enabling fraud, and so forth. Models presenting systemic risks are the more powerful GPAIs, and will be subject to further obligations, including performing evaluations to identify and mitigate such risks, keep track of incidents and corrective measures taken, and maintain adequate cybersecurity.

Obligations for all GPAI providers include publishing summaries of the content used to train the model and on the testing process, and to make detailed documentation on this available to downstream deployers of the model. Other notable obligations include:

  • Labelling content as AI generated: Under Article 52, providers of systems, whether GPAI or not, which generate image, video, text or audio content, need to mark such content as AI-generated. The effects of this will mean that AI-generated images (such as the Willy’s Chocolate Experience advert) or videos (such as deep-fakes, which the obligation expressly applies to) need to be labelled as such. Additionally, AI-generated public interest articles or other media text also need to be labelled unless they have undergone human review.
  • Compliance with copyright laws: Article 52C requires providers of GPAI models to put in place a policy to respect EU copyright laws. The Copyright in the Digital Single Market legislation (EU Directive 2019/790) requires EU member states to provide for an exception to copyright protection for the purpose of enabling data mining of published and lawfully accessible works. The exception opens up a wealth of content resources for training AI models, free from copyright restrictions, which can be highly valuable for developers. But publishers can reserve their rights if they wish to prevent their content being used for data mining. As part of the copyright protection policy that providers of GPAI models are required to adopt, technical means would have to be put in place to ensure that systems that scrape data from content resources for the purpose of training AI models can automatically identify and respect such reservations of rights. These rules are particularly relevant given the recent wave of copyright infringement lawsuits against GPAI developers relating largely to the use of published content for training AI models.

Other Parts of the Act: Low-risk Systems and Balancing Innovation

AI systems not prohibited or designated as high-risk, and which are not GPAI, are subject to little or no regulation under the Act. Systems which are not high risk but which still generate certain AI content such as chatbots are considered limited risk, and developers must still adhere to some obligations, including transparency to ensure users are notified that content they interact with is AI-generated (see above). Otherwise, systems presenting minimal or no risk are unregulated.

Certain members of the industry have expressed concern that over-regulation will stifle the development of beneficial technology or will present a disproportionate burden on businesses. Specific parts of the Act attempt to address effects on technological advancement, especially for SMEs, by encouraging responsible development of AI systems. Article 53 requires “regulatory sandboxes” in each member state, to foster AI innovation in a controlled setting under the supervision of authorities. SMEs and start-ups are to be prioritised under this provision.

Implementation and Consequences

Following the Act being approved by the European Council and published in the EU’s Official Journal (likely to occur around May), it will become law and various parts and obligations will enter into force over a period of six months to three years following that. In addition to the role of notified bodies in relation to conformity assessments, the Act establishes the AI Office, part of the European Commission, to implement and enforce the obligations, and dictates that the Office will within 18 months publish guidelines to provide providers and deployers with practical examples of the various categories of risk and detailing actionable steps in order to assist them in complying with their obligations.

Impact on Industry and Markets

The rapid development of AI and the significant implications that the technology could soon have on people’s lives have raised great concerns not just from commentators and academics but also from governments and many industry leaders. The risks are broad, varied and very real. It is no surprise that authorities are keen to address and regulate the potential threats the technology could introduce to people’s rights and safety.

The EU AI Act does not set out to exhaustively identify or evaluate each and every potential risk. Rather, whilst identifying some obvious areas of concern, its main function is to put the onus on developers of AI systems and on other organisations that wish to put on the market products and services powered by AI, to identify and weigh the risks and to address them in the framework of a regulatory system that mandates oversight, transparency and accountability.

The European regulatory approach will be successful if it can ensure that AI technologies and AI powered products and services placed on the market in Europe are designed to service the requirements of consumers and other users whilst avoiding serious harm. To achieve this, a significant investment will have to be made by EU member states to build the necessary regulatory capabilities and to guarantee a high level of enforcement. Robust, highly professional and efficient regulatory and enforcement mechanisms can promote safety and quality without stunting safe and responsible innovation. If those systems can be put in place quickly enough and if they are equipped with the necessary resources, the European regulatory framework can achieve the task of protecting consumers in Europe and it can help to nudge the global AI industry in the right direction. It could also potentially provide a blueprint for regulations to be introduced in other parts of the world.

But Europe alone cannot shape a global industry (particularly one that has so far been led by major players elsewhere, particularly in the US and China). Other major countries will have to play their parts as well, whether by adopting similar regulatory processes as the new EU framework or through alternative approaches, to ensure that AI technology is used to make the world a better place for people, whilst eliminating or minimising the potential threats.

Firm Highlights

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

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

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.