Fix the System Before You Clean the Mess
- Jenn Brantmier
- Feb 24
- 3 min read
If you only clean the mess and never fix the system, you will have to clean the mess forever. When a pipe bursts, you turn the water off before you clean the mess. Shouldn't you do the same for messes in your operational flow? This might be happening at your hotel right now. And the system may not be as obvious as a pipe bursting. Here is how it played out at a hotel we recently worked with.
Sunday, 10:12 AM. Brunch Service.
The terrace is full.
Sunlight. Espresso machines. Linen dresses. A line at the host stand.
At a 180-room independent luxury property, this played out almost every weekend.
Two tables on bottomless mimosa packages tied to their room.
A suite guest mentioning their brunch credit should apply.
A server pausing because the credit wasn’t visible in the POS.
Accounting isn’t in.
Revenue isn’t in.
It’s Sunday.
So the team does what they’ve trained themselves to do.
Manager walks to the front desk.
Front desk pulls up the PMS folio.
Someone overrides the charge in the POS.
A note goes into the system to “reconcile Monday.”
No crisis.
Just workarounds.
Over time, those small overrides were adding up. Comped items that shouldn’t have been comped. Staff pulled off the floor. Credits fixed after checkout. Quiet erosion that costs the property tens of thousands annually in leakage and labor friction.
The instinct had been to retrain.
Instead, we traced the architecture.
Here’s what we found in the systems review:
PMS
The Brunch Package was built separately from the room package logic two years earlier during a software update.
Rate rules had been layered over older rate rules instead of rebuilt cleanly.
Credits were attached through a manual folio routing structure that depended on consistent mapping.
POS/PMS Integration
The POS was “technically” integrated with the PMS
Charge codes weren’t fully aligned.
Credit fields weren’t consistently passing through the interface.
CRM
Recorded entitlements beautifully, but entitlement flags weren’t reliably pushing into operational systems.
Staff were cross-checking between platforms because there was no true source of truth.
Nothing was broken enough to trigger a red flag. It was configuration drift. The team wasn’t failing. They were compensating. So we didn’t change platforms. We worked directly in configuration.
Here’s what we changed in the systems:
PMS
Rebuilt the PMS package logic from the base rate architecture instead of layering another fix on top.
POS/PMS Integration
We cleaned up folio routing and standardized charge codes so the POS recognized credits automatically.
We corrected field mapping in the PMS ↔ POS interface and removed the workaround created years earlier.
CRM/PMS Integration
We clarified which system served as the source of truth and ensured entitlement fields were pushed correctly from CRM to PMS.
Final Testing and Roll-out
Then we tested the full cycle live Booking → Check-in → F&B charge → Checkout.
The following Sunday?
No manager walking to the desk.
No override in the POS.
No “check it Monday” note.
The brunch credit simply applied.
Observable Outcomes
Manual adjustments dropped dramatically.
Manager interruptions decreased.
Audit trails became clean.
Staff stopped holding their breath.
Guests never noticed the change.
Ownership did.
Luxury isn’t about solving problems gracefully.
It’s about building systems strong enough that your team doesn’t have to compensate for them.
If your weekends require quiet heroics, you may not have a service issue.
You may have a system that needs to be fixed instead of cleaned.
At CLV, we start with diagnosis, not demos. We map your current stack, identify configuration drift, review renewal exposure, and rebuild logic within your existing systems before recommending change.
If this feels familiar, let’s look under the hood together.
Comments