Marriott just added climate change and extreme weather to its official risk disclosures. The headline reads like a corporate formality — another line item in the 10-K, another nod to ESG language that makes the legal team feel better.

But I've been inside enough mechanical rooms to know this isn't a footnote. This is an operational alarm.

Look, when a company the size of Marriott tells its investors that extreme weather is raising costs and threatening property operations, they're not speculating. They're reporting what their asset managers and GMs have already been dealing with — probably for years — and they've finally decided the exposure is material enough that the SEC filing needs to reflect it.

Here's what the vendor floor at HITEC doesn't talk about: most hotel building management systems were designed for a climate that doesn't exist anymore.

My parents' property in Charlotte — 90 keys, built in 1978 — has an HVAC system that was sized for historical weather patterns. Summer used to mean a few brutal weeks in July and August. Last year, my dad ran the chillers at near-max capacity from May through October. The compressor failed twice. Each repair was north of $8,000. The building wasn't engineered for that kind of sustained load, and no software patch fixes undersized ductwork or aging refrigerant lines.

Scale that up to a 500-key full-service property and the math gets ugly fast.

What Marriott's disclosure is really telling you — if you read it like an engineer instead of an investor — is that the physical infrastructure of their portfolio is being stressed beyond its design parameters. More cooling demand. More storm damage. More insurance cost. More unplanned capital expenditure. And the properties absorbing those costs are the ones owned by franchisees, not by Marriott.

Now here's where my brain goes: this should be a technology story. Energy management systems, predictive maintenance platforms, smart building controls — these are the tools that can actually respond to climate variability in real time. Adjust HVAC load dynamically based on occupancy AND weather forecasting. Flag equipment degradation before the compressor dies on a sold-out Saturday in August. Route power consumption away from peak-rate hours when the grid is stressed.

The technology exists. I've evaluated several of these platforms. Some of them actually work — not in the demo, in production. Predictive maintenance tools that monitor vibration patterns in chillers and flag failure probability weeks before it happens. Energy management systems that integrate with the PMS to pre-cool occupied rooms and scale back on empty ones. The ROI is real. I've seen properties cut energy costs meaningfully with proper deployment.

But here's the problem — and this is the part that keeps me up at night.

Most hotel technology stacks weren't built to talk to building systems. Your PMS talks to your CRS. Your CRS talks to the channel manager. Your channel manager talks to the OTAs. That chain is reasonably mature, even if it's held together with duct tape in a lot of places. But the building side? The HVAC controls, the lighting systems, the water management, the electrical metering — those systems live in a completely separate universe. Different protocols. Different vendors. Different maintenance contracts. Often no API at all.

The integration layer between hotel operations technology and building management technology barely exists. And that's the layer you need if you want to respond to climate variability intelligently instead of just eating the cost.

I ran into this exact problem with a 200-key client last year. They wanted to connect their energy management system to their PMS so unoccupied rooms would automatically adjust climate settings. Sounds simple. The PMS vendor said it was possible. The BMS vendor said it was possible. What nobody mentioned was that the PMS pushed room status updates every 15 minutes, and the BMS needed real-time data to respond efficiently. A 15-minute lag meant the system was always reacting to where guests WERE, not where they ARE. The energy savings evaporated.

This is what I mean when I say hotel technology was built for a different set of problems. We spent 20 years optimizing distribution and revenue management — and we did a decent job. We spent almost no time building the infrastructure layer that connects the building itself to the operational brain of the hotel.

Marriott's climate disclosure is the canary. The real question isn't whether climate change raises costs — obviously it does. The question is whether the technology ecosystem that hotels depend on can adapt fast enough to manage those costs before they become unmanageable.

And right now, that answer fails the Dale test. If your chief engineer can't understand the system well enough to override it when the weather forecast is wrong or the sensors drift — and they will drift — then the technology isn't ready for prime time. I've seen beautiful energy management dashboards that nobody on the property actually uses because the interface was designed by someone who's never met a chief engineer.

The vendors building climate-adaptive building technology for hotels need to understand something fundamental: the person who operates this system is not a data scientist. They're the same person who's also fixing the ice machine and responding to a noise complaint on the fourth floor. If your product can't survive contact with that reality, it doesn't matter how good your algorithm is.

Marriott put climate risk in their SEC filing. That's the disclosure. What comes next — whether brands mandate building technology upgrades the way they mandate PMS migrations, and whether those mandates come with realistic implementation timelines and cost-sharing — that's the story I'm watching.

Because if the answer is another unfunded mandate pushed down to franchisees who are already dealing with rising insurance premiums and deferred maintenance backlogs, then the disclosure isn't a warning. It's a preview of the next wave of franchise disputes.

Kasumigaseki Hotel REIT just raised its first-period forecast, citing strong hotel demand in Japan.

That's the headline. Here's what I'm actually thinking about.

Japan's inbound tourism numbers have been staggering since the post-COVID reopening. The weak yen has turned the country into one of the best travel values on the planet, and hotel operators — especially in Tokyo, Osaka, and Kyoto — are seeing occupancy and ADR levels that are rewriting their underwriting assumptions. A REIT raising its forecast in that environment isn't surprising. It would be more surprising if they didn't.

