Anonymized hotel case study · 10 properties
What 10 Hotels Recorded After Requiring ID Scans for Every Guest
In the same months of 2025 and 2026, these hotels recorded 94% more ID scans and lower police case, trespass notice, and unrecovered loss rates per 1,000 scans. Here is what the numbers show and what they cannot prove.
The short answer
What changed across the 10 hotels?
Recorded ID scans rose from 17,196 to 33,393, a 94% increase. During the same comparable months, the police case rate fell 51%, the trespass notice rate fell 62%, and unrecovered loss per 1,000 scans fell 40%. All 10 hotels required an ID scan for every guest on every reservation. These are observed portfolio results, not a measure of unique bookings or proof that criminal screening alone caused the changes.
Same months · 2025 versus 2026
The results at a glance
Using a rate per 1,000 ID scans allows the incident and loss figures to be compared even though the number of recorded scans changed substantially.
| Measure | 2025 | 2026 | Change |
|---|---|---|---|
| ID scans | 17,196 | 33,393 | 94% more |
| Police cases per 1,000 scans | 3.14 | 1.53 | 51% lower |
| Trespass notices per 1,000 scans | 2.27 | 0.87 | 62% lower |
| Unrecovered loss per 1,000 scans | $498 | $301 | 40% lower |
Percent changes are rounded. Police and trespass figures are event rates, and loss figures are dollars per 1,000 recorded ID scans.
Police cases per 1,000 scans
Trespass notices per 1,000 scans
Unrecovered loss per 1,000 scans
Understanding the scan increase
Why does 94% more scanning matter?
Every participating hotel required staff to scan an ID for every guest on every reservation. That policy makes the scan record a useful view of documented check in activity across the portfolio. The rise from 17,196 to 33,393 scans is substantial, especially alongside lower incident and loss rates when expressed per 1,000 scans.
What about bookings?
More scans under this requirement point to more recorded guest traffic. A scan is not the same as a unique reservation: more than one guest can be scanned for a stay, and a guest might be scanned again. The study did not measure booking growth, occupancy, or revenue.
A consistent check in process
The operational value behind the numbers
Requiring an ID scan for every guest makes the process consistent across shifts. It gives teams a reliable opportunity to see existing Do Not Rent alerts, document incidents, and apply a property policy before completing check in.
- Use the same ID scan step for every arriving guest.
- Document and review incidents with rates that account for scan volume.
- Escalate relevant alerts to a manager using a written property policy.
The lower rates in this comparison are encouraging. They reflect the broader Guest Ban program and should not be attributed to a single feature.
Optional screening layer
How criminal screening fits into the ID scan
Hotels can add automated criminal background screening to their existing Guest Ban scan process. The property sets its ruleset in advance. If a scan meets a configured rule, the front desk receives only a simple Do Not Rent alert and calls a manager. Authorized managers and owners can review the underlying report and verify the match before a decision.
Scan the ID
The agent follows the usual check in step.
Apply the ruleset
The background check runs automatically.
Show a simple alert
The agent sees Do Not Rent and a prompt to contact a manager, without the reason.
Manager reviews
An authorized manager verifies details and applies the written policy.
See how Guest Ban criminal background screening works for hotels. It is an optional add on; contact sales for pricing.
What this comparison can and cannot tell us
The analysis compares the same months in 2025 and 2026 at 10 comparable, unnamed properties. It shows changes in recorded scan activity and rates per 1,000 scans. It is observational. Staffing, occupancy, local conditions, use of Guest Ban features, and reporting practices may also have changed.
The results cover the broader ID scanning, Do Not Rent, incident documentation, and optional screening program where enabled. They do not isolate the effect of criminal background screening, establish a causal reduction in incidents, or measure unique bookings, reviews, occupancy, or revenue.
Frequently asked questions
Questions hotel owners ask about the results
Did these hotels get 94% more bookings?
The 94% figure refers to ID scans, which rose from 17,196 to 33,393. Every property required an ID scan for every guest on every reservation, so the increase points to more recorded check in activity. Unique bookings were not counted.
Did criminal screening cause fewer police cases?
The police case rate per 1,000 scans was 51% lower in the comparison period. The analysis cannot separate the effect of optional screening from ID scanning, Do Not Rent alerts, documentation, staffing, or other changes.
What does a front desk agent see when a ruleset matches?
The agent sees a simple Do Not Rent alert and contacts a manager. The alert does not display the offense or full report. Authorized managers and owners can review the result and verify the match.
Would screening automatically refuse a guest?
No. A potential match requires manager review. The manager verifies identity and context and follows the hotel’s written policy and applicable requirements before deciding how to proceed.
Explore the optional add on
Bring your screening policy into the check in you already use
See how automatic rulesets, a simple front desk alert, and manager only report access work together in Guest Ban.
Explore criminal background screening
