What is a skipper in a hotel?

A skipper is a guest who leaves the hotel without settling the bill. The term comes from 'skipping out' and appears in property management systems as a skipper report, which is normally produced during the night audit — often a day or more after the guest has gone. Revenue leakage is the broader category: it also covers unregistered occupancy and room hopping.

Can room control hardware actually stop a guest from leaving without paying?

No, and any vendor claiming otherwise should not be trusted. Payment authorisation at check-in and PMS billing rules are what protect the money. A room controller can only validate authorisation and detect anomalies early. What it changes is the time between the event and someone knowing about it: from roughly 30 days at the audit, to the same day.

Does this require cameras in guest rooms?

No. Occupancy is detected with infrared or millimetre-wave presence sensors, door contacts and key-card events. No camera is used in any guest room, and presence data is used only for room state logic, not for identifying individuals.

Which PMS systems can the controller validate against?

Validation needs the in-house stay list — room number, credential identifier and departure date. That is available from Opera, Protel, Mews, Cloudbeds and most other PMS platforms through their APIs, or through a scheduled export where no API exists. The controller caches the list locally and validates on-card without a network round trip.

How quickly is an unregistered or departed guest detected?

The controller evaluates room state continuously. A room drawing power with no matching stay record is flagged within minutes. A suspected departure is flagged after a configurable window with no power draw, no door events and no presence detected — typically set between 8 and 24 hours, because a guest out for the day must never trigger an alert.

Does a hotel need to replace its existing room controllers?

Not necessarily. Where an existing controller can report card, power and door events over an open interface, it can feed the same logic. Where it cannot, the controller is replaced room by room; the wiring, wall boxes and switch plates are usually reusable, so the room is out of service for roughly half a day.

Revenue Protection for Hotels — Every Room Accounted For

Detect unregistered room use and unpaid departures the same day, not at the month-end audit — on the room control layer you may already be installing.

Send your room list How detection works

Three ways a hotel loses room revenue

They are usually treated as three separate problems, owned by three different people. They share one cause.

Leak	What it looks like	How it is normally found	Exposure
Unregistered occupancy	A room is in use but nobody is checked in — a staff room, a friend of a friend, a cash guest	Housekeeping notices something odd. Often never.	100% of the room rate, per night
Room hopping	A guest occupies a room they are not registered to, or a single booking occupies two rooms	Night audit cross-check, where one exists	Rate difference plus occupancy error
Skipped folio	The guest departs without settling the bill	Month-end audit — the guest is long gone	The full outstanding balance

The shared cause: the room is being used, and nobody compares that fact against the PMS in real time. The gap is not a procedure that people forgot to follow — it is a missing data path.

The gap is structural, not procedural

The PMS knows who should be in the room. The lock knows who entered. The room itself — the lights, the AC, the sockets — knows nothing, and reports nothing.

PMSWho should be here, and the folio status

Door lockWho entered, and when

RoomPassive devices. No record, no report.

Room controllerReconciles all three in real time, and acts locally

Put a controller in that gap and the room stops being silent. It becomes the only device in the building that knows, continuously, whether the room is occupied and whether it is allowed to be.

Three levels of validation

Most key-card switches stop at level 1. The dividing line is level 2.

Level	What is verified	Data source	Note
1	Is this card issued by this hotel?	Card credential or issuing system	Where ordinary key-card switches stop
2	Does this card still hold a valid stay for this room, right now?	PMS in-house list: room, credential, departure date — cached on the controller	The dividing line. This is what separates a power switch from revenue protection
3	Is the folio or payment status acceptable?	PMS accounting or pre-authorisation	Optional. A hotel policy decision, not a technical requirement

A folio is an accounting record, not an access right. It says what is owed, not who may enter. Conflating the two produces both false denials (a paid-up guest denied power) and false acceptances (an old card still drawing power). We validate the stay first, and offer folio status as a separately configurable policy.

Four signals, four room states

A card in a slot is not occupancy. Guests leave the card in to keep the AC running, and two guests sharing a room insert one card. A system that trusts the card alone under-reports vacancy and over-reports savings.

Signal	Question it answers	Role
Validated key card	Who is entitled to this room?	Access gate and revenue protection
Presence sensor (IR / mmWave)	Is a person in the room right now?	True occupancy
Door contact	Has someone left, and when?	Departure detection
PMS room status	Should anyone be here at all?	In-house / vacant / checked out / unrented

Combined, the four signals resolve each room into one of four states, and each state has its own policy: occupied (guest settings honoured), temporarily vacant (setback after a delay, pre-conditioned before return), checked out (deep setback, card rights revoked at checkout), unrented (deepest setback with a periodic airing cycle for humidity).

What the front desk actually sees

An exception that arrives as a report gets ignored. It has to arrive as a decision.

A short list, not a dashboard. Rooms requiring a human decision, with the reason attached.
Flagged as suspected, never as confirmed. Absence is not departure, and sensors can be wrong.
The evidence behind each flag — how long without power draw, how long without a door event, whether presence was detected.
Thresholds set per property. A resort and a city business hotel do not have the same definition of "too long".
Card rights revoked at checkout, so an old card cannot draw power the next day — the most common source of unregistered use.

What it cannot do

These are design constraints, not disclaimers. We expect to be held to them.

What the system does

Detects and alerts, within minutes to hours
Revokes card rights at the moment of checkout
Records the evidence trail for each flag
Keeps working when the network is down

What it never does

Stop a guest from walking out — payment control is the PMS and the pre-authorisation
Lock a guest in, or disable emergency egress
Cut essential power over a billing dispute
Use cameras in guest rooms
Treat an empty room as proof of departure

The honest claim: we do not prevent the loss. We move the discovery of it from the month-end audit to the same day — and that time difference is the product.

What it takes to deploy

Item	Requirement
PMS data	In-house stay list (room, credential, departure date) via API — Opera, Protel, Mews, Cloudbeds and most platforms — or a scheduled export where no API exists
Existing hardware	Reusable if the current controller reports card, power and door events over an open interface; otherwise replaced room by room with wiring and plates usually retained
Network	Controller caches the stay list locally and validates without a round trip, so a PMS or network outage does not lock guests out
Pilot	Four rooms, 30 days: two weeks of baseline event logging, then two weeks with validation enabled, compared on comparable rooms

Send the room list, get a revenue-protection proposal

Tell us the PMS you run, the room count and the current audit process. We reply with the integration options, the detection thresholds we would recommend, and a four-room pilot plan.

Contact Hotekey