### WordPress - Web publishing software Copyright 2011-2019 by the contributors This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA This program incorporates work covered by the following copyright and permission notices: b2 is (c) 2001, 2002 Michel Valdrighi - m@tidakada.com - http://tidakada.com Wherever third party code has been used, credit has been given in the code's comments. b2 is released under the GPL and WordPress - Web publishing software Copyright 2003-2010 by the contributors WordPress is released under the GPL --- ### GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. ### Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. ### TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION **0.** This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. **1.** You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. **2.** You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: **a)** You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. **b)** You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. **c)** If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. **3.** You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: **a)** Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, **b)** Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, **c)** Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. **4.** You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. **5.** You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. **6.** Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. **7.** If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. **8.** If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. **9.** The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. **10.** If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. **NO WARRANTY** **11.** BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. **12.** IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ### END OF TERMS AND CONDITIONS ### How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. one line to give the program's name and an idea of what it does. Copyright (C) yyyy name of author This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands \`show w' and \`show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than \`show w' and \`show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the [GNU Lesser General Public License](http://www.gnu.org/licenses/lgpl.html) instead of this License. Transaction Satisfied “Entire Fairness,” Despite Serious Sale Process Flaws—BGC Partners - sinth.info

Transaction Satisfied “Entire Fairness,” Despite Serious Sale Process Flaws—BGC Partners

[ad_1]

In In re BGC Partners (Aug. 10, 2023), the Delaware Supreme Court, in an en banc decision, without commentary, affirmed the Court of Chancery’s post-trial decision (Aug. 19, 2022) holding that the acquisition of a company indirectly controlled by the buyer’s controller met the entire fairness standard—notably, notwithstanding the lower court’s finding that there were serious flaws in the sale process. BGC Partners follows two other decisions in recent years in which the Court of Chancery also has found entire fairness satisfied in conflicted-controller transactions despite serious flaws in the transaction process—Hsu Living Trust v. Oak Hill (2020) and ACP Master v. Sprint/Clearwater (2017). These decisions stand in contrast to the Delaware courts’ historic trend of virtually never finding, when the entire fairness standard applies, that it has been satisfied.

Key Points

  • There is now increased potential for a buyer to establish that a transaction meets the stringent “entire fairness” standard—even if the sale process was seriously flawed. BGC Partners furthers the court’s evolution toward an emphasis on the fairness of the price over the fairness of the process in the “unitary” entire fairness analysis. Notwithstanding this evolution, however, in our view, even after BGC Partners, in the event of a clearly materially unfair price or process, it would be unlikely that the court would find entire fairness satisfied.
  • There is still a high bar to establishing entire fairness—in each of the recent decisions, the court found that, although there were serious process flaws, there was strong evidence that the special committee and its advisors had functioned effectively and had achieved a fair price.
  • Buyers should consider taking certain steps to maximize the potential of a finding of entire fairness—see “Practice Points” below.

Discussion

Increased potential for a buyer to establish “entire fairness,” even of a transaction in which the sale process was seriously flawed. BGC Partners involved an acquiror and target that both were indirectly owned by the same controller. A special committee of the acquiror’s board, comprised of the four outside directors, approved the acquisition. Minority stockholders of the acquiror brought suit, alleging that the controller had presented the transaction as a “fait accompli” and had caused the acquiror to overpay because the controller owned a far larger stake in the target than in the acquiror. The court rejected the defendants’ motion to dismiss at the pleading stage; and also rejected a shift of the burden of proof to the plaintiffs given uncertainty about the independence of the special committee members. After trial, Vice Chancellor Lori Will found that there were serious process flaws—the controller having identified the financial advisors for the special committee, having asked the committee’s co-chairs to serve, and having engaged in “one-off” discussions about the transaction with a member of the committee. The Vice Chancellor concluded, however, that the transaction nonetheless met the entire fairness standard. The Vice Chancellor determined that the special committee members were independent, and emphasized that the committee had negotiated the price paid and that the price was within the range of fairness as determined by the committee’s financial advisor.

