Premises-Liability Litigation: Experts and the Document Record

By John Mahoney · June 2026 · 9 min read

A slip-and-fall or inadequate-security case rarely turns on what the plaintiff felt — it turns on what the owner or occupier knew, when they knew it, and what they did about it. That makes premises liability a documents case before it is an expert case. The incident report, the surveillance video, the inspection and maintenance logs, the sweep sheets, the prior-incident history, the work orders, and the security and staffing records are where duty, notice, and causation are actually proven or disproven. The expert — a safety engineer, a building-code consultant, a security criminologist, a flooring specialist — is the witness who reads that record against a standard of care and tells the jury what it means. But the expert is only as strong as the record they were given, and the record is only as useful as your ability to verify what each page actually says.

This guide walks through the document record a premises case is built on, the duty-notice-causation spine that organizes it, the expert disciplines that carry different fact patterns, how the opinions get attacked, and the signals that separate a strong case from a weak one — for plaintiff and defense attorneys evaluating a premises file.

Disclaimer: This article is for informational purposes only and does not constitute legal advice. The duty owed, the notice standard, the open-and-obvious doctrine, comparative-fault rules, and the controlling expert-admissibility standard all vary by jurisdiction and by the facts of each case. Always verify the controlling law and the underlying record before relying on any generalization.

The Document Record — Where a Premises Case Is Won or Lost

Premises liability is unusually document-driven because the central questions — did the owner know of the hazard, should they have known, and did they meet their own standard of care — are answered by the records the property generates in the ordinary course. The credibility of any expert opinion, on either side, rises or falls with the completeness and integrity of that record:

• The incident report. The first written account of the event — who responded, what the hazard was, how long it had been present, what the witness statements say, and (critically) what the property's own employee characterized at the time. Internal characterizations made before counsel is involved are often the most candid evidence in the file.
• Surveillance video. When it exists, video can establish the hazard's duration, whether employees walked past it, and the mechanism of the fall directly — and when it does not exist, has gaps, or was overwritten, its absence (and any spoliation question) becomes its own issue.
• Inspection and maintenance logs. The records that show whether the property actually did what its own policies required. Gaps, after-the-fact entries, or logs that conflict with the video are where notice fights are won.
• Sweep sheets and floor-care schedules. In retail and grocery cases, the documented inspection cadence is the spine of the notice analysis — the question is whether the last documented sweep was real and whether the interval was reasonable for the conditions.
• Prior-incident history. Earlier falls, complaints, or assaults at the same location or under the same conditions go directly to whether the hazard was foreseeable and whether the owner was on notice of a pattern.
• Work orders and repair records. Open or repeated work orders on the same defect — a known leak, a failing handrail, a broken light — are some of the strongest notice evidence available, because they are the owner's own record of a problem left unfixed.
• Security and staffing records. In negligent-security cases, the guard post orders, patrol logs, staffing rosters, camera-maintenance records, lighting surveys, and police call history establish what protection existed and whether it matched the known risk.

The practical lesson for the attorney: much of this record is perishable or routinely overwritten, and a preservation letter that locks down the video, the maintenance and sweep logs, the work-order system, and the prior-incident reports in the first days is often worth more than any single expert retention later.

The Duty–Notice–Causation Spine

A premises opinion is a chain, and each link has to hold against the record. The analysis — for both sides — moves through a sequence the other side will test link by link:

