.

Client Alerts/eUpdates/Alerts

Justice Issues Final Rule Restricting Transfer of Personal U.S. Data to Countries of Concern, Effective in April 2025

January 14, 2025

by Dave Townsend, Austin T. Chambers, Lawrence Ward, T. Augustine Lo, and Justin T. Huff

Download as a PDF

Share this page

The U.S. Department of Justice (“DOJ”) published its final rule (“Final Rule”) on January 8, 2025, that will prohibit or restrict transfer of certain data of U.S. persons to countries of concern, including to China. The Final Rule largely tracks with DOJ’s notice of proposed rulemaking (“Proposed Rule”), which we summarized in a previous eUpdate. The Final Rule therefore adopts the basic structure of prohibiting certain data transactions, while permitting restricted transactions only if security requirements are implemented to protect U.S. personal data.

In short, knowing the type of data, the type of transaction, and the location of any person who can access the data is required to determine whether a prohibition or restriction applies to the proposed transaction or transfer of the data under the Final Rule. As explained below, the Final Rule reaches many types of transactions, may cover merely providing access to certain data of U.S. persons, and has a framework of exclusions that may allow companies that would otherwise be regulated by the Final Rule to continue to transfer personal data to countries of concern.

The Final Rule is generally effective starting on April 8, 2025, meaning that data transfers after that date will be subject to the Final Rule and the potential penalties for transactions that violate the Final Rule. DOJ delayed the effective date for certain due diligence and auditing requirements to October 5, 2025. In its discussion of the Final Rule, DOJ rejected delaying the effective date further due to what it describes as the need to quickly address transfers of sensitive U.S. personal data to countries of concern. DOJ also holds open the possibility of delaying the effective date of the Final Rule, either in part or in full, through general licenses or regulatory changes.

This eUpdate summarizes key aspects of the Final Rule, with a particular focus on changes since the Proposed Rule. The eUpdate does not comprehensively describe the Final Rule. In particular, we note our previous summary of the auditing requirements, due diligence, potential penalties, and other details of the Proposed Rule (see link above), most of which are unchanged by the Final Rule.

Legal Background

By issuing the Final Rule, DOJ has concluded the rulemaking process to implement Executive Order (“EO”) 14117 dated February 28, 2024.

As a basis for regulating international data transfers, EO 14117 and the Final Rule declare an international emergency under the International Emergency Economic Powers Act (“IEEPA”). In particular, President Biden in EO 14117 identified efforts to access and exploit government-related data or bulk U.S. personal data by countries of concern as an unusual and extraordinary threat to U.S. national security. DOJ identifies counterintelligence concerns, the risk of blackmail and ransomware, and the ability to use artificial intelligence (“AI”) tools as justifying action under the Final Rule. DOJ also notes a gap in federal law that currently does not address international data transfers to countries of concern. 

Who is Impacted by the Final Rule?

The Final Rule broadly applies to and regulates the activities of U.S. companies and individuals operating in many industries and markets. The framework for the Final Rule is outlined below. Initially, however, it is worth highlighting some examples of activities that DOJ believes are subject to the Final Rule, which are indicative both of the scope of and priorities reflected in the Final Rule.

We note these examples with caution, as the status of these examples under the Final Rule could change depending on the precise facts (e.g., amount of data collected), and the activities described below may be permissible if relevant parties adopt security measures, or if the activities qualify for an exemption. We thus refer to these examples as subject to potential restrictions under the Final Rule, depending on the facts and circumstances of the transactions.

  • A U.S. company develops mobile app games that collect data on U.S. users. The U.S. company hires a CEO from a country of concern, who will be provided access to data on the U.S. users. The hiring of the CEO is subject to potential restrictions under the Final Rule.
  • A U.S. company develops social media apps that systematically collect data of U.S. users. A foreign company from a country of concern purchases a minority stake in the U.S. business. The investment agreement allows the foreign company to access the data of U.S. users. The investment agreement is subject to potential restrictions under the Final Rule.
  • A U.S. company operates an app that gathers geolocation data of U.S. users. The U.S. company enters into a vendor agreement with a country of concern to process and store the data. The vendor agreement is subject to potential restrictions under the Final Rule.
  • A medical facility with health data about U.S. patients contracts with a company in a country of concern to provide IT-related services, including by providing access to the data about U.S. patients. The contract is subject to potential restrictions under the Final Rule.
  • A multinational company maintains data about U.S. persons and contracts with a service provider in a country of concern to process and store the data, including the data about U.S. persons. The service agreement is subject to potential restrictions under the Final Rule.
  • A U.S. company hires a data scientist who is a citizen of a country of concern to develop an AI personal assistant intended for the U.S. company’s financial services customers. The data scientist’s responsibilities require access to data on large numbers of U.S. persons. The employment of the data scientist is subject to potential restrictions under the Final Rule.

As is apparent from these examples, the Final Rule applies to and potentially restricts the activities of companies in many industries and in a wide range of common IT and business operations. Below we summarize key aspects of the Final Rule.

Key Definitions in Final Rule

The Final Rule applies to U.S. persons who process sensitive U.S. government or bulk U.S. sensitive personal data as described below, and in particular those who engage in transactions with or have operations in countries of concern. However, the Final Rule also will significantly impact non-U.S. persons or operations involving countries other than countries of concern, to the extent they may be involved with U.S. government data or bulk U.S. sensitive personal data and there is or may be potential access to personal data in countries of concern.

DOJ adopts the following key definitions in the Final Rule, all of which are closely aligned with those in the Proposed Rule.

  • “Bulk U.S. Sensitive Personal Data.” The Final Rule adopts “bulk” thresholds consistent with the Proposed Rule. These categories are summarized in the chart at the end of this eUpdate. In a change from the Proposed Rule, DOJ also established a bulk threshold for epigenomic, proteomic, or transcriptomoic data of U.S. persons.
  • “Countries of Concern.” The Final Rule designates six countries—China (including Hong Kong and Macau), Cuba, Iran, North Korea, Russia, and Venezuela as countries of concern. This list can be expanded upon further designations of countries that pose a risk to U.S. national security.
  • “Covered Person.” The Final Rule prohibits or restricts transfers to a Covered Person in addition to a Country of Concern. DOJ revised the definition of a Covered Person to cover the following: (1) foreign entities that are 50 percent or more owned (individually or in the aggregate) by a Country of Concern, organized under the laws of a Country of Concern, or have their principal place of business in a Country of Concern; (2) foreign entities that are 50 percent or more owned (individually or in the aggregate) by a Covered Person; (3) foreign employees or contractors of countries of concern or entities that are Covered Persons; and (4) foreign individuals primarily resident in Countries of Concern. DOJ also can specifically designate persons, regardless of location, that it determines to be, or to have been, controlled by or under the jurisdiction of a Country of Concern or a Covered Person.
  • “U.S. Person.” A U.S. person includes any individual or entity who is located in the United States; individuals who are U.S. citizens, nationals, or permanent residents, or have refugee or asylee status under U.S. law; and corporations organized solely under the laws of the United States.
  • “U.S. Government Data.” U.S. Government-Related Data includes two types of data, regardless of the volume of the data: (1) geolocation data covering any precise location data within specific longitude and latitude coordinates within areas identified in the Final Rule; and (2) data about U.S. Government personnel marketed as linked to current or recent former U.S. Government employees or contractors. The Final Rule defines “recent employees or contractors” as those who worked for the U.S. Government (including the military and intelligence community) within a two-year period preceding a covered transaction.

