Syndication
The management company: the wall that is also a conflict
Separating operations from ownership keeps the lawsuits that operations generate away from the asset. But if the sponsor owns the management company, the same separation that protects the asset is also where the sponsor pays fees to itself.
Running a property generates a stream of exposure that owning it does not: employees, payroll, vendor contracts, tenant disputes, slip-and-fall claims. That operating risk should not sit in the entity that owns the building, which is why operations are usually pushed into a separate management company. But this particular wall has a second face. The management company is also where the sponsor often collects the management fees, and when the sponsor owns it, the entity that protects the asset from operating liability is the same entity through which the sponsor pays itself. The separation is real, and so is the conflict.
The same separation that keeps operating lawsuits off the asset is where the sponsor is on both sides of the fee.
The wall
The protective logic is straightforward. Property operations involve people and contracts, and people and contracts generate claims: an employment suit, an injured worker, a vendor dispute, a tenant injury. If the entity that owns the building is also the entity that employs the staff and signs the service contracts, those claims land on the asset. Putting operations in a distinct management company keeps that exposure in the operating entity, where a claim can be met without reaching the property itself. This is the same one-function-per-entity discipline that runs through the whole architecture: operations and ownership are different risks and belong in different boxes.
The conflict
Now the second face. The management company earns fees, property management fees, asset management fees, sometimes construction management fees, and those fees are paid out of the deal. When the sponsor owns the management company, as sponsors very often do, the sponsor is on both sides of that arrangement: setting the fees as the manager of the deal and collecting them as the owner of the management company. That is a related-party transaction and a genuine conflict of interest, covered in the risk section, and it connects directly to the fee-load analysis, because these are exactly the fees that get paid regardless of whether the deal performs.
The conflict is not automatically improper. Sponsor-affiliated management is common and often sensible, since the sponsor knows the asset. But it has to be disclosed, and the fees have to be reasonable and at market, because an undisclosed or above-market related-party management arrangement is the kind of self-dealing that anti-fraud liability and the fiduciary analysis are built to catch.
The structuring consequence
Separate operations from ownership for the liability protection, and treat the related-party management arrangement as something to disclose and price honestly, not to bury, because the structure that shields the asset is also a channel through which the sponsor extracts fees from the deal. An investor reading the structure should see both faces at once: the management company is a firewall against operating claims and a place to check whether the sponsor is paying itself fairly. Both are true, and a sponsor who presents only the first is hiding the second.