What is a hotel lost and found log?

A hotel lost and found log is the system of record that proves your lost and found procedure actually happened. The procedure is the SOP: intake, storage, guest notification, claim, return, and disposal. The log is the evidence trail behind it. Owning that distinction is the whole point, because a generic SOP page tells you what steps to follow, and this page tells you which record answers the guest's lawyer.

Two functions share ownership of found items in a hotel. Housekeeping finds most items during room turnover: bedside tables, bathroom counters, under beds, safes left open. The front desk fields the inbound guest inquiry ("I left my charger in 412"). A good log is the single place both functions read and write, so a housekeeper's find and a guest's call meet in one record instead of two disconnected conversations.

Every found-item record should include:

• A unique item ID or tracking number
• Description of the item and its category (valuable, non-valuable, perishable)
• Exact date and time found
• Specific location found (for example "Room 412 bathroom counter" or "Lobby, chair by window")
• Name of the staff member who found it
• A photo taken at intake
• Current storage location and condition notes
• The return or disposal outcome, with date, method, and recipient once resolved

Item categories drive everything downstream: retention, storage, and notification urgency. Valuable items (phones, wallets, laptops, jewelry, passports, cash) go in a locked safe or locker with longer retention and tighter access. Non-valuable items (clothing, chargers, toiletries, books) sit in general secured storage with shorter retention. Perishable items (food, medication, opened toiletries) get very short retention and are usually disposed within days.

Digital versus paper is the reframe. Paper binders and shared spreadsheets fail on three axes. They are not searchable at speed when a guest calls. They carry no photo evidence. They have no access control, so anyone can edit or quietly "lose" a line. For the single-property SOP depth, see the digital lost and found log for hotels, schools, and airports. This page owns the layer above it: chain-of-custody as liability control and above-property visibility across a portfolio.

How does security lost-and-found tracking work in Xenia?

In Xenia, a lost and found log runs as a digital form with required image capture at intake, a secure item record with role-scoped access, and location-hierarchy visibility so found-item trends roll up across every property. The item record carries the photo, the custody trail, and any return or shipping task in one place.

Intake starts with proof, not a memory. A housekeeper finds a phone charger in 412 during turnover. She opens the lost and found form on the tablet, selects the location, and the form asks the follow-up questions: category, description, condition, and a required photo. No photo, no submission. In Xenia, the intake photo is documented in-line and attached to the record at the moment of discovery, so a later "that is not the condition it was in" dispute has a documented answer.

The record is the custody trail. Every action on the item is a timestamped, attributed entry: found, moved to locker, guest contacted, claimed, shipped, disposed. This is the difference between a spreadsheet and a chain-of-custody log. A spreadsheet shows the current state. The Xenia record shows every hand the item passed through and when.

Access is scoped by role, across the whole portfolio. A front-desk agent logs an item and searches the log to answer a guest call. A housekeeping supervisor verifies claims and authorizes releases. A property GM sees their property. A regional or corporate lead sees every property's log. In Xenia, the property GM sees their property and the regional lead sees all properties, one account with different scopes, so there is no over-visibility and no separate spreadsheet to reconcile. That above-property view is what makes lost and found tracking software worth running across a group instead of at one site.

Return and shipping are tracked tasks, not afterthoughts. When a guest claims an item, the release or shipping step becomes a task with an assignee and a deadline. If the item ships, the record holds the carrier, tracking number, and proof of delivery. Compare this to guest-facing operations in guest request management, where the same task workflow routes and closes requests.

Xenia complements the PMS, it does not replace it. Many hotels use the PMS auto-trace function in Opera, Cloudbeds, or Mews to flag a guest profile that an item is being held. Xenia does not touch the reservation, the guest profile, or billing. It holds the physical-item record, the photo, the custody trail, and the operational tasks. If you already run front-desk incident tracking in Xenia, the lost and found log lives in the same app on the same login.