Prohibited, Restricted, and Exempt Transactions

The Final Rule creates a framework of prohibited, restricted, and exempt transactions. Companies will need to consider whether they have transactions of U.S. Government or Bulk Sensitive U.S. Person Data with Countries of Concerns or Covered Persons, and if so, whether those transactions are prohibited, restricted, or exempt. The Final Rule also prohibits facilitating prohibited or restricted transactions, actions taken to circumvent the Final Rule, or causing a violation of the Final Rule.

This framework ultimately will allow certain companies to continue working or collaborating with countries of concern. Companies can rely on the categories of exempt transactions to permit sharing of certain data between the United States and a Country of Concern. Alternatively, certain restricted transactions may, however, proceed if companies adopt security requirements specified in the Cybersecurity and Infrastructure Security Agency (“CISA”) rules. The CISA security requirements can be found online and are summarized below.

The Final Rule prohibits U.S. persons from engaging in two types of transactions.

  1. Data Broker Transactions. The Final Rule prohibits a “Data Brokerage” transaction with a Country of Concern or a Covered Person that involves Bulk U.S. Sensitive Personal Data. A “Data Brokerage” transaction means selling, licensing, or similar commercial transactions where the recipient did not collect or process the data directly from the individuals linked or linkable. By definition, a “Data Brokerage” transaction is not an employment agreement, investment agreement, or vendor agreement as those terms are defined below. These Data Brokerage transactions are defined more broadly than transactions under other data brokerage laws, and the DOJ notes as justification for this broad definition that the operation of ad exchanges, the use of social media, or other “tracking” pixels can allow access to Bulk Sensitive U.S. Personal Data or U.S. Government Data by a Covered Person or in a Country of Concern.
  2. Human Genetic Data. The Final Rule prohibits a U.S. person from engaging in a transaction with a Country of Concern or a Covered Person involving bulk human genomic data, or data concerning bulk epigenomic, proteomic, or transcriptomoic as defined below at the end of this eUpdate.

The Final Rule makes the following three classes of transaction restricted: (1) employment agreements, (2) non-passive investment agreements, and (3) vendor transactions (collectively, “Restricted Transactions”). Unless the U.S. person adopts CISA’s proposed risk mitigation security requirements, U.S. persons cannot engage in the following Restricted Transactions with Countries of Concern or a Covered Person if they involve Bulk U.S. Sensitive Personal Data.

  1. Employment Agreements. Agreements or arrangements where an individual, other than an independent contractor, performs work or job functions in exchange for payment or other consideration, including on a board or committee, executive-level arrangements or services, or employment services at an operational plant.
  2. Investment Agreements. The exchange of payment or other consideration for direct or indirect ownership interests or rights in relation to real estate in the United States or a U.S. legal entity. The Proposed Rule excludes from an “Investment Agreement” passive investments such as for publicly traded securities, index funds, or as a limited partner in a venture capital fund.
  3. Vendor Agreements. The provision of goods or services, including cloud-computing services, in exchange for payment or other consideration, other than an Employment Agreement.

The Final Rule also establishes a framework of exempt transactions that will make many data processing activities and transactions outside of the Final Rule’s prohibitions or restrictions. In particular, the following nine types of activities or transactions may qualify for exemptions under the Final Rule.

  1. Personal communications, informational materials, and travel information are exempt under the Final Rule. This exclusion recognizes long-standing exclusions, mandated under the IEEPA statute, from IEEPA-based U.S. economic sanctions administered by the U.S. Department of the Treasury Office of Foreign Assets Control (“OFAC”). Companies will need to carefully consider the scope of these exemptions, which DOJ likely will interpret narrowly, similar to OFAC’s narrow interpretation of them.
  2. Activities involving U.S. Government operations.
  3. Financial services for banking, capital markets, futures or derivatives, or financial insurance services, e-commerce, and certain investment management services.
  4. Corporate group transactions between a U.S. person and its foreign subsidiary or affiliate, if they are ordinarily incident to and part of routine administrative or business operations, such as human resources, payroll, taxes, permits, compliance, risk management, travel, and customer support.
  5. Transactions related to certain federal law or international agreements. DOJ cites the following legal instruments as authorizing transactions under this exemption: the Convention on International Civil Aviation (2022); the WHO constitution (1946); various U.S.-China agreements on customs, legal assistance, and taxation; the U.S.-Cuba Extradition Treaty (1905); U.S.-Russia agreements on customs (1994) and legal assistance (1999); the U.S.-Venezuela Legal Assistance Treaty (1997), the International Health Regulations (2005); and certain public health surveillance and response mechanisms.
  6. Investment agreements that are subject to mitigation or other action taken by the Committee on Foreign Investment in the United States (“CFIUS”), if CFIUS explicitly designates them as exempt.
  7. Transactions that are ordinarily incident to and part of the provision of telecommunications services, including voice and data communications services regardless of delivery method. DOJ lists communications via cable, Internet Protocol, wireless, fiber, or other transmission mechanisms, as well as arrangements for network interconnection, transport, messaging, routing, or international voice, text, and data roaming as potentially qualifying for this exemption.
  8. Transactions involving data transfers or access to data with a Country of Concern or Covered Persons involving drug, biological product, device, or combination product approvals or authorizations if such approvals are necessary to obtain or maintain regulatory approval. “Regulatory approval data” means sensitive personal data that is de-identified or pseudonymized under FDA regulations (21 C.F.R. 314.80(i)) and required by a regulatory entity to research or market a drug, biological product, device, or combination product, including post-marketing studies and surveillance.
  9. Clinical investigations and post-marketing surveillance data if the transactions are part of clinical investigations regulated by the FDA under sections 505(i) and 520(g) of the Federal Food, Drug, and Cosmetic Act, or to support FDA applications for research or marketing permits for drugs, biological products, devices, combination products, or infant formula, and the data are de-identified or pseudonymized consistent with FDA regulations (21 C.F.R. 314.80(i)).

Final CISA Security Rule

            Under the Final Rule, Restricted Transactions may be permitted on the condition that certain security procedures and controls are put in place to protect U.S. Government Data or Bulk Sensitive U.S. Personal Data (collectively, Covered Data). These security controls must be implemented with respect to any “Covered System” that is used to process Covered Data as part of a Restricted Transaction, regardless of whether Covered Data has been deidentified or encrypted on that system. Further, in a clarification in the Final Rule, the existence of security measures does not affect the application of the Final Rule, in principle, meaning that the existence of comparable security controls (e.g. encryption) does not impact companies’ obligations to comply with other requirements of the Final Rule.

Under CISA’s final security rule requirements, there were relatively few changes to the mandatory security processes and controls relative to the proposed CISA rule. However, certain incremental changes were made, and the final CISA rule allows companies to take a slightly more flexible and risk-based approach with respect to certain controls, in particular those relating to vulnerability management, logging, and certain systems documentation. 

            As with the Proposed Rule, CISA’s security requirements borrow heavily from NIST Cybersecurity Framework and Privacy Framework standards. However, the specificity of these requirements, and CISA’s intent to build on the specific national security objectives set out in the Order, mean that these requirements include a number of new and unique obligations for affected organizations. Organizations engaging in Restricted Transactions that must conform to the CISA rules will therefore be required to conduct additional IT system reviews, update applicable policies, and establish additional security controls in order to properly secure Covered Data in Restricted Transactions.

