As Dante warned in the Inferno, abandon all hope, ye who enter here. When the Committee on Foreign Investment in the United States (“CFIUS”) announced the Critical Technology Pilot Program (the “Pilot Program”),(1) many CFIUS practictioners expressed cautious optimism that the Pilot Program would offer a less complex, less burdensome, and less time-consuming alternative to the traditional joint voluntary notice (“JVN”) process. CFIUS has been accepting mandatory declarations under the Pilot Program for almost a month now.(2) As we quickly approach the end of the 30 calendar day review period for the mandatory declarations filed on November 10th, when the Pilot Program was launched, we thought it worth assessing what outcomes the parties to these mandatory declarations can expect from CFIUS and whether those outcomes are consistent with the initial hope some felt at the Pilot Program’s announcement. Below, we list the outcomes in the order we think they are likely to issue, from most common to least common, and discuss the implications of this ranking.
Outcome 1: CFIUS states it has insufficient information to issue a no-action letter, resulting in no safe harbor
Outcome 2: CFIUS requests the parties submit a traditional joint voluntary notice
Outcome 3: CFIUS issues a no-action letter and the parties have their safe harbor
Outcome 4: CFIUS unilaterally initiates an investigation into the notified transaction
We think that the most common outcome is that, at the end of the 30 calendar day review period, CFIUS will notify parties that it has insufficient information to issue a no-action letter. Without a no-action letter, the parties will not benefit from the legal certainty of the CFIUS safe harbor, the incentive to encourage parties to participate in the traditional, voluntary CFIUS process.
While this prediction may be initially disappointing, it is unfortunately not surprising given CFIUS’ resource constraints and its historically high case load, which will only get heavier due to the influx of mandatory declarations. In particular, we doubt the intelligence community will be able to complete a full threat assessment of declared transactions in the vast majority of instances. This, in turn, will likely impede CFIUS’ willingness to grant a safe harbor against future action.
To briefly discuss the other potential outcomes, our expectation is that any complication involved with a mandatory declaration, either from the acquirer or from the nature of the target’s business, will likely cause CFIUS to request a traditional JVN. Further, we expect CFIUS to only approve relatively benign mandatory declarations by acquiring parties that are already quite familiar to CFIUS (e.g., the acquiring party had successfully completed a CFIUS review recently).. Finally, we expect CFIUS to rarely need to initiate a unilateral review because a request to submit a traditional JVN under outcome #2 will likely be sufficient.
Because we think that the most common outcome for a given case will be that CFIUS declines to issue a no-action letter, parties to transactions covered by the Pilot Program will be confronted with a choice: whether to submit a mandatory declaration or a traditional JVN. When making this choice, parties should carefully assess a number of factors, including the total likely duration of the anticipated review and the relative burdens of preparing a mandatory declaration as compared to a traditional JVN. Most importantly, parties will need to determine whether they can accept an outcome that satisfies their legal obligations under the Pilot Program, but may not yield the legal certainty of a safe harbor at the end of the process. Regardless of how parties decide to proceed based on this choice, one thing is certain: the Pilot Program has made the CFIUS process more challenging to navigate, not less.
For further analysis of the trends which we are currently seeing in public interest and foreign investment, read our report Public interest or protectionism? Navigating the new normal (PDF).
(1) https://home.treasury.gov/news/press-releases/sm506
(2) https://home.treasury.gov/system/files/206/FR-2018-22182_1786904.pdf
