Kept turns the morning room report you already run into a board your team drives from the front desk and from their own phones. A room is not clean until the checklist is, and the moment it is, the whole property knows. No printouts. No radio guesswork. No wondering what is ready to sell.
Built alongside the people who run a real hotel floor, not around a conference table.
From a forty room independent to a flagged three hundred room property, the systems are installed and the front desk is still calling upstairs to ask if a room is ready. The problem was never the software. The problem is whether anyone opens it.
One screen, everyone on it. The calls stop because the answer is already on the board.
Kept is not another system, and it does not replace your PMS. It is the layer your teams actually open: one job per screen, in the language of the floor, with a timestamped record of who did what, and when. When someone asks what happened in room 214 last Tuesday, the log answers.
That is not a story about one bad vendor. It is what happens when a product is sold to the person who signs and shipped to the person who cleans. Two different people, two different jobs, and only one of them is ever in the room when the software gets chosen.
Read the one star reviews and the complaint is rarely a missing feature. It is nearly always one of these four.
The dead one in the headline is not a figure of speech. The property Kept was built in owned one, paid for it, and ran the floor on a radio and a printed list anyway.
On the second room of the day, does the checklist get tapped step by step, standing in the room, or all at once at two in the afternoon, standing at the door?
In flow taps mean the times are real and you own a record. Batch taps mean Kept became the old app with better colors. That is the whole test, and you can run it yourself in an afternoon without asking us anything.
Which is why nobody gets trained. Day one is a sticky note with a first name and four digits, and one sentence from the manager: your rooms are on your phone today. That is the entire rollout. If Kept needs a class, it has already lost, because the next property's crew will not get one either.
Every system in this category will hand you a report. A report is a claim, worth exactly as much as the vendor who printed it. Here is the difference between a report and a record, in three parts. You can check all three without taking our word for it, and the third one you can still check after we are gone.
Mark clean does not press until every step of the room checklist has been tapped. Not greyed out with an override for the manager. It does not press.
A room that is clean because someone said so from a chair at 4pm is the thing your current data is made of. This is the mechanic that ends it.
Every action appends to a log that cannot be quietly edited. Not by staff, not by the manager, not by us.
Each entry is built from the one before it, so altering an old line breaks every line after it, visibly, on a page your manager can open while you stand there.
Once a day the head of that chain is sent to public RFC 3161 timestamp authorities, DigiCert and FreeTSA, and their signed reply is stored exactly as it came back.
The chain catches an edited row. The anchor catches the harder case: someone deletes the log and rebuilds a tidy fake whose hashes all recompute correctly. To fake history you would now also have to alter records held by a certificate authority.
And the proof outlives us. RFC 3161 is the same standard used to sign software and notarise documents. The reply is ordinary DER on your disk, so an auditor checks it years from now with openssl ts -verify, on a laptop, with no Kept account, no vendor, and no us. If we disappear, your record still stands up.
Ask your manager to show you a room that ran over forty minutes last week, and what happened in it. A trashed checkout, a broken AC, a deep clean.
If the answer comes off the board while you are standing there, the record is alive. If it does not, then no software in your building is working, and that includes ours. It is a fair test either way, which is why it is the one we hand you.
Kept is not one app with a role switch. It is three front doors, and the hardest design work went into keeping everything complicated behind the one your floor never opens.
No email, no password, no code from an inbox, no expiring anything. Your rooms and nothing else, in your own language, with an icon checklist so the tap never depends on the word.
It installs to the home screen. In the dead spots it holds the taps on the phone and catches up the moment the signal returns.
Not what the report said this morning. What is true right now, and who is standing in the room.
Plus one field for the thing only the desk knows: early arrival, guest waiting at the counter, VIP in 214. That field exists to end the phone call upstairs, which is the call Kept was built to eliminate.
The board, assignment in one tap, the maintenance log and its work orders, supplies, the morning import, the end of shift sheet, and the audit log with its verification.
Access is granted per person rather than baked into a job title, so a lead housekeeper who also covers the desk is one grant your manager makes, not a support ticket.
Kept runs in English, Spanish and Haitian Creole, and the language belongs to the person, not to the device. Maria signs in and the whole app is Spanish. She hands the same phone to Jean at shift change, Jean signs in, and the same app is Kreyòl Ayisyen. Nobody changes a setting, and nobody is handed a phone in a language they do not read.
Three written interfaces, not one run through a translate button. Every word was written in all three, down to the message that says the phone is full and the one that says to use the radio because help is not coming through the app.
In South Florida that is not a nice touch, it is whether the crew can use the software at all.
Most housekeeping tools are built around one clean day at a time. Real properties are not, and the gap between those two facts is where the manager's morning goes.
With its reason attached. Nobody re marks the same four rooms every single morning, and no room quietly slips back into inventory because today's report did not know it was out.
Recarpet 214. Repaint floor two. Ordered steps, a real deadline, many rooms at once, and a hold that survives every morning import until the work actually passes.
One tap, LOW or OUT. That is the floor's entire relationship with inventory, because a slower workflow is a dead workflow, and barcodes on a housekeeping cart are how you get neither the count nor the clean.
The buy list assembles itself, and a floor alert overrides the ledger, because the shelf is more honest than the spreadsheet.
It already knows where you are, because you started the room. Locating the person is the expensive half of every system in this category, and here it is a column that has been filling itself in all day.
The alert is never queued offline. If it cannot reach the server it says so, in your own language, and tells you to use the radio, because a queued panic alert is a lie told to someone in trouble. Raised, seen, and stood down each land on the chain, because nobody came and nobody was told are different facts.
Florida has no statewide employee safety device mandate, and several mandates elsewhere call for dedicated Bluetooth hardware, which a phone is not. So Kept does not describe this as ESD compliance, in the product or on this page, and it will not start. If you are in a city with a real ordinance, we will tell you what Kept does and does not satisfy before you buy it.
You will find these out anyway. Better on a web page you are reading for free than on the third call.
Kept reads the morning room status report you already run, and at the end of the shift produces a sheet that mirrors your PMS columns so your lead re keys the clean rooms in one pass.
It never writes into your PMS. That is a decision, not a gap: writing into a PMS means a certification cycle, and you would be waiting on that instead of running your floor.
Room numbers, staff first names, checklists, and photographs of broken things. No guest names, no reservations, no cards.
There is nothing in it worth stealing, which is the correct amount of guest data for a housekeeping tool to be carrying around on twelve personal phones.
Multi property is designed and it is not built. If you own eight hotels, the honest answer today is that Kept would run one of them properly while we build the rest of the answer in front of you.
Some owners want exactly that. Most do not. Assume this is the state of it until we tell you otherwise in writing.
The whole adoption argument, and nothing you would have to explain to a housekeeper.
Everything in Floor, plus the parts that break every other morning.
Everything in Operations, plus the management layer on top.
The record is never the upsell. Checklist gated clean and the anchored audit log are in the $199 tier, because a tier that could not prove who did what would not be Kept.
Here is the arithmetic, so you can redo it on the back of a folio instead of trusting a slide.
Put your own wage number on that. Then add the comped night. Then add the clean room that sat unsold for three hours on a full Saturday because the desk did not know it was ready.
Your number will be different from ours. It will not be zero. If we look at your floor and cannot find a leak worth more than the fee, we will say so on the call and you will have lost twenty minutes.
The day opens anyway, with every room dirty. A room wrongly listed dirty costs a walk through. A room wrongly listed clean costs a guest walking into an unmade bed. Kept picks the cheaper mistake on purpose, and the manager reconciles from the board rather than from a phone call.
The record does not leave with them. That is most of the point. Access is granted per person and revoked per person, a new manager is opened up from the back office rather than from a support queue, and the history the next manager inherits is the same history that was there the day before.
JQT Enterprises, a forward deployed engineering firm in Fort Lauderdale, Florida. We embedded in a working hotel, built Kept inside its actual mornings rather than around a conference table, and we still answer for it after go live.
JQT embeds in an operation, builds the system that operation runs on, and stays to run it. What we learn on one floor becomes the product the next floor opens on day one. Kept is the first, which makes it the proof as well as the product.
The next one will not be a hotel. It will be built exactly the same way.
See how JQT works →Send us tomorrow's room status report, the one you already run. We put it through Kept and show you your own floor, your own room numbers, gaps and all, before you change anything or pay anything. Twenty minutes. You keep the map either way, including the part where we tell you the leak is too small to bother us about.