One property serves dinner and the other does not, so are the meals worth it?

The exhibit listing what staff can't do is the whole deal, Warrant. It is the section that stalls more of these packages than anything else in the file. The problem with the evening staff member is that residents don't read the exhibit. They see a person in a polo shirt at 8pm and they ask for help getting out of a chair. Once that happens a few times you're either training and supervising to a standard the agreement says you don't meet, or you're the community where staff say no to a 79-year-old. Neither is comfortable. The pure active adult one is boring to read, and that's a point in its favor for a first deal. You can add a vendor later. Unwinding a service program once residents depend on it is much harder.

On the debt side those two documents do not get looked at the same way at all. A pure active adult rental generally gets underwritten close to conventional multifamily, and the agency and bank programs that price best are built around that shape. Once meals and staffing sit inside the rent, some lenders start calling it senior housing, and proceeds, reserve requirements and pricing all move. The same sponsor can end up with two very different term sheets on two buildings a mile apart for exactly that reason, so confirm in writing with whoever you are talking to how they would classify it before you model anything. The services themselves are fine. What matters is knowing which bucket the asset falls into before the purchase agreement is signed, because the answer changes the equity check.

Dumb question that I've been sitting on. If the resident base ages in place, doesn't the pure active adult building end up needing the services anyway? Somebody moves in at 62 and stays eleven years like ember's example, they're 73 and they're not the same customer. Do you just let them move out to a real independent living community, or does the building slowly turn into the second document whether the owner planned it or not?

Because if it's the second, then choosing "no services" isn't really choosing, it's just deferring. And I'd rather have the kitchen and the shuttle in the original design than try to retrofit them into a building that has neither.

Compass, the standard answer from the capital side is that the building does not age if it gets re-leased. Vacancy is the reset. Every unit that turns comes back at whatever age the market is sending, and marketing aimed at 58-year-olds keeps producing 58-year-olds. The building only drifts when turnover is near zero and nobody is watching who moves in. Whether that works in practice depends on turnover actually happening, and in this product turnover is the thing everyone calls low. So the point survives partially. My vote is third-party vendors. Let a meal service and a transport company sell to residents directly, keep the contracts at arm's length, and most of the appeal arrives without the payroll or the supervision problem landing on the ownership books.

Sable's arm's length version is the one that keeps showing up in the deals I get shown, and I'd push back slightly on why. It isn't purely risk management. It's that the meal program almost never makes money as a standalone line. You staff a kitchen for a hundred covers and half your residents cook for themselves, so you're carrying fixed labor against variable participation, and the rent premium has to cover the gap on its own.

The communities where it works have participation baked in, meaning the meal is in the rent and everyone pays whether they eat or not. That's a different business and residents notice they're paying for dinners they skip.

Warrant, if I were reading those two packages I'd ask the second one's operator for participation rates by meal for the last two years. If it's under 50 percent on dinner, the kitchen is a marketing expense wearing a revenue line's clothes.