Conclusion

            Companies involved in many industries should consider whether the Final Rule requires adoption of new or revised data policies, including companies involved in cloud computing, e-commerce, education, healthcare, financial services, manufacturing, software design, and others. Please contact one of the Dorsey & Whitney attorneys below if you have questions about the Final Rule.

Summary of Bulk U.S. Sensitive Personal Data

 

Definition

“Bulk” Threshold (U.S. persons)

Biometric Identifiers

Physical characteristics that are measurable or behaviors used to recognize or verify the identity of an individual, including facial, voice, retina or iris, palm, fingerprints, gait, or keyboard usage data that are enrolled in a biometric system and the templates used to create such a system.

1,000

Geolocation

Real-time or historical data that identifies the physical location of an individual or a device with a precision of within 1,000 meters

1,000

Human Genomic

Nucleic acid sequences that are the entire set or a subset of genetic instructions found in human cells, including the result of an individual’s genetic test and genetic sequencing data.

100

Other Genetic Data (‘omic data)

Epigenomic, proteomic, or transcriptomoic data of individuals

1,000

Personal Financial

Data about an individual’s credit, charge, or debit card, or bank account, including purchases and payment history; data in a bank, credit, or other financial statement, including assets, liabilities, debts, or trades in a securities portfolio; or data in a credit report or in a consumer report.

10,000

Personal Health

Health information about past, present, or future physical or mental health or conditions of an individual; healthcare information about an individual or payment information about healthcare.

10,000

Personal Identifiers

Identifiers that in combination with any other listed identifier or other data is linked or linkable to sensitive personal data. This includes names linked to device identifiers, social security numbers, driver’s license or other government identification numbers, and many others. The definition excludes certain data (e.g., demographic data linked only to other demographic data).

100,000

 

Firm Highlights

News

Dorsey Partner Melissa Raphan Elected a Fellow of the College of Labor & Employment Lawyers

International law firm Dorsey & Whitney LLP is pleased to announce that Partner Melissa Raphan has been elected a Fellow of the College of Labor & Employment Lawyers (CLEL) as part of its 2026 class. “Melissa’s election to this prestigious fellowship comes as no surprise to those of us who have had the privilege of working with her,” says Peter Nelson, Dorsey’s Managing Partner.  “She is an exceptional employment lawyer, a trusted advisor, and a leader whose impact extends far beyond her matters. Clients rely on her deep knowledge, strategic counsel, and ability to navigate complex workplace disputes and sensitive employment matters with both confidence and compassion. She has helped shape our firm, strengthen our profession, and opened doors for countless others through her commitment to mentorship and diversity. We are incredibly proud of her accomplishments and delighted to see her receive this recognition.” CLEL is a nonprofit professional association that honors the nation’s leading attorneys in the field of labor and employment law. Originally established to recognize excellence in the profession, CLEL has evolved into a respected intellectual and practical resource for the legal community and its many audiences. Its mission centers on recognizing individuals who have made significant contributions to the field, fostering the exchange of knowledge and delivering value to academia, government, the judiciary, and the broader public. Election as a fellow represents the highest level of peer acknowledgment, reflecting sustained achievement, integrity, and a commitment to advancing the profession. Melissa’s career reflects CLEL’s mission. She has been recognized both regionally and nationally for her advocacy, leadership, and achievements both inside and outside of the courtroom. Her employment litigation experience spans class actions, collective actions, and high-stakes individual disputes in state and federal courts, as well as arbitration forums including the American Arbitration Association and the Financial Industry Regulatory Authority (FINRA). She is also a trusted advisor on a full range of workplace issues, from hiring and performance management to sensitive terminations and organizational change. She brings decades of experience representing clients across the financial services, healthcare, food and agriculture, and energy sectors. Melissa will be formally inducted during CLEL’s installation ceremony held in conjunction with the American Bar Association’s Labor & Employment Law Conference in Washington, D.C., on November 7.

Insights

State Affordability Infrastructure Districts (SAIDs) — A Financing Tool for Taiwanese Investment in Arizona Science and Technology Parks

If you have developed a facility inside one of Taiwan's science or technology parks, you are accustomed to the one-stop-shop of government planning the park and delivering the roads, water, power, and other infrastructure before your building is even constructed. In the United States, including Arizona, land development generally does not work that way. In Arizona, the cost of infrastructure such as water, sewer, stormwater, roads, power, and the digital backbone, typically falls on the private landowner and is incurred up front before operations generate revenue to offset that cost. For a company entering the Arizona market, this is often the largest and earliest capital burden of the entire project. Arizona recently created a tool that provides a more cost-effective way for landowners and developer to finance some of that infrastructure. House Bill 2999, signed into law June 2026 and codified at Chapter 40 of Title 48 of the Arizona Revised Statutes, establishes the creation of a State Affordability Infrastructure District (SAID). How a SAID Works Landowners are now able to use a SAID to finance public infrastructure such as water, sewer, stormwater, roads, parking, lighting, communications, rail sidings and signalization, and similar improvements, through tax-exempt bonds. The bonds are repaid over up to 30 years and secured solely by the property within the SAID. No city, county, or state credit is pledged, and no obligation falls on other taxpayers, and therefore no city, county, or state approval other than from the Arizona Finance Authority (AFA). In effect, a SAID lets you spread the cost of horizontal infrastructure over the life of the asset instead of funding it entirely at the outset. And tax-exempt bonds often offer a lower interest rate than taxable or other types of financing. How a SAID is Formed A SAID is formed upon the filing of a petition with the AFA. The petition must include the finance plan, general plan, estimated costs, maximum tax rate, appraisal, bond counsel certificate, consultant list, petitioner experience, legal description, title report, and other materials. While the landowner is required to provide notice to the local governing jurisdiction, local governing jurisdiction does not have the right to approve or deny. The petition is reviewed administratively by the AFA through a standards-based process. For an inbound investor without long-standing local relationships, an objective, criteria-driven process is a meaningful advantage to the overt political process associated with other financing districts in Arizona. Formation requirements. A SAID requires consent from 100% of landowners within the proposed district; public infrastructure costs must exceed $5 million (easily met at any real scale); the district property must all be in the same county and need not be contiguous provided that noncontiguous property is located within five miles of the district's other property; and the board is initially appointed by the forming owners of the SAID district, later transitioning to election as ownership diversifies. Actual bond issuance requires an election of the SAID property owners. Ownership and corporate structure. Consent rights and board seats run with title. If you hold the Arizona land through a U.S. blocker beneath your Taiwan parent, the standard model for Taiwanese/Arizona real estate and operating investment, the U.S. property-holding entity, rather than it’s corporate parent, is the landowner of record for the district. Before formation, our Dorsey team will confirm that you have the proper corporate structure and board mechanics to be compliant.  Board composition has no citizenship or residency requirement. This is a common concern for foreign investors, and the statute answers it cleanly. Under A.R.S. § 48-7004, a director must either hold fee title to real property in the district or be an individual designated or appointed by a fee-title owner. Corporations, partnerships, and other business entities are expressly permitted to be those owners, to vote as owners, and to designate an individual to serve. There is no requirement that a director be a U.S. citizen or resident. So your U.S. property-holding entity, as landowner of record, can appoint whichever of your principals you choose, including a Taiwan-based individual, as the three-member board.  Power infrastructure limitation. The enacted definition of "public infrastructure" in A.R.S. § 48-7001 does not include electrical power generation or transmission. The reference to electrical facilities appears only as components of lighting and traffic-control systems, and the Legislature removed broader energy infrastructure from the definition during the Senate amendments. A SAID will likely not finance the high-load power infrastructure required for semiconductor fabrication, data storage, or heavy manufacturing.  Water infrastructure within a current utility CC&N. Where water, sewer, or wastewater facilities fall within a regulated utility's certificated service territory, the SAID cannot build or own them without the utility's written consent and must convey them to the utility on completion. Entitlements and zoning: The determination of entitlements, zoning, and other land use permitting, as well as construction permitting for a technology or manufacturing facilities remain with the local jurisdiction and run on a separate track. Our Dorsey team will help you coordinate the financing and entitlement timelines together. Our Dorsey team works regularly with Taiwanese and other Asia-Pacific companies entering the Arizona market. If a SAID fits your project, we can structure it for your cross-border ownership.