But I keep coming back to something I've seen play out at properties much closer to home.

My parents run a 90-key independent in Charlotte. When demand surges — when there's a big NASCAR weekend or a convention that fills the market — the first thing that breaks isn't the front desk. It isn't housekeeping. It's the systems. The channel manager can't push rate changes fast enough. The PMS lags on check-in volume. The revenue management logic, if it exists at all, was calibrated for a normal Tuesday, not a sold-out Saturday. You end up with my dad manually adjusting rates in the PMS at 10 PM because the automated rate push timed out.

Now scale that to an entire REIT portfolio riding a demand wave across Japan's hotel market.

Look, I don't know the specifics of Kasumigaseki's technology stack. But I know the Japanese hotel market. I've talked with operators and consultants who work there. The technology infrastructure at many Japanese hotels — especially older properties and those outside the major international brand ecosystems — is a generation behind what you'd see in comparable U.S. or European markets. PMS systems that still require manual rate entry. Channel management that doesn't sync in real time. Revenue management that's more art than algorithm.

When demand is this strong, you can get away with it. High occupancy covers a lot of sins. If every room is selling, does it matter that your rate optimization is manual and imprecise? Actually, yes. It matters enormously. Because the difference between capturing $180 and $220 on a night when you're going to sell the room regardless — multiplied across a portfolio, across hundreds of nights — is the difference between a good year and a great year. It's the difference between a REIT that raises its forecast modestly and one that blows past it.

This is the thing nobody's writing about when they cover these REIT forecast revisions. The demand story is real. The operational capture of that demand — turning market conditions into actual optimized revenue — depends entirely on the technology layer sitting between the market opportunity and the guest folio.

I helped build a revenue management tool once. FrontEdge. We raised $12M. The product looked beautiful in demo. And then it crashed on opening night at a 300-key resort in Scottsdale because we hadn't accounted for real-world PMS integration failures under load. I know exactly what happens when the technology layer can't keep up with demand. You leave money on the table. Every night. And nobody notices because the top line still looks good.

That's the trap. When the market is hot, operators and asset managers focus on the demand side — how many rooms are we filling, what's RevPAR doing, how's the comp set. Nobody's asking: are we actually capturing the maximum revenue the market is offering? Or are we leaving 8-12% on the table because our rate-push logic is stale, our channel manager has a 15-minute sync delay, and our dynamic pricing model — if we even have one — hasn't been recalibrated since pre-COVID?

The Dale test applies here. Dale was a night auditor I worked with during my worst professional failure. He'd been doing everything by hand for 19 years. When my system crashed, he was the one who saved the night. But Dale shouldn't HAVE to save the night. The system should work. And if Kasumigaseki or any hotel REIT is riding a demand wave with properties whose technology infrastructure was built for a different era of Japanese tourism, they're running a Dale test every single night across their portfolio.

Raising the forecast is the easy part. The hard question — the one that determines whether this REIT outperforms or merely performs — is whether the technology at the property level is sophisticated enough to capture what the market is giving them.

I'd want to see their tech stack before I'd get excited about the revision.

CoStar just published a look at the top 25 hotel markets in the Southeast, and the headline is resilience. Hotels held up during a year of economic uncertainty. Markets showed strength. Operators weathered the storm.

Look, I'm not going to argue with the topline. The Southeast has been a bright spot. Population growth, business relocation, tourism momentum — the demand drivers are real, and operators in those markets deserve credit for the performance they've delivered.

But here's what I keep running into when I'm actually on-site at properties in these markets: the revenue held up, and the systems didn't.

I've been consulting with independent and small-portfolio operators across the Carolinas, Georgia, Tennessee, and Florida for the past three years. The story I hear over and over isn't about demand softening. It's about properties running at strong occupancy on technology infrastructure that was duct-taped together during COVID and never properly rebuilt.

My parents' hotel in Charlotte is a perfect example. The Magnolia did solid numbers last year. My dad was proud of it — and he should be. But the PMS they're running is two versions behind on updates because the last update broke the integration with their channel manager. Their rate-push to OTAs has a manual step that my mom does every morning at 6 AM because the automated connection timed out eight months ago and nobody could figure out why. They're leaving money on the table every single night because the rate optimization is effectively manual.

Multiply that across thousands of independent and select-service properties in the Southeast and you start to see the issue. The resilience CoStar is measuring is top-line resilience. RevPAR held. Occupancy held. ADR grew in a lot of these markets. What isn't being measured is the operational friction underneath those numbers — the revenue that's being lost to manual workarounds, broken integrations, and technology platforms that were chosen in 2019 and haven't been re-evaluated since.

I did a technology assessment for a 12-property portfolio based in Atlanta earlier this year. Every property was performing above market. Every single one also had at least one critical system integration that required a manual workaround. Rate management, housekeeping dispatch, guest communication — somewhere in every property's tech stack, there was a human being doing something a working system should have handled automatically. When I calculated the labor hours spent on manual workarounds across the portfolio, it came to the equivalent of roughly two full-time employees. Not per property — total. But at the labor rates they were paying, that adds up fast.

