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

A restaurant bathroom cleaning log can be useful after a fall, but it is not a verdict on liability. An entry may report when an employee inspected or cleaned the room, who completed a task, or whether mopping occurred shortly before the incident. A gap may raise questions about the restaurant’s recordkeeping or inspection practices.

None of those facts, standing alone, proves that the floor was unreasonably dangerous, that the restaurant was negligent, or that a particular condition caused the fall and resulting injury.

Under Washington law, the cleaning record must be considered with evidence about the physical condition of the floor, how that condition arose, what the restaurant knew or reasonably should have discovered, what safeguards or warnings were present, and what caused the fall. The record’s authenticity, admissibility, credibility, and weight may also be disputed.

This article addresses Washington law and provides educational information only. It is not legal advice for any individual situation.

The Short Answer: A Cleaning Log Is One Piece of the Evidence

The most useful way to read a cleaning log is as one part of a larger timeline. It can generate leads and help test other accounts, but it should not be treated as conclusive proof for either side.

What a cleaning log may help show

Depending on what the restaurant recorded and how its system worked, a log may help show:

a reported inspection or cleaning time;
the location, employee, or task associated with an entry;
whether the record describes mopping or another task shortly before the incident;
whether the ordinary record contains a blank, overdue entry, or post-fall notation relevant to the timeline; and
what should be compared with employee accounts, photographs, messages, maintenance records, incident records, and any relevant nearby footage.

These are qualified points. A reported entry still must be authenticated before it can be used as evidence, and admission into evidence does not make the entry conclusive or necessarily credible.

What a cleaning log cannot establish by itself

A cleaning log alone generally cannot establish:

that the floor was dry or reasonably safe at the moment of the fall;
when an unidentified spill first appeared or how long it remained;
that mopping left an unreasonably dangerous condition;
that warnings or safeguards were absent or inadequate;
that a particular condition caused the fall or that the fall caused the claimed injury;
that a missing entry proves negligence, falsification, spoliation, or a right to an adverse inference; or
what percentage of fault, if any, belongs to the restaurant or the injured person.

A completed log does not automatically clear the restaurant. A gap does not automatically prove a claim.

How Washington Premises-Liability Questions Fit Around the Log

Washington’s premises-liability framework separates several questions that a single timestamp cannot answer. The analysis may involve whether the restaurant created the condition, had actual or constructive notice of it, or could face a fact-specific reasonable-foreseeability analysis tied to its business and operating methods. Under any route, proof of an unreasonably dangerous condition, negligence, causation, and injury still matters.

The restaurant’s reasonable-care duty to invited customers

A restaurant patron in an area held open to customers is ordinarily a business invitee, although the boundaries of the invitation and control of the location can be fact-sensitive. Washington applies a reasonable-care framework to invitees. That care can include inspection for dangerous conditions and reasonably necessary repair, safeguards, or warning under the circumstances.

Washington authority does not make a restaurant an insurer of customer safety. It also does not establish one fixed inspection interval for every restaurant restroom. The practical question is what reasonable care required under the circumstances at that location and time.

Creation: Did the restaurant or its employee create the condition?

When a restaurant or its employee created the dangerous condition, the notice rule used for a transient condition created by someone else does not apply in the same way. A log stating that an employee mopped shortly before a fall may therefore support investigation into a created-condition theory.

But the entry is only a starting point. It does not establish that water remained, that the floor presented an unreasonable risk, that reasonable warnings or safeguards were missing, or that the condition caused the fall. Those questions require additional evidence.

Notice: Did the restaurant know, or should it reasonably have discovered the condition?

If someone other than the restaurant or its employee created a transient condition, traditional Washington analysis generally asks whether the restaurant had actual or constructive notice in time to remedy the condition or warn customers.

Actual notice might be supported by a timed employee observation, a customer complaint made before the fall, or another pre-fall communication. An entry created only after the fall does not, by itself, show that anyone at the restaurant knew about the condition beforehand.

Constructive notice concerns whether the condition existed long enough to give the restaurant a sufficient opportunity, using ordinary care, to inspect and remove the danger or provide a warning. A logged inspection can anchor the reported check time, but it usually does not establish when an unidentified spill first appeared. The spill might have appeared before or after the entry. Other evidence must address that gap.

Reasonable foreseeability tied to the restaurant’s methods is fact-specific

Washington also recognizes a reasonable-foreseeability alternative to traditional notice when the nature of a proprietor’s business and its methods of operation make the specific type of unsafe condition reasonably foreseeable.