1. Duty and status. What duty was owed, which often depends on the entrant's status (invitee, licensee, trespasser) and the jurisdiction's framework. The duty defines the standard the rest of the case is measured against.
2. The hazard and the standard of care. Was there a dangerous condition, and what did the applicable standard — a building or life-safety code, an industry safety practice, the property's own policies — require the owner to do about it? This is where the safety or code expert does their work.
3. Notice. The heart of most premises cases. Actual notice means the owner knew of the specific hazard; constructive notice means the hazard existed long enough that a reasonable owner should have discovered and remedied it. Duration is the pivot — the sweep sheet, the video timestamp, and the maintenance log are what prove or disprove it. The mode-of-operation rule, where it applies, can shorten or sidestep the notice burden when the business's chosen method of operation makes recurring hazards foreseeable.
4. Defenses to duty. The open-and-obvious doctrine and comparative-fault arguments test whether the hazard was one the plaintiff should have avoided — and whether the owner should nonetheless have anticipated harm despite the obviousness.
5. Causation. Tie the breach to the injury: did the unaddressed hazard actually cause this fall or this assault, and are the mechanism and forces consistent with the claimed injuries — sometimes a human-factors or biomechanics question that belongs to a separate expert.

A clean chain reasons from the preserved record to a conclusion with each standard identified and each notice inference tied to a dated document. A weak chain substitutes assertion for the record at one of these links — an assumed inspection interval, a notice claim with no duration evidence, a standard of care the expert cannot anchor to a code or a recognized practice — and hopes no one checks. The cross-examination, and the admissibility motion, target exactly those substitutions.

The Expert Disciplines — and Matching Them to the Facts

Premises cases draw experts from several distinct fields, and the qualification fight starts with which discipline actually fits the hazard at issue. The recurring mistake is retaining a generalist where the facts call for a specialist — or letting one expert reach across disciplines they cannot support.

Safety and human factors

Safety engineers and human-factors specialists address whether a condition created an unreasonable risk, whether warnings and guarding were adequate, and how a reasonable person would have perceived and reacted to the hazard. Human-factors testimony — on visibility, expectancy, and distraction — is often what answers the open-and-obvious question on its merits rather than by assumption.

Building-code and architecture

Code and architecture experts measure the as-built condition against the applicable building code, life-safety code, and accessibility standards — stair geometry, riser and tread uniformity, handrail height and continuity, ramp slope, guard heights, and illumination levels. A code violation is powerful because it supplies an objective, externally defined standard of care rather than the expert's own opinion of what was reasonable.

Premises-security criminology

In negligent-security cases, security and criminology experts assess foreseeability (often through prior-incident and area crime history), the adequacy of the security measures actually in place against that risk, and whether reasonable measures would have prevented the harm. The discipline is heavily records-dependent — police call data, prior incidents, post orders, and patrol logs do the work.

Flooring and coefficient-of-friction

In slip cases, flooring and tribology experts test the walking surface — its slip resistance and coefficient of friction, the effect of contaminants and finishes, and whether the surface met recognized slip-resistance standards under the conditions present. This is the discipline most exposed to method and measurement challenges, because the test must replicate the real-world condition to mean anything.

The recurring qualification trap is scope: a flooring expert is not a code expert, a code expert is not a security criminologist, and none of them is automatically a human-factors or biomechanics witness. Match the expert's demonstrated expertise to the specific opinions the case actually needs, and keep each one inside their lane.

How the Opinions Get Attacked

Premises opinions are routinely the subject of reliability and foundation challenges, and the attack is almost always aimed at the gap between the record and the conclusion rather than at the discipline itself. The recurring lines of attack:

• Notice by assertion. A claim that the owner had notice with no duration evidence — no video timestamp, no sweep-sheet gap, no prior-incident record — to support how long the hazard was present.
• An unanchored standard of care. An opinion on what the owner "should have done" that is not tied to a code, a recognized industry practice, or the property's own written policy — the expert's personal preference dressed as a standard.
• Unrepresentative testing. Coefficient-of-friction or lighting measurements taken under conditions that do not replicate the incident — a dry test for a wet fall, a measurement of a resurfaced floor, a daytime survey of a nighttime assault.
• Foreseeability gaps. In security cases, a foreseeability opinion built on crime data that is not actually comparable in type, location, or time period to the incident.
• Cherry-picking the record. Crediting the logs and statements that help the retaining party while ignoring the video, work order, or prior-incident report that cuts the other way, without a principled reason.
• Reaching beyond the discipline. A code expert opining on human perception, a flooring expert opining on adequate staffing, a security expert opining on injury causation.

