our oklahoma personal injury attorneys handle negligent security claims across Oklahoma, where the core legal question is whether a property owner’s failure to maintain adequate security was a contributing cause of a foreseeable criminal attack. This resource is a practitioner-facing issue spotter covering what facts at intake signal this theory, what records to request immediately, and what the foreseeability analysis requires before filing. The overview of negligent security liability in Oklahoma covers the legal framework; this guide focuses on the intake and evidence questions attorneys need to work through before the complaint goes out.
Intake triggers: what facts signal a negligent security analysis
Not every crime on someone else’s property becomes a viable civil claim. At intake, look for facts that suggest the owner knew or should have known that criminal activity was a risk and failed to take reasonable steps to address it. Common triggers include:
- The crime occurred on commercial or multi-unit residential property where the owner controlled access points, lighting, and surveillance systems
- The client is an invitee with a commercial or public invitation, which means the owner owes the highest duty of care; the property owner liability FAQ explains how Oklahoma courts distinguish invitee, licensee, and trespasser status
- Prior crimes at the same property or nearby have been documented in police call logs, incident reports, or management records in the years preceding the attack
- The physical security infrastructure, including locks, lighting, cameras, or staffed guard positions, was visibly inadequate, non-functional, or absent at the time of the incident
- Management had received written complaints from tenants, guests, or employees about security conditions before the attack occurred
When two or more of those facts appear, pursue the negligent security theory alongside any direct-negligence or premises liability claims. Use the premises liability intake checklist to run the full visitor-status and evidence inventory at the same time.
Foreseeability: the element that controls everything else
Foreseeability is the predicate for duty in every negligent security case (Cornell Law’s foreseeability overview sets out the general doctrinal frame). The controlling Oklahoma Supreme Court authority is Bray v. St. John Health System, Inc., 187 P.3d 721 (Okla. 2008), which adopted Restatement (Second) of Torts § 344 comment f in full and disapproved earlier Court of Civil Appeals decisions reading duty narrowly. Under Bray, duty arises when the owner “knows or has reason to know, from past experience, that there is a likelihood of conduct on the part of third persons in general which is likely to endanger the safety of the visitor.” Post-Bray, Lewis v. Wal-Mart Stores, 225 P.3d 6 (Okla. Civ. App. 2009), held Oklahoma does not require proof the owner foresaw “the exact crime or the specific location” of injury. Oklahoma is best characterized as a § 344 comment f / hybrid foreseeability jurisdiction: prior similar incidents are highly persuasive but not an absolute threshold predicate.
Look first for documented prior similar incidents at the property or in the surrounding area. Look for police call logs (three to five years before the incident, via open records request), management incident reports, on-site security guard shift reports, written tenant or guest complaints, and maintenance work orders for security equipment in the area where the crime occurred. Even a pattern of lower-level crimes (vandalism, trespass, vehicle break-ins) can establish foreseeability for a subsequent assault if the property type and crime pattern are consistent. The negligent security claims FAQ covers how Oklahoma courts weigh prior incident evidence in duty and proximate cause analysis.
What to look for in CCTV, lighting, and security personnel records
Security infrastructure records are often the most direct evidence of whether the owner met the reasonable care standard. Request the following in your initial preservation demand, sent within the first week of signing the client.
Surveillance and camera systems: Request the system vendor name, installation date, camera count and placement diagram, last maintenance date, and the retention schedule. The key question is whether cameras were functional during the incident and whether footage covering the relevant area was preserved before the overwrite cycle ran. Most commercial systems operate on 30-day rolling overwrite cycles, though some properties run shorter windows. The security camera footage FAQ outlines what to demand and how Oklahoma courts have addressed spoliation when footage is not preserved after notice.
Lighting: Obtain the owner’s lighting maintenance log, any work orders for burned-out or non-functioning fixtures in the area where the crime occurred, and photographs taken by responding officers showing illumination conditions at the scene. Where the jurisdiction has minimum foot-candle requirements for parking areas or building entries, building code compliance records establish the measurable standard.
Security personnel records: If the property employed guards, request staffing schedules for the 30 days before the incident, post orders describing guard duties and patrol routes, training certifications, and the security contractor’s full contract. An understaffed patrol schedule or a contract giving the security company broad discretion to reduce coverage without notice can be as probative as the complete absence of guards. For the notice-of-deficiency record structure, see the notice proof documentation guide.
Common fact patterns that generate negligent security claims
Negligent security claims concentrate in settings where property owners control access and have an ongoing commercial relationship with those they invite onto the premises. The Bureau of Justice Statistics tracks victimization data showing that violent and property crimes disproportionately occur at commercial and residential locations where security measures are within the owner’s control. Common fact patterns include:
- Apartment complexes: Tenants and guests attacked in stairwells, parking structures, or common areas where management knew of broken entry-point systems, inadequate lighting, or prior assaults. See landlord liability for common area injuries in Oklahoma for the duty-of-care framework in residential settings.
- Hotels and motels: Guests assaulted in rooms with non-functioning security hardware or in parking areas with inadequate lighting or limited camera coverage. Ask whether management had flagged known deficiencies in any prior security review.
- Parking lots and structures: Lighting levels, camera placement, and staffed security collectively determine whether the owner took reasonable precautions for the known crime environment. Prior incident reports from the same parking area, even for vehicle break-ins, are often the most direct foreseeability evidence available.
- Bars and nightclubs: Operators who fail to control known violent patrons face civil exposure in negligent security alongside any dram shop theory. Ask whether management had previously ejected the assailant and failed to prevent re-entry, or whether prior altercations at the same venue were documented by security staff.
- Retail stores and shopping centers: Inadequate lighting or absent surveillance at locations with documented prior crime. CDC violence prevention data identifies assaults as a leading cause of injury-related emergency department visits, supporting foreseeability arguments at high-traffic commercial locations with a history of prior incidents.
CPTED analysis as a framework for expert testimony
Crime Prevention Through Environmental Design (CPTED) is a methodology used by security experts to evaluate whether a property’s physical design and management practices reduced or increased criminal opportunity. A CPTED-trained expert can assess whether lighting, sightlines, access control, and territorial signage at the property met security design standards for the property type and known crime environment.
Key CPTED concepts include natural surveillance (visibility-supporting lighting and design), access control (entry barriers and management), and territorial reinforcement (signage distinguishing public from restricted space). A documented CPTED-design failure moves expert testimony beyond a simple prior-incident count toward a systematic security-design analysis.
When preparing an expert, build the evidentiary foundation through the evidence preservation checklist first, then layer in CPTED methodology connecting physical conditions to the owner’s failure to act.
Foreseeability proxies when prior incident records are thin
Many property owners, particularly small landlords and independent operators, maintain poor incident records. When the management file is sparse, look to these proxies:
- Area crime statistics and 911 call data for surrounding blocks establish elevated crime risk for the property type and location, supporting a reasonable-care argument even without on-site incident reports.
- Industry security standards from hotel associations, apartment industry groups, and retail loss-prevention organizations describe baseline practice; a material gap is probative of negligence independent of prior incidents.
- Security audit reports commissioned by the owner are among the highest-value documents when the owner’s own consultant flagged the risk and the owner failed to act. Request audits and risk assessments for the five years preceding the incident.
- Insurance loss-control correspondence sometimes flags security deficiencies, demonstrating the owner received direct notice from its own insurer.
Damages, comparative fault, and the limitations period
Compensatory damages follow the same categories as any personal injury claim: medical expenses, lost wages and reduced earning capacity, and non-economic damages for pain, suffering, and emotional distress. Serious attacks including stabbings, shootings, and sexual assaults frequently produce catastrophic injuries with long-term care needs and permanent impairment. For the non-economic damages calculation framework applicable to these claims, see how pain and suffering damages are calculated in Oklahoma.
Punitive damages. Under 23 O.S. § 9.1, Category I punitives require clear and convincing evidence of “reckless disregard for the rights of others” (defined in Therrien v. Target Corp., 617 F.3d 1242 (10th Cir. 2010), as conduct creating “a substantial and unnecessary risk… a high probability that the conduct would cause serious harm to another person”). No Oklahoma state appellate decision has affirmed a § 9.1 punitive award in a negligent-security case; the theory is record-driven. Build the file around § 9.1(A)’s factors (awareness of the hazard, duration of misconduct, response upon discovery, and number of employees involved) through prior-incident logs, security audits, internal memoranda, tenant complaints, and management communications.
Comparative fault. Defense counsel will argue the claimant assumed the risk of the location, provoked the altercation, or was present for a purpose unrelated to the commercial invitation. Under 23 O.S. § 13, a claimant whose assigned fault is less than 50% recovers, with damages reduced proportionally; assigned fault of 50% or more bars recovery. The partial fault FAQ details how the reduction operates in premises cases.
Several liability and the criminal co-defendant. 23 O.S. § 15 makes fault-based liability several only: each defendant pays its proportionate share. The statute contains no express intentional-tort exception, and Oklahoma appellate authority has not squarely decided whether “fault” under § 15 reaches intentional criminal conduct for apportionment between a negligent property owner and a criminal co-defendant; the question is unsettled. A jury allocation to a judgment-proof criminal can sharply reduce recovery. The doctrinal counterargument grounded in Mansfield v. Circle K, 1994 OK 80, and Graham v. Keuchel, 1993 OK 6 (intentional or willful conduct differs in kind from negligence and cannot be apportioned on the same percentage scale) is plausible but untested in this context. The operative trial strategy is to prove the owner’s security failures were a substantial, foreseeable cause and resist superseding-cause framing under Oklahoma’s foreseeability doctrine. Warn the client about collectability before contingency engagement.
Under 12 O.S. § 95, the limitations period for negligent security personal injury claims is two years from the date of injury. Flag any government property ownership at intake: notice requirements under the Governmental Tort Claims Act can materially shorten the effective window. The Oklahoma statute of limitations for personal injury covers deadline exceptions that apply when claimants are minors or when the discovery rule tolls the period.
Intake questions that sharpen the issue-spotting analysis
These questions help identify evidentiary gaps early and give the client a realistic picture of the claim’s strength before the investigation fully opens.
- Was the client an invited guest, tenant, or customer of the property? Trespasser status is a threshold issue defense counsel will raise immediately. Confirm the basis for the client’s presence and whether the owner had prior notice the client would be there.
- Had anything similar happened at this location before? Ask whether the client was aware of any reputation for danger, prior incidents they had heard about, or visible security problems on prior visits. Anecdotal client knowledge helps direct the initial records request.
- What security was visible on site? Ask whether the client observed guards, whether cameras appeared functional, whether lighting in the area was working, and whether entry points were locked or controlled. These observations help identify specific security failures without waiting for formal records.
- Was a police report filed? The responding officer’s report establishes a contemporaneous record of scene conditions and witness statements. Obtain it immediately. The responding agency’s complete call log for the property address over the preceding years is a separate public records request that establishes the prior incident pattern.
- Who controls the property? Identify whether ownership is held by an individual, LLC, management company, or institutional operator. Early defendant identification allows you to direct parallel preservation demands to the right parties before overwrite cycles and routine records purges eliminate the most probative evidence.
After intake, send the preservation demand by certified mail to the property owner and its liability insurer, submit a public records request for police call logs at the property address, and canvass the scene while conditions match the incident. Our firm integrates this sequence with the premises liability intake checklist for pre-filing workflow on property-owner claims in Oklahoma.
