(b) in a manager-managed, members are not agents, but managers are.
(b) manager-managed LLCs are managed by managers.
(c) things that require the unanimous consent of all members: modification of the operating agreement, admission of a new member, sale of the company, etc.
(d) action requiring the consent of members or managers may be taken without a meeting. In corporations, a meeting is required.
(e) a member or manager can appoint a proxy to vote. This is different from corporations: shareholders can vote by proxy, but not directors.
Now, this is a company that owns really only one asset: can they sell it without the consent of one of the members? Under the model act, probably not: § 404(c).
This is member-managed. So any member can sign over the deed and bind the company. But if he didn't have authority to do that, there are internal consequences. But still, they can take action without notice; that didn't happen, though.
But this isn't really like the case: there's no third party here. But they're maybe violating their fiduciary duties: self-dealing, e.g.
This decision related more to statutory construction than to LLCs. There's one rule that says any deed signed by the manager of a manager-managed LLC is binding. And another that says any manager can bind the LLC unless provided otherwise in the operating agreement.
We aren't going to make operating agreements public record, but we want third parties to be able to verify things without too much busywork. You can put things in the articles of organization, though.
So the court could have said the manager's action was binding to third parties, unless the information was available in the articles of organization.
But for LLCs, there's less formality, so therefore the veil is less piercy, perhaps. So there's got to be the alter-ego problem, but also causation.
What's the point of limited liability when the guy who owns the company is also the guy who runs the company? That's why we pierce that veil: limited liability isn't protecting otherwise innocent shareholders.
There's sort of a balancing test we apply to determine whether there's unfair shifting of risk: an LLC with insurance, for example, isn't such a worry. A reason to allow an individual to limit liability is to allow an individual to put some of their assets at risk, but not all of them.
When we're trying to decide whether the veil should be pierced, we look at things like whether the company is undercapitalized, who the directors are, etc.
If we have fiduciary duties for all other business arrangements, it would sort of make sense to have them for LLCs as well, lest people be blindsided by their absence.
A member may have some damage when the value of the LLC decreases. They may be allowed to file suit in the name of the LLC in order to correct this, even if they're minority owners and the majority (who caused the harm) are refusing to proceed.
See §§ 1101-1104. That governs derivative actions. A minority member suing on behalf of the LLC can get attorney fees if successful (and proceeds of the action go to the LLC). There are some restrictions on the pleadings: you have to show that the suit wouldn't happen elsewise. Suing derivatively is different from forcing the company to sue: you derive your standing from your position as a member of the LLC, but it's you who are suing (and if you lose, you bear the costs, as a result).
It's an imperfect system, to say the least, and allowing derivative suits on behalf of LLCs isn't obviously a good idea. It might be, but that's debatable.
Even though it's an LLC, it turns out ironically that he's worse off than he would have been in a GP, because they altered the default rules.