<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lodgcore — field notes</title>
    <link>https://www.hotelpmssystem.com/insights/</link>
    <description>Field notes on hotel operations, systems and the guest experience.</description>
    <language>en</language>
    <lastBuildDate>Mon, 02 Nov 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://www.hotelpmssystem.com/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why every property defines occupancy differently — and how to stop</title>
      <link>https://www.hotelpmssystem.com/insights/group-reporting/</link>
      <guid isPermaLink="true">https://www.hotelpmssystem.com/insights/group-reporting/</guid>
      <description>A group report is a governance document. If the definitions are not owned centrally, the number is a negotiation.</description>
      <category>Groups</category>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Cloud or on-premise PMS: a decision guide for independent hotels</title>
      <link>https://www.hotelpmssystem.com/insights/cloud-vs-on-premise-hotel-pms/</link>
      <guid isPermaLink="true">https://www.hotelpmssystem.com/insights/cloud-vs-on-premise-hotel-pms/</guid>
      <description>The hosting question is really about resilience, data residency and who owns the 02:00 problem.</description>
      <category>Systems decision</category>
      <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Night audit without the overtime: what to automate and what to keep human</title>
      <link>https://www.hotelpmssystem.com/insights/night-audit-design/</link>
      <guid isPermaLink="true">https://www.hotelpmssystem.com/insights/night-audit-design/</guid>
      <description>A close is a sequence of decisions, not a pile of reports. Design the sequence and the overtime disappears.</description>
      <category>Operations</category>
      <pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One guest record: the discipline behind recognition</title>
      <link>https://www.hotelpmssystem.com/insights/one-guest-record/</link>
      <guid isPermaLink="true">https://www.hotelpmssystem.com/insights/one-guest-record/</guid>
      <description>Loyalty programmes fail at the handoff, not at the sign-up. A profile is infrastructure.</description>
      <category>Guest data</category>
      <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The 90-second check-in: designing the desk for a queue</title>
      <link>https://www.hotelpmssystem.com/insights/check-in-design/</link>
      <guid isPermaLink="true">https://www.hotelpmssystem.com/insights/check-in-design/</guid>
      <description>Speed is not typing faster. It is removing decisions from the arrival.</description>
      <category>Front office</category>
      <pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
