Compliance program review

An assessment of the pest management program a facility already has, against the regulatory regimes that actually govern that facility, delivered as a written finding the facility can hand to a surveyor, a board, or counsel.

What the engagement is

Most pest management programs in regulated facilities were designed by the pest management company that sells the service. That is not an accusation; it is the ordinary commercial arrangement. But it means the program is usually built around what can be delivered on a route, and the facility's obligation is built around what an inspector can ask for. Those two things overlap. They are not the same thing.

This engagement establishes the difference. It starts from the regulatory side, not the service side: which authorities govern this facility, what each one actually requires, and what a facility has to be able to produce to show it. Only then does it look at the program in place.

Why it starts with the regime and not the pests

Because the regimes disagree, and because several of them are silent in ways that facilities do not expect. A hospital operating under the CMS Conditions of Participation is governed by a requirement to maintain buildings so that patient safety and well-being are assured — and by no pest-specific standard at all, because none exists in the surveyor manual. A food service operation in the same building is governed by a Food Code section that names four specific means of pest control, three of which are not pesticide application. A HUD-assisted apartment two miles away is inspected under a standard where an active extermination contract is explicitly not a defense to a finding.

A single program cannot be assessed sensibly without knowing which of those it has to satisfy. The industry pages set out the governing regimes for each sector the practice serves, with exact citations.

What it does not do

It does not apply pesticides, write treatment recommendations for an active infestation, or replace the facility's pest management vendor. Where an infestation requires immediate operational response, that is the vendor's work and the review says so. It is also not legal advice; where a finding has legal consequence the written finding is built to be usable by counsel, not to substitute for them.

What the client receives

• A regime map: every federal, state, local, accreditation, and contractual authority that reaches pest management at this facility, cited exactly, with what each one requires stated in plain language.
• A gap register: each place the current program does not meet a requirement, ranked by whether it is citable today, citable at the next survey, or a latent exposure.
• A documentation schedule: what record has to exist, who generates it, how long it is retained, and where it is produced from during an inspection.
• A vendor scope review: what the incumbent pest management contract actually obligates the vendor to do, measured against what the regime requires the facility to be able to show.
• A written finding signed by a Board Certified Entomologist, suitable for the compliance file.

Who the engagement is for

• Facilities with an incumbent pest management vendor and a compliance obligation that nobody has mapped against the contract.
• Organizations that have inherited a program — through acquisition, a management change, or a new construction handover — and cannot evidence why it is built the way it is.
• Boards, owners, and executives who need an independent read rather than a reassurance from the vendor being assessed.

Retaining the practice

Engagements are national and fee-based. Fees are set in conversation against the scope of the facility and the work; no schedule is published on this site.Describe the facility and what is coming — a survey, a citation already issued, or a matter in litigation — and the practice will respond with scope.