A guest calls three days after checkout. She left her grandmother's ring on the nightstand, the one she never travels without and this one time did. She is not really asking whether you have it. She is asking whether she can trust the people who cleaned her room, whether anyone wrote anything down, whether the place she stayed is the kind of place that would find a ring and get it back to her, or the kind of place where it simply disappears. In that one phone call, your entire lost and found operation is on trial, and she will know the verdict in about ninety seconds.
Most hotels treat lost and found as an afterthought: a cardboard box in a back office, a drawer nobody logs, a pile of phone chargers and single earrings that grows until someone throws it out. That is not a lost and found. That is a junk drawer with liability attached. A real lost and found is a trust system, and it is protecting three things at once: the guest who left something behind, the employee who found it, and the hotel that has to stand behind both. Run it as a system and all three are protected. Run it as a drawer and all three are exposed.
Why it is a trust system, not a storage problem
Start with who is actually at risk when a guest leaves something behind, because it is not just the guest.
The guest is trusting that their property is safe in your building even after they have left it. The employee, usually a room attendant, who finds a ring on a nightstand is in a genuinely vulnerable position: if there is no system, and the guest later claims the ring is missing, the last person known to be in that room is the one under suspicion. And the hotel is exposed to a dispute it cannot resolve, because without a record it is one person's word against another's.
A proper lost and found protects everyone by turning a private moment, an attendant alone in a room finding a valuable, into a documented, witnessed, traceable event. The attendant who immediately logs and turns in a found ring is not just being honest. They are being protected, because now there is a record that says they found it, reported it, and handed it over. The system is what makes integrity safe to practice. That is exactly why the tone of the whole thing matters so much, and why it belongs in the same conversation as service standards that people actually follow, which I get into in service standards that don't feel scripted. A standard that protects the person following it is one they will follow.
The intake: log everything, the moment it is found
The system lives or dies at intake, the moment an item is found. If it is not captured well here, nothing downstream can be trusted.
Every found item, and I mean every item, gets logged. The discipline is that there is no threshold, no "it is just a charger, do not bother." The moment you let people decide what is worth logging, you have handed them the discretion that lets the valuable things slip through. So everything gets recorded, and the record captures the same few facts every time:
- What it is, described plainly and specifically. Not "jewelry" but "gold ring, single stone, engraving inside."
- Where it was found, down to the room number and the spot in the room. Location is what lets you match it to the right guest later.
- When it was found, the date and time.
- Who found it, by name. This is the fact that protects the finder.
Then the item is tagged with a unique reference tied to that log entry, and it goes into secure storage, not into a pocket, not onto a desk, not into the drawer. The tag is what connects the physical object to the record for the rest of its life in your building. Valuables, cash, phones, laptops, jewelry, and documents get held separately and more securely than a forgotten phone charger, because the risk they carry is different.
The habit that makes intake reliable is speed. An item logged the moment it is found is logged accurately. An item that rides around on a cart all afternoon and gets written up at the end of the shift is half-remembered and often lost. Found means logged, right then, is the standard worth holding.
Storage, retention, and knowing when to let go
Once an item is logged and secured, it enters a holding period, and the holding period needs a rule, not a vibe.
Every property sets a retention window, a defined length of time it holds unclaimed property before disposing of it, and the window is often different for different kinds of items. Valuables and high-value electronics are typically held longer than low-value everyday items, and perishables like food or opened toiletries are usually not held at all. The exact numbers matter less than the fact that they exist, are written down, and are applied the same way to everyone. A retention policy that changes based on who is asking is not a policy.
Storage has to match the value of what it holds. General items can live on labeled shelving in a secured room, organized so they can actually be found when a guest calls. Valuables belong in a safe or a locked cabinet with limited access, because the whole point of the system is defeated if the ring you carefully logged can be quietly lifted from an open shelf.
Disposition, what happens when the window closes, needs to be as documented as intake. When an unclaimed item reaches the end of its retention period, it should be disposed of according to a clear, written rule and that disposition should be recorded. Common approaches include returning the item to the finder, donating it, or discarding it, but whatever the property chooses, it has to be consistent and logged. The record that an item was disposed of, when, and how, closes the loop and protects the hotel just as much as the record that it was found.
The return: verify, then make it easy
The return is where the trust system pays off, and it is also where a careless operation undoes all its good logging in a single move. The two failures are opposite and equally bad: returning an item to the wrong person, or making it so hard for the right person to get their property back that they give up.
Verification comes first. Before anything goes back, you confirm the person claiming it is the person who lost it, and the log is what makes this possible. Ask the claimant to describe the item and where they think they left it, and match their answer against the record. The guest who can tell you it was a gold ring with an engraving, left on the nightstand of the room they stayed in, is almost certainly the owner. The one who says "I think I might have left some jewelry somewhere" is not describing, they are fishing. Good intake notes are what let you tell the difference. For anything mailed rather than picked up, you confirm identity and shipping details carefully, because a shipped item leaves your custody for good.
Then you make the return itself easy and gracious. Once ownership is confirmed, the guest should feel the hotel is glad to reunite them with their property, not that they are imposing. Offer to ship it, handle the logistics cleanly, and keep the guest informed. This is the moment a small operational function becomes real service, the kind of gesture that outlasts the stay, which I get into in small gestures guests remember. A ring returned quickly, with a warm note rather than a bureaucratic runaround, is a story that guest tells for years. It is also the natural companion to the personal attention I describe in notes that make a guest feel known, because both come from the same instinct: treat the guest as a person whose things, and whose trust, matter.
Make the system remember, so people do not have to
The quiet reason lost and found operations fail is the same reason deep cleans and followups fail. They depend on someone remembering, and people are busy. A guest who calls about a claim gets a callback promised, and the callback never happens. An item that needs to be shipped waits for a slow afternoon that never comes. The retention window passes unnoticed and items pile up.
The fix is to stop relying on memory and put the followups into a system that will not forget, the same trace and task discipline I describe in trace and task systems. A claim that needs a callback becomes a dated task with an owner. An item awaiting shipment gets traced to the day it should go out. The end of a retention window triggers a disposition task rather than being noticed by accident months later. When the system carries the memory, the human just has to show up and do the next thing in front of them, which is the only way any of this survives a genuinely busy week.
The takeaway
A lost and found tells you whether a hotel means what it says about service. Done as a junk drawer, it exposes your guests, your team, and your name to the worst version of an honest mistake. Done as a trust system, logged at intake, stored by value, held to a real retention rule, and returned with verification and grace, it turns one of the most anxious moments a guest can have into proof that they chose the right place. Build it so the system does the remembering, and let your people do the caring.
Questions from the desk
What is a hotel's lost and found policy?
It is the set of rules for handling property guests leave behind: logging every found item with what, where, when, and who found it; storing it securely; holding it for a defined retention period; verifying ownership before returning it; and disposing of unclaimed items in a documented, consistent way. The point is to protect the guest, the employee who found the item, and the hotel.
How long do hotels keep lost and found items?
Each property sets its own retention window, and it is often longer for valuables than for low-value everyday items, while perishables are usually not held at all. The specific length matters less than having a written rule that is applied the same way to everyone.
How do hotels verify who an item belongs to before returning it?
They match the claimant's description against the intake log. A real owner can usually describe the item and where they left it; the record of what was found, and where, is what lets staff confirm the claim rather than guess. For shipped items, identity and delivery details are confirmed carefully because the item leaves the hotel's custody.
Why should staff log even low-value found items?
Because the moment you let people decide what is worth logging, valuable items start slipping through that same discretion. Logging everything keeps the system honest and, just as importantly, protects the employee who found the item by creating a record that they reported it.