Baltimore Negligent Security Claims in Maryland: What You Need to Know

What Is a Negligent Security Claim in Baltimore?

Negligent security generally refers to a premises-liability claim alleging that an owner, landlord, or operator failed to use reasonable care to address foreseeable criminal risks on the property. The allegation is not that the property owner committed the crime, but that inadequate security measures (for the circumstances) contributed to the harm.

Maryland appellate decisions have addressed when property controllers may have duties related to third-party criminal acts, including in common areas under a landlord’s control where the landlord has notice of prior criminal activity. See, for example, Scott v. Watson and Hemmings v. Pelham Wood L.P..

When Property Owners May Be Responsible

These cases are highly fact-specific. In broad terms, Maryland negligent-security claims often turn on what the defendant knew (or reasonably should have known) about the risk and whether their response was reasonable under the circumstances. Maryland courts’ analyses often focus on notice/foreseeability and control over the area where the crime occurred. See Scott v. Watson and Hemmings v. Pelham Wood L.P..

Examples of alleged security failures can include:

• Broken locks, doors, or gates that are not repaired
• Poor lighting in entrances, stairwells, hallways, or parking areas
• Lack of controlled access (for example, known propped doors or failed entry systems)
• Inadequate security staffing for known risk periods
• Non-functioning cameras or lack of monitoring where monitoring is part of the security plan
• Failure to address repeated complaints, prior incidents, or known problem areas
• Inadequate policies for crowd control or patron management

Key Elements: What You Typically Must Prove

Although the exact framing can vary by facts and defendant, negligent-security cases typically require proof of:

• Duty: the defendant owed a duty of reasonable care under the circumstances (often informed by the visitor’s status and the defendant’s control of the premises).
• Foreseeability/notice: the risk of the type of criminal harm was reasonably foreseeable (for example, prior similar incidents or recurring problems). See Scott v. Watson and Hemmings v. Pelham Wood L.P..
• Breach: the defendant failed to take reasonable steps (maintenance, lighting, access control, staffing, policies) given the risk.
• Causation: the breach was a cause of the injury. Defendants often argue the crime was an independent act of a third party; plaintiffs typically focus on whether reasonable measures would have reduced the likelihood or severity of the harm.
• Damages: medical expenses, lost income, pain and suffering, and other losses.

Common Locations for Baltimore Negligent Security Cases

In Baltimore, negligent-security allegations commonly arise in places with significant foot traffic, late-night activity, cash transactions, or known prior calls for service, such as:

• Apartment complexes and multi-unit buildings
• Parking lots and garages
• Nightclubs, bars, and restaurants
• Convenience stores, gas stations, and liquor stores
• Hotels and short-term lodging
• Shopping centers and entertainment districts

Depending on who controlled the premises and security decisions, potentially responsible parties can include property owners, property managers, security contractors, and event organizers.

Evidence That Can Make or Break a Negligent Security Claim

Evidence is often time-sensitive. Important categories include:

• Surveillance video (and proof the system existed and was working)
• Incident reports, 911 call records, and dispatch logs
• Police reports and witness statements
• Maintenance records (locks, doors, lighting, gates)
• Security contracts, post orders, staffing schedules, and guard logs
• Prior incidents (on-site and sometimes nearby), as relevant to foreseeability
• Photographs of lighting, sight lines, broken hardware, and entry points
• Tenant/customer complaints and email communications about safety issues

A prompt written preservation request can be important because footage and logs may be overwritten or discarded as part of ordinary business practices. Spoliation issues can arise in appropriate circumstances. See Klupt v. Krongard.

Damages in Maryland Negligent Security Cases

Depending on the facts, a negligent-security claim may seek compensation for:

• Past and future medical costs (ER care, hospitalization, surgery, therapy)
• Lost income and diminished earning capacity
• Pain and suffering and loss of enjoyment of life
• Emotional distress (including anxiety and post-traumatic symptoms)
• Scarring, disfigurement, and disability-related losses
• Out-of-pocket expenses

Maryland also has a statutory cap on non-economic damages in most personal injury cases, subject to annual adjustments and specific rules for certain claims. See Md. Code, Courts & Judicial Proceedings § 11-108 at mgaleg.maryland.gov.

Defenses Property Owners Often Raise (and How Cases Are Evaluated)

Common defenses include:

• Not foreseeable: no notice of prior similar incidents or no reason to anticipate the crime.
• Reasonable security: measures were appropriate for the location and circumstances.
• Contributory negligence / assumption of risk: Maryland generally follows contributory negligence, which can bar recovery if the plaintiff is found negligent and that negligence contributed to the injury. See Coleman v. Soccer Ass’n of Columbia.
• Third-party criminal act: the criminal actor was the sole cause (often litigated through causation and foreseeability evidence).

Because these issues are fact-driven, early investigation (layout, lighting, access control, staffing, prior incidents, and policies on the date of the event) can be critical.

How Long Do You Have to File a Negligent Security Claim in Maryland?

Maryland’s general statute of limitations for many civil claims is three years. See Md. Code, Courts & Judicial Proceedings § 5-101 at mgaleg.maryland.gov. Wrongful death claims are also subject to a three-year limitations period from the date of death. See Md. Code, Courts & Judicial Proceedings § 3-904(g) at mgaleg.maryland.gov.

Important: If a government entity or employee may be involved, special notice rules and deadlines can apply. For example, the Local Government Tort Claims Act contains a notice requirement that is commonly one year after the injury, subject to statutory exceptions and litigation over good cause. See Md. Code, Courts & Judicial Proceedings § 5-304 at mgaleg.maryland.gov.

FAQ

Is a property owner automatically liable if a crime happens on the property?

No. These cases typically turn on duty, control of the area, and whether the type of harm was reasonably foreseeable, along with whether reasonable security measures were taken.

What if there were no prior crimes on the property?

Lack of prior incidents can make foreseeability harder to prove, but it does not necessarily end the analysis. Other facts (complaints, security failures, recurring dangerous conditions, and the setting) may matter.

What if the business says the video was overwritten?

That is one reason acting quickly matters. Preservation requests and follow-up can be critical, and spoliation issues may be litigated in appropriate circumstances.

Does Maryland’s contributory negligence rule affect negligent security claims?

Potentially. Maryland generally follows contributory negligence, and defendants may argue a plaintiff’s own negligence contributed to the injury. See Coleman v. Soccer Ass’n of Columbia.

Talk to a Baltimore Negligent Security Lawyer

If you were harmed by criminal activity on someone else’s property in Baltimore, you may have potential civil options in addition to any criminal investigation. A negligent-security case often focuses on what was known about the risk, what security measures were in place, and whether reasonable steps could have reduced the likelihood or severity of harm.

Contact us to discuss preserving evidence, identifying potentially responsible parties, and evaluating next steps.

Maryland-specific disclaimer

This article is for general informational purposes only and is not legal advice under Maryland law. Reading this article or contacting us through this website does not create an attorney-client relationship. Deadlines and legal standards can depend on specific facts and can change; you should consult a qualified Maryland attorney about your particular situation.