Historically, application of the entire fairness standard was outcome-determinative in favor of plaintiffs challenging a conflicted transaction. Entire fairness, which is Delaware’s most exacting standard of judicial review, is applicable to transactions involving a conflicted controller or conflicted board of directors (unless the MFW prerequisites for business judgment review were met). For a transaction to meet the entire fairness test, the court conducts a “unitary” analysis to determine if there was both a “fair price” and a “fair process.” As the standard requires intensive factual inquiries into both the economics of the transaction and the process leading to the transaction, a determination by the court at the pleading stage that entire fairness is the applicable standard has usually led to prompt settlement by the parties given the near impossibility of meeting the standard.

The court’s entire fairness jurisprudence has been evolving toward an emphasis on fairness of the price over fairness of the process. As the parameters for the entire fairness analysis have evolved in recent years, the Court of Chancery has indicated an inclination to elevate the “price” prong of the analysis over the “process” prong, reasoning that the purpose of a fair process is simply to arrive at a fair price. At the same time, however, the court generally has emphasized the unlikelihood of arriving at a fair price without a fair process—and thus generally has found entire fairness not satisfied when there were indications that the price was fair but there were serious flaws in the process. BGC Partners reinforces the emphasis on price over process in the analysis. The court stated: “Price…is often the paramount consideration because procedural aspects of the deal are circumstantial evidence of whether the price is fair.”

A board should not underestimate the critical importance of a fair process in the entire fairness analysis, however. Of note, in BGC Partners, the Court of Chancery found that, notwithstanding the apparently significant process flaws, the special committee had functioned effectively on behalf of the minority stockholders. The court wrote: “[There was] no evidence that th[e] problems [with the process] rendered the process unfair.” The court noted that the controller’s overinvolvement had occurred at the early stages of the process and that he had separated himself from the process once the special committee was formed and functioning. Further, the court concluded that the committee and its advisors were independent of the controller; were fully informed (with all of their diligence requests having been met); had worked tirelessly and “bargained hard” for the minority stockholders, over a period of several months; had successfully “pushed back” against the controller on certain points (including timing of the process); and ultimately had achieved a structure and price that were fair to the minority stockholders.