This is not an automatic rule for restaurants, bathrooms, wet floors, or slip-and-falls. The analysis remains tied to the particular business, location, condition, and operating methods. Evidence about recurring sink splash, prior similar complaints, plumbing problems, traffic, and actual restaurant practices may be relevant.

Even when this route applies, it does not eliminate the need to prove that an unreasonably dangerous condition existed, that the restaurant breached a duty, that the condition caused the fall, and that the fall caused the claimed injury.

Dangerous Condition and Causation Still Need Their Own Proof

A cleaning-log discrepancy may matter, but it is not a substitute for evidence about the floor or the causal chain.

A slip and the presence of some water are not automatically enough

Washington authority requires “something more” than the fact of a slip and the presence of some water to show that the particular floor presented an unreasonable risk of harm. That does not mean water can never create a dangerous condition. It means the circumstances matter.

Relevant proof may include:

the amount and location of the water;
whether it was tracked or spread across the floor;
the floor material and its condition;
lighting;
the presence, placement, and visibility of warnings;
photographs;
witness observations; and
competent testimony where appropriate.

The record should identify the condition with as much specificity as the available evidence permits rather than assuming that any wetness necessarily proves unreasonable danger.

Notice or a missed check is not the same as causation

It helps to ask the questions separately:

What was the physical condition?
Did it present an unreasonable risk?
Did the restaurant create it, know about it, or have a reasonable opportunity to discover it?
Did that identified condition cause the fall?
Did the fall cause the claimed injury?

A cleaning-log gap, a missed inspection, or evidence that a type of spill was foreseeable does not answer the final causation questions on its own.

How to Read Common Cleaning-Log Scenarios Without Overstating Them

Common log entries can point an investigation in different directions. Each has important limits.

The log says the bathroom was just mopped

This entry may help identify who performed the task, when it reportedly occurred, and whether the restaurant may have created the condition. It may also direct attention to warnings, safeguards, employee accounts, or nearby footage.

The entry does not prove that water remained, that any remaining water created an unreasonable danger, that warnings were missing, or that mopping caused the fall.

The log says “clean” or “inspected” shortly before the fall

This may establish the restaurant’s reported inspection time and shed light on its stated procedure. But “clean” or “inspected” may not say whether the floor was dry. A spill could also have appeared after the entry.

The entry’s accuracy may be tested against other evidence, and admitting a record does not require a factfinder to accept the entry as true.

The entry is blank, overdue, or missing

A blank or missing entry may raise legitimate questions: Was a check expected? Was it performed but not recorded? Did the restaurant regularly record every check? Were entries routinely preserved? How trustworthy was the system?

Under Washington’s rule concerning the absence of a business-record entry, the significance of an omission depends in part on whether the matter was ordinarily recorded and preserved and whether the source appears trustworthy. Even an admissible absence does not establish when a spill appeared, how long it remained, whether the restaurant had notice, or whether the condition caused the fall. It also does not prove falsification or spoliation by itself.

The first entry was made after the fall

A post-fall entry may help show response timing and what someone documented after the incident. Without additional evidence, however, it does not show that an employee knew about the condition before the fall.

Admissibility and weight are different questions

Washington ER 901 addresses authentication. If a log is offered for the truth of what it reports, Washington’s business-records statute also includes foundation considerations such as the record’s identity and preparation, whether it was created in the regular course of business, whether it was made at or near the time of the event, and whether the source and method appear trustworthy. A custodian or another qualified witness may be involved in establishing that foundation.

Admissibility answers whether the record may be considered. It does not require a judge or jury to believe the entry or give it controlling weight.

Other Evidence Can Confirm—or Undercut—the Log’s Timeline

Cleaning records become more useful when they can be compared with independent evidence.

Evidence about the condition itself

Photographs and witness observations may document the amount, location, tracking, or spread of water. They may also show the floor material and condition, lighting, and any warnings. Competent testimony may provide additional evidence depending on the disputed issue, but no one category of evidence should be assumed to decide every claim.

Evidence about timing, employees, and restaurant response

Other potentially relevant materials include:

employee schedules and task history;
messages and timed communications;
customer complaints;
incident records;
maintenance or plumbing records; and
witness accounts.

These materials may help identify who made an entry, what occurred before or after it, and whether the same kind of condition had previously been reported or was recurring. They may also undercut a proposed timeline.