The reliability inquiry is foundation- and methodology-focused, and the strongest defense against exclusion is an opinion that anchors the standard of care to an external source, ties every notice inference to a dated document, tests under representative conditions, and grounds each step in the preserved record. The strongest attack is a record showing the opinion rests on an assumption the documents do not support.

Strong Signals vs. Weak Signals — for Both Sides

Both sides screen the same record for the same tells, and the factors separating a strong premises case from a vulnerable one are largely symmetrical.

What strengthens a premises case

• Documented duration of the hazard — a video timestamp, a sweep-sheet gap, or a maintenance log — that pins the notice question to dates and times.
• A standard of care anchored to an applicable code, a recognized industry practice, or the property's own written policy.
• Prior-incident or work-order history showing the same hazard was known and foreseeable.
• Expert testing performed under conditions that replicate the incident, with disclosed methods.
• An expert opining squarely within their demonstrated discipline, consistent with the rest of the record.

What weakens a premises case

• A notice claim with no duration evidence, or sweep and inspection logs that conflict with the video.
• A standard of care that rests on the expert's personal opinion rather than any external benchmark.
• Surveillance footage missing, gapped, or overwritten — a preservation and spoliation problem — with no explanation.
• Slip-resistance or lighting measurements taken under conditions that do not match the incident.
• An expert reaching beyond their field, or an opinion that ignores unfavorable documents without a principled reason.

Notice usually decides the premises case — so the disciplined work for either side is to separate the links carried by dated, objective records from the links carried by assertion, and to attack or defend the opinion at exactly those joints.

Why a Verifiable, Page-Cited Review of the Underlying Records Matters

A premises case is built on a stack of documents — the incident report, the inspection and maintenance logs, the sweep sheets, the work-order history, the prior-incident reports, the security post orders and patrol logs, the expert reports on both sides, and the deposition transcripts of the corporate representative and the responding employees. The opinions are only as good as those underlying records, and the case is won or lost on whether each claim is actually grounded in them. That makes the document-review step decisive: which timestamp on which page of the sweep log proves the inspection interval, what the responding employee actually wrote in the incident report before counsel arrived, where the opposing expert quietly assumes a standard the code does not impose, and whether a corporate-representative deposition admission contradicts the written maintenance policy.

This is exactly where a verifiable, page-cited AI review earns its place. MedLegal AI reviews the full record and ties every finding back to the exact source page — so when the system flags a gap in the sweep log, a work order that predates the fall, or a notice assumption the transcript undercuts, you can click straight to the page and confirm it. Nothing is asserted without a citation, which is the difference between a usable cross-examination outline and an AI summary you cannot trust. The platform supports non-medical cases — including premises-liability and negligent-security files — and connects litigators to a network of non-medical expert witnesses.

Bottom Line

Premises liability is a documents case before it is an expert case. Duty, notice, and causation are proven or disproven in the incident report, the surveillance video, the inspection and maintenance logs, the sweep sheets, the prior-incident history, the work orders, and the security and staffing records — and the expert, whether a safety engineer, a code consultant, a security criminologist, or a flooring specialist, is only as strong as the record they were handed. The duty-notice-causation spine runs from the standard of care through actual and constructive notice to causation, and each link is a place the other side will press. Discipline matters, but scope matters more, and the foundation attack almost always targets the gap between the preserved record and the conclusion.

For both sides, the work is the same: confirm what was preserved and when, separate the links carried by dated records from the links carried by assertion, anchor the standard of care to an external benchmark, pin the notice question to documented duration, and keep each expert inside their demonstrated discipline. The record should decide the case — so verify every claim against the actual documents, page by page.

Questions? Contact us at [email protected] or (856) 979-6525