Rodent control is the compliance record that gets the least respect and the most audit attention. Everyone knows bait stations should be checked; almost nobody can produce a dated, per-station record on the spot when an auditor, an integrator, or a customer asks. The weekly rodent inspection in Poultry Log is built to change that: twenty-five bait points per house, each marked at the time of the check, feeding both the grower's own record and the processor network's alert stream.
What the Weekly Rodent Inspection Records
The inspection is a per-house, per-week record. For each of up to twenty-five bait stations, the grower marks the station as replaced, untouched, or not applicable, and the form captures the flock reference, placement date, completion time, and the person who completed it. Corrective action notes are required before a failed check can be submitted, so the record carries the response with the finding rather than as a separate memory. The completed inspection sits in the farm's searchable history and exports to Excel with every station column intact.
What the Processor Console Does With It
When three or more bait points in a house show activity in the same inspection, the processor console raises a rodent alert, filterable by severity, grower, and date, with the triggering inspection attached. Beyond single alerts, the week-over-week view reports rodent incident rate percentage across the network, so a processor can tell whether one farm has a station problem or whether rodent pressure is rising across a whole region in the same weeks. The compliance logs tab holds the full inspection history, searchable and exportable for audit packages.
Why the Record Matters in an Audit
- Biosecurity audits routinely ask for rodent control evidence with dates, not descriptions of intent.
- Integrator reviews cross-check rodent records against equipment checks for the same houses and weeks.
- Customer assurance programs treat documented pest control as a baseline requirement.
- A dated per-station record turns a recurring problem into a trend the farm can act on rather than rediscover each quarter.
What the Record Does Not Claim
The inspection documents what the grower recorded at each station. It does not certify that a pest control program met a legal or third-party standard, and the processor console deliberately does not compute a compliance percentage from it. The record's value is that the dated history is complete, findable, and consistent enough to review against the program the farm is actually held to.
Where Poultry Log Fits
The rodent inspection runs in the same grower app as the rest of the daily and weekly record, so the processor's view is the same evidence the farm already keeps. The alert mechanics are covered in the processor biosecurity alerts guide, the template set in the grower checklist templates guide, and the audit export path in the audit trail exports guide. Start free at poultrylog.com.
Frequently Asked Questions
How often should poultry farms inspect rodent bait stations?
Weekly is the working cadence in integrator programs and in the Poultry Log record: a per-house inspection covering up to twenty-five bait stations, marked as replaced, untouched, or not applicable, with corrective action recorded before submission.
How do poultry processors monitor rodent control across farms?
By reviewing the weekly inspections growers submit. The Poultry Log processor console raises a rodent alert when three or more bait points show activity in one inspection, and the week-over-week view reports rodent incident rate across the whole network.
Does a rodent inspection record certify pest control compliance?
No. The inspection documents the stations as checked and any corrective action taken; it supports audit readiness but does not certify that a pest control program met a legal or third-party standard. The applicable standard comes from the farm's program and authority.