Commercial IPM Documentation and Pest Control Logs

A technician services 68 monitoring devices in a food warehouse. The customer’s pest-control binder receives one handwritten line:

Checked all traps. Sprayed as needed. No problems.

Two weeks later, an auditor finds stored-product insects near receiving. Nobody can tell which devices were accessible, what was observed, which product was applied, where it was placed, whether the application followed the registered label, what sanitation issue was reported, who owned the corrective action, or whether activity had been increasing for three visits.

The problem is not merely untidy paperwork. The record fails to connect evidence to a decision.

Integrated pest management is a decision process: define the site and pest risks, inspect and monitor, identify accurately, compare evidence with action thresholds, correct conditions that support pests, choose an appropriate control, evaluate the result, and adjust. EPA describes IPM as a series of evaluations, decisions, and controls—not a single treatment method. Documentation is how a commercial customer proves that sequence occurred.

A useful IPM file therefore shows:

• what the contractor was retained to manage;
• what was inspected and what was inaccessible;
• what pest or evidence was found, where, and in what amount;
• what threshold or condition triggered action;
• what nonchemical and chemical controls were selected;
• what pesticide was used, if any, exactly where and how;
• what the customer must repair, clean, remove, or change;
• who owns each action and when it is due;
• whether the problem improved, moved, or worsened;
• which legal, label, safety, and customer requirements applied.

This guide addresses U.S. commercial pest-management records. Pesticide business and applicator licensing, product registration, application records, notice, posting, reentry, school, healthcare, food, housing, wildlife, fumigation, and retention rules vary by state, tribe, territory, locality, product, site, and pest. The pesticide labeling governs lawful use. Build the account file from the current label and local requirements, not from a generic national checklist alone.

Use Documentorium for the customer-facing service chain, while keeping agency-required records and current product labels in their required form. Put covered sites and pests, service boundaries, access, customer duties, reporting, and corrective-action rules in the pest-control contract. Issue a pest-control work order with the visit purpose, due devices or zones, pest history, known hazards, access, and permitted tasks. Record the actual inspection, findings, controls, customer actions, and follow-up in the pest-control service report, and use the pesticide use record for the application details the form supports. The general work-order guide shows how contract scope becomes field instructions without replacing technician judgment or label requirements.

Separate four different documentation duties

Commercial customers often combine every request under compliance documents. Keep the sources distinct.

Pesticide law and product labeling

EPA registers pesticide products for specified uses and conditions. The product label is legally enforceable and defines matters such as:

• allowed sites;
• target pests;
• application methods;
• rates and concentrations;
• frequency or maximum applications;
• personal protective equipment;
• ventilation, posting, and entry restrictions where applicable;
• environmental hazards;
• food/feed handling restrictions;
• storage and disposal;
• first aid and precautionary statements.

EPA states plainly that using a pesticide inconsistently with its labeling violates federal law. A customer’s preferred technique, auditor checklist, or service contract cannot authorize a use the label does not allow.

Applicator and business requirements

Federal law requires certification for people who apply or supervise restricted-use pesticides under EPA and applicable jurisdictional programs. EPA notes that many states require certification for all commercial pesticide application, not only restricted-use products.

Identify, as applicable:

• pesticide business license;
• certified applicator and categories;
• technician registration or license;
• supervision status;
• jurisdiction and expiration;
• required insurance;
• product or method endorsements;
• state application-record fields and retention;
• customer notification or posting duties.

Do not describe an unlicensed employee as a certified technician because the company holds a license. Record the credential that actually authorizes the work.

Worker and site safety

The pesticide label supplies use-specific protection. OSHA’s Hazard Communication standard separately addresses workplace chemical information, including written programs, labels, safety data sheets, and training where the standard applies. The HCS does not require labeling of a pesticide that is subject to FIFRA labeling requirements, but that exemption does not remove other applicable workplace duties or obligations to provide access to SDSs where the standard applies.

At a multi-employer workplace, contractor and host also need a practical exchange about chemicals, site hazards, emergency procedures, restricted areas, and foreseeable exposure. Determine which employer owns each duty.

