Avoiding Due Diligence Failure: Follow Up on All Red Flags
This blog takes no position on the malpractice allegations by HSBC that its law firm, Troutman Sanders, dropped the ball on its due diligence of a borrower who ended up costing the bank $75 million when the borrower put fake securities up as collateral. You can read about the lawsuit here and here.

A key portion of the allegations is that Troutman was tipped off to some inconsistent information when it was checking into the faked collateral, but didn’t investigate further or tell its client about the red flag waving brightly before its eyes.
Whatever really happened in this case, we find it’s worth reminding clients and those who may become clients that if something doesn’t seem right during due diligence, you have to assume that it isn’t right.
This can take some doing. We’ve written before about how the smarter you are, the easier it will be to convince yourself that it’s OK to do what you want to do, in our entry JPM, Feynman and Investigations. We’ve also written about need to be on guard regarding people who come well recommended from third parties, in Due Diligence on Expert Witnesses: Assume the Worst.
Due diligence shouldn’t be about digging for dirt that you hope will be there – as in litigation – or that you hope won’t be there – because you want your client to close the deal.
It’s about being on guard for the unexpected and reporting exactly what you find. It should never be “good news” or “bad news.” Never mind that your client will be angry that you’re wrecking a deal, or that the major witness on the other side appears to have no skeletons in his closet. All a good investigator is doing is presenting findings. Whatever you think your client wants, in the end telling the truth about what you find is the only way to go.
For a good starting checklist on a solid approach to due diligence, see our entries In Plain Sight: Corporations and Public Records and Scratching the Surface: Due Diligence and Public Record Searches.
One of the biggest misconceptions about due diligence is that it is a one-way street. People assume that either they are scrutinized or doing the scrutinizing, but never the twain shall meet. But this shouldn’t always be the case. In some instances, the person under the microscope also has a responsibility to make sure that they subject the other party to thorough due diligence.
Clients are often surprised to learn how much corporate information is on the public record. Of course, public companies are forced to disclose a lot more data than private ones, but it's still possible to learn about private companies using smart and thorough public records searches.
Context matters. We know this instinctively, and yet somehow we forget. We still tend to assume that facts live in their own separate bubbles. So when we research and analyze, we warily keep our findings in separate categories—information on person A separate from information on person B, which are both separate from facts uncovered about company C. We go to great lengths to avoid any cross-contamination because that may be messy or unwieldy and keeping things tidy is so satisfying.
You have an opening in your company. You get a slew of resumes for the position, you interview a number of candidates, and then you finally narrow it down to two people: One has experience that’s right on the mark, but during the interview you had glimpses of an attitude that might not mesh with your corporate culture. The other person is lacking a number of important skills, but it seems that she makes up for her shortcomings with an energy and attitude you admire. She seems like a real go-getter who will be a good fit among your staff. So what do you do?



