Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fl-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uabb domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 48

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 49

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 50

Deprecated: Function WP_Dependencies->add_data() was called with an argument that is deprecated since version 6.9.0! IE conditional comments are ignored by all supported browsers. in /home/bailey/public_html/wp-includes/functions.php on line 6131
Litigation Risks and Insurance Issues for SPAC Sponsors - Bailey Cavalieri

Litigation Risks and Insurance Issues for SPAC Sponsors

Over the past two years, special purpose acquisition companies (“SPACs”) have become a popular means of taking private companies public. SPACs accounted for 247 public listings in 2020 (52% of all initial public offerings (“IPOs”) for that year) and 613 in 2021 (59% of all IPOs that year).[i] While the SPAC craze has cooled somewhat in recent months, SPACs are likely to account for a significant number of public listings in 2022 as well.

As one would expect, the eruption in SPAC transactions over the last two years has given rise to a corresponding uptick in SPAC-related lawsuits. These include securities class actions, shareholder derivative lawsuits, and breach of fiduciary duty actions. SPACs have also been in the crosshairs of the SEC.

This article analyzes SPAC-related litigation and regulatory risks from the perspective of the private equity firms that increasingly sponsor SPACs, as well as the insurance coverage implications associated with such risks.

Read More

Authors
Elan Kandel
Member
James Talbert
Associate
Service Affiliation
Share
Scroll to Top