Contract, customer, and audit requirements

A hospital, food plant, apartment portfolio, school, hotel, warehouse, data center, or audited supplier may request records beyond the regulatory minimum. Those requirements can be valid contract obligations even when they are not statutes.

Examples include:

• numbered device maps;
• electronic service verification;
• pest trend charts;
• approved-product lists;
• advance treatment approval;
• organic, allergen, or contamination controls;
• food-safety audit evidence;
• tenant or department notifications;
• corrective-action aging;
• proof of technician training;
• insurance and background screening;
• key and restricted-area logs;
• sustainability or reduced-risk reporting.

Label each field’s source: label, state rule, customer specification, audit scheme, or provider practice. That prevents an audit preference from being presented as federal law—and prevents a real legal duty from being dismissed as optional paperwork.

Do not apply the Worker Protection Standard to every commercial site

The EPA Worker Protection Standard in 40 CFR Part 170 protects agricultural workers and pesticide handlers from occupational exposure to pesticides used in the production of agricultural plants. EPA identifies covered settings such as farms, forests, nurseries, and greenhouses, along with commercial pesticide-handling employers serving covered agricultural establishments.

The WPS can require, depending on role and facts:

• worker and handler training;
• pesticide application and hazard information;
• safety data sheets;
• restricted-entry intervals;
• oral warnings or posted signs;
• application exclusion zones;
• decontamination supplies;
• emergency assistance;
• personal protective equipment;
• respirator medical evaluation, fit testing, and training when required;
• information exchange between an agricultural employer and commercial handler employer;
• retention and access to specified records.

An office tower with cockroach service is not automatically a WPS agricultural establishment. Neither is a restaurant simply because it handles food. Conversely, a pest-management company entering a nursery or greenhouse should not assume its ordinary structural-service report covers the WPS information exchange.

Use an applicability gate:

If WPS applies, use a dedicated WPS compliance packet. Do not reduce the rule to put the SDS in the binder.

Start with an account-specific IPM plan

The service agreement says what is purchased. The IPM plan says how the pest program operates at this site.

Create a controlled plan with:

• customer legal name and site address;
• covered buildings, exterior areas, vehicles, and excluded spaces;
• facility use and operating schedule;
• sensitive populations and operations;
• target pests and explicitly excluded pests;
• baseline inspection findings;
• historical activity and prior treatments when available;
• structural, sanitation, moisture, storage, and landscaping risks;
• monitoring devices and inspection zones;
• action thresholds or escalation criteria;
• routine service frequency and seasonal adjustments;
• callout and emergency process;
• permitted control methods and approval gates;
• customer and provider responsibilities;
• applicator, manager, quality, and emergency contacts;
• reporting, corrective-action, trend, and meeting cadence;
• label/SDS and approved-product library;
• record retention and access;
• audit and regulatory support limits;
• plan review and change control.

Do not promise a pest-free facility as the operational standard. Define observable performance:

Program objective is to prevent pest establishment, detect activity promptly, keep monitored activity below the account thresholds, correct conducive conditions, and respond under the stated escalation plan. The provider does not warrant that no individual pest will enter or be observed.

That wording supports prevention without pretending the contractor controls open doors, incoming goods, neighboring properties, drains, weather, or sanitation.

Record the site profile before placing devices

The baseline survey should explain why monitoring is arranged as it is.

Record:

Facility characteristics

• floor plan, square footage, levels, roofs, basements, crawlspaces, and utility tunnels;
• construction, penetrations, expansion joints, false floors, suspended ceilings, and wall voids;
• loading docks, receiving, compactors, dumpsters, drains, kitchens, breakrooms, storage, and waste routes;
• doors, sweeps, screens, vents, dock seals, and utility entries;
• neighboring uses and external pressure;
• landscaping, standing water, bird habitat, and rodent harborage;
• temperature, humidity, condensation, and water sources;
• hours, shutdown windows, and restricted areas.

Operating risks

