What Defends You

Pest Records That Hold Up: What Courts Have Actually Looked At

Written for: Restaurant owners and managers, multi-unit operators, insurers, counsel on either side

Parts of this page marked Professional synthesis, not law are a Board Certified Entomologist's reading of published records. They are not legal rules, they are not legal advice, and they are written to read the same for an owner, a customer, or either side's counsel.

This site will not tell you that records win cases. No published restaurant decision was found that turned on pest-control service records, and the records that do appear in the opinions helped one side as often as the other. What the decisions show is narrower and more useful: which records courts looked at, and what each one proved. Not legal advice.

What the decisions did with records

A sighting log proves knowledge. In the patio spider case, the employees’ log and its handoff to the pest company were what established that the restaurant knew about the spiders. What it did not establish was what the restaurant did next:

The Mission Inn presented evidence that it had employees monitor for pests and insects and report their observations. The Mission Inn then recorded the sightings and gave the report to its pest control company. As will be explained post, it is unclear what, if anything, the Mission Inn did in regard to warning patrons about black widows or controlling the black widow population. — Coyle v. Historic Mission Inn Corp., 24 Cal. App. 5th 627 (Cal. Ct. App. 2018)

An inspector’s findings did not prove causation. In a food-poisoning case, the health inspectors’ testimony about unsanitary conditions was not enough, by itself, to show the food caused the illness:

The only other evidence relied upon to support respondents claim of causation, was testimony of two health inspectors. This evidence concerned certain unsanitary conditions found at restaurant. These conditions, absent further evidence, could not establish probable cause. — Minder v. Cielito Lindo Restaurant, 67 Cal. App. 3d 1003 (Cal. Ct. App. 1977)

Records from the wrong period were kept out. In a foreign-object case against a restaurant and its meat supplier, inspection documents from later years were excluded:

the incident complained of was in 1984 while the documents dealt with Quik-To-Fix operations in 1986 and after, and they were ruled inadmissible. — Tidwell v. Quik-To-Fix Products, Inc., 304 Ark. 706 (Ark. 1991)

Process and inspection evidence won a Utah case for the defendant. In the fly-in-the-bottle case, the Utah Supreme Court reversed a plaintiff’s verdict on evidence that included the health officer’s regular inspections of the plant:

A Salt Lake City health officer testified that he had inspected defendant’s plant regularly, and that the plant was clean and well kept up, that the screens were up during September and that he had never seen insects in defendant’s plant. — Jordan v. Coca Cola Bottling Co., 117 Utah 578 (Utah 1950)

And inspection reports carried a tenant’s claim. In the Utah residential case that recognized the warranty of habitability, the tenant’s evidence was the city’s housing inspection reports:

the tenant presented two city housing inspection reports detailing numerous code violations which were, in the words of the trial judge, “a substantial hazard to the health and safety of the occupants.” — Wade v. Jobe, 818 P.2d 1006 (Utah 1991)

Read together: a record of a sighting or a violation is a record that the condition existed and that you knew. It becomes a record in your favor only when it is paired with a dated record of what was done.

The six records

Professional synthesis, not law. Each of these is asked for by a rule, and each is a page in the Pest Records Binder.

1. The sighting log. Date, time, where, what, who saw it, who was told. This is the Coyle log. It is the record that establishes notice, so it must never be the only record.
2. The corrective-action log. For every sighting and every inspection line: what was done, by whom, on what date, and the date the health department set. Salt Lake County’s regulation sets those dates: critical items at the time of inspection or within 10 days by agreement, non-critical within 30 (the county regulation). This is the column Coyle found empty.
3. The service report. Utah requires a licensed applicator to record every application within 24 hours, with the product, its EPA registration number, the amount, the target site and pest, and the applicator’s license number, and to keep it two years (who may apply pesticide). Your copy of that report is the proof that the program existed and what it consisted of. If your pest company’s report lacks any of those items, ask for one that has them (questions to ask).
4. The monitor and station log. A map of every monitor and bait station, and the count at each service. This is the record that shows a program was effective, which is the word OSHA uses (OSHA’s standard), and the record that shows when a problem ended.
5. The delivery inspection log. The Food Code’s first duty under Controlling Pests is inspecting incoming shipments. A one-line entry per delivery, with the rejections, is that duty on paper (Delivery Inspection Card).
6. The inspection report itself, with your response. Every county report, the signed acknowledgment, and the corrective-action entries for each line, filed together. Tidwell is the reason to keep them by date: records from the wrong period do not help anyone.

Three rules for all six

1. Write it the day it happens. A log reconstructed later is a log a court can discount, and Utah’s own rule for applicators is 24 hours.
2. Write what was seen, not what it means. “Two dead German cockroaches under the dish machine, removed, area wiped, technician called” is a record. “Roach problem” is an opinion.
3. Keep the “what was done” column filled. It is the difference between a record of a problem and a record of a program.