.

Client Alert

Improvements to technology used in your business are eligible for patenting — it’s not your business.

November 17, 2016

by Bridget Hayden

Download as a PDF

Share this page

    If you have talked about patenting inventions lately, you might have been told that software per se is not eligible for patenting and that you should protect your business’s intellectual property (IP) using copyrights, trade secrets and trademarks – all forms of “soft” IP. While software’s source code itself (software per se) cannot be directly patented, it can be protected in a patent claim by expressing the software as a process describing how the software works. This approach is not without its challenges. It can be difficult to capture the software at a level of detail that is both patentable over the prior art and difficult to design around. Since the Supreme Court’s recent Alicei decision, a new challenge has appeared: expressing software in a patent eligible way. Despite the challenges of patenting software and the availability of soft IP approaches, patenting technology improvements provides unique advantages over other kinds of IP protection and recent court decisions have provided meaningful pathways to address challenges to patent eligibility.

    Patents give the patent owner the right to exclude others from making, using, selling, offering for sale or licensing their patented invention. Software-related patents provide protection beyond that afforded by other forms of IP, such as copyright protection. Copyright protection attaches at the time of creation of software code, but covers the code itself and not necessarily the code’s function. Further, copyright protection best protects the software from direct copying (e.g., software piracy), but does not protect software from a competitor independently designing a competing product having the same functionality. By contrast, software patents can be used to protect the functionality of the technology — the software code, network or computer architecture, and their interplay. In this manner, a patent covering the functionality of code can protect a patentee from independently-designed competing products that have the patented functionality. As coders are aware, functionality of a competitor’s product can often be mimicked without pirating source code, but when the functionality of the software is patent-protected, design around options become more difficult. This results in patents providing a broader scope of IP protection, and when combined with other forms of IP protection, can add robustness to your IP portfolio. Consequently, companies that use unique business processes implemented in software commonly seek to protect their technologies using a combination of IP protection that includes patents.

    
The patentability of software is often discussed along with the patentability of so-called “business method patents.” For many years, methods of doing business were considered to be unpatentable subject matter, but ultimately, the acceptability of business method patents was affirmed in 1998 when the Federal Circuit decided State Street Bankii .

    For years, both business method and software patents continued to flourish until July 2014 when the Supreme Court decided Alice Corp. v. CLS Bank.iii There, the Supreme Court established a two-step framework for distinguishing patent ineligible abstract ideas from applications of those concepts that are patent eligible. In step one, the framework asks whether a claim is directed to a judicial exception amounting to an abstract idea. If so, the claim is patent ineligible unless it passes step two in the framework by further reciting an “inventive concept” amounting to something significantly more than the judicial exception. While not outright banning software or business method patents, the effect of this decision is that the ability to protect software has become increasingly difficult, and exact boundaries of patentable subject matter in view of Alice remained undefined. Indeed, immediately after the Supreme Court decided Alice, the U.S. Patent and Trademark Office (USPTO) began rejecting patent applications related to business solutions implemented in software, alleging the inventions are not subject matter eligible. Several hundred software-related patent applications set to issue into a patent were even withdrawn from issuance by the USPTO. The rejection rate for lack of subject matter eligibility in some segments of the USPTO reached 90 percent.

    
Patent attorneys are now faced with a new landscape for patenting software-related innovations. Over the two years since Alice, the Federal Circuit has issued five primary decisions in favor of subject matter eligibility for software technologies that have provided meaningful guidance for practitioners: Amdocs, McRO, Bascom, Enfish, and DDR.

Amdocs v. Openet Telecomiv

    
The most recent Federal Circuit decision, Amdocs, was decided on November 1, 2016. There the court found patent eligible an invention directed to software for processing network accounting information. Uniquely, the court had the benefit of prior claim term construction from a related proceeding to inform its understanding of certain functional claim terms, which is in contrast to the vast majority of decisions where subject matter eligibility has been decided as a threshold issue, thus removing the opportunity to define claim terms during the subsequent claim construction phase. In Amdocs, because the functional claim term “enhance” had been interpreted as being dependent on distributed computer architecture, it was defined as “to apply a number of field enhancements in a distributed fashion,” a critical improvement over the prior art. Other claim interpretations helped illustrate the network accounting information is processed by software in one location and then transmitted over a network to a centralized manager, adding structure to the otherwise functional claim language. The court’s understanding of the claimed invention was further bolstered by the specification, which the court characterized as disclosing “a critical advancement over the prior art” that resulted in an unconventional technological solution to a technical problem. Illustrating improvements to the prior art and interpreting the claims as including structural components for implementing software helped the court find the claims were patent eligible. Including these features in software-related patent applications should be useful in avoiding or overcoming abstractness rejections under the Alice framework.

    
In making its decision, the court relied, in part, on DDRv, which is the first Federal Circuit decision to find claims subject matter eligible after Alice.

DDR Holdings v. Hotels.comvi

    
Decided in December 2014, in DDR, the court found claims to be patent eligible that were “necessarily rooted in computer technology in order to overcome a problem specifically arising in the realm of computer networks.” The claims addressed the “business challenge” of “retaining website visitors” that would have otherwise been transported away to a different website after clicking a link. While claims addressing business challenges have typically received significant scrutiny before the USPTO and Federal Circuit, the court found that the invention included a patentable hook — the claims addressed a business challenge particular to the Internet. Based on this rationale, the court found the claims patent eligible. In doing so, the court ultimately held that inventions necessarily rooted in computer technology, such as Internet-centric inventions, that provide a result which “overrides the routine and conventional sequence of events ordinarily triggered by the click of a hyperlink” can be patent eligible under step two of the Alice framework as being significantly more than an abstract idea.

    
While many claims still struggled under Alice even in view of DDR, the decision cleared a path to subject matter eligibility for claims amounting to significantly more than an abstract idea by being rooted in computer technology. DDR remained a go-to citation for practitioners for nearly a year-and-a-half until the Federal Circuit released its Enfish decision which further expanded the path cleared by DDR.