• incoming raw materials and pallets;
• returned goods and quarantined products;
• food, feed, pharmaceuticals, medical supplies, textiles, paper, or other vulnerable material;
• employee lockers and personal food;
• cleaning and sanitation schedules;
• stock rotation and damaged-goods process;
• tenant turnover or unit access;
• patient, child, elderly, allergy, asthma, or animal exposure concerns;
• open product, packaging, production, or sterile areas;
• data, security, electrical, fire, and equipment constraints.

Pest history

• verified pest species or lowest reliable identification;
• location and season;
• counts or evidence type;
• damage or contamination;
• treatment history and outcome;
• unresolved structural or operational cause;
• customer sightings that were not confirmed;
• samples, lab identification, or expert review.

Use small fly activity consistent with phorid/drain fly group—species not confirmed instead of guessing a species from a blurry photograph. The identification level should match the treatment decision.

Give every device a stable identity

A dot on a map is not enough.

For each trap, monitor, bait station, insect light trap, pheromone device, remote sensor, or other device, record:

• unique ID;
• device type and model where relevant;
• interior/exterior status;
• exact zone, room, and location reference;
• floor/wall/ceiling placement;
• target pest;
• install date;
• service interval;
• bait, lure, glue board, battery, or consumable;
• anchoring/locking/tamper status;
• sensitivity or food-zone restriction;
• active, temporarily removed, inaccessible, damaged, missing, or retired status;
• reason and approval for relocation;
• replacement history.

Example asset record:

Use the same ID on the map, device label, service report, trend data, corrective action, and photo. Renumbering all devices after a small move destroys history.

Control the map revision

The map needs:

• site and building;
• drawing title;
• revision number;
• effective date;
• author/approver;
• legend by device type;
• stable device IDs;
• north arrow or orientation;
• floor/area designation;
• inaccessible or restricted zones where useful;
• retired devices distinguished from active devices;
• confidentiality/access classification for sensitive sites.

Do not put bait formulations, access codes, alarm details, or security vulnerabilities on a broadly distributed public map. Link to a controlled record.

Use a structured pest-sighting log

A commercial program needs one intake point for employees, tenants, residents, sanitation staff, security, and managers.

Capture:

• report ID;
• report date and time;
• observer and contact;
• exact location;
• pest description;
• live, dead, droppings, gnawing, webbing, cast skin, damage, odor, sound, or other evidence;
• count or approximate amount;
• photo or retained specimen;
• affected product/equipment;
• immediate action already taken;
• whether food, patient, resident, child, employee, or animal exposure is possible;
• urgency classification;
• assigned provider/customer owner;
• inspection result and identification;
• linked work order and closure.

Do not let a sighting become closed merely because the technician visited. Close it when the defined response is completed or when the inspection documents why no further action is indicated.

Separate report from verification

Use two fields:

• Reported as: bed bug, mouse, moth, bite, droppings.
• Verified finding: species/evidence identified by qualified person, not confirmed, or no evidence observed during defined inspection.

This protects the customer from a false pest declaration and the provider from claiming that an inconclusive inspection proves absence.

Make the service report device-level and decision-level

Every visit should produce one master report with device observations attached.

Visit header

• customer, site, and service agreement;
• visit ID, date, arrival, departure, and service window;
• technician name, license/registration number, and category where required;
• customer contact and access method;
• weather for exterior or pest-relevant work;
• routine, callback, emergency, follow-up, installation, or inspection visit;
• areas scheduled;
• areas actually inspected;
• inaccessible or deferred areas and reason;
• active incidents, sightings, and open actions reviewed.

Inspection findings

For each zone or device:

• ID;
• condition/access;
• target and non-target findings;
• count and evidence;
• bait consumption or device activation;
• sanitation, moisture, structural, storage, or operational condition;
• product damage or contamination concern;
• photo/sample reference;
• trend significance;
• action taken;
• follow-up required.

OK is not a finding. Use defined values:

• inspected—no target evidence;
• activity count zero;
• inaccessible—locked room;
• device missing;
• device damaged;
• non-target capture;
• target evidence present;
• serviced/replaced;
• action threshold reached;
• follow-up scheduled.