Insights

Proposed CMS Rule Ramps Up Potential Medicare Fraud Administrative Remedies

On July 6, 2026, the Centers for Medicare & Medicaid Services (“CMS”) proposed a rule that would expand its administrative remedies to combat potential fraud. The proposed rule is the latest in a round of administrative actions that signal CMS’s intent to aggressively pursue allegations of Medicare and Medicaid fraud and heighten the risk of fraud enforcement against even well-intentioned Medicare and Medicaid providers and suppliers. The proposed rule includes several changes to regulations that govern Medicare billing privileges. Providers and suppliers should be aware that these changes dramatically expand the flexibility afforded to CMS in enrollment and revocation actions, potentially leading to harsh consequences for ministerial and administrative errors. If finalized, moreover, the proposed rule could have material implications for providers and suppliers facing threatened revocation, including heightened risk of overpayment liability and increased hurdles to challenging revocations and denials of enrollment. Added Flexibility to Existing Revocation Grounds CMS has proposed to remove a number of factors that the regulations list as relevant to a determination of whether a provider has engaged in “abuse of billing privileges.” While acknowledging that the inclusion of these factors in the regulations was permissive (requiring consideration only where “as appropriate or applicable”), CMS stated that it must be afforded “the maximum flexibility to address all possible . . . scenarios without the rigid constraints of our existing factors.” CMS provided little guidance as to the outer bounds of what conduct could constitute an “abuse of privileges” that merits revocation of Medicare billing privileges. Instead, CMS noted that a “pattern of practice” of abuse of billing privileges might be established “by a simple finding that several of a provider’s claims do not meet Medicare requirements.” Similarly, CMS has proposed to expand the regulatory provision that permits revocation of enrollment if a provider certifies as “true” false or misleading information in Medicare enrollment application or renewal forms to include any scenario in which a provider submits “false or misleading information on or associated with any CMS Medicare enrollment-related form,” including materials submitted to Medicare contractors. CMS stated that it interprets this expanded rule to include anything related to Medicare enrollment, and not only those submissions that are “intended to gain or maintain Medicare enrollment.” If finalized, the proposed rule would add significant flexibility to CMS’s ability to pursue revocation of a provider’s enrollment. While CMS has assured providers that it would “invoke [the revised regulations]. . . only when legitimately warranted under the facts and circumstances and not as a matter of course,” such expanded flexibility threatens unpredictability in the event of even administrative or ministerial errors in submissions and claims. These changes would, moreover, make it more difficult for providers to challenge a revocation action. Expanded Revocation Grounds In addition to adding flexibility to existing grounds for revocation, CMS’s proposed rule adds to and expands CMS’s already broad authority to revoke provider and supplier enrollment. Such proposed changes include adding the following grounds for revocation: Denial of Enrollment Application. Where CMS could previously revoke a provider’s other enrollments if one enrollment is revoked, CMS would also be able to revoke a provider’s existing enrollments if an application for enrollment submitted by the provider is denied. High-Risk Enrollments. CMS would be able to revoke enrollment if it determines the provider or supplier (including owning/managing employees or organizations) poses a high risk of fraud, waste, or abuse due to “. . . an affiliation under [42 C.F.R.] § 424.519” or “the provider’s or supplier’s location within a limited geographic area that has an excessive number of providers and suppliers.” Certain Misdemeanor Convictions. CMS would be able to revoke enrollment if a provider or supplier—or its owners, managing employees, managing organizations, officers, or directors—are convicted of a “misdemeanor related to sexual assault or financial misconduct within the past 10 years that CMS deems detrimental to the best interests of the Medicare program and its beneficiaries.” Ownership Changes (HHA, Hospice, DMEPOS). CMS would have broad authority to revoke enrollment of home health agencies, hospices, and DMEPOS suppliers who do not comply with the regulations governing provider changes of ownership. These proposed, expanded grounds for revocation are notably broad, and CMS provides only limited guidance as to what conduct might result in revocation under these grounds. As with the proposed expansion of existing grounds for revocation, the open-ended nature of these proposed grounds for revocation may make it more difficult for providers and suppliers to challenge revocation actions. Expanded Grounds to Deny Medicare Enrollment As with revocations, CMS proposes to expand the grounds under which a provider’s application to enroll in Medicare can be denied. These expanded and additional grounds include many of the grounds added for revocations, but also include: Medicare Debt or Payment Suspension. CMS proposes expanding the ground to deny enrollment based on Medicare debt or payment suspension to include a provider or supplier’s “managing employee, managing organization, or individual or entity with any other form of business or financial relationship with the provider or supplier[.]” Significantly, this expansive definition (called an “associated party” under the proposed regulation) currently contains no material limitations, meaning almost any person or entity with whom an applicant does business could create denial liability. Sharing Locations with Denied/Revoked Providers or Suppliers. CMS would have authority to deny applications where a “provider’s or supplier’s practice location is in the same suite or office as another provider or supplier whose Medicare enrollment has been revoked or denied.” Hospices with Distant Medical Directors or Administrators. CMS would have discretion to deny hospice applications if the hospice’s medical director or administrator serves “multiple other hospices” or practices/is located “at such a distance (for example, in a different state) from the enrolling hospice that the medical director cannot realistically perform all medical director functions,” with a similar provision for administrators. In addition, CMS proposes applications denied for “other program termination or suspension,” may be applied to the provider or supplier in its own name or NPI or that of its owners, managing employees, or managing organization regardless of whether any appeals are pending. Retroactive Revocation CMS proposed to restructure and expand the regulatory grounds for retroactive revocation of billing privileges. Currently, Medicare regulations provide that revocations are, by default, prospective in nature: effective 30 days after CMS or the CMS contractor mails notice to the provider. Under certain circumstances, the regulations provide for revocations to be retroactive, such as when a provider is convicted of a felony, the date a professional license is suspended, revoked, or surrendered, or when a provider submits a false certification in their enrollment application. CMS has proposed to reframe the rule so as to default to retroactive revocation of billing privileges. CMS expressed concern that providers may collect payment from Medicare while remaining so non-compliant with enrollment requirements as to merit revocation. To address this concern, CMS proposed that all revocations be retroactive to the date of determined non-compliance.[1] As a result, providers suspected of misconduct or non-compliance are likely to face claims of retroactive overpayments in addition to the immediate concern no longer receiving Medicare payments while their enrollment is revoked. Reapplication Bar CMS’s proposed rule expands the grounds from which a provider may be prohibited from seeking reapplication as a Medicare provider. Under current regulations, CMS may prohibit prospective providers from enrolling in Medicare for up to 10 years if its enrollment application is denied because the applicant submitted false or misleading information in its application. Under the proposed rule, CMS will have the discretion to prohibit a provider from enrolling in Medicare if their enrollment application is denied for any reason. Conclusion As a part of the federal government’s increasingly aggressive push to combat real or perceived healthcare fraud, the proposed rule both broadens CMS’s authority to revoke and deny Medicare enrollment and raises the stakes for revocation and denial. What the proposed rule does not share is how CMS plans to exercise this expanded discretion: as a result, the proposed rule, if enacted, increases the unpredictability and potential ramifications of even technical noncompliance with CMS rules. As a result, Medicare providers should keep a close eye on potential revisions to these rules and their potential implementation and consider proactively evaluating their compliance under CMS standards. [1] In the proposed rule, CMS identifies, with respect to each ground for revocation, what it will consider to be the effective date of revocation.

