Foreseeability in negligent security claims is the one question that decides almost every Nevada case. It is not whether the attack happened or how badly the victim suffered. Instead, it is whether the property owner should have seen it coming. Nevada calls that foreseeability. People new to these claims tend to treat it as a rhetorical point. They picture something a lawyer argues at the end of a case in front of a jury. In fact, it is not. Rather, foreseeability is a proof problem. It comes out of records, dates, addresses, radii, incident logs, post orders and staffing sheets. The side that gathers those documents first usually controls how the case turns out.
That matters more in Southern Nevada than almost anywhere else, because the property mix here is unusual. Resort corridors, twenty four hour taverns, sprawling surface lots and multi level garages. Apartment complexes with open breezeways and convenience stores that never close. The volume of foot traffic is enormous, and the documented police activity attached to individual addresses runs just as high. That documentation is the raw material of a foreseeability case, and it is public, retrievable and time sensitive.
What Nevada Law Requires Before a Property Owner Pays for a Stranger’s Crime
Start with the statute that governs lodging properties. It is the most explicit rule in this area of Nevada law. NRS 651.015 covers the owner or keeper of a hotel, inn, motel, motor court, boardinghouse or lodging house. Under it, that owner is not civilly liable for a patron’s or other person’s death or injury on the premises in one situation. Specifically, that is where the cause was someone who is not an employee under the owner’s control or supervision. The rule has an exception with two parts. First, the wrongful act that caused the death or injury was foreseeable. Second, a preponderance of the evidence shows the owner did not exercise due care for the person’s safety on the premises. Injuries on resort property follow their own playbook, which our Las Vegas Strip injury lawyer page walks through.
The statute then flips the frame. It states affirmatively that the owner is liable in a defined case. That is where the act was foreseeable and the owner failed to take reasonable precautions against it. Two features of NRS 651.015 do a lot of quiet work in real litigation.
Who decides foreseeability and what the statute rules out
First, the statute assigns the foreseeability question to the judge. It says the court shall determine as a matter of law whether the wrongful act was foreseeable. The court also decides whether the owner or keeper had a duty to take reasonable precautions. In practice, the fight over foreseeability in negligent security cases at a lodging property often happens on a written motion. It plays out on a paper record before any jury ever hears a word. If the crime history record is thin at that stage, then there may be no trial at all.
Second, NRS 651.015 defines when an act is not foreseeable. Under the statute a wrongful act is not foreseeable unless one of two things is true. Either the owner failed to exercise due care for the safety of the person on the premises. Or prior incidents of similar wrongful acts occurred on the premises. The owner must also have had notice or knowledge of those incidents. That second path is the reason prior crime evidence is the center of gravity in these claims. In other words, the statute is telling you what to go find.
Properties outside the lodging statute
Of course, many properties are not lodging establishments. Those include apartment complexes, shopping centers, standalone parking structures, office buildings and retail stores. Ordinary Nevada premises liability principles govern them rather than NRS 651.015. The analysis still runs through foreseeability. Nevada courts examine the totality of the circumstances around the property rather than mechanically counting identical past crimes. The evidence you gather looks much the same either way. Our overview of negligent security claims in Nevada walks through how the duty analysis differs by property type.
Calls for Service History Pulled by Address and by Radius
The first request in a serious negligent security investigation is usually a calls for service history for the address. That comes from the Las Vegas Metropolitan Police Department. Then comes a second, wider pull covering a radius around it. Calls for service records show dispatched police activity tied to a location. They include the date, the time, the call type as coded by dispatch, and often the disposition. They are not the same as crime reports, though, and the difference is important. Calls for service capture activity that never produced a report, an arrest or a conviction. That is exactly the kind of low visibility history a property manager sees every week. It is also the history a defense expert will insist never happened.
Records requests to LVMPD run through the department’s records function. The Records and Fingerprint Bureau publishes its report request procedures, hours and fee structure for the public. Meanwhile, Nevada’s public records law sets the clock. Under NRS 239.0107, the deadline is generally the end of the fifth business day after a written or oral request. The governmental entity can respond in one of four ways. It can produce the record or identify the agency that actually holds it. It can give written notice of the earliest date the record will be available. Or it can deny the request with a citation to the specific statute that makes the record confidential. If the agency withholds a portion as confidential, you have a right to know which legal authority it is relying on. That gives you something concrete to push back against.
Jurisdiction and the format of the data
Two practical notes. First, jurisdiction matters. LVMPD covers the City of Las Vegas and unincorporated Clark County. But North Las Vegas, Henderson, Boulder City and Mesquite have their own police departments. Nevada Highway Patrol handles some corridors too. A garage on the Henderson side of a boundary needs a Henderson request, not a Metro request. Second, ask for the data in a usable export rather than a stack of scanned pages. You can sort, map and chart a spreadsheet with date, time, call type and location. You cannot do that with a PDF, and the difference shows up when you need to present a pattern.
The Property’s Own Incident Reports Are Usually the Stronger Evidence
Police records prove that crime happened nearby. The property’s own records, by comparison, prove that the property knew. That second point is what NRS 651.015 asks about when it refers to notice or knowledge. It is also what a jury actually responds to.
Through requests for production and deposition, several documents are worth chasing. Start with the in house security incident log or daily activity report for a multi year window. Add written incident reports generated by security officers, trespass and ejection records, guest complaint files and front desk logs. Add work orders for broken lighting, damaged gates, failed card readers and inoperable cameras. Then come prior civil claims and demand letters involving assaults at the property, internal risk management memos and insurer loss runs. Finally, ask for any security assessment or survey commissioned by the owner or the insurer. Loss runs and risk assessments are often the single most persuasive documents in the file. They hold the owner’s own numbers from before anyone was thinking about this lawsuit.
In addition, ownership structures in Nevada complicate this. A hotel tower, its garage, its retail spaces and its security staffing can sit under different entities. A management company may operate under contract, with a separate contract security vendor supplying officers. The vendor’s records are frequently better than the owner’s, and the vendor is a separate defendant with separate insurance. The management agreement and the security services contract tell you who was responsible for what. That includes the officer budget and who had authority to increase coverage. When the assault occurred in a structure, see our discussion of parking garage assault claims in Nevada. It covers how to sort out those control questions.
Post Orders, Staffing Schedules and Camera Coverage Maps
Once you have shown the property knew, the case shifts to whether the precautions were reasonable. That is a documents question too. Post orders are the written instructions telling officers what to do and where to be. They cover patrol frequency, required rounds, response protocols and escalation. Compare the post orders to the actual staffing schedule and the timecards for the shift in question. Suppose the post orders call for a roving garage patrol every thirty minutes. Suppose the timecards show one officer covering three towers and a garage on a Saturday night. Then that property has a problem that does not require expert opinion to understand.
Camera coverage, meanwhile, is the other half. Ask for the camera map or system schematic and the retention policy. Ask for the maintenance log and any list of known inoperable cameras too. Some cameras record but never get monitoring. Others point at cash handling areas and not at the stairwells where attacks happen. Those tell a story about what the property was actually protecting. Lighting is similar. Photometric plans, lighting maintenance records and repeated work orders for the same dead fixture all matter. They connect directly to the conditions on the night of the attack.
Preservation is especially urgent here. Surveillance systems commonly overwrite on a short cycle, sometimes within a few weeks. Access control and card reader data can purge faster than video. A written preservation demand identifying specific cameras, specific time windows and specific systems should go out immediately. Destruction of evidence after notice can support an adverse inference against the party that lost it. Hotel claims raise this issue constantly. Our page on whether you can sue a hotel for negligent security addresses how to frame those requests.
Security Industry Standards Testimony and What It Can and Cannot Do
Qualified security experts do two useful things in a Nevada negligent security case. They interpret the crime history as the industry itself does, using recognized methods for assessing risk at a location. They also compare what the property did against what a reasonably prudent operator would have done. That means an operator of a similar property in a similar setting. That comparison covers officer staffing ratios, patrol design, access control, lighting levels and camera placement. It also covers training and supervision, and how the property responded to prior incidents.
What an expert cannot do is manufacture foreseeability out of nothing. Suppose the underlying records show a quiet address with no meaningful prior activity. An expert saying the attack was foreseeable then offers an opinion without a foundation. Under NRS 651.015 that opinion goes to a judge who decides foreseeability as a matter of law. The records come first. The expert then explains them.
How Far Back and How Wide the Crime History Should Reach
This is where these cases are often overbuilt. A three to five year window before the incident is the most common range. It works because it is long enough to show a pattern. It is also short enough that ownership, management and staffing were reasonably stable. Go back ten years and you invite the obvious response. The property changed hands, the operator changed, and the neighborhood changed. None of that old activity has anything to do with the current owner’s knowledge.
Radius works in the same way. Start with the property itself, then the parcel, then a tight ring around it. A quarter mile ring in a dense resort corridor is usually defensible. A one mile ring in metropolitan Las Vegas sweeps in thousands of calls from unrelated properties. It tells a jury nothing except that a city is a city. It also hands the defense an easy argument that you are blaming this owner for the whole valley.
Similarity matters more than volume. Under NRS 651.015 the reference is to prior incidents of similar wrongful acts. Two hundred noise complaints and parking violations do not make a stabbing foreseeable. Nine documented assaults, four robberies and a string of trespass ejections in one garage stairwell over three years does. And it does so with a fraction of the paper. The strongest presentation is almost always narrow, specific and mapped. It ties to the exact location within the property where the attack occurred. And the property’s own records show it knew about each one.
Deadlines and Fault Allocation in Nevada
The filing deadline for a personal injury action in Nevada is two years under NRS 11.190(4)(e). That deadline is shorter than the useful life of a negligent security investigation. That is one reason the records work should start in the first weeks rather than the final months. A government body may own or operate the property, such as a public parking structure or a transit facility. Then a separate framework applies with its own claim requirements and damages limits. It is not the same case as one against a private resort.
Nevada applies modified comparative negligence under NRS 41.141. A plaintiff’s own negligence does not bar recovery on its own. The limit is that it must not be greater than the negligence of the parties from whom recovery is sought. The jury returns both a total damages figure and a special verdict allocating percentages. Expect the defense to argue that the victim ignored a posted warning, had been drinking, or was in the wrong place. Those arguments move percentages. Even so, they do not by themselves end a claim.
Talking to a Nevada Injury Lawyer About Foreseeability in Negligent Security
The Bourassa Law Group offers a free consultation after an assault at a hotel, casino, apartment complex, garage, bar or store. That covers properties across Southern Nevada. The firm reviews what happened and identifies every entity that controlled and staffed the property. It also gets records requests and preservation demands out before the video and the incident logs cycle away. Talking it through costs nothing, and there is no obligation.
This article is general information about Nevada law and is not legal advice. Reading it does not create an attorney client relationship. Every case turns on its own facts, so speak with a licensed Nevada attorney about your specific situation.
1-800-870-8910