Control decision

Document why a control was or was not selected:

Three German cockroach nymphs captured at IMT-041 and IMT-042 in the dish-area wall line, up from zero on the prior two inspections. Moisture and food debris observed behind the undercounter unit. Account threshold for verified reproduction in a food-preparation zone reached. Technician vacuumed accessible insects/debris, replaced monitors, applied listed crack-and-crevice bait per label in documented placements, and opened customer corrective action CA-118 for equipment pullout, cleaning, and leak repair. Follow-up set under escalation schedule.

That is an IPM record. Sprayed kitchen is not.

Complete the pesticide application record

The exact legal record fields and retention period come from the jurisdiction, product, applicator category, and site. Use the pesticide record only after its fields and retention settings have been checked against the strictest applicable requirement and the customer’s legitimate audit needs.

Common fields include:

• application record ID;
• customer and exact site;
• building, room, zone, device, or treated area;
• date and start/end time where required;
• target pest;
• product name exactly as labeled;
• EPA registration number;
• active ingredient when required or useful;
• formulation;
• lot/batch number when required by customer risk program;
• general-use or restricted-use status;
• amount of concentrate and finished material used;
• rate, concentration, dilution, or number of placements;
• application method;
• treated area, linear feet, volume, number of units, or other basis;
• applicator name and credential;
• supervising certified applicator where applicable;
• equipment;
• label-required PPE and controls;
• posting, notification, ventilation, evacuation, reentry, or restricted-entry details;
• weather/wind for applicable outdoor work;
• spill, exposure, drift, non-target, or complaint status;
• customer approval and notice;
• label and SDS version/link;
• follow-up or efficacy inspection.

Record what was actually applied

Do not prefill a planned product and leave it in the report when the technician used another. Do not state 1 gallon applied when one gallon was mixed and 0.4 gallon remained. Distinguish:

• concentrate measured;
• finished mixture prepared;
• finished mixture applied;
• unused mixture managed under label and law;
• bait placements or units;
• product removed/recovered.

Use the EPA registration number, not only a brand name

Similar brand families may contain different active ingredients, concentrations, sites, or directions. The EPA registration number links the record to the registered product. Record the exact product label used at the time, including supplemental labeling when applicable.

Describe the location precisely

Interior perimeter is weak in a large facility. Use:

Warehouse 1, receiving vestibule R-02: crack-and-crevice placements in wall/floor junction behind dock control cabinet and within labeled non-food areas shown on Treatment Sketch TS-17; no exposed food or food-contact surface treated.

Precision helps an auditor, medical responder, future technician, and investigator understand exposure and efficacy.

Keep the label and SDS distinct

Customers still ask for MSDS. The current term is Safety Data Sheet (SDS) under OSHA’s Hazard Communication system.

The pesticide label and SDS have related but different jobs.

An SDS does not authorize application to a site. A marketing brochure is not the label. A current online label may not prove which labeling accompanied the product used on a historical visit. Maintain controlled documents linked to the product and application record.

Keep an approved-product register

Track:

• internal product ID;
• exact product name;
• EPA registration number;
• active ingredient/formulation;
• target pests and approved account uses;
• label revision or retrieval record;
• SDS revision;
• restricted-use status;
• state registration or restriction status;
• customer approval status;
• food, organic, sensitive-area, or species limitations;
• storage location;
• obsolete/removed status;
• owner for updates.

Do not let an expired customer approval or superseded label remain selectable in the field system.

Turn conducive conditions into corrective actions

A note saying customer should clean does not assign work.

Create a corrective-action record:

Avoid vague recommendations:

• Improve sanitation → name location, material, cleaning outcome, and responsible team.
• Seal holes → identify each penetration and suitable trade; do not seal an active pest inside without a plan.
• Fix door → record sweep gap, door ID, desired closure/seal, and verification.
• Remove clutter → map the zone and clearance needed for inspection.

The pest provider should not mark a customer action closed based only on an email saying it was done. Use completed—awaiting verification until observed when verification matters.

Use thresholds that fit the pest and facility