Nearby video may matter even without a camera inside the bathroom

Relevant footage need not come from inside a restroom. Depending on the restaurant’s layout and camera placement, nearby video might show the bathroom entrance, a corridor, an employee’s cleaning route, the placement of warnings, or the restaurant’s response.

Do not assume that useful footage exists or that Washington requires a business to retain every video whenever someone reports a slip. Johnson Law’s article on preserving nearby surveillance and cleaning-route footage is an Oregon-focused companion that discusses general preservation concepts; it is not Washington legal authority.

Comparative Fault Is Separate From the Restaurant’s Records and Knowledge

Washington’s contributory-fault law generally reduces compensatory damages in proportion to fault attributed to the injured person rather than automatically barring recovery. That analysis remains separate from whether the restaurant created or knew about a dangerous condition.

What claimant-conduct evidence may involve

Depending on the facts, claimant-conduct evidence might concern visibility, warnings, lighting, footwear, distraction, intoxication, or an opportunity to avoid the condition. No particular result or percentage follows from any one fact, and a cleaning log cannot assign fault.

A visible condition does not automatically end the claim

A known or obvious condition does not automatically resolve liability. Under Washington law, a possessor may still face liability when it should anticipate harm despite the invitee’s knowledge or the danger’s obviousness. Whether harm should have been anticipated and whether the injured person bears comparative fault are distinct, fact-specific questions.

Washington Sanitation Rules Provide Context, Not a Fixed Liability Formula

Washington’s food-establishment rules provide sanitation context, but they should not be converted into an inspection schedule or automatic civil-liability rule that the text does not contain.

What the statewide food code says

The Washington State Retail Food Code requires food-establishment physical facilities to be cleaned as often as necessary to keep them clean. It separately requires handwashing sinks, toilets, urinals, and other plumbing fixtures to be cleaned as often as necessary.

The cited statewide rules do not prescribe a fixed bathroom floor-safety inspection interval. They also do not require every restaurant to create or retain a bathroom cleaning log.

Local requirements, permits, corrective plans, contracts, franchise rules, or internal policies may differ at a particular restaurant. Those site-specific materials should not be mistaken for a universal statewide rule.

Why a sanitation issue does not decide the injury claim

In Washington, breach of an administrative-rule duty is generally not negligence per se, although the trier of fact may consider the breach as evidence of negligence. A sanitation concern therefore does not automatically establish a civil premises-liability claim.

The evidence must still address the dangerous condition, breach, causation, and injury, along with any applicable analysis of who created the condition or what notice the restaurant had.

Preserving a Log Is Different From Obtaining It

Evidence may be lost or overwritten, so identifying relevant materials promptly can matter. But asking that evidence be preserved is not the same as having legal authority to compel its production.

A prompt, specific preservation request may identify the evidence at issue

A presuit preservation request can identify a potential claim and describe the records believed to be relevant. Specificity can help: the request can identify the incident date, approximate time window, exact location, and record categories, without asserting that every requested item exists.

Potential categories may include:

cleaning or inspection logs;
task history and employee schedules;
messages and photographs;
incident and maintenance records;
plumbing records; and
relevant nearby video.

It may also be necessary to identify who controls a record. Depending on the facts, that could be the restaurant operator, franchisee, owner or manager, janitorial contractor, plumber, or video vendor. Record custody and potential liability are not the same question.

A preservation request may provide notice and lead to voluntary disclosure. It guarantees neither preservation nor production.

A preservation letter is not a subpoena or discovery request

A presuit letter does not compel production under Washington CR 34 or CR 45. Once a superior-court action has been filed, CR 26 governs discovery, and CR 34 permits in-scope requests to a party for documents, electronically stored information, things, and property inspection within that party’s possession, custody, or control.

CR 45 may permit a subpoena for documents from a nonparty, subject to procedural notice, scope, objections, privilege, burden, and place-of-compliance rules. A subpoena cannot make a record exist if it was never created.

CR 27 is a limited preaction process for perpetuating testimony when its verified-petition and notice requirements are met and perpetuation may prevent a failure or delay of justice. It is not a general presuit discovery device.

Privilege and work-product issues may affect incident reports, investigation materials, and insurer communications. Their discoverability cannot be predicted from the document label alone.

A missing log does not automatically mean spoliation

Washington does not impose a general evidence-preservation duty merely because an injury occurred and litigation is possible. Whether missing evidence supports an adverse inference or another remedy can depend on duty, control, materiality, culpability, prejudice, motive, and discovery conduct.