Enfish v. Microsoftvii

    
Decided in May 2016, in Enfish, the court noted that Alice should not be read so broadly as to find software-related inventions inherently abstract, thus failing step one of the Alice analysis and requiring analysis under step two of the framework. Rather, the court found that it is “relevant to ask whether the claims are directed to finding an improvement to a computer functionality versus being directed to an abstract idea, even at the first step of the Alice test.” Following this view, the court found that the claims were directed to a “specific asserted improvement in computer capabilities” under step one, rather than an abstract idea for which a computer was merely invoked as a tool. Stated another way, the court explained that “when the plain focus of the claims is on an improvement to computer functionality itself, not on economic or other tasks for which a computer is used in its ordinary capacity,” the claims are not directed to an abstract idea and are patent eligible.

    
Enfish provided strong arguments for inventions that improved the functioning of a computer and provided two avenues for such inventions to be patentable: under step one as being directed to an improvement (as in Enfish) or under step two as being necessarily rooted in computer technology (as in DDR). However, the lines between these two avenues remained blurry and many patentees still faced patent ineligibility concerns for inventions that presented a close call. Practitioners did not have to wait long for clarity as the very next month the court decided Bascom.

Bascom v. AT&Tviii

    
Decided in June 2016, Bascom examined the subject matter eligibility of an invention related to filtering of internet content. While improvements to internet filtering technology could be characterized as an improvement to computer technology, the court did not find the claims patent eligible under step one like in Enfish. Rather, the court found the claims directed to filtering content generally, which the court characterized as a patent ineligible abstract idea. With the claims found to be directed to an abstract idea, the court moved on to step two of the analysis. In doing so, the court noted that “some inventions’ basic thrust might more easily be understood as directed to an abstract idea, but under step two of the Alice analysis, it might become clear that the specific improvements in the recited computer technology go beyond well-understood, routine, conventional activities and render the invention patent-eligible.” Moving on to step two, the court indicated that the invention described how its particular overall arrangement of elements is a technical improvement over prior art ways of filtering such content. The prior techniques were “susceptible to hacking and dependent on local hardware and software, or confined to an inflexible one-size-fits-all scheme.” Further, in this analysis, the court found that this inventive concept in the claim as a whole, rather than in the form of an individual recitation. In this manner, the court held that step two of the analysis need not rest on individual elements, but can instead lie on the combination of elements, even where those elements are generic computer elements that cannot alone contribute to subject matter eligibility.

McRO v. Bandai Namcoix

    
Decided in September 2016, McRO continues the line of cases finding patent eligibility in an improvement to a computer. However, McRO is noteworthy for finding the improvement not merely in improvements to the operation of a computer. Rather, the invention in McRO related to a set of mathematical relationships that allowed a computer to perform a function not previously performable by a computer — namely the ability of a computer to perform 3D animation techniques that previously required a human animator. McRO further makes it clear that an invention cannot be oversimplified by the USPTO or the courts. The invention set forth in the claims must be viewed as a whole and individual requirements cannot be ignored. In this manner, even though the improvement involved a set of mathematical relationships that would have been unpatentable if taken individually, the overall effect of the invention was to allow computers to perform new tasks, which provided patentability.

- - -

    With the trend starting in DDR and continuing through Amdocs, it appears that courts are loosening their belt on subject matter eligibility by emphasizing the patentability of improvements to computers under both step one and step two of the Alice test. The trend appears to be trickling-down to the USPTO by its recent issuance of new examination guidelines on subject matter eligibility.x

    
Businesses seeking to protect their software-related inventions with patents, should keep these cases in mind when developing invention disclosures and preparing patent applications. The lessons learned from these cases can help reframe inventions as improvements to the functioning of a computer or can add structure to otherwise functionally-described software, which — while not guaranteeing patentability — appear to provide substantial steps down the path to patentability.


i  Alice Corp. v. CLS Bank Int’l, 134 S.Ct. 2347 (2014).

ii State Street Bank and Trust Co. v. Signature Fin. Group, Inc., 149 F.3d 1368 (Fed. Cir. 1998).

iii Alice Corp. v. CLS Bank Int’l, 134 S.Ct. 2347 (2014).

iv Amdocs v. Openet Telecom, No. 2015-1180 (Fed. Cir. Nov. 1, 2016).

v DDR Holdings v. Hotels.com, 773 F.3d 1245 (Fed. Cir. 2014).

vi Id.

vii Enfish, LLC v. Microsoft Corp., No. 2015-1244 (Fed. Cir. May 12, 2016).

viii Bascom Global Internet Servs., Inc. v. AT&T Mobility LLC, No. 2015-1763 (Fed. Cir. June 27, 2016).

ix McRO v. Bandai Namco, No. 2015-1080–1101 (Fed. Cir. Sept. 13, 2016).

x USPTO, RECENT SUBJECT MATTER ELIGIBILITY DECISIONS, Nov. 2, 2016.

Firm Highlights

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.

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

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?