Other conflicted-controller cases in which the court has found entire fairness satisfied despite serious flaws in the sale process have involved unusual fact situations.

  • In Hsu v. Oak Hill (2020), the court applied the entire fairness standard to a controller’s and its board designee’s decision to pursue a cash-accumulation strategy in anticipation of redeeming the controller’s preferred shares, rather than investing in the company’s business for long-term growth for the possible benefit of the common stockholders. In a post-trial decision, the court found that, although an independent special committee had been utilized, the members were subject to subtle influence of the controller that undermined their independence. The court emphasized, however, the price aspect of entire fairness and found that, because the defendants proved that a growth strategy likely would not have been successful, what the common stockholders received (which was zero) was the same as what they would have received had a different strategy been pursued. Although the process raised concerns, the court noted that the controller “spent countless hours” working to enhance the value of the company and, as the majority stockholder, had a “counterbalancing incentive not to harm the value of the common stock.” (We note also an earlier case, In re Trados (2013), which involved a similar rationale for a finding of entire fairness despite process flaws. The court stressed that the value per share that the common stockholders received in the conflicted-controller merger (zero) was equal to the value of the common stock prior to the merger (zero).)
  • In ACP Master v. Sprint/Clearwire (2018), the court, in a post-trial decision, held that a presumed controller’s cash-out merger was entirely fair. Although the court found serious flaws with the process, the court emphasized that the price ultimately achieved “exceeded wildly” what the board had expected could be achieved. In this case, the flaws occurred early in the process, before a competing bid emerged that led to a renegotiation and ultimately the higher price that was achieved. Moreover, the court viewed the special committee as having taken their responsibilities seriously and having bargained at arm’s length; and sophisticated stockholders with deep knowledge of the company’s business had agreed to sell their shares even at the initial, lower price. (Notably, in the related appraisal action, the court determined that the appraised value of the dissenting shares was less than half the deal price.)
  • A controller should consider the benefits of the MFW framework when structuring a proposed transaction. MFW provides for business judgment review (Delaware’s most deferential standard of review) of conflicted-controller or conflicted-board transactions when, from the outset of negotiations, the transaction was conditioned on approval by a special committee of independent directors and by the minority stockholders. A controller may decide to forego the business judgment rule protections available under MFW because the controller does not want to subject the transaction to the uncertainty of a vote by the minority stockholders. Compliance with either of the two MFW prerequisites (for example, approval by a clearly independent special committee but not by the minority stockholders), while not providing business judgment review, shifts the burden of proof under the entire fairness standard to the plaintiffs (so that they must prove the transaction was unfair, rather than the defendants having to prove that the transaction was fair).
  • In cases in which the entire fairness standard is applied, dismissal at the pleading stage is highly unlikely given the highly facts-intensive nature of the entire fairness inquiry. The possibility of dismissal at the pleading stage may be maximized (or at least the burden of proof may be shifted to the plaintiffs to prove unfairness)—and thus the parties’ respective negotiating leverage may be affected—when a clearly independent special committee, advised by independent and experienced advisors, considered and negotiated the transaction and maintained a clear record establishing the committee’s effective functioning and fairness of the price. BGC Partners highlights that, even if claims are not dismissed at the pleading stage, entire fairness may be proved at trial (albeit after what is likely to be protracted, expensive and distracting litigation).
  • A special committee should be actively engaged and a record of its efforts should be maintained. Committee members should ask questions, request information, keep abreast of process developments, and so on. These efforts should be documented, for example in the committee’s meeting minutes (which can also reflect information provided or actions taken outside of the committee’s meetings). A special committee should “push back” against the controller in negotiating the transaction on behalf of the minority stockholders and, most importantly, should be prepared to “say no” to a transaction if it is not fair to the minority stockholders.
  • Special committee members should be independent of the controller. In selecting members of a special committee, the board should be mindful that even outside directors may be viewed by the court as non-independent if they are “beholden” to, or otherwise subject to the influence of, the controller. A controller should consider having at least one or more unquestionably independent directors on the board so that a special committee, if needed, can be formed that will be clearly independent. In BGC, although there were issues about the independence of some of the outside directors, the court ultimately found them to be independent—perhaps, we surmise, at least in part due to their particularly distinguished credentials (which the court detailed in its opinion). Efforts should be made, where possible, to document the independence of outside directors so that an appropriate determination can be made at the early pleading stage of litigation. For example, consideration should be given to reflecting in committee minutes that directors (especially those as to whom there could be some question about independence) were deeply engaged, asked questions, sought information, and at times “pushed back” against the controller’s interests or requests.
  • A controller should not seek to influence a special committee’s work. A controller should remove himself from the process to maintain the independence of the committee. Such removal would involve not only abstaining from voting on the transaction at issue, but also not attending board or committee meetings at which the transaction is discussed, not engaging in one-off discussions about the transaction with committee or board members, and not participating in the process of selecting advisors to or chairs of the committee.
  • However, a controller’s involvement to some degree in the process is not necessarily fatal to satisfying the entire fairness standard. For example, if the controller played a role in selecting or recommending the committee’s advisors, then the committee, once fully empowered, should itself reconsider the selection of advisors and choose for itself (and, if it reaffirms the controller’s selection or recommendation, the reasons for the committee’s judgment should be documented). If the controller engaged in one-off discussions with members of the special committee, the discussions should be reported to the full committee, the committee should consider reporting the discussions to the full board, and the committee should consider whether any actions should be taken to counteract any disadvantages to the process resulting from the discussions and to prevent further such discussions. At times, there may be a special need for a controller’s involvement (due to, for example, special knowledge about the company or a counterparty’s insistence on the involvement). In these situations, the special committee should consider whether the controller’s involvement will outweigh concerns about the conflicts. The committee should consider the extent to which the controller’s interests may be unaligned with the interests of the other stockholders with respect to the transaction, and what actions can be taken to seek to manage the conflicts, including the committee’s active and effective overseeing of the process. Such actions could include establishing specified parameters for the controller’s role (such as limiting the role so that it does not include, say, price negotiations), and/or having a special committee member join the controller in any discussions (or in any discussions that relate to specified topics).
  • A special committee and its financial advisor should consider the benefits of a “detailed” fairness opinion. In BGC Partners, the court’s determination that the merger price was fair was based largely on its being “in line with what [BGC’s] financial advisor determined to be appropriate…[in] a detailed fairness opinion” that was delivered “after more than a month of additional due diligence” by the banker. (The court also stressed that the price “was forged in the crucible of objective market reality,” coming after “months of arm’s length negotiations.”)

[ad_2]

Source link

Previous Article

Hearsay Systems launches program to help advisors level up on social media

Next Article

Black Teenagers Should Learn 4 Things About Personal Finance