Insights

Litigation Privilege Does Not Automatically Protect Communications with Funders: The Commercial Court Clarifies the Limits of Privilege in the Context of Litigation Funding

In Uber London Ltd & Ors v Garry White & Ors; Mishcon de Reya LLP [2026] EWHC 1610 (Comm), the Commercial Court held that documents created to help a funder decide whether to invest in a claim will not ordinarily attract litigation privilege. This means that information a firm gathers while acting for a funder can later fall within the control of the claimants it goes on to represent in the same matter. Background The Claimants (a claim group of over 10,000 individual London black cab drivers and the assignee of two former minicab operators) alleged that the Defendants (three companies in the Uber group) obtained and retained their private hire operator's licence through an unlawful means conspiracy alleged to involve fraud. Because the claims were issued outside the ordinary six-year limitation period, the Claimants relied on section 32 of the Limitation Act 1980, contending they could not, with reasonable diligence, have discovered the fraud before June 2018. A preliminary issue trial was listed to determine the question of whether the Claimants discovered, or could have discovered with reasonable diligence, the alleged fraud and/or deliberate concealment only after June 2018. The Claimants were represented by Mishcon de Reya ("MdR"). However, before MdR’s engagement with the individual drivers had begun, in late 2017 it was engaged by the litigation funder Harbour to investigate the merits and value of the potential claim. During that stage, MdR corresponded extensively with Harbour and with the Licensed Taxi Drivers' Association ("LTDA"), a black cab drivers' trade association. MdR was not formally engaged by the Claimants until October 2018 onwards. Once the proceedings had started, the Defendants sought disclosure of communications exchanged between MdR and Harbour before the engagement of MdR by the Claimants (the "Harbour Communications"). This included correspondence between MdR and Harbour, communications with the LTDA, and documents held on MdR's file opened in Harbour's name in connection with the potential claim. The Claimants resisted disclosure on four grounds: (i) that the documents were not relevant; (ii) on the grounds of litigation privilege; (iii) that the documents were outside their control; and (iv) that disclosure occurring so close to trial would be disproportionate. Judgment (i) Were the Harbour Communications relevant to the preliminary issue? The Court held that the Harbour Communications were likely to contain relevant material, on two bases. First, where the Claimants or the LTDA had communicated directly with MdR, that material could shed light on individual Claimants' actual knowledge of the alleged facts. Secondly, what MdR and Harbour had discovered during their investigation could inform the question of what a Claimant could reasonably have discovered at the time (even though the Defendants accepted that MdR's knowledge could not simply be imputed to the Claimants). (ii) Were the Harbour Communications protected by litigation privilege? As set out in the classic cases of Three Rivers (No. 6) [2005] 1 AC 610 and WH Holding Ltd v E20 Stadium LLP [2018] EWCA Civ 2652, communications between parties or their solicitors and third parties for the purpose of obtaining information or advice in connection with existing or contemplated litigation are privileged when the following conditions are satisfied: Litigation must be in progress or in reasonable contemplation. The communications must have been made for the sole or dominant purpose of conducting litigation. The litigation must be adversarial, not investigative or inquisitorial. The Court rejected the Claimant’s claim to be able to withhold the Harbour Communications on the basis of litigation privilege. The Court confirmed that litigation privilege protects only communications created for the dominant purpose of conducting litigation. The Court found that Harbour had instructed MdR so that Harbour could decide whether to fund the proceedings. As such, the dominant purpose of the communications was in relation to funding, not the conduct of litigation. This was distinguished from the situation where an individual litigant who takes its own funding decision. In that situation, the decision whether to fund and the decision whether to litigate are one and the same, made by the person who will actually be the claimant, and so it forms a part of that person's conduct of their own litigation. In contrast, a third-party funder's commercial decision whether to fund someone else's claim is not necessarily part of conducting that litigation. The fact that litigation privilege can, in principle, be claimed by a non-party funder (as recognised in the case of Al Sadeq v Dechert [2024] EWCA 28) did not assist Harbour, since there was no evidence it intended to play any role in the litigation itself beyond funding it. Communications between Harbour and MdR did remain capable of attracting another kind of privilege: legal advice privilege, because of the solicitor-client relationship between Harbour and MdR. But communications with third parties such as the LTDA were not automatically protected in the same way. (iii) Were the Harbour Communications within the Claimants' control? The Court also rejected the argument that the Harbour Communications sat outside the Claimants' control because they belonged to Harbour and not the Claimants. The Court’s reasoning was that once the individual Claimant drivers became MdR's clients, MdR also owed them a duty to disclose material information. That included information that MdR had originally acquired while acting for Harbour. As held in the case of Hilton v Barker Booth & Eastwood (a firm) [2005] 1 WLR 567, a solicitor owing duties to two clients cannot simply prefer one over the other, and it was unrealistic to suppose MdR would investigate the same claims for Harbour, then represent the Claimants, while disregarding everything it had already learned. The obvious commercial expectation was that this earlier work would be used to advance the Claimants' case. MdR sought to rely on a confidentiality clause in a 2024 retainer agreement between it and RGL Management Ltd (a claims management company acting on behalf of the Claimants) to argue that it was relieved of any duty to disclose information obtained while acting for other clients. The provision stated that MdR may "have acted for persons in the same or similar sector as yours and by agreeing to the terms of this letter you agree that will have no duty to disclose to you any confidential information that we have obtained, or might in the future obtain, from acting for such persons or which is derived from any other source". The Court rejected this on several grounds. Claimants who had already become MdR's clients had an existing right to information in the Harbour Communications where it was relevant to their claims before the 2024 retainer agreement. If they were to surrender that right, it would have required their informed consent (also required under the SRA Code of Conduct). The Court found no evidence that such informed consent had been given. The terms had simply been made available to the Claimants through a portal, with no indication that Claimants understood they were giving up existing rights to relevant information. The Court found that even if the terms had been contractually binding, that would not have amounted to informed consent. In addition, the wording of the clause was not sufficiently clear to show that the Claimants had agreed to waive access to this information. (iv) Was disclosure reasonable, proportionate, and necessary at this stage? The Claimants argued that it was neither reasonable nor proportionate for disclosure to be given at such a late stage (approximately two weeks before the start of the preliminary issue trial) and that it was not necessary for the just disposal of the proceedings. The Court rejected this, but it drew a distinction between two categories of documents within the Harbour Communications: Documents bearing on the actual knowledge of the individual drivers, including communications with the LTDA, were not privileged, likely straightforward to review, and directly relevant to the preliminary issue. Their disclosure was ordered as reasonable, proportionate, and necessary. Documents reflecting only MdR's or Harbour's own assessment of the merits were of more marginal, indirect relevance and largely likely to fall under legal advice privilege. A review to isolate the smaller pool of non-privileged material in this category would be time-consuming for limited benefit, so this was excluded from the order. Key Points to Note The judgment is an important reminder of several practical points: However closely a funder is involved in evaluating a claim's merits, litigation privilege will only apply to communications where the sole or dominant purpose of the communication is the conduct of litigation, not the funder's own decision on whether to finance it. Unless that communication separately attracts legal advice privilege, it may need to be disclosed. The same considerations apply to other communications. For example, in RBS Rights Litigation [2017] 1 WLR 3539 the argument that an After the Event (ATE) policy was subject to litigation privilege was rejected on a similar basis. Whilst in this case, there was no dispute as to whether litigation was in contemplation, it is important to note that litigation privilege will not automatically apply to the investigative stages of a claim, i.e. before litigation is in contemplation. Even where litigation is reasonably contemplated, the dominant purpose test must still be satisfied. Material created primarily for fact-finding, risk assessment, or other investigative purposes will not attract litigation privilege unless those activities are actually undertaken for the dominant purpose of conducting the litigation. (See The Director of the Serious Fraud Office v Eurasian Natural Resources Corporation Ltd [2017] EWHC 1017 (QB)). When engaging a law firm, clients should ensure that they understand whether the firm has previously obtained information about their claim while acting for another party (for example, a funder or another interested party) and how that information will be handled. Any restrictions on the firm’s ability to share relevant information with the client should be explained clearly at the outset, including what information may be withheld and why. If this decision raises questions about your own funding arrangements, disclosure strategy, or privilege position, please get in touch with our Commercial Litigation team.

News

37 Dorsey Attorneys Named 2026 Top Lawyers by Minnesota Monthly

Minnesota Monthly has recognized 37 Dorsey attorneys across 27 practice areas as 2026 Top Lawyers in Minnesota. Honorees are selected through a peer nomination process and a curated survey of practicing attorneys in Minnesota, who identify leading lawyers across a range of practice areas. Administrative / Regulatory Law Jennifer Coates Antitrust Law Michael Lindsay Banking & Financial Service Law Peter Nelson Copyright Law  Jeffrey Cadwell Corporate Law  Robert Hensley Robert Rosenbaum Criminal Defense: White-Collar  Beth Forsythe Edward Magarian RJ Zayed Health Care Law  Claire Topp Immigration Law  J. Mike Sevilla Insurance Law  Daniel Brown Intellectual Property and Patent Law  Stuart Hemphill International Trade Law  Jonathan Van Horn Labor and Employment Law  Edward Magarian Ryan Mick Melissa Raphan Land Use & Zoning  Jay Lindgren Marcus Mollison Litigation – Antitrust  Michael Lindsay F. Matthew Ralph Jaime Stilson Litigation – Commercial  Michael Lindsay Litigation – Construction  Eric Ruzicka Litigation – Intellectual Property  Peter Lancaster RJ Zayed Litigation – Labor Employment Benefits  Ryan Mick Melissa Raphan Litigation – Trusts and Estates  William J. Berens Theresa Bevilacqua Bridget Logstrom Koci Mass Tort Litigation / Class Actions  James K. Langdon Mergers & Acquisitions Law  Keith Ahlgren Rachel Benedict Brian Burke Morgan Helme John Jorgenson Brian Moore Robert Rosenbaum Jonathan Van Horn Bri Whiting Municipal Law Jay Lindgren Nonprofit/Charities Law Claire Topp Securities / Capital Markets Law Cam Hoang Robert Rosenbaum Securities Regulation Theresa Bevilacqua James K. Langdon Tax Law William J. Berens Trusts and Estates Jennifer Ede Bridget Logstrom Koci Sonny Miller Kiley Petty Henry

News

Real Estate Attorney Alexis Olsen Joins Dorsey in Phoenix

Attorney Alexis Olsen has joined Dorsey & Whitney LLP as Of Counsel in the Real Estate group in Phoenix, the law firm announced today. Alexis focuses her practice on large-scale residential, mixed-use, and multi-asset development projects as well as multi-state commercial leasing transactions. She guides clients through sophisticated acquisitions, dispositions, leasing, entity structuring, investment strategies, and due diligence matters. She has structured co-investment arrangements that drive capital deployment into housing subdivisions nationwide and has represented both landlords and tenants in commercial leasing transactions involving office, retail, industrial, and specialty-use properties, including cannabis dispensaries. Alexis received her J.D. from Sandra Day O’Connor College of Law and her B.A. from the University of Arizona. Alexis comes to Dorsey from Squire Patton Boggs. “Alexis strengthens Dorsey’s real estate capabilities at a time when Phoenix remains one of the fastest-growing and most dynamic real estate markets in the country,” said Scott Jenkins, Dorsey’s Phoenix office head. “Her addition further enhances our deep bench of 12 real estate attorneys in Phoenix and reflects our continued investment in serving clients throughout Arizona and supporting their real estate transactions and objectives across the country. We are thrilled to welcome Alexis to Dorsey.” “Joining a firm with such a deep bench of experienced attorneys in the Phoenix office, especially in the Real Estate group, presents an exciting opportunity not just for my own professional growth, but for the clients we service,” said Alexis Olsen. “I look forward to building on this strong foundation, growing our national practice, and delivering top-tier service to our clients.”

Insights

Alaska HB 126: What Changes for Alaska Native Corporations, Proxy Filings, and Annual Reports

Alaska House Bill 126 (HB 126), sponsored by Representative Neal Foster and passed by the 34th Alaska Legislature, is now law. The bill changes which Alaska Native Corporations (ANCs) must file proxy and annual report materials with the State of Alaska, and makes it easier to reinstate certain dissolved Village Corporations. For many smaller Village Corporations, the practical result is less public disclosure. For shareholders, advisors, and the public, it means some financial information that used to be available through the State will no longer be readily obtained. This eUpdate explains what HB 126 does in plain terms, walks through the practical trade-offs, and answers common questions. 1. What HB 126 Changes The old rule Under prior law (Alaska Statutes Sec. 45.55.139), an Alaska Native Corporation had to file its annual report, proxies, and proxy statements with the Alaska Division of Banking and Securities (the Division) if it had more than $1 million in assets and 500 or more shareholders on its current rolls. A filing ANC was also required to follow the Division’s proxy rules (3 AAC 08.305 through .365), which require specific disclosures such as top 5 executive compensation, and related-party transactions. Because these filings are treated as public records, they gave non-shareholders, including the public and the press, visibility into ANC financial information that is not filed with the SEC. The new rule HB 126 changes how the 500-shareholder test is measured. Now, the asset test is removed, and the shareholder count is based on how many shareholders the corporation originally enrolled when it was formed under the Alaska Native Claims Settlement Act (ANCSA), not how many it has today. As shares have passed down through families over the decades, some Village Corporations that started with fewer than 500 shareholders now have more than 500 recordholders. Under the old current-count test, when those corporations had crossed the threshold, they had to file. Under the new original-enrollment test, they do not. Who is affected Village Corporations that originally enrolled fewer than 500 shareholders are the main beneficiaries. They no longer have to file proxy and annual report materials with the Division or follow the Division’s proxy regulations at 3 AAC 08.305 through .365. Two groups must continue to file as before: all twelve ANCSA Regional Corporations, each of which enrolled more than 500 shareholders at creation, and all Village Corporations that originally enrolled 500 or more shareholders. As reported by the Alaska Beacon, when the bill was under consideration, the Division identified 59 corporations then filing, expected at least seven village corporations to become exempt, and was reviewing roughly 30 more. 2. Practical Analysis HB 126 reduces a real compliance burden for smaller Village Corporations, which now need not spend time and money on State filings. In coming years, the exempt Village Corporations may experience benefits associated with less public disclosure and less regulation. But at the same time, less public disclosure carries trade-offs. Benchmarking will become harder Publicly-filed proxy statements and annual reports have long served as a reference set. Shareholders, corporations, advisors, and counsel use them to compare governance practices, compensation, and financial results across similarly-situated ANCs. Since fewer of these materials will be filed publicly, there will be fewer comparable documents available, which will make benchmarking and market-checking more difficult for like-sized ANCs over time. Executive compensation transparency may be reduced The Division’s proxy rules require disclosure of the compensation of ANC’s top five most highly compensated individuals (3 AAC 08.345(b)(2)), related-party transactions above $20,000 (3 AAC 08.345(b)(3)), and audited financial statements and management’s discussion and analysis (3 AAC 08.365). When a corporation is no longer required to file these disclosures publicly, it becomes harder for shareholders and others to obtain the information, to understand how compensation is set for their corporate leadership, and how it compares across corporations of similar size and complexity. Transparency may matter more as ANCs grow Some ANCs have grown into large, complex enterprises with substantial revenue and many subsidiaries, even with fewer than 500 shareholders. For an ANC with a broad and dispersed shareholder base, public materials can be an important way for shareholders and other stakeholders to understand governance, compensation, and performance across ANCs. Reduced disclosure may carry more practical weight in those settings than for a small corporation whose shareholders are closely connected to the business. The ANCSA annual report obligation continues It is important not to overstate what HB 126 does. HB 126 changes the state filing proxy requirements. It does not remove the separate obligation under ANCSA itself. That obligation comes from ANCSA at 43 U.S.C. Sec. 1625(c), which requires a Native Corporation that would otherwise be subject to the Securities Exchange Act of 1934 to prepare and transmit to its shareholders an annual report containing substantially the information a company subject to that Act would include. Similarly, ANCs that solicit proxies for an annual meeting are still required to furnish shareholders with those proxy materials under general Alaska corporate law. However, ANCs are now no longer required to transmit proxy statements to the State. ANCs’ reporting obligations to their shareholders are unaffected by HB 126. Any corporation newly exempt from state filing still owes its shareholders a detailed annual report and a proxy statement, even though that report is no longer routed through the State and made public. Reinstatement of dissolved Village Corporations Separately, HB 126 amends AS 10.06.960(k) to remove the prior deadline (previously December 31, 2020) for reinstating an involuntarily dissolved Native Village Corporation. A dissolved Village Corporation may now apply to be reinstated under AS 10.06.633(e) at any time. Reinstatement still runs through the commissioner under AS 10.06.633(e). In general, that means the ANC must apply, cure the neglect or delinquency that led to dissolution, and pay the amounts owed, and the corporation’s name must be available or be changed to one that is. Once reinstated, the corporation and its shareholders are restored to the rights, privileges, liabilities, and obligations they would have had as if the dissolution had never occurred, and corporate and shareholder actions taken during the dissolution are treated as valid. If the previously-used corporate name is no longer available, the board alone may amend the articles to adopt a new name (without the necessity for shareholder approval). 3. Frequently Asked Questions What does HB 126 do? It changes how Alaska measures the 500-shareholder test that decides which ANCs must file proxy and annual report materials with the state. It removes the asset test, and it counts shareholders based on original enrollment rather than the current rolls. It also removes the deadline for reinstating an involuntarily dissolved Native Village Corporation. Which ANCs are affected? Village Corporations that originally enrolled fewer than 500 shareholders, because they may no longer need to file with the Division. Regional Corporations and Village Corporations that originally enrolled 500 or more shareholders must continue to file as before. Does HB 126 eliminate all reporting obligations? No. It changes the state filing requirement under AS 45.55.139, but it does not remove the separate ANCSA obligation (43 U.S.C. Sec. 1625(c)) to provide shareholders with an annual report, and general corporate law still calls for a proxy statement when the ANC solicits proxies. Corporations that remain subject to state filing requirements must also continue to comply with the Division's rules. We think we are now exempt. What should our ANC board and management consider? Confirm your ANC’s original enrollment number and whether your corporation falls below the new threshold. Watch for communications from the State on this topic as they proceed with their research. If your ANC is now exempt, decide how your corporation will meet its continuing ANCSA obligation to shareholders, review proxy and annual meeting materials and timelines, and consider what to communicate to shareholders about any change in how they will receive information. It is worth documenting the basis for any exemption. What should ANC shareholders watch for? Shareholders should watch for how and when they will continue to receive annual report and proxy statement information directly from their ANC, since some material that used to be available through the State’s online website will no longer be publicly filed. If something is unclear, shareholders can ask their ANC how it intends to meet its ANCSA reporting obligations. How Dorsey Can Help HB 126 lightens the State filing load for smaller Village Corporations, but it also raises practical questions: confirming who is exempt, meeting continuing ANCSA obligations to shareholders, keeping proxy and annual meeting processes on track, and maintaining benchmarking when public materials become less available. These are exactly the kinds of judgment calls that benefit from early planning. Dorsey’s attorneys work closely with Alaska Native Corporations and related stakeholders. If you have questions about HB 126, ANC governance, proxy filings, annual reports, disclosure obligations, or shareholder communications, please contact your Dorsey attorney, including the authors of this eUpdate.

Insights

The Long-Awaited Public Infrastructure Financing Solution for Development in Arizona

Every developer who has taken raw Arizona ground to a finished project knows the largest upfront cost other than the land price is almost always the cost to install the public infrastructure. Water, sewer, stormwater, streets, dry utilities, and the fiber backbone all have to be in the ground before a single lot closes or a building opens. That capital is deployed early and generates no return for years. For decades the standard workaround has been the Community Facilities District (CFD). That tool has grown materially harder to use, for reasons cited below, and House Bill 2999, signed in June 2026 and now codified as Chapter 40 of Title 48, is Arizona's response. Some Background I have spent a good part of my career on the other side of this problem. In the 1990s and early 2000s I served as general counsel of SunCor Development Company, one of Arizona's most active master-planned community developers, where we used Community Facilities Districts to finance hundreds of millions of dollars of major infrastructure across Arizona in cities such as Goodyear, Phoenix, Tempe, Litchfield Park, and Prescott Valley. For its time the CFD was an effective structure, and a great deal of what is now on the ground in those communities was financed with this tool. Unfortunately, CFDs have over time become considerably harder to use. Successive legislative amendments have layered on tax-rate ceilings, homebuyer disclosure obligations, and added procedural steps. Another drag on the use of CFDs is that formation of them runs through the municipality, where approval can turn as much on local politics as on the merits of a project. Developers now routinely are asked to absorb delay and uncertainty that a project's economics cannot support, which is a large part of why Arizona has fallen behind Colorado, Texas, and Utah in getting infrastructure financed. A better tool was needed, and Chapter 40 is it. How a SAID Improves on a CFD A State Affordability Infrastructure District (SAID) keeps what worked about the CFD: tax-exempt, property-secured, non-recourse infrastructure financing — while shedding much of what made the CFD cumbersome. Its principal advantages over a traditional CFD: Administrative formation. A SAID is formed by the Arizona Finance Authority against fixed statutory criteria, through a yes-or-no compliance review on a sixty-day clock, rather than through the discretionary approval of a city council or a board of supervisors. Insulation from municipal politics. Because formation is a state-level compliance determination, a meritorious project is far less exposed to local political headwinds than it is under the CFD process. Landowner control of the board. A SAID is governed by a board of the landowners — appointed at formation, then elected on an acreage basis. In a typical municipal CFD, the city council sits as the district board; here, the developer controls governance. Advance funding of impact fees. A SAID can use bond proceeds to advance-pay municipal development impact fees, unlike CFDs, removing one of the largest upfront cash burdens in a project. A uniform, statewide process. The criteria are the same regardless of jurisdiction, replacing the municipality-by-municipality variation that has made CFD outcomes hard to predict. Flexible boundaries. A district may include noncontiguous parcels in the same county within five miles of one another, which fits phased and multi-tract development. Capped cost and a fixed timeline. Authority fees to form a district are capped at $15,000, and a complete petition must be acted on within sixty days. The full range of bonds. A SAID may issue general obligation, special assessment, revenue, and refunding bonds, secured solely by district property and creating no obligation for any other taxpayer. What is a SAID A SAID is a special taxing district that the owners of a development form to finance public infrastructure with tax-exempt bonds: general obligation bonds, special assessment bonds, and revenue bonds. The bonds are secured only by the property inside the district and are repaid over the long term, with terms up to 30 years. They do not affect the credit of the city, the county, or the State, and they create no obligation for any taxpayer outside the district. In practical terms, a SAID lets you finance horizontal infrastructure over the life of the asset instead of writing the check at the front end. The maximum ad valorem rate securing general obligation bonds is capped by statute at $5.00 per $100 of net assessed limited property valuation, with a limited step-up to cover a debt-service shortfall. SAIDs Work for Commercial as Well as Residential Development The SAID bill drew most of its press as a housing-affordability measure, and it appears to be a strong one. It is the first Arizona district statute to let bond proceeds advance-fund municipal development impact fees, which pulls one of the largest upfront cash burdens off a homebuilder's pro forma. But the statute's eligible infrastructure categories apply with equal force to commercial, industrial, and mixed-use projects. An industrial or logistics project can finance roads, rail crossings, sidings, and grade separations. A life-sciences or technology campus can finance its water, sewer, roads, and broadband the same way a subdivision can. Read Chapter 40 as a general-purpose infrastructure finance platform, not a subdivision-only device. How Formation Works A SAID is formed administratively by the Arizona Finance Authority. The Authority reviews the petition for compliance with the statute; it is a yes-or-no review against fixed criteria, not a discretionary negotiation with a city council or a board of supervisors, and it runs on a sixty-day clock once a complete petition is filed. Formation requires the written consent of 100% of the landowners in the proposed district and an engineer's certification that public infrastructure costs will exceed $5 million. The district may include noncontiguous parcels so long as they lie in the same county and within five miles of the district's other property, which accommodates phased and multi-tract development; if any part of the district sits inside a municipality, the whole district must stay within that municipality's limits or planning area. The Authority's fees to form a district are capped at $15,000. Issuing bonds requires a district election. Governance Simplified A SAID is run by a three-member board. The initial directors are named in the petition; after that, directors are elected by the landowners on an acreage basis as ownership diversifies. Board service runs with ownership; a director must either hold fee title inside the district or be an individual designated by a fee-title owner; and corporations, partnerships, and other entities may hold that ownership, vote as owners, and designate the individual who serves. A district has no power of eminent domain and no zoning authority, and directors may not be officials or employees of the municipality in which the district sits. What a SAID Does Not Do It finances; it does not entitle. Zoning, platting, rezonings, use permits, and the specialized approvals a manufacturing or life-sciences facility may need all remain with the local jurisdiction and proceed on their own track. The financing and entitlement timelines should be coordinated with formation of the SAID, but they are separate processes. Two substantive limits are worth flagging at the planning stage. First, electric power is largely outside the tool: the statutory definition of public infrastructure does not reach power generation or transmission, and broader energy infrastructure was removed from the bill during the Senate amendments. A power-intensive user should not assume a SAID will carry its electrical load. Second, where water, sewer, or wastewater facilities fall within a regulated utility's certificated service territory, the district cannot build or own them without the utility's written consent and must convey them to the utility upon completion. Our Take For most master-planned residential work, and for a wide range of commercial and industrial development, a SAID will be the most efficient infrastructure-financing structure Arizona has offered. The right time to evaluate it is early in the acquisition and pre-development process, while the capital stack, the development agreement, and the entitlement strategy are still being set. Once the district's boundaries, general plan, and financing parameters are set, it is cumbersome at best to bring those into conformance later. Our Dorsey team has begun advising our developer clients on SAID formation on residential, commercial, and industrial projects statewide. If you would like us to assess whether a SAID fits a project you are working on, please reach out.

News

Patent Partners Al Araiza and Lena Petrovic Join Dorsey in Palo Alto

Patent partners Al Araiza and Lena Petrovic have joined Dorsey & Whitney LLP in Palo Alto, the international law firm announced today. Al Araiza works with clients to develop and implement patent strategies that align with corporate objectives, supporting growth initiatives, financing efforts, and successful exits, including initial public offerings and acquisitions. He advises on building, managing, and optimizing patent portfolios across a broad range of emerging and frontier technologies, with depth in wireless communications, artificial intelligence, and energy innovation. Before practicing law, Al gained engineering experience in the defense industry, working on energy system modeling and communications circuitry design. He also conducted biomedical research, with findings published in peer-reviewed journals. He has been recognized in the IAM Patent 1000 for his work advising clients on patent strategy and portfolio development. Al received his J.D. from Duke University School of Law, his M.E. in Biomedical Engineering from Tulane University, and his B.S. in Electrical Engineering from UCLA. Lena Petrovic works across the software and hardware industries to develop clear, well-supported patent applications. She guides clients through the prosecution process and advises on global trademark and copyright matters, including licensing and portfolio management. Lena regularly supports clients developing technologies such as artificial intelligence and machine learning, fintech, cryptography, interactive and immersive experiences, and digital media, and works with companies in entertainment, gaming, and sports. Before practicing law, Lena spent a decade at Pixar, where she contributed to major films including The Incredibles, Ratatouille, WALL‑E, and Brave. Lena received her J.D. from Santa Clara University School of Law, her M.S. in Computer Science from Princeton University, and her B.S. from California Institute of Technology. “Al and Lena bring a practical, technical, and business-focused approach informed by extensive experience working with technology companies, startups, and investors,” said Gina Cornelio, Patent Practice Group Co-Leader. “We are thrilled to welcome them to the Patent team and our growing Palo Alto office.” “Dorsey’s Patent practice is dedicated to understanding each client's business deeply, tailoring patent strategies that directly advance their goals,” said Al Araiza. “We are proud to join this outstanding team and look forward to driving success for our clients.”