Luggage System Commissioning and Handover Checklist
Q&A

Luggage System Commissioning and Handover Checklist

HOME > Q&A

A hotel luggage management system is ready for guests only when every tag, scanner, storage location and message has been tested with real bell desk staff, and a VIP bag can be traced from kerb to room in the system without a phone call. Commissioning should prove that end to end, and the handover should leave the bell captain able to run it without the supplier.

This checklist is written by Singapore-based AV and IPTV integrator Prestige Solutions for hotel operations managers who are commissioning or comparing luggage management systems. It covers the hardware and data checks, the workflow tests including VIP arrivals, the pass criteria we use, and what the bell desk team should hold at handover. It also works as a comparison list: a system that cannot pass these checks in a demonstration will not pass them on site.

Checklist 1: hardware and infrastructure

Hardware checks come first because every workflow test depends on them. Confirm each item in the actual locations where staff will use it, not in the back office.

ItemCheckPass criterion
Handheld scanners or phonesScan tags at kerb, lobby, storage room and service liftFirst-scan read success on almost every attempt; no dead spots
Wi-Fi or mobile data coverageWalk the route with a scanner, including storage rooms and basementScans sync within a few seconds, or queue offline and sync later
Tag stockBarcode or RFID tags, claim stubs and printersTags print clearly; stubs match tag numbers; spare stock for 2–4 weeks
Label and receipt printersPrint at the bell desk and conciergeNo alignment faults; paper stock and spares on site
Storage locationsEvery shelf, cage or room labelled with a scannable location codeLocation codes in the system match the physical labels
ChargingCharging points for all handhelds at shift changeDevices last a full shift
Hotel bell desk staff scanning luggage tags with a handheld device
Test scanners and coverage in every place staff will actually use them.

Checklist 2: data and integrations

A luggage system is only as accurate as the guest and room data it receives. Check each integration with live test reservations before go-live:

  • PMS link: guest name, reservation, room number and arrival and departure dates arrive in the system; room changes update the luggage record.
  • VIP and special handling flags: VIP level, fragile, oversized and "deliver on arrival" flags carry from the PMS or are set at tagging.
  • Guest notifications: SMS, email or messaging notifications for stored-bag claims and deliveries send correctly and show the hotel's name and contact.
  • User accounts: each staff member has their own login; roles limit who can release bags or edit records.
  • Time sync: device and server time match, so timestamps are reliable for disputes.
  • Data retention: how long guest data is kept and who can export it is agreed with the hotel's data protection officer, in line with Singapore's PDPA.

Checklist 3: workflow tests with real staff

Run every workflow with the bell desk team, using their shift patterns, not the supplier's demonstration users. Each test should be recorded with timestamps from the system:

  1. Standard arrival: tag at kerb, move to storage, deliver to room after check-in; confirm every scan and the delivered status.
  2. VIP arrival: VIP flag visible at tagging; bags delivered to the room before or with the guest; supervisor alert if delivery exceeds the target time.
  3. Group arrival: tag 30 or more bags under one group, split by room; confirm no bag remains unassigned.
  4. Left luggage after checkout: store with claim stub, notify guest, release on scan of stub and ID check.
  5. Room change: move a guest in the PMS; the luggage record follows.
  6. Exception: a bag scanned to the wrong room or missing a scan; the system shows it on the exception list.
  7. Offline: disable Wi-Fi on a device, scan several bags, restore; records sync without duplicates.
Luggage storage room with labelled shelves and scannable location codes
Every storage position needs a scannable location code that matches the system.

Checklist 4: pass criteria before go-live

Agree the pass criteria in writing before testing starts, so go-live is a decision against numbers rather than impressions. The criteria we propose to hotels:

MeasureTarget at commissioning
Bags tracked end to end in test runs100% with every required scan present
Time to find a stored bag from the claim stubUnder 2 minutes
VIP bags with the flag visible at every scan100%
PMS room changes reflected in luggage recordsWithin 1 minute
Offline scans synced without duplicates100%
Staff able to complete each workflow unaidedEvery bell desk staff member on the roster, not just supervisors

Checklist 5: staff handover and training

Handover is complete when the bell captain can train new staff without the supplier. Training should be short, practical and done on shift:

  • 30–45 minute hands-on session per shift, with each staff member scanning real test bags.
  • A one-page quick guide at the bell desk and in the storage room.
  • Supervisor training on the exception list, reports and user administration.
  • A named system owner in operations and a deputy.
  • Support contact, response times and the escalation route for device or server faults.
  • A procedure for manual fallback if the system is down: paper tags with the same numbering, entered later.
Hotel operations team reviewing luggage tracking reports during handover
Supervisors should own the exception list and reports from day one.

Checklist 6: first 30 days after go-live

The first month shows whether the system is being used as intended. Review the exception list daily in week one and weekly after that; check the share of bags with a missing scan; ask staff where scanning slows them down; and confirm tag and paper stock reorder levels. Adjust storage location codes if staff are using locations that are not in the system. Other hotel projects are listed on the Prestige Solutions home page.

Using this checklist to compare systems

When comparing suppliers, ask each to run workflows 2, 4 and 7 from Checklist 3 live in the demonstration, with your staff scanning. Systems differ most on offline behaviour, PMS integration depth and exception reporting, and those differences only show up when the workflow is run rather than described.

Common commissioning failures and their causes

Most commissioning failures on luggage systems are process gaps rather than software defects. The patterns we see most often:

  • Missing scans at the storage room: the storage room has poor Wi-Fi and staff skip the scan; fix coverage or confirm offline queuing works before go-live.
  • Bags stuck in "stored" after delivery: staff deliver directly from the kerb and never scan the delivery; the workflow should allow a direct kerb-to-room path with one delivery scan.
  • VIP flag lost: the flag is set in the PMS after the bags have already been tagged; the system must update existing records when the flag changes.
  • Duplicate records: two staff tag the same bag on busy arrivals; tags should be issued from one point per arrival.
  • Shared logins: the team uses one account for speed, so exceptions cannot be traced to a person; personal logins with quick PIN entry solve this.

Each of these shows up in the workflow tests if the tests are run with real staff at realistic speed, which is why supplier demonstrations alone are not a commissioning.

Schedule the workflow tests during a real but moderate arrival period, such as a mid-week afternoon, rather than an empty lobby. Staff then use the system under normal pressure, and gaps in coverage, printer placement or scan steps show up before the first large group or VIP arrival relies on it.

FAQ

Should hotels use barcode or RFID luggage tags?

Barcode tags are cheaper and suit most hotels, since each scan is a deliberate staff action. RFID can speed up bulk handling for large groups but costs more per tag and needs readers in fixed positions to add value.

Can guests track their own luggage?

Some systems send guests status messages or a link showing when bags are stored or delivered. It reduces calls to the bell desk, but the messages must be accurate, so enable it only after scan discipline is proven.

What happens to luggage records after the guest leaves?

Records should be kept only as long as the hotel's policy requires for dispute handling, then deleted or anonymised. Agree the retention period during commissioning and configure it in the system.

Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337, message us on WhatsApp, or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.

Previous Article Mirror TV Service Access Options for Recessed Inst Next This is the last article

Interested in Our Solutions?

Explore our full product range or speak with our technical team for a tailored consultation.