Facilities
Predictive maintenance for hotels, without the sensors. Lance turns the records your team already files into a condition signal on every asset — so you fix what is changing, not what is scheduled.
Every record your team files is a reading on a specific asset. Lance puts all five types into one classified layer tied to a room or a piece of equipment — which is how a pile of tickets becomes a condition signal.
Preventive vs predictive
Every hotel runs preventive maintenance. Almost none run predictive.
They are not two speeds of the same thing. They are triggered by different events, reason about different objects, and answer different questions.
Preventive
Predictive
What sets off the work
Preventive
A date. Every ninety days, every five hundred hours — whether this unit needs it or not.
Predictive
A change in the unit itself: a reading drifting off its band, a repair pattern forming.
What it knows about
Preventive
The equipment class. The average service life of every unit like this one.
Predictive
This unit. What it has cost, what it has needed, and where it is heading.
The question it answers
Preventive
Is it time yet?
Predictive
Is this one changing?
How it fails you
Preventive
You service healthy equipment on schedule — and the unit that was degrading early fails anyway, between intervals, in front of a guest.
Predictive
It needs a real condition signal. Without one it is a dashboard making guesses.
What it needs to run
Preventive
A calendar, and the labour to keep it honest.
Predictive
Condition monitoring. Which normally means sensors on the asset, a year or two of deployment, and someone who can read the output.
Your building has been generating condition data for years.
That last row is why hotels stop. Predictive maintenance needs condition monitoring, condition monitoring means instrumenting the asset, and nobody is wiring four hundred guest-room PTACs with vibration sensors. So the category calls preventive “proactive” and leaves it there.
But the signal already exists. Three work orders on the same unit in ninety days is condition data. A reading drifting off its band is condition data. A guest complaint about 214, an engineer's note, a line on a radio call — all of it describes the state of a specific asset, generated every day by the people already doing the work, and dropped into five systems that cannot see each other.
Connect it to the asset and you have the input predictive maintenance runs on — without buying a single sensor.
What it does
Built around the two things that decide whether any of this works.
Whether an engineer will file the record, and whether the chief engineer will believe what comes back. Everything else is downstream of those two.
Capture
Faster than the radio
Voice and camera are first-class inputs, not attachments. An engineer files a work order in under twenty seconds without leaving the room. If logging work is slower than doing it, the radio wins and the record never happens.
Connection
Tied to everything it touches
A warm AC in 214 is not one ticket. Lance sets it against the unit's history — third work order in ninety days, readings on that loop trending off, the same unit class failing at year six in a sister property.
Evidence
One click down
Every insight names the records it was built from, and low-confidence findings arrive as suggestions to accept or dismiss rather than filing themselves. An insight you cannot audit will not survive a chief engineer.
Reporting
Stops being a job
Any view, insight or answer becomes a formatted report from live data. The daily chain to the GM and the Head of Facilities generates itself, consistent and comparable across every property.
Lance detects what is changing by reading your property's own records — trends, anomalies and threshold events across the layer above. Asset registries and capital planning build on this foundation and are the road ahead of it.
The field surfacePrivacy and Security at Every Layer
Protect guest data, hotel systems, and AI workflows with enterprise-grade security.
Learn MoreSOC 2 Type I
Independently audited against the AICPA SOC 2 Security criteria to ensure your data is protected with industry-standard security and access controls.
GDPR
Built to support GDPR compliance for groups operating across borders, with clear data subject rights and documented international transfers.
PCI DSS
PCI DSS compliant (self-attested) under SAQ A — a self-assessment, not a third-party certification.
Aligned with ISO 27001
Follows ISO 27001 practices for managing and protecting sensitive information — alignment, not a certification.
Related
Find out what your building has been telling you.
Book a demo and we'll walk your property's maintenance picture — your records, your equipment, your team.