How do retention windows and chain-of-custody reduce liability?

Retention windows and a chain-of-custody log reduce liability by giving a hotel a defensible, timestamped answer to two questions: how long an item was held before disposal, and who was responsible for it at every step. Without both, a "you lost my ring" claim becomes the hotel's word against the guest's.

A common house framework sets standard items at 30 days, high-value items at 90 days, then donation or disposal per local law. That aligns with the published SOP consensus. Retention periods "typically range from 30 to 90 days" for standard items before donation or disposal, per the Deliverback lost and found procedure guide. The Flexkeeping hotel lost and found SOP and the SetupMyHotel housekeeping SOP document tiers of roughly 30 to 60 days for non-valuables, about 3 days for perishables, and up to 6 months for valuables in a secure locker. Brand standards vary: Marriott properties typically hold found items 90 to 180 days depending on estimated value.

Local law matters more than any blog default. In some jurisdictions a hotel must turn unclaimed property over to local authorities after a set period. In others the hotel has discretion. Set your window to your own legal counsel and local statute, not to a default you copied from a template.

Because each Xenia record carries the date found, the retention clock is deterministic. The system flags items approaching the end of their window, so nothing gets disposed early (a liability) or hoarded past policy (clutter and a different liability). Dashboards and summaries surface items aging past the retention window per property, so the view shows where the next problem is forming, not just yesterday's completion count.

Chain-of-custody is the core liability control. A lost and found dispute is a liability event, and the defense is a record:

1. Item photographed at intake
2. Every custody transfer timestamped and attributed
3. Claim verified against a description or photo ID before release
4. Disposal or return logged with date, method, and recipient confirmation

Claim verification is where fraud stops. The claimant must describe identifying details or show ID before the item is released, and the log stores that verification step as part of the record. Proof of delivery closes the loop on shipped items: carrier, tracking number, and delivery confirmation stay on the record. For the broader security-function context, see the hotel safety and security checklist and the key control reference.

How does Xenia compare to hotel-only tools?

Hotel-only tools like Flexkeeping, Quore, and HelloShift offer lost and found modules built into a hospitality suite. Xenia offers lost and found as one workflow inside a multi-vertical operations platform, with required photo intake, role-scoped above-property visibility, and the same task workflow that runs the rest of the hotel.

The hotel-only tools are genuinely good at what they do. Quore has a dedicated Lost and Found app inside a hospitality-specific suite and flags items at 90 days so teams know when to clear them. HelloShift builds lost and found into the same platform staff use for tasks and messaging, with description, location, finder, photo upload, status tracking, search, and automatic guest notification. Flexkeeping is the closest housekeeping-specific competitor and owns the SOP search results with deep, hospitality-native content. Deliverback specializes in the return and shipping half of the problem.

Xenia does not try to out-feature them on hotel-only housekeeping depth. It wins on scope and workflow integration.

| Capability | Hotel-only tools (Flexkeeping, Quore, HelloShift) | Xenia |
|---|---|---|
| Lost and found log with photo | Yes, hospitality-native | Yes, with required image capture enforced at intake |
| Guest notification | Yes, some auto-notify | Xenia holds the item record and task, PMS auto-trace handles the guest profile |
| Above-property rollup | Varies, oriented to single-property operations | Location hierarchy: property, regional, and corporate scopes on one login |
| Role-scoped access | Yes, within the property | Yes, and scoped across the whole portfolio |
| Runs the rest of ops | Hospitality workflows only | Multi-vertical: audits, maintenance work orders, daily checklists, comms in one app |
| Retention-window aging view | Quore flags at 90 days | Dashboards surface items aging past window per property |
| Pricing | Per-property hospitality SaaS | Flat per-location, growth adds no per-form or per-seat penalty |