Intentional destruction or willful nonpreservation with an improper motive presents a different issue from a blank entry, routine overwrite, or innocent loss. Spoliation and sanctions for separate discovery violations are related but distinct subjects. A missing record does not automatically establish either one.

Practical Evidence Checklist After a Washington Restaurant Bathroom Fall

The goal is to build a timeline from more than one record and keep each piece of evidence tied to the question it may answer.

Record the basic timeline and condition

Note the incident date, approximate time, and exact location.
Preserve available photographs showing the condition, its location, the floor, lighting, and warnings.
Identify witnesses and record what they observed.
Note available details about the amount, spread, or tracking of water.
Preserve information about any warning sign, cone, or other safeguard and where it was placed.

Identify records that may test the timeline

Cleaning or inspection logs.
Employee task history and schedules.
Timed messages, complaints, or other communications.
Incident records and photographs.
Maintenance and plumbing records.
Nearby footage covering an entrance, corridor, cleaning route, warning placement, or response area.

For each item, ask what it may address: the physical condition, creation, notice, causation, response, or comparative fault. Avoid assuming that one record answers every question.

Make preservation requests specific but realistic

Identify the date, time window, exact location, and relevant record categories.
Consider who may control each record rather than sending a request only to one possible holder.
Do not assume that a requested record exists.
Remember that a preservation request neither compels production nor guarantees preservation.

Do not confuse the evidence clock with the filing deadline

Washington’s general limitation period for an action for injury to the person is three years. A specific deadline may differ because of accrual, tolling, minority, incapacity, death, a government defendant, service requirements, or other facts.

A preservation letter, insurance claim, or request for a cleaning log does not commence an action or toll the limitation period. Under RCW 4.16.170, an action is deemed commenced for tolling when the complaint is filed or the summons is served, whichever occurs first, but the other step must follow within the required 90-day period. This focused explanation is not a complete limitations analysis.

Frequently Asked Questions

Does Washington require restaurants to keep bathroom cleaning logs?

No statewide statute or rule identified in the approved research requires every Washington restaurant to create or retain a bathroom cleaning log. The cited food-code rules require cleaning as often as necessary but do not set a fixed bathroom inspection interval or impose a statewide log mandate. Local or site-specific requirements and policies may differ.

Does a completed cleaning log prove the bathroom floor was safe?

No. It may report a check or task at a stated time, but it does not necessarily prove that the task occurred exactly as recorded, that the floor was dry when the fall happened, or that no condition arose after the check.

Can a missing or overdue entry prove the restaurant had notice?

Not by itself. Its significance depends on the restaurant’s regular recordkeeping practices, whether those records were ordinarily preserved, the source’s trustworthiness, and the surrounding timeline. Other proof is still needed to address when the condition appeared and whether the restaurant had enough time to discover and address it.

What if the log shows the floor was mopped shortly before the fall?

That entry may support investigation into whether the restaurant created the condition. It does not alone establish that the floor was unreasonably dangerous, that safeguards or warnings were inadequate, or that the condition caused the fall.

Can I make a restaurant provide its cleaning log before filing a lawsuit?

A presuit request may receive a voluntary response, but it does not compel disclosure. Formal procedures for obtaining in-scope materials from parties or nonparties generally operate through Washington court rules and remain subject to custody or control, scope, privilege, objections, burden, and other limits.

Does a visible wet floor automatically bar a Washington slip-and-fall claim?

No. Whether the restaurant should still have anticipated harm and whether the injured person bears comparative fault require separate, fact-specific analysis. Comparative fault may proportionately reduce damages, but it does not automatically bar recovery.

Questions About Restaurant Bathroom Evidence in Vancouver or Southwest Washington

The value of a cleaning log depends on the full record: the condition of the floor, the timeline, restaurant practices and communications, warnings, witness observations, and evidence connecting the condition to the fall and injury. An entry or gap may justify closer investigation, but it should not be read as a guaranteed answer about liability.

Developing and evaluating that evidence is one factor in what can affect a Washington injury-claim timeline.

People looking for local information can visit Johnson Law’s page for Vancouver and Clark County personal injury help. Any assessment must account for the particular facts, available evidence, and applicable deadlines; no outcome can be predicted from a cleaning log alone.

This article is for educational and informational purposes only and is not legal advice. Reading it does not create an attorney-client relationship.