Oregon Restaurant Bathroom Slip-and-Fall Claims: What Cleaning Logs Can—and Cannot—Show

A cleaning or inspection log can be important after a fall in an Oregon restaurant bathroom. If the record is authentic and complete, it may identify when someone reportedly inspected or cleaned the area, which employee performed the task, and what work was recorded.

But a log is not a liability shortcut. A signed entry does not necessarily prove the floor was safe. A missing or overdue entry does not, by itself, prove how long a spill was present or that the restaurant is legally responsible. Oregon law does not establish that every restaurant must create or retain a bathroom cleaning log.

The useful question is not simply, “Was there a log?” It is how the log fits with the rest of the evidence. A careful analysis keeps five issues separate:

Did restaurant staff or a contractor create the condition?
Did the restaurant actually know about it before the fall?
If it was an unidentified spill, was it present long enough that the restaurant should have discovered and removed it?
Did that condition cause the fall and the claimed injury?
Does the patron’s conduct affect recovery under Oregon comparative-fault law?

Start With Oregon’s Basic Premises-Liability Framework

Oregon’s general premises-liability rule requires a land possessor to use reasonable care to discover conditions that present an unreasonable risk to invitees and to eliminate the condition or provide an adequate warning.

In a foreign-substance case, a claimant generally seeks to show one of three paths: the occupant placed the substance there; the occupant knew it was there and failed to use reasonable diligence to remove it; or the substance remained long enough that the occupant should have discovered and removed it. These paths make the source and timing of the condition central to many Oregon premises-liability claims.

The way a restaurant bathroom is used may inform what precautions are reasonable. Location-specific evidence of recurring sink splash, plumbing trouble, restroom traffic, or known wetness from cleaning may matter. But a general possibility that bathrooms can become wet does not prove that a particular unidentified spill was present long enough to be discovered.

What a Restaurant Bathroom Cleaning Log Can Show

A cleaning log is most useful as part of a timeline. It may supply a recorded data point, but other evidence is needed to test what the entry means.

Recorded inspection times, assigned employees, locations, and tasks

A paper or electronic log may identify:

the bathroom or area reportedly checked;
the time of an inspection or cleaning;
the employee or contractor associated with the entry; and
the task reportedly completed.

Employee schedules and assignments may also show who had inspection, cleaning, maintenance, or complaint-response duties and who had an opportunity to act. That can help identify witnesses and records. It does not establish when an unidentified spill appeared.

A recently signed entry does not necessarily establish that the inspection happened exactly as recorded or that the floor was safe at the time of the fall. At the same time, the mere fact that someone mopped or inspected the bathroom does not establish unreasonable conduct. The details matter.

Consistency—or conflict—with other evidence

A log entry can be compared with:

employee and patron accounts;
staffing schedules and time records;
electronic task systems and communications;
maintenance tickets and plumbing records;
complaints tied to the same bathroom and circumstances;
photographs and contemporaneous observations; and
corridor, entrance, or cleaning-route footage, if any exists.

These comparisons may support or challenge the recorded timeline. For example, a task entry and employee schedule might identify who reportedly cleaned the bathroom shortly before the incident. Evidence about the cleaning method, the amount and source of moisture, drying time, and any signs or barriers would still be needed to understand whether that activity relates to the condition.

Video should not be assumed. A camera may not exist, may not cover the relevant approach, or may not capture the useful time period. A camera also ordinarily would not record inside a restroom.

Gaps, missing entries, and incomplete records

A gap may raise questions: Was an inspection missed? Did someone inspect but fail to make an entry? Is a paper or electronic record incomplete? Does the entry conflict with a schedule, witness account, or other timestamp?

The gap does not answer those questions by itself. It also does not supply the missing proof of when a transient substance reached the floor. A missing document or discrepancy is not automatic proof of falsification, negligence, constructive notice, or evidence suppression.

Created Condition: Did Restaurant Staff or a Contractor Cause the Wet Floor?

Creation is different from notice based on duration. If evidence supports that an employee or contractor acting on the restaurant’s behalf created the condition, the claim does not depend on proving how long an unidentified spill sat on the floor. Oregon’s decision in Bryant v. Sherm’s Thunderbird Market also explains why a storekeeper cannot delegate to a third party its duty to customers to keep the premises reasonably safe. Creation, however, cannot rest on guesswork, and a contractor’s involvement does not automatically establish that a condition was unsafe or caused a fall.

Relevant evidence may include:

when and how the area was mopped;
who performed the work;
the source and amount of water;
the expected or observed drying time;
whether a plumbing or maintenance activity was underway; and
whether mats, signs, barriers, or out-of-service notices were present before the fall.