An action threshold is the point at which evidence or conditions trigger a defined response. It is not always a numeric count.

Examples:

• one verified cockroach nymph in a neonatal or sterile area;
• any rodent evidence in exposed-food production;
• a rising trend across adjacent monitors even below a single-device number;
• repeated drain-fly activity plus a confirmed organic source;
• one stored-product pest in a vulnerable ingredient with product-hold implications;
• a specified exterior bait-consumption level;
• a pest sighting without confirmation that triggers inspection, not treatment;
• a structural gap that triggers exclusion work before pests are captured.

Document:

• pest and life stage;
• zone risk class;
• metric and observation period;
• threshold;
• required response;
• escalation contact;
• reset or closure criterion;
• authority that approved the threshold.

Do not use the same threshold for an exterior fence line and an operating room.

Trend data without manufacturing certainty

Trend reports should help people decide, not decorate an audit binder.

Track comparable data:

• captures by pest, device, zone, and period;
• sightings verified and unverified;
• bait consumption or activations using a consistent method;
• recurring conducive conditions;
• corrective actions opened, aging, completed, and verified;
• inaccessible devices/areas;
• pesticide and nonchemical interventions;
• callbacks and response time;
• seasonal or operational events;
• product holds, contamination events, or audit findings where applicable.

Preserve denominators

Activity fell 50% is misleading if half the devices were inaccessible. Report:

• captures;
• active device count;
• inspected device count;
• inaccessible/missing count;
• captures per inspected device where useful;
• changes to device placement or service interval.

Annotate changes

A spike may reflect:

• increased pest pressure;
• a new monitor type;
• more devices;
• a loading-dock construction project;
• sanitation failure;
• a weather event;
• improved access;
• corrected species identification;
• a change in reporting method.

Put those events on the trend record. Do not claim causation from timing alone.

Define zero correctly

0 should mean the device or area was inspected under the stated method and no target evidence was found. It should not mean missing data, no access, inactive device, no report, or technician assumed normal.

Use explicit null states:

• zero observed;
• not inspected;
• inaccessible;
• device missing;
• device inactive;
• result invalid;
• not applicable.

Adapt the packet to the facility

Food manufacturing and warehousing

21 CFR 117.35 requires food plants subject to that rule to take effective measures to exclude pests and protect against contamination by pests. The FDA’s 2026 Food Code is a model for retail and food-service jurisdictions, not automatically the enacted code in every location. Confirm the edition and provisions actually adopted by the relevant jurisdiction.

Customers commonly expect:

• food-safety contact and escalation;
• facility risk zones;
• current device map and inspection results;
• product and ingredient protection;
• approved-product list;
• pesticide records and labels/SDS;
• evidence that exposed food, packaging, and food-contact surfaces were protected;
• incoming-goods and stored-product monitoring;
• corrective actions and verification;
• trend reports;
• technician GMP and site-orientation evidence;
• audit-ready access with controlled revisions.

Do not claim FDA-approved pesticide. EPA registers pesticides; FDA food rules and tolerances address food safety in different ways.

Retail food and hospitality

Coordinate kitchen hours, food storage, cleaning, drains, grease, waste, guest areas, housekeeping reports, and local health-code requirements. Separate guest complaint details from broadly accessible pest logs. A bed bug report needs privacy, inspection boundaries, specimen/evidence handling, room adjacency decisions, and follow-up—not an automatic pesticide application.

Healthcare and life science

Add patient/resident sensitivity, infection-control coordination, pharmacy/lab/animal areas, sterile or controlled zones, medication/equipment protection, security, and treatment authorization. Do not let a routine technician enter a restricted clinical area because the device map says monthly.

Multifamily housing

EPA emphasizes that effective housing IPM requires a team: management, maintenance, residents, and pest professionals. Track unit access, resident notice, privacy, preparation assistance, maintenance defects, adjacent-unit strategy, clutter or disability accommodations, and follow-up. Do not label a resident noncompliant when notice, language access, disability, or entry coordination failed.

Schools and childcare

