Hotels & Hospitality

The stake: Bed bug liability, brand-standard audits, and the reputational cost of a single confirmed report.

What is actually at stake when a guest reports a bed bug?

A liability exposure, a review that outlives every other thing your property does well, and a brand relationship that assumes you have a system.

Start with the part that is genuinely unfair, because getting it wrong distorts everything downstream. A hotel does not acquire bed bugs through poor housekeeping. It acquires them because it takes in strangers’ luggage at a rate of hundreds of pieces a week, and some proportion of that luggage has been somewhere else first. Rate of introduction correlates with occupancy and turnover far more than with cleanliness. A five-star property with a full house is exposed more often than a quiet one with half the rooms empty. Any operator who believes incidence is a measure of their standards will build the wrong program, punish the wrong people and hide the wrong information.

What is not unfair, and what every subsequent process turns on, is the response. The exposure in hospitality sits almost entirely in the interval between a guest saying something and the property doing something, and in whether the property can prove what it did. Claims arising from hotel bed bug incidents typically turn on notice and response: what the operator knew, when it knew it, what it did about it, and whether the same room or the room next door had generated an earlier report that was closed without a proper inspection. A property that took a room out of inventory the same hour, inspected it and its neighbors, documented the findings and held the room back until verification is in a completely different position from one whose file shows a complaint, a cleaning ticket and the room re-let the following night.

Reputation runs on a parallel track and moves faster. A single review with a photograph attached is permanent, algorithmically durable and immune to any explanation you might offer. It reaches prospective guests at the exact moment they are choosing between you and the property down the road, and it does not care that your response was excellent. This is why the operational objective is not merely to resolve infestations but to resolve them before a guest experiences one — which is what makes proactive inspection worth paying for in a way it never is in a residential building.

Then there is the brand layer. Franchised and managed properties operate against brand standards that include pest management, and the audit does not ask whether you have insects. It asks whether you have a program: written, resourced, trained, documented and demonstrably operating. A property can pass with an incident in the log and fail with an empty binder, and operators are consistently surprised by that.

The financial arithmetic is worth stating plainly because it makes the case for proactive work on its own. A room out of inventory for a verification period costs a known number of room nights. A claim, a brand finding and a reputational hit do not have a known cost, and they arrive together.

What do brand-standard auditors and inspectors actually look for?

Evidence that a system exists and is being used, in five specific places.

A written program. Scope, frequency, who does what, the pests of concern for this property, and the escalation path. It must be specific to the building rather than a contractor’s template with the property name inserted at the top.

Service records. Dates, areas covered, what was found and what was done, with findings written down rather than smoothed over. Auditors treat sanitised records as a signal to look harder.

Training records for staff. Particularly housekeeping. A brand standard that requires room attendants to be trained in bed bug recognition is checking for a training record with names and dates, and often for a refresher cycle. Turnover in housekeeping is high, so a training log a year old with none of the current staff on it is a finding.

A proactive inspection schedule. Evidence that rooms are inspected on a cycle rather than only when someone complains, with the cycle defined, the coverage recorded and the results logged.

An incident log. Every guest report, with the date and time received, the room, what was done, which adjacent rooms were inspected, the findings in each, the treatment, the verification, and the date the room returned to inventory. This is the document that does the most work in every scenario an operator worries about, and it is the document most properties do not keep in a usable form.

Beyond the paper, auditors walk back of house, and they walk it more carefully than the guest floors. Laundry, refuse rooms and staging areas, the loading dock, kitchen and banqueting spaces, staff areas, storage, and the mechanical spaces in between. Guest floors in a well-run hotel look immaculate because they are cleaned every day. Back of house is where the actual conditions are, and an experienced auditor knows that.

Where a property has food and beverage operating on site, it carries a second regime entirely. A hotel restaurant, banqueting kitchen or lobby bar is inspected on the same terms as any standalone operation, with the same violation categories and the same consequences, and the restaurant pest control page covers that in detail. Properties routinely run an excellent rooms program and a neglected kitchen program, and the kitchen is where the closure risk lives.

How should a proactive inspection program be built?

Around the recognition that finding low-level activity in occupied rooms is the entire problem, and that visual inspection of every room continuously is not achievable.