If mopping created the wet condition, the amount of water, cleaning method, drying time, and precautions may bear on whether reasonable care was used. A log showing recent mopping could help locate that event in time, but it does not, standing alone, establish that the mopping caused the fall or that the precautions were inadequate.

A plumbing leak presents similar proof questions. Evidence would need to connect the leak to the relevant place and time and clarify what the restaurant or another responsible actor did or knew. The fact that a bathroom contains plumbing does not establish the source of a particular condition.

Actual Notice: Did the Restaurant Know About the Condition Before the Fall?

Actual notice asks what the restaurant knew before the incident and what opportunity it had to respond. Evidence may include:

an employee who observed the condition;
a patron complaint;
a recent similar event in the same area;
knowledge of a location-specific recurring wet condition; or
communications or records showing a warning or response.

Timing is critical. A complaint made after the fall does not establish knowledge before it. A prior complaint or recurring condition also needs a meaningful connection to the bathroom location and surrounding circumstances. General awareness that restaurant bathrooms sometimes become wet is not the same as actual knowledge of the condition that allegedly caused the fall.

A cleaning log might help identify which employee was present or when someone last entered the bathroom. It may then be compared with complaints, messages, witness accounts, and warning placement. The entry itself does not necessarily show what the employee saw or knew.

Constructive Notice: What Shows How Long the Substance Was There?

When the source of a transient spill is unknown, constructive notice generally turns on duration: was the substance present long enough that the restaurant should have discovered and removed it through reasonable care?

Oregon decisions require evidence from which a factfinder can infer how long the substance was present. It is not enough to establish only that the floor was wet when the patron fell.

Why an overdue inspection or weak schedule is not enough by itself

An overdue inspection can be relevant to the restaurant’s practices, but it does not reveal when a spill occurred. In Diller v. Safeway Stores, Inc., a record showing that a floor had not been swept for more than an hour did not itself establish constructive notice because the spill could have occurred immediately before the fall.

The Oregon Court of Appeals reinforced the same timing problem in Kummer v. Fred Meyer Stores, Inc.: an inadequate inspection or cleaning schedule does not alone establish when a transient substance reached the floor.

That is why neither a long gap nor a missed entry automatically establishes constructive notice. The record must be connected to evidence about the condition’s timing.

Evidence that may support a duration inference

Depending on the facts, evidence that may help support an inference about duration includes:

the substance’s apparent age;
spread or drying;
footprints or track marks;
witness observations;
prior complaints connected to the location and condition; and
relevant video showing timing, traffic, employee activity, warnings, or response.

No single category automatically proves how long a condition existed. A cleaning entry may anchor one point in the timeline, but its meaning depends on what other evidence shows. If a log records an inspection at 7:00 p.m., for example, that entry alone does not establish whether a spill appeared before the inspection, just after it, or immediately before a later fall.

The broader principles concerning how Oregon businesses may be shown to have known about a spill still require bathroom-specific proof here. That may include the cleaning method, employee task timing, plumbing or maintenance activity, and physical clues about the condition’s age.

Causation: What Condition Caused the Fall and the Claimed Injury?

Creation and notice do not replace causation. The evidence still must connect an identified condition to the fall and connect the fall to the claimed injury.

Useful evidence may include:

photographs of the area or substance;
contemporaneous descriptions of its location and appearance;
witness accounts of the fall or floor condition;
footwear or clothing evidence, when relevant;
details in an incident report, if one exists; and
evidence addressing whether the fall caused the claimed injury.

Poor inspection practices do not fill a gap about what caused the patron to fall. Nor does proof that an employee knew about some condition establish that the same condition caused the incident. An incident report may preserve observations, witness names, warnings, and the reported injury, but a report may not exist and may not be automatically available before litigation.

Comparative Fault: The Patron’s Conduct Is a Separate Question

Oregon uses a modified comparative-fault framework. Under ORS 31.600, recovery is available when the claimant’s fault is not greater than the combined fault of the persons whose fault is compared under the statute, and damages are reduced in proportion to the claimant’s percentage of fault.

Evidence about visibility, lighting, footwear, warnings, distraction, and the opportunity to avoid the condition may be disputed as part of that analysis. A visible condition does not create an automatic “open and obvious” bar to recovery under the Oregon framework described in Woolston v. Wells. But visibility and the patron’s opportunity to respond may still affect comparative fault.

This issue should not be collapsed into notice. A restaurant’s knowledge concerns what it knew or reasonably should have discovered. Comparative fault concerns the patron’s conduct. The same evidence may be relevant to both, but the questions remain distinct, and no fault allocation can be predicted from a cleaning log alone.

Other Records That May Complete—or Challenge—the Cleaning-Log Timeline

