Pest-control service report: what it must include
The service report is the proof of the work for the client, the food-safety inspector and the auditor. A good one can be read without calling the technician.
The basics
- Site name and address, and the areas or rooms covered.
- Date and time of the visit, and the technician's name.
- Type of service: inspection, rodent control, insect control, call-out.
Monitoring points
- The points checked, numbered as on the site plan.
- The condition of each: no activity, feeding, catch, damaged, moved, missing.
- Catches by species, such as mouse, rat, cockroach, house fly or Indian meal moth.
Products used
- Product name and active substance with its concentration.
- Quantity, where it was applied, and the method.
- The batch number, if the company tracks it in its stock.
- Safety notes, such as a re-entry or withholding period.
Recommendations for the client
What the client should fix, where and by when: proofing, housekeeping, storage. Ideally with a photo.
Signatures
The technician's signature and the client representative's. The client gets a copy after every visit.
Fields to copy
- Site
- name, address, area
- Visit
- date, time, technician, type of service
- Points
- number, type, condition, catches by species
- Products
- product, active substance and concentration, quantity, location, batch
- Recommendations
- description, location, due date, photo
- Signatures
- technician, client representative
A report without retyping
In Pestnode the technician records the points, catches and products on the phone during the visit, the client signs on the screen, and the PDF report is created by itself and lands in the client's portal. See how reports go into the audit folder.