Risk-tier the room inventory. Not all rooms are equally exposed. Ground and lower floors, rooms near lifts and stairwells, rooms that take the most turnover, rooms in an extended-stay or crew-block allocation, and rooms with a prior incident all carry more risk than a quiet suite at the end of a corridor. A cycle that inspects the high-risk tier more often and the rest on a longer rotation covers the actual exposure with the resource available.

Inspect at turnover where it counts. A quick, defined check of the bed at strip-down — mattress seams and piping, the box spring dust cover, the headboard back and edges, and the joint where the bed frame meets the wall — costs a room attendant a minute and finds a large share of early-stage introductions. The specifics of where the insect harbors are set out on our bed bug treatment page, and that page is a reasonable basis for the visual part of a training session.

Use interceptors and monitors under bed and seating legs in high-risk rooms. They cost little, they accumulate evidence over weeks rather than giving a snapshot, and a housekeeper can be trained to check one in seconds.

Consider canine screening for scale. Detection dogs are widely used in hospitality for one reason: a trained team can screen a floor of rooms in the time a careful visual inspection takes for a handful, which changes what is affordable. Quality varies enormously, and it depends on the training and the handler rather than on the animal. If you are evaluating a provider, ask what standard the team is trained and evaluated against, how often that evaluation is repeated, how the handler avoids cueing the dog, what the protocol is when the dog alerts, and — critically — whether every alert is visually confirmed before a room is taken out of service or treated. An alert is a reason to look, not a finding in itself.

Screen the high-turnover soft goods and the storage. Luggage rooms, bell carts, staff break areas, lost property, and any furniture removed from a room and stored rather than discarded.

Set a rhythm with the pest contractor. Proactive inspection is not a substitute for regular service; it is a layer on top. The recurring visits handle back of house, the food operation, the exterior, the rodent and cockroach program and the monitoring network, and the room program runs alongside it.

The measure of whether this is working is not zero incidents. It is the ratio of activity found by the property to activity reported by guests. A property finding most of its own cases early is running a program. A property whose cases arrive exclusively through the front desk is being audited by its guests.

What should happen in the first hours after a room is reported?

A defined protocol, executed the same day, with nobody improvising.

Take the room out of inventory immediately. Before anything is confirmed. The cost of holding a room that turns out to be clear is one room night. The cost of re-letting a room that turns out not to be is the scenario the whole program exists to prevent.

Do not move the guest and their belongings casually. Relocating a guest with unexamined luggage into a clean room converts one affected room into two, and it is the single most common way a property spreads its own problem. The guest’s belongings need to be handled deliberately: bagged, and their clothing laundered and dried at high heat, with the property meeting the cost and organizing it rather than asking the guest to. Where possible, relocate to a room that is not adjacent to the reported one and is not directly above or below it.

Inspect properly rather than glancing. A real inspection lifts the dust cover on the box spring, takes the headboard off the wall, opens the frame joints and works outward from the bed. A room attendant’s visual check at turnover is a screen; this is not the same activity and should not be done by the same person under time pressure.

Inspect the ring. At minimum the rooms on either side, the room directly above and the room directly below. Those rooms share wall assemblies, back-to-back electrical boxes, conduit runs and floor penetrations, and in a hotel they also share the corridor and the housekeeping cart. The ring rooms are inspected whether or not anyone in them has said anything, and the result is recorded for each — including the negatives, because “no evidence found in 412, 414 and 512 on the 3rd” is exactly the sentence you will want later.

Confirm with physical evidence. Live insects, cast skins, eggs or characteristic fecal spotting. Bites alone are not confirmation; reactions vary enormously between people and many other things bite. Recording a room as confirmed without evidence produces unnecessary treatment and a distorted incident history. Recording it as clear when the inspection was superficial produces the opposite and much worse problem.

Treat, then verify before the room returns. Whatever the method, the room stays out of inventory through a defined verification period with monitors in place and a follow-up inspection, because eggs present at treatment hatch afterwards. Returning a room to the board on the same day it was treated is the decision that generates second reports, and second reports are what turn an incident into a claim.