State school-IPM laws can impose specific notice, posting, product, registry, timing, and record requirements. Track occupied schedules, sensitive persons, parent/guardian notice where required, approved applications, reentry, and after-hours work. Do not infer that one state’s school rules apply nationally.

Agriculture, nurseries, and greenhouses

Run the WPS applicability review. Exchange required application, treated-area, restricted-entry, and hazard information between the agricultural employer and commercial handler employer. Preserve label, REI, AEZ, training, PPE, respirator, decontamination, emergency, notification, and record evidence as applicable.

Warehouses, offices, and data centers

Priorities may include dock and incoming-goods control, cable penetrations, raised floors, sensitive electronics, battery rooms, restricted access, fire systems, and no-liquid zones. A product approved for a warehouse generally is not automatically appropriate inside a server cabinet or energized enclosure.

Define customer responsibilities without shifting applicator duties

The customer controls many root causes. The provider controls pesticide selection and application under its role.

Customer responsibilities may include:

• access and escort;
• accurate site and hazard information;
• employee/resident reporting;
• sanitation and waste;
• moisture and plumbing repair;
• door, screen, penetration, roof, and landscape maintenance;
• stock rotation and damaged-goods control;
• food/product protection and shutdown;
• required internal notifications;
• completion of assigned corrective actions;
• preserving devices and reporting disturbance;
• maintaining restricted-entry or exclusion controls assigned to the host;
• emergency and exposure contacts.

Provider responsibilities may include:

• correct identification and inspection;
• trained, licensed, and supervised personnel;
• current label and lawful application;
• equipment and PPE;
• device installation and service;
• complete application and service records;
• timely escalation;
• spill/exposure/damage response;
• label/SDS availability;
• trend review;
• verification of pest-related corrective outcomes;
• protecting customer data and keys.

No contract clause can authorize label misuse or transfer a legal applicator duty to the customer.

Make records audit-ready without making them fictional

An audit-ready record is controlled, retrievable, and truthful. It is not perfect-looking after reconstruction.

Use:

• required fields and valid values;
• timestamps and user identity;
• immutable original entries or visible correction history;
• electronic signatures tied to role and meaning;
• attachment versioning;
• map and approved-product revision control;
• license-expiration alerts;
• device and location master data;
• offline field capture with later sync status;
• exception queues for missing records;
• access controls and retention rules;
• backups and export capability;
• customer acknowledgment separate from technical approval.

Correct errors visibly

If a technician selects the wrong product in a report, do not overwrite the record silently. Preserve:

• original entry;
• corrected value;
• correction date;
• person making correction;
• reason;
• evidence used;
• notification or incident review if the wrong product was actually applied.

A clerical correction and a misapplication are not the same event.

Avoid backdated signatures

The customer contact’s signature can acknowledge access or receipt of the report. It does not necessarily certify legal compliance, approve every application, or prove every device was inspected. Label the signature meaning.

Retain source documents

Do not store only a dashboard. Preserve underlying service records, device observations, application records, labels, SDS, photos, corrective actions, communications, and credential evidence for the required period. Exportability matters when a customer changes software or provider.

Use a separate incident branch

When there is an exposure, spill, misapplication allegation, property damage, or other unusual event, preserve the service and application records and open an incident report for facts, immediate response, notifications, and follow-up. For customer coordination in occupied offices, clinics, and retail settings, the recurring cleaning contract guide offers useful access, chemical, key, and site-responsibility language. When photographs are allowed, use the work-order photo guide to label the site, device, condition, and date without capturing unrelated people or confidential material.

Routine service records should trigger a separate incident workflow for:

• human or animal exposure;
• spill or release;
• drift or off-target movement;
• application to the wrong site or with the wrong product/rate;
• food, packaging, medicine, feed, water, or surface contamination concern;
• pesticide odor or illness complaint;
• missing bait or device in a sensitive area;
• dead or trapped non-target animal;
• tampered station;
• employee injury;
• regulatory inspection or notice;
• label deviation;
• customer emergency or evacuation.

The incident record should capture immediate protection, emergency/medical information, product and label, people and areas affected, notifications required by law/label/customer plan, evidence preservation, regulatory and insurer contacts, corrective action, and release to resume work.

