Assaulted in Baltimore? Negligent Security Liability in Maryland

When an assault becomes a negligent security case

Some assaults happen in settings where the owner or operator has responsibilities tied to keeping the premises reasonably safe. A negligent security claim is usually a premises-liability theory alleging the business or property operator did not take reasonable security precautions in light of known or knowable risks, and that lapse contributed to the harm (see generally Scott v. Watson (Md. 1976)).

These claims often arise in places such as:

• Apartment complexes and student housing (especially common areas)
• Bars, clubs, and event venues
• Hotels and motels
• Convenience stores and shopping centers
• Parking lots and parking garages
• Office buildings with controlled access

Negligent security cases are highly fact-specific. A central question is whether violent crime was sufficiently foreseeable to require additional precautions, and whether reasonable precautions could have reduced the risk (see Hemmings v. Pelham Wood (Md. 2003)).

Who can be responsible (it is not always just the property owner)

Depending on how the location is owned and operated, responsibility may involve more than one entity, including:

• The property owner (including a holding company in some structures)
• A property management company
• A tenant business (for example, a bar leasing the space)
• A contracted security vendor or guard company
• An event promoter or venue operator

Identifying the right defendants early matters because key evidence (video, incident reports, access-control records, staffing schedules) is often controlled by the businesses involved and can be lost in the ordinary course if not preserved.

What you generally must prove in a Maryland negligent security claim

Negligent security claims typically track standard negligence concepts: duty, breach, causation, and damages. Maryland appellate decisions addressing criminal acts on premises commonly focus on foreseeability, the reasonableness of precautions, and whether the alleged security lapse is connected to the injury (see Scott v. Watson (Md. 1976); Troxel v. Iguana Cantina (Md. Ct. Spec. App. 2011)).

• Duty of care: Whether the owner or operator owed you a duty to use reasonable care under the circumstances.
• Breach: Whether security measures were unreasonable in light of the risk (for example: broken locks, inadequate lighting, non-functioning access controls, or security practices not followed).
• Causation: Whether the lapse in security likely played a meaningful role in allowing the assault to occur or escalate.
• Damages: The harm you suffered (medical bills, lost income, pain and suffering, etc.).

Foreseeability: the fact pattern that often drives liability

Foreseeability is frequently the engine of a negligent security case. Depending on the location, evidence that may support foreseeability can include:

• Prior violent incidents at the same property
• Repeated police calls for service at or near the property
• Prior complaints from tenants, patrons, or employees about safety issues
• A known pattern of altercations connected to the business (for example, recurring fights tied to a bar’s closing time)

Common security failures that may matter (depending on the facts)

Examples that can be relevant in Baltimore premises cases include:

• Broken gates, locks, or door hardware not repaired within a reasonable time
• Uncontrolled access to “secured” buildings or garages (propped doors, broken key fobs)
• Inadequate lighting in stairwells, entryways, and parking areas
• Cameras that do not work, do not record, or are poorly positioned
• Insufficient staffing or monitoring during known high-risk times
• Failure to follow internal safety policies or respond appropriately to repeated disturbances

What to do after an assault (health first, then evidence)

Your safety and medical care come first. If you can do so safely, steps that often help preserve evidence include:

• Get medical attention promptly and follow up; records can document injuries and symptoms that develop later.
• Report the incident to police and request the report number.
• Report the incident to the property or business and request an incident report.
• Photograph or video the scene (lighting, entry points, broken locks or gates, posted rules).
• Collect witness names and contact information.
• Preserve clothing and personal items in their post-incident condition where relevant.
• Write down what you remember while it is fresh (timeline, locations, staff responses).

Timing: do not ignore Maryland deadlines

Many Maryland civil claims are subject to a three-year statute of limitations, though the correct deadline can depend on the specific claims and parties involved. If you are considering a claim, it is wise to get case-specific advice promptly (see Md. Code, Cts. & Jud. Proc. § 5-101).

Anticipating common defense arguments (Maryland-specific issues)

Defendants and insurers often contest negligent security cases by arguing:

• The assault was not reasonably foreseeable.
• Security measures were reasonable under the circumstances.
• The attacker, not the property, caused the injury.
• Even different security would not have changed the outcome (causation).
• You were contributorily negligent or assumed the risk.

Maryland remains a contributory negligence jurisdiction, meaning certain findings of plaintiff negligence can bar recovery in many negligence cases (see Coleman v. Soccer Ass’n of Columbia (Md. 2013)). Assumption of risk is also commonly litigated (see ADM P’ship v. Martin (Md. 1997)).

FAQ

Do I have a case if the attacker was never caught?

Possibly. A negligent security claim focuses on the property-side conduct (foreseeability, reasonable precautions, and causation), not only the identity of the attacker.

What kind of evidence helps show foreseeability?

Prior violent incidents, repeated calls for service, prior complaints, and documented safety issues can matter, depending on the location and facts.

How long do businesses keep surveillance video?

It varies. Some systems overwrite in days or weeks, which is why early preservation requests can be important.

Is there a deadline to file in Maryland?

Many civil claims are subject to a three-year deadline under Md. Code, Cts. & Jud. Proc. § 5-101, but exceptions and different rules may apply. Get case-specific advice as soon as possible.

Talk to a Baltimore negligent security attorney

If you believe inadequate security contributed to an assault, consider getting legal guidance early, especially when video and records may be time-limited. Contact our team to discuss next steps and evidence preservation.

Maryland-specific disclaimer: This post is for general informational purposes only and is not legal advice. No attorney-client relationship is created by reading or contacting us through this page. Maryland law (including deadlines and defenses) is fact-sensitive and may change; consult a qualified Maryland attorney for advice about your specific situation.