The consolidation argument is the honest one. A hotel group already running Xenia for housekeeping room turnover, preventive maintenance work orders, and daily checklists gets lost and found in the same app, on the same login, with the same custody and photo model. Flat per-location pricing means adding properties or staff does not add a per-seat charge, so the math does not punish a growing group. It is not another vendor to buy, train, and reconcile. For the maintenance side of that stack, see the hotel maintenance industry page. Xenia does not replace a PMS auto-trace and it does not ship items itself, so if guest-paid return logistics is your core need, a specialist still has a role.

Where do operators see results?

Operators see results in three places: faster answers to guest inquiries, fewer disputes that stick, and portfolio-level visibility no single-property spreadsheet can give. The proof point is the shift from a paper binder or shared spreadsheet to a tablet-based, photo-proof, searchable record.

Speed to answer a guest. A guest calls: "I left my ring in 812." Instead of walking to the back office and opening a binder, the front-desk agent searches the log by location and date and answers in seconds. The same searchable-record benefit Flexkeeping, HelloShift, and Deliverback all cite, now on the platform that also runs the hotel night audit checklist and the rest of the front-office shift.

Fewer disputes, stronger defense. A photo at intake, a timestamped custody trail, and a verified claim release mean a contested claim has a documented answer. This is the liability payoff from the retention section, restated as an outcome the GM can point to.

Above-property visibility. A regional lead opens one dashboard and sees found-item volume by property, open items aging toward disposal, and any property whose log has gone quiet (a sign staff stopped logging). An AI summary reads something like "Property Aspen: 14 open found items, two aging past the 30-day window, all guest inquiries this week answered from the log." That portfolio view is what single-property tools do not deliver.

Paper-to-digital rollout is fast, and there is verified evidence of the pace outside hospitality. In the C-store vertical, Tempstop went paperless in 14 days on Xenia. That is a convenience-store example, not a hospitality claim, but it shows how quickly a paper process converts once the form and the roles are set. For the security-function framing across property types, see the security management industry page, and to see how a dedicated log differs from an event record, compare it with the hotel quality assurance audit workflow.

Ready to track found items across every property instead of one binder at a time? Book a Xenia demo for hotel operators and see the lost and found log, the custody trail, and the portfolio dashboard in one walkthrough.

How to set up a lost and found log in Xenia

Setting up a lost and found log in Xenia takes about an hour. Build the intake form with required photo capture, set item categories and retention windows, define who logs, verifies, and releases, then turn on the portfolio rollup. Here is the sequence.

1. Build the intake form. Create a lost and found log with the required fields: item ID, description, category (valuable, non-valuable, perishable), date and time found, exact location found, staff member, and a required photo. Use follow-up-question logic so a "valuable" selection prompts the locker-storage field. Xenia's AI Template Agent can convert an existing paper SOP or spreadsheet into this digital form in minutes.
2. Set item categories and retention windows. Standard items 30 days, high-value 90 days, perishables disposed within days, per house policy and local law. Set the window per category so the retention clock starts automatically at intake.
3. Define roles and access. Front-desk agents log and search. Housekeeping supervisors verify claims and authorize release. Property GM sees the property. Regional and corporate see the rollup. This is location hierarchy plus scoped permissions.
4. Configure claim verification. Require a description match or photo ID capture before an item is released. Store the verification as part of the record.
5. Set up return and shipping as tasks. When an item is claimed, generate a release or shipping task with an assignee and deadline. Capture carrier, tracking number, and proof of delivery for shipped items.
6. Turn on the portfolio view. Enable dashboards and AI summaries so a regional lead sees found-item volume, open items, and anything aging past its retention window across every property.
7. Roll it out from a proven structure. Start with the lost and found log template or the lost and found template. Short-term-rental operators can use the Airbnb lost and found log. The rollout pattern is the same one that runs across the hospitality operations platform: replace the paper binder with tablet-based, photo-proof intake while keeping your existing PMS.

That last point is the whole hotel found item retention policy in practice. The window is only enforceable if the intake date is captured cleanly and every item follows the same form.