Do not diagnose pesticide poisoning in a service note. Provide the current label, SDS, exposure facts, and emergency contacts to qualified medical or emergency personnel as required.

A practical document set

Account level

1. Contract and scope of service
2. Site profile and baseline inspection
3. IPM plan and threshold matrix
4. Responsibility and contact matrix
5. Approved-product register
6. License, insurance, and qualification packet
7. Current labels and SDS library
8. Device master and controlled maps
9. Site safety, access, and emergency information
10. Record-retention and distribution matrix

Visit level

1. Work order and areas due
2. Sighting-log items
3. Device-level inspection data
4. Service report
5. Pesticide application record
6. Photos, specimens, and sketches
7. Customer notification/acknowledgment
8. Corrective actions
9. Follow-up schedule
10. Incident report if triggered

Management level

1. Trend report
2. Open-action aging report
3. Device exceptions and access failures
4. Product-use summary
5. License/training expirations
6. Complaint/callback analysis
7. Plan-review minutes
8. Audit/regulatory request log
9. Annual program assessment

Sample service report narrative

Scope completed: Routine weekly service for receiving, dry storage, production perimeter, employee breakroom, and exterior stations. Inspected 64 of 66 due devices. ERBS-019 inaccessible because a delivery trailer blocked the station; IMT-028 missing after rack relocation. Exceptions opened for customer receiving and provider replacement.

Findings: No rodent captures indoors. Fresh rub/gnaw evidence not observed in inspected zones. Exterior bait consumption increased at ERBS-014 and ERBS-015 on the east dock wall. Two stored-product moths captured at PHT-021 in ingredient room A; prior comparable inspections recorded zero and one. Species confirmation pending retained specimen SP-004. Open flour residue observed beneath rack A2 and damaged bag held by customer quality staff.

Controls: Replaced listed monitors and lures. Cleaned accessible non-product debris from device areas. No broadcast pesticide application. Applied the named registered bait only in locked exterior stations ERBS-014/015 at the recorded amount and according to the current label; see Application Record PA-311. Stations remained anchored and locked.

Customer actions: CA-204—quality team to evaluate and disposition damaged bag; sanitation to vacuum rack A2 floor/underside; facilities to inspect receiving-door sweep D3. High priority, with completion evidence requested before follow-up.

Next step: Provider to identify specimen, reinspect PHT-021 and adjacent devices, verify corrective actions, and review whether the ingredient-zone action threshold is reached. Follow-up scheduled under the account escalation plan.

Commercial IPM documentation checklist

Program foundation

• [ ] Covered sites, areas, and pests are defined
• [ ] Baseline risks and pest history are documented
• [ ] IPM plan separates monitoring, prevention, correction, and control
• [ ] Action thresholds fit pest and zone risk
• [ ] Customer/provider duties are assigned
• [ ] WPS applicability is assessed instead of assumed
• [ ] State/local licensing, records, notice, and posting rules are mapped
• [ ] Customer and audit requirements are labeled separately from law

People and products

• [ ] Business and applicator credentials match the jurisdiction and category
• [ ] Supervision is documented where required
• [ ] Training and site orientation are current
• [ ] Approved-product register uses exact names and EPA registration numbers
• [ ] Current label/labeling is available before use
• [ ] Current SDS is accessible under the applicable program
• [ ] Restricted-use and customer-sensitive products are gated
• [ ] Obsolete products and documents cannot be selected

Devices and inspections

• [ ] Every device has a stable ID and exact location
• [ ] Controlled map matches the device master
• [ ] Moves, retirements, and replacements preserve history
• [ ] Sighting log separates reports from verified findings
• [ ] Service report identifies inspected and inaccessible areas
• [ ] Device-level counts use defined values
• [ ] Missing, damaged, inactive, and inaccessible devices are not recorded as zero
• [ ] Photos and samples link to the finding

Applications and safety