Log every step with times. Report received, room removed from inventory, inspection performed, ring inspected, findings, treatment, verification, room returned. That sequence with timestamps is the document that answers the only question anyone will ask afterwards.

How does housekeeping reporting actually work, and why does it usually fail?

It fails because of incentives, not because of training, and fixing the training without fixing the incentives changes nothing.

A room attendant is measured on rooms per shift. Reporting something means the room comes out of service, a supervisor arrives, questions get asked and the day gets longer. If there is any implication — real or imagined — that finding bed bugs in an assigned room reflects on the person cleaning it, the rational response is not to look too closely. This is the mechanism by which properties with excellent written training programs discover their infestations through guest reviews.

Three changes address it.

Make reporting blameless and say so repeatedly. The person who finds early-stage activity has saved the property a claim. That framing has to come from management, in the language staff actually use, and it has to survive the first time someone reports something inconvenient.

Make reporting take seconds. A photograph to a defined number or channel, with the room number, and nothing else required. Any process that requires filling in a form at the end of a shift will produce a report rate of approximately zero.

Protect the time. If a report costs the attendant their break or their room count, no policy statement will overcome it. Adjust the board.

The training itself is straightforward and should be visual and hands-on rather than a slide deck. What fecal spotting looks like on a white mattress seam versus a printed one. What a cast skin looks like. Where to look on a headboard, which in a hotel is one of the highest-yield sites in the room precisely because it is fixed to the wall and rarely moved. What an interceptor with something in it looks like. And an explicit list of what not to do: do not spray anything, do not move the mattress to another room, do not put the linen down the chute with the rest of the floor’s load.

Extend the same training to maintenance, front desk and night staff. Maintenance opens walls and moves furniture and sees things nobody else does. Front desk receives the report and their first sentence to the guest matters more than anything that happens later.

Why is documentation the property’s actual defense?

Because in every scenario where a hotel’s pest handling is examined, the question asked is not whether there were insects. It is what the operator knew and what it did.

That question is answered from records or it is not answered at all. Memory is worthless two years later, staff have turned over, and the guest’s account will be specific and sympathetic. What holds is a contemporaneous log that shows the report arriving, the room coming out of inventory within the hour, the inspection performed and by whom, the ring inspected with findings for each room, the treatment, the verification, and the release date. A file like that demonstrates a reasonable, systematic response. A file with a maintenance ticket saying “guest complaint, room cleaned” demonstrates the opposite, and it does so in the operator’s own handwriting.

Several practices make the record hold up.

Log every report, including the ones that turn out to be nothing. A property with an incident log containing negatives looks like a property that investigates. A property that only logs confirmed cases looks like one that decides what to write down.

Record the negatives in the ring. Rooms inspected and found clear are evidence of scope. Without them, the record shows only that you dealt with the room the guest was in.

Keep the pest contractor’s reports and your internal log connected. Two systems that never reference each other produce gaps at exactly the seams where the story needs to be continuous.

Photograph findings and closures. Dated images of evidence found and of the room after verification are more convincing than any description.

Retain for longer than feels necessary. Claims arrive well after the event, and the useful record is the one from the incident before the one being litigated.

Take advice from your own counsel and insurer on retention, disclosure and what you say to guests — we are a pest contractor, not your lawyers. What we can do is make sure the pest side of the file is complete, specific and legible to somebody reading it cold. The general shape of audit-ready reporting is set out under commercial pest management.

What about the rest of the property?

Back of house is where the rodents and cockroaches are, and it is the part of the pest program that gets least attention because it does not generate guest complaints until it does.

Laundry. Warm, humid, running long hours, full of linen carts and lint, with floor drains and often a below-grade location. It is close to ideal habitat for cockroaches and it is a reliable rodent harborage. Lint accumulation under and behind machines is both a fire risk and a nesting material, and the drains behind the machines are rarely inspected.

Loading dock and refuse. The dock door corner that no longer seals, the compactor and its pad, the interval between refuse leaving the kitchen and leaving the property, and whatever gets stored against the wall by the dock because there is nowhere else. This is the primary rodent entry point at most properties and the primary source of fly pressure.