Here's what I think the Southeast resilience story is actually telling us: these markets have enough demand tailwind to cover up a lot of operational inefficiency. That's great when the wind is at your back. What happens when occupancy dips even a few points and suddenly those manual workarounds aren't being absorbed by strong revenue?

The properties that scare me aren't the ones struggling with demand. They're the ones performing well on broken infrastructure. Because the performing properties aren't getting the technology investment — ownership looks at the numbers, sees green, and says "why would I spend money fixing something that's working?" My dad says this to me every other Sunday. The WiFi is terrible. The PMS integration is held together with manual processes. But the hotel is making money, so the $15,000 rewire I've been quoting him for two years stays on the "someday" list.

The Southeast's top 25 markets have earned the resilience label. I'm not disputing that. But resilience built on strong demand and manual workarounds is fundamentally different from resilience built on strong demand and strong systems. The first kind looks identical to the second kind — until it doesn't.

What would I tell an operator in one of these markets right now? Do a technology audit while you can afford to. Not the kind where your PMS vendor sends you a satisfaction survey. The kind where someone actually maps every integration point, identifies every manual workaround, and calculates what it's costing you in labor and lost revenue optimization. Do it while your occupancy is high and your ownership group is feeling good about the numbers. Because the best time to fix infrastructure is when you can afford the disruption.

Dale — the night auditor I watched handle a system failure at a resort in Scottsdale years ago — told me something I think about constantly: "The computer's supposed to make it easier, not add a new way to mess up at midnight." A lot of Southeast hotels right now are running on systems that have quietly become new ways to mess up at midnight. The strong demand is just masking it.

Every time a GM appointment hits the wire, the industry treats it like a birth announcement. Congratulations. Here's the headshot. Here's the career trajectory. Here's the quote about being "thrilled" and "honored."

Gorav Arora has been appointed General Manager of JW Marriott Kolkata. That's the news. That's all the news we got — a name, a title, a property.

And look, I'm not here to evaluate Arora's qualifications. I don't know the man. I have no idea whether he's a phenomenal operator or a placeholder. The source material is a headline and a tagline. That's it. There's no detail on his background, his priorities, his operating philosophy. So I'm not going to pretend I have insight into HIM.

But I do have insight into what happens at a property when the GM changes. Because I've watched it happen — at my parents' 90-key independent in Charlotte, and at properties ten times that size.

Here's what the press release never covers: a GM transition is a technology event.

Every GM inherits a tech stack. PMS configuration. Revenue management platform settings. The integrations between the two. Guest-facing mobile tools. Back-of-house workforce scheduling. Energy management. Payment processing. Loyalty system touchpoints. At a JW Marriott, you're inside Marriott's ecosystem — so a lot of this is standardized. But "standardized" doesn't mean "understood." It means someone before you made configuration choices, set thresholds, built workarounds, and in some cases duct-taped integrations together in ways that work fine until somebody touches them.

I've seen this at the Magnolia — my parents' property. My dad has run the place for over 20 years and he STILL doesn't fully understand every setting in the PMS, because some of them were configured by a vendor rep in 2011 who's long gone. At a 90-key independent, that's a manageable risk. At a full-service JW Marriott? The surface area for things to quietly break during a leadership transition is enormous.

The new GM changes a reporting structure. The person who understood why the rate-push timing was set to 11:47 PM instead of midnight — because it collides with the night audit batch at midnight — is now reporting to someone who doesn't know to ask. Nobody documents this stuff. It lives in one person's head.

This is the Dale test. My old night auditor test. What happens when the institutional knowledge walks out — not because someone quit, but because the person who used to ask "why is it set up this way?" has been replaced by someone who doesn't know the question exists?

At a branded property like JW Marriott, the brand provides a safety net. There are regional tech support teams. There are standard configurations. There's a playbook. But anyone who's been through a Marriott PMS migration — or any brand-mandated platform rollout — knows that the playbook covers about 70% of reality. The other 30% is property-specific tribal knowledge.

I helped build a product that crashed on opening night at a 300-key resort because we didn't understand the gap between the sandbox and the real world. GM transitions are a version of the same problem. The system doesn't change. The person who understood the system's quirks does.

So what should a new GM actually do about this? Here's what I tell my consulting clients during any leadership transition:

First 30 days: audit your integrations. Not the ones on the vendor diagram — the ones actually running in production. Find out which ones have workarounds. Find out who built the workarounds and whether those people are still on your team.

Document the "why" behind non-obvious configurations. Rate-push timing. Housekeeping scheduling rules. Energy management overrides. If the answer to "why is it set this way?" is "because Carlos set it up three years ago," you have a single point of failure wearing a name badge.

Meet your night auditor before you meet your director of sales. Seriously. The night auditor knows where every system breaks. They know which workaround runs at 2 AM. They know which vendor's support line actually answers.

None of this will be in the press release about Gorav Arora. None of this will be in the congratulatory LinkedIn comments. But for the 200-plus people inside that property whose daily work depends on systems running correctly — this is the transition that matters.