Pest Control Treatment and Infestation Log (Public Housing)

It records unit-level pest findings, infestation severity, harborage conditions, treatment actions, resident communication, and follow-up. The template is built for integrated pest management (IPM), so it captures both the pest issue and the conditions that support it. It also leaves room for corrective actions and reinspection status so the record can support closure.

It can be completed by a housing inspector, property manager, maintenance lead, pest control vendor, or another assigned competent person. The key is that the person entering the record can identify the pest, document observable conditions, and confirm what action was taken. If a vendor performs the treatment, the housing team should still review and sign off on follow-up items.

Use it whenever a pest complaint, inspection, treatment visit, or follow-up reinspection occurs. In active infestation cases, it is also useful for recurring visits to the same unit so the history stays tied to the unit record. Many housing programs use it as a running log rather than a one-time form.

No. It is designed for IPM, so it can document sanitation corrections, exclusion work, trapping, baiting, vacuuming, and chemical application when used. That matters because many infestations are resolved by removing food, moisture, and harborage conditions rather than relying only on pesticides. The chemical section is included for cases where a product is applied and needs to be recorded.

The template supports documentation practices commonly expected under public housing pest management programs, IPM policies, and vendor oversight. It also aligns with general workplace safety expectations around pesticide handling, PPE, resident notification, and safe access control. Where applicable, it can help support recordkeeping tied to EPA pesticide labeling, local housing authority rules, and public health requirements.

The biggest mistake is writing vague notes such as "pests present" without naming the species, affected rooms, or evidence observed. Another common gap is documenting treatment without recording resident access problems, which can explain why follow-up was delayed. Teams also miss the underlying cause, such as open food storage, leaks, or clutter that creates harborage.

Yes. You can tailor the infestation section for roaches, bed bugs, rodents, flies, ants, or wildlife-related entry points, and you can add property-specific fields for vacant units, family housing, or senior housing. Many teams also add photo attachments, work order numbers, or vendor product details. The structure stays the same even when the pest type changes.

An ad hoc note usually captures only one piece of the story, such as a complaint or a treatment date. This template ties together findings, treatment, resident communication, and corrective actions in one record, which makes trends easier to track by unit. It also reduces missed follow-up because the due date and reinspection requirement are visible in the same log.

If your workflow allows it, attach photos, work orders, pesticide labels or product names, resident notices, and reinspection results. Those attachments help verify what was found and what was done without relying on memory. They are especially useful when multiple departments or vendors touch the same unit.