The records worth examining depend on the disputed issue. A broad list is less useful than asking which record might bear on creation, actual notice, duration, causation, or comparative fault.

Restaurant-controlled information

Potential categories, if they exist, include:

cleaning policies and paper or electronic logs;
schedules, assignments, and time records;
task-system entries and employee communications;
plumbing or maintenance tickets;
photographs and recordings;
complaint records; and
an incident report.

It may also be necessary to determine who controlled the bathroom and the records—the restaurant operator, franchisee, property owner, or manager. That is an evidence question, not a reason to assume that every possible entity possessed the same information or bears responsibility.

That threshold question differs in other property settings. For example, determining who controlled inspection and repairs at a short-term rental may require examining the actual authority of a host, owner, or property manager. This restaurant-bathroom analysis remains focused on what cleaning records and related evidence can show about the condition, timing, and notice.

Contractor or vendor information

A janitorial contractor, landlord, plumber, security provider, or surveillance vendor may hold relevant records. Their involvement should not be presumed. When a contractor actually performed cleaning or maintenance, its task records, schedules, and employee accounts may help test the restaurant’s log and timeline.

This differs from a broader dispute over hotel and cleaning-vendor responsibility. The central question here remains what the restaurant bathroom records show about the condition, notice, response, and causation. In litigation, records held by a nonparty may be sought through Oregon subpoena procedures, but access is not automatic.

Preserving Evidence Without Confusing Preservation With Production

Potentially relevant records or footage may disappear well before Oregon’s general two-year personal-injury limitation period expires. That two-year period is general information under ORS 12.110(1); ORS 12.020 also governs when an action is deemed commenced, and other facts may affect an individualized deadline.

Evidence categories a preservation request can identify

A tailored preservation request can identify the incident date, approximate time, exact location, and likely record holders. Depending on what may exist, it can identify:

cleaning and inspection logs;
electronic task data;
employee schedules;
maintenance tickets;
relevant communications and photographs;
incident records, if any; and
corridor, entrance, or cleaning-route footage, if any.

Guidance about preserving nearby surveillance and cleaning-route footage should be applied with the restroom setting in mind. Potentially useful footage is more likely to show an approach, corridor, entrance, employee activity, warning placement, or response than the inside of the bathroom.

What a preservation request does not do

A preservation request can identify evidence and give a recipient notice. It is not a subpoena, is not a document request in a filed case, and does not compel pre-suit disclosure. It also does not guarantee that a record exists, will be preserved, or will ultimately be produced.

In a filed Oregon civil action, ORCP 43 permits requests for relevant, nonprivileged documents, electronically stored information, photographs, recordings, tangible things, and property inspection. ORCP 55 addresses subpoena procedures that may be used for nonparty records. ORCP 37 provides a limited petition procedure to perpetuate testimony or evidence when its requirements are met; it is not general pre-suit discovery.

Why prompt identification still matters

Promptly identifying potential evidence can reduce uncertainty about what should be preserved and who may hold it. But no one should assume that a request will stop deletion or result in production.

Oregon Evidence Code 311 addresses a presumption concerning evidence that was willfully suppressed. Routine deletion is not automatically willful suppression, and missing evidence does not produce an automatic adverse presumption. Immediate cleanup, later repairs, added warnings, or procedure changes also should not be treated as an admission of negligence; Oregon Evidence Code 407 generally limits the use of later remedial measures to prove negligence, while recognizing other possible uses in specific disputes.

What Oregon Sanitation Rules Do—and Do Not—Establish

Oregon’s 2026 Food Sanitation Rules require physical facilities and plumbing fixtures to be cleaned as often as necessary. That provides sanitation context, but the cited provisions do not set a fixed patron-slip inspection interval, generally require every restaurant to maintain a bathroom cleaning log, or independently establish civil liability.

A sanitation concern and a premises-liability claim can involve some of the same facts without being the same legal question. The civil analysis still requires attention to creation or notice, causation, and comparative fault.

Rapid Evidence Checklist After a Restaurant Bathroom Fall

The following questions can help organize the evidence without assuming what happened or predicting a claim outcome:

Condition and causation: What was the substance or hazard? What photographs, observations, witnesses, clothing, or footwear evidence connect it to the fall?
Creation: Is there evidence of recent mopping, plumbing or maintenance activity, or another employee or contractor action? What shows the time, method, source, amount of water, or drying conditions?
Actual notice: Did an employee observe the condition or receive a complaint before the fall? Was there a location-specific recurring problem or recent similar event?
Constructive notice and duration: Did the condition show drying, spread, footprints, or track marks? What do witnesses, complaints, or any relevant footage show about timing?
Cleaning log: Does a paper or electronic log exist? What time, place, employee, and task does it actually record? Is it consistent with schedules, testimony, maintenance records, and other timestamps?
Warnings and visibility: Were mats, cones, signs, barriers, or out-of-service notices present before the fall? What was the lighting, and where was the condition in relation to the walking path?
Record holders: Who controlled the bathroom and each possible record—the operator, franchisee, owner, manager, janitorial contractor, plumber, security provider, or surveillance vendor?
Preservation: Has a request precisely identified the date, approximate time, location, and categories of evidence that may exist, without assuming the request compels production?