• [ ] Application record meets label, state, and customer fields
• [ ] Product, EPA registration number, amount, rate, method, and site are exact
• [ ] Planned and actual product use are distinguished
• [ ] Applicator and supervisor credentials are recorded
• [ ] PPE, notice, posting, ventilation, entry, and environmental controls are documented as applicable
• [ ] Host/contractor hazard information is exchanged
• [ ] Spill, exposure, drift, misapplication, and contamination trigger incident workflow

Corrective action and trends

• [ ] Each conducive condition has location, evidence, owner, priority, and due point
• [ ] Customer-completed work is verified when required
• [ ] Threshold decisions and treatment reasons are written
• [ ] Trend reports preserve inspected-device denominators
• [ ] Map, device, frequency, and method changes are annotated
• [ ] Recurring causes and overdue actions are escalated
• [ ] Follow-up documents efficacy and closure

Record control

• [ ] Required fields, timestamps, users, and correction history are preserved
• [ ] Signature meaning is explicit
• [ ] Labels, SDS, maps, reports, and credentials are version controlled
• [ ] Records are searchable by site, pest, device, product, applicator, and period
• [ ] Sensitive resident, patient, security, and facility data have access controls
• [ ] Retention follows legal, label, customer, audit, and litigation requirements
• [ ] Customer can receive a usable export at transition

Sources

Sources were reviewed September 22, 2026. Pesticide labels, registrations, state and tribal certification programs, school rules, food-code adoptions, and customer audit standards can change. Verify the current product labeling and the rules for the actual jurisdiction, site, pest, method, and applicator before service.

• U.S. Environmental Protection Agency — Integrated Pest Management Principles, updated July 22, 2026 and accessed September 22, 2026.
• U.S. Environmental Protection Agency — Pest Control Resources for Housing Managers, accessed September 22, 2026.
• U.S. Environmental Protection Agency — Introduction to Pesticide Labels, for legally enforceable use directions and restrictions, accessed September 22, 2026.
• U.S. Environmental Protection Agency — Pesticide Labeling Questions and Answers, for container and supplemental-labeling context, accessed September 22, 2026.
• U.S. Environmental Protection Agency — About Pesticide Registration, accessed September 22, 2026.
• U.S. Environmental Protection Agency — Federal Certification Standards for Pesticide Applicators, updated February 26, 2026 and accessed September 22, 2026.
• U.S. Environmental Protection Agency — Certification Standards for Pesticide Applicators, for federal restricted-use coverage and broader state-program context, accessed September 22, 2026.
• U.S. Environmental Protection Agency — Agricultural Worker Protection Standard, including WPS applicability, the 2024 Application Exclusion Zone rule and implementation guidance, information-exchange, PPE, respirator, emergency-assistance, and record-access guidance, accessed September 22, 2026.
• U.S. Environmental Protection Agency — Worker Protection Standard “How to Comply” Manual, for WPS application and hazard-information retention details, accessed September 22, 2026.
• U.S. Environmental Protection Agency — WPS Central-Location Information, accessed September 22, 2026.
• Occupational Safety and Health Administration — 29 CFR 1910.1200, Hazard Communication, including the written-program, multi-employer, label, SDS, and training provisions, accessed September 22, 2026.
• Food and Drug Administration — 21 CFR 117.35, Sanitary Operations, accessed September 22, 2026.
• Food and Drug Administration — 2026 Food Code, the current FDA model code for retail and food service, accessed September 22, 2026.
• QualityPro — current U.S. standards, version 6.1, accessed September 22, 2026.
• National Pest Management Association — QualityPro Accreditation and Version 6.1 Overview, March/April 2026, accessed September 22, 2026.
• National Pest Management Association — 2026 Pest Management in Food Processing & Handling Facilities Exam, for current food-facility standards context, accessed September 22, 2026.

---

Disclaimer

This article provides general U.S. operational information, not legal, regulatory, pesticide-label, food-safety, workplace-safety, medical, environmental, or audit-certification advice. Verify the current product labeling and the federal, state, tribal, territorial, and local requirements for the actual site and work with the applicable regulator, customer program owner, and qualified pesticide and safety professionals before acting.