Kitchen and banqueting. The same structural realities as any commercial kitchen: floor drains, hollow equipment legs, wet areas under dish machines, cracked coving, dry storage on the floor, and cardboard arriving daily. Banqueting adds a specific risk, because equipment and stock are moved between spaces and stored in rooms that are not cleaned on a kitchen schedule.

Storage, mechanical and staff areas. Old furniture, broken FF&E awaiting disposal, staff lockers and break rooms with food in them, and the riser and chase spaces that connect all of it vertically to the guest floors.

The connection between back of house and the guest floors is structural and it is the reason a lobby-level sighting is rarely a lobby-level problem. Chases, risers, dropped ceilings and conduit runs carry populations upward from a cellar or a kitchen without anything crossing an open floor. When a guest room reports a cockroach, the productive question is what is directly below it. The species-level detail is on our cockroach control page, the below-grade routes are covered under rodent control, and the sealing work that closes them is on structural exclusion.

How should guests be communicated with?

Promptly, plainly, and by someone who has been told what to say before the situation arises.

Guests escalate when they feel dismissed. The front desk response that produces a claim is the one that sounds like management of the guest rather than management of the problem — a suggestion that it was probably something else, an offer of a different room with no explanation, a promise that the room will be “taken care of.” What defuses the situation is the opposite: taking the report seriously in the first sentence, moving the guest away from the affected area, handling their belongings at the property’s expense, telling them what is being done and when they will hear back, and then actually coming back to them.

Scripting helps, provided the script is written with your counsel and insurer rather than improvised at the desk at two in the morning. Three principles hold generally. Never describe a room as clear before it has been inspected and verified — that statement is both untrue and quotable. Never speculate about where it came from in front of the guest. And never let the resolution depend on the guest chasing you, because the chase is what turns a complaint into a review and a review into a claim.

Internally, the equivalent principle is that the guest-facing message and the operational record have to match. A guest told the room was treated and verified, alongside a file showing the room was returned to inventory the same afternoon, is a problem entirely of the property’s own making.

What should the file hold when a brand auditor asks for it?

Documents about your property, and candour about what is actually driving the pressure.

Expect a written baseline after a full survey covering guest floors, back of house, the food operation, the exterior and the below-grade spaces, with photographs and a clear statement of the structural conditions creating pressure. Expect a device and monitor map that matches the building. Expect service reports that record findings by area rather than confirming attendance. Expect the corrective list to name owners inside your organization and to include the items that belong to engineering or to a capital cycle rather than to us.

Expect help building the internal side of the program: the housekeeping training content, the report-to-response protocol, the incident log format, and the definition of the inspection ring. That is where most of the risk reduction actually comes from, and a contractor who only wants to sell visits will not offer it.

Expect an honest answer about verification periods, including when it is too early to return a room. And expect us to say when the source is outside your control — an adjacent tenancy, a shared refuse area, a neighboring building’s cellar — because unexplained recurrence looks like program failure to a brand auditor and explained recurrence looks like a managed risk.

What no contractor can offer is an assurance that a property will never have a bed bug incident. Any firm implying otherwise is describing something the biology and the business model do not support, and it is worth treating that claim as information about the firm.

How should a property put this in place?

With a survey of the whole property rather than a quote for a monthly visit.

Graduate has worked on New York City and Long Island buildings since 1983, and the approach is the same one we take everywhere: find the condition, correct the condition, document both. In a hotel the twist is that half the program is operational rather than structural — protocols, training, logs and response times — and a contractor who ignores that half is leaving most of the exposure in place.

The wider framework for commercial accounts is on the commercial pest management page. If your property runs food and beverage, read restaurant pest control alongside this, because that operation carries its own inspection regime. Operators running mixed portfolios of residential and hospitality assets will find the consistency problem addressed under property management, and buildings with resident shareholders sit under co-op and condo pest control.

The pest-specific pages worth reading are bed bug treatment for the biology and the treatment options, and rodent control for the back-of-house picture. Our coverage across the city and the Island is listed under locations, and Ryan Katz sets out how the diagnostic side of the work is approached.

To begin, contact us with the property type, the room count, whether there is food and beverage on site, and what your incident history looks like. If you are currently dealing with an active report, say so first — that changes the order of everything.