The answers may be incomplete or disputed. Their value comes from building a specific timeline and keeping the legal questions separate—not from treating one document as decisive.

Frequently Asked Questions

Does an Oregon restaurant have to keep a bathroom cleaning log?

The authorities discussed here do not establish that every Oregon restaurant must create or retain a bathroom cleaning log. The cited Oregon sanitation provisions require physical facilities and plumbing fixtures to be cleaned as often as necessary, but they do not generally mandate a bathroom cleaning log.

Does a missing or overdue cleaning-log entry prove the restaurant was negligent?

No. A gap may raise questions about whether or when an inspection occurred, but it does not by itself prove when a transient spill appeared, whether the restaurant had notice, what caused the fall, or whether the restaurant is liable.

What can show how long a bathroom floor was wet?

Possible evidence includes the condition’s apparent age, drying or spread, footprints, track marks, witness observations, complaints tied to the location, and relevant video. No one category automatically proves duration, and a camera may not exist or cover the relevant area.

Do I need to prove how long the water was there if an employee created it while mopping?

Evidence that an employee or contractor created the condition can support a created-condition theory that is separate from constructive notice based on duration. But the source of the condition, the cleaning activity, causation, and the adequacy of any precautions still require evidence rather than speculation.

Can I obtain the restaurant’s cleaning log before filing a lawsuit?

Production should not be assumed. A preservation request does not compel pre-suit disclosure. ORCP 43 document requests and ORCP 55 nonparty subpoenas operate in litigation, while ORCP 37 is a limited procedure for perpetuating evidence rather than general pre-suit discovery. Whether a log exists, is preserved, is relevant and nonprivileged, and is ultimately produced depends on the circumstances and applicable procedures.

Does an open or visible wet floor automatically prevent recovery in Oregon?

No automatic open-and-obvious bar should be assumed. Visibility, lighting, warnings, distraction, footwear, and the opportunity to avoid the condition may instead be considered under Oregon’s comparative-fault framework. The allocation of fault depends on the evidence.

Educational Disclaimer

This article provides general educational information about Oregon law and is not legal advice. It does not evaluate any specific incident, establish an attorney-client relationship, or predict liability, fault allocation, damages, or claim outcome. Deadlines and evidence issues can depend on facts not addressed here.

Source Notes

Kummer v. Fred Meyer Stores, Inc., 337 Or App 720, 722–27 (2025) (Oregon foreign-substance framework, duration evidence, and limits of inspection-schedule evidence): Oregon Judicial Department opinion.
Diller v. Safeway Stores, Inc., 274 Or 735, 738–39 (1976) (a cleaning gap alone did not establish how long a spill had been present): case text.
Pribble v. Safeway Stores, Inc., 249 Or 184, 186–88 (1968) (actual knowledge and Oregon’s foreign-substance framework): case text.
Woolston v. Wells, 297 Or 548, 553–58 (1984) (general premises duty and treatment of claimant knowledge): case text.
Van Den Bron v. Fred Meyer, Inc., 86 Or App 329, 331–33 (1987) (created-condition evidence): case text.
Vandeveere-Pratt v. Portland Habilitation Center, Inc., 242 Or App 554, 556–61 (2011) (mopping circumstances and precautions): case text.
Bryant v. Sherm’s Thunderbird Market, 268 Or 591, 595–602 (1974) (contractor-created conditions and a storekeeper’s nondelegable duty to customers): case text.
Fulmer v. Timber Inn Restaurant and Lounge, Inc., 330 Or 413, 427–30 (2000) (premises use, foreseeability, and reasonable precautions): case text.
Joshi v. Providence Health System of Oregon Corp., 342 Or 152, 158–64 (2006) (causation): case text.
ORS 31.600 (comparative fault); ORS 12.110(1) and ORS 12.020 (general personal-injury limitation and commencement rules); and Oregon Evidence Code 311 and 407 (willfully suppressed evidence and subsequent remedial measures).
Oregon Rules of Civil Procedure 36, 37, 43, and 55 (discovery scope, limited pre-action procedure, document requests, and subpoenas).
Oregon Health Authority, 2026 Oregon Food Sanitation Rules, sections 6-501.12 and 6-501.18 (cleaning requirements and sanitation context).