Guest Safety Claims and Foreseeability on the Premises

An establishment does not guarantee a guest's safety, and the criminal act of a stranger is generally the responsibility of the person who committed it. There is a recognized exception. Where the operator knew or should have known of a risk and did not take reasonable measures against it, the harm can be attributed to the operator as well. The whole argument in these cases sits inside the phrase should have known.

What the claim consists of

The elements are the ordinary ones: a duty owed to this person on this property, a breach of that duty, causation, and damages. A registered guest is owed the highest of the categories most states recognize, because the guest is on the property by invitation for the operator's commercial benefit. Someone crossing a parking lot as a shortcut is owed considerably less, and the boundary is drawn by statutes and cases addressing trespassers.

Duty and breach are usually argued together, because the content of the duty depends on what was foreseeable. A property in a location with no history of violent crime, with functioning locks and adequate lighting, owes ordinary care and has probably met it. The same property after a series of assaults in its parking lot owes something more specific, and the question becomes what it did after the first one.

How foreseeability is proved

Two approaches dominate, and states divide between them. The prior similar incidents approach asks whether crimes of the same general type occurred on or near the premises closely enough in time and place to put the operator on notice. It is a demanding test, and it produces the uncomfortable proposition that the first victim rarely recovers. The totality of the circumstances approach is broader, allowing the nature of the business, its location, the design of the property, the hours of operation and general crime data to be weighed together.

Several states blend the two, using prior incidents as the primary evidence while allowing other factors to fill gaps. What all versions share is a preference for records over impression: police calls for service to the address, the establishment's own incident reports, security logs, and complaints from guests and staff. Discovery in these cases is largely a fight about how far back those records go and how they were kept.

What reasonable measures look like

The standard is proportionality, not maximum security. Courts have not required guards, and they have not required a specific technology. What recurs in the cases is the unglamorous set: functioning locks on room and exterior doors, controlled access after hours, lighting in parking areas and walkways, key control so that a departed guest's key no longer opens a door, staff trained to respond to disturbances, and a practice of actually removing people who are behaving in a way the operator is entitled to act on.

That last measure is often overlooked. Lodging statutes give an operator a specific power to require a disorderly person to leave, described in removing a guest who has become a trespasser. An operator that repeatedly logged complaints about a person and never used that power has documented both the foreseeability and the failure to act, which is the worst combination available.

Statutory safe harbors and what they do

Several legislatures have responded by prescribing measures and attaching a presumption. A recent pattern lists items — recorded cameras at entry and exit points with a minimum retention period, lighting to a specified level in parking areas, deadbolts and window locks, peepholes, controlled pool access, a crime prevention assessment by law enforcement, and security training for staff within a set period after hire — and gives a property that substantially implements them a presumption against liability for third-party criminal acts.

Those statutes are usually written for a defined property category rather than for lodging generally, so their direct application has to be checked against the definition. Their broader significance is that they set out, in one place, what a legislature considers reasonable, and a plaintiff's expert will use the same list against a property that has none of it. A presumption is also not immunity; it shifts the burden and can be rebutted.

Causation, apportionment and the file that decides it

Causation is the second real battleground. The defense argument is that the criminal act would have happened regardless of the measure said to be missing, and it succeeds where the connection is loose. It fails where the mechanism is direct: a door that could not latch, a key that was never deactivated, an unlit stairwell where the attack occurred. Plaintiffs who can tie a specific failure to the specific entry point tend to survive summary judgment.

Apportionment then reduces what is recovered. Most states divide responsibility among the operator, the criminal actor and the guest, and a guest's own conduct can carry a share. Damages caps and thresholds vary widely, as does whether the criminal actor's share is collectible in practice, which is usually the reason the operator is a defendant at all.

Both sides live on the same documents: incident reports, calls for service, maintenance tickets for locks and lighting, key system audit trails, camera retention settings, staffing records for the shift, and training files. Establishments that keep those in order defend these claims well, and the same records support compliance with the physical safety requirements in state lodging statutes and with the room-level obligations described in accessible rooms and how they must be held. Where a property is branded but independently operated, the further question of who answers for the failure is examined in hotel brands, operators and who answers for the property.