A stack of signed service slips proves that a technician turned up. It does not tell you whether your pest situation is getting better or worse. That is the gap trend analysis fills, and it is the reason a facility can hold a full year of service records and still get a non-conformance for pest control. The records exist; the analysis does not. An auditor is not asking whether you were serviced. They are asking whether you understand what the servicing is telling you.
Trend analysis converts a year of individual observations into a picture. Instead of "station 14 had two mouse droppings on 3 March, " you see mouse activity in the dry store climbing steadily from January, crossing your action level in April. That is the difference between data and information, and it is the difference between reacting to an infestation and preventing one.
Key takeaways
- Raw service slips are data; trend analysis is the information auditors and HACCP actually need.
- Trend catch counts by pest type and by zone over at least twelve months, not as a single site total.
- Set threshold triggers (action levels) per pest and zone, so a spike automatically launches a documented corrective action.
- BRCGS expects trend analysis fed into the hazard analysis; missing trending is one of the most common pest control findings.
Why raw service slips are not enough
A service slip is a snapshot. Read in isolation, three mouse droppings at one station on one day look trivial, and often they are. The risk is invisible at the level of a single visit and only appears in the aggregate: the same station, plus two neighbours, showing small activity every visit for four months, in a zone that used to be clean. No individual slip flags that. The trend does. Relying on slips alone means you only notice a problem once it is large enough to see on a single day, which is exactly when it has become expensive and audit-relevant.
This is also why trending has to be structured. Recording everything in free text scattered across paper makes aggregation impossible. Data that is captured at station level, tagged by pest type and zone, and stored digitally can be trended in seconds. That is one of the reasons our myASConline portal trends every data point automatically as technicians capture it, rather than leaving trend graphs to be reconstructed by hand the week before an audit. It is why every commercial pest control programme we run captures data digitally at station level.
How to trend activity by zone over time
Effective trending has three dimensions: what, where and when.
By pest type
Trend each pest category separately: rodents (external stations, internal traps and monitors), crawling insects, flying insects (insect light trap catch counts), stored-product pests, and birds. Mixing them into a single "pest activity" number hides the signal. A rising fly count and a falling rodent count average out to "flat, " which is worse than useless.
By zone
Break the site into the same risk zones used in your risk assessment. A spike confined to goods-receiving points at an external pressure or a delivery; the same spike in an open-product area is a far more serious signal. Zoning the trend tells you not just that activity rose, but where, which is the first step to finding the source.
Over time
Plot at least twelve rolling months so seasonality is visible. In South African conditions rodent pressure typically climbs as it cools and food moves indoors; stored-product insect activity climbs with summer heat. A rise you would panic over in isolation may be an expected seasonal pattern, and a rise that breaks the seasonal pattern is the one that matters. Catch-count graphs, a simple line per zone per pest, make both obvious at a glance.
Threshold triggers and action levels
A trend graph is only an early-warning system if something happens when the line crosses a line. Threshold triggers, or action levels, are pre-agreed catch counts per pest and per zone that mandate a defined response when reached. For example: an insect-light-trap catch above an agreed count in a packing hall triggers investigation of doors and lighting; internal rodent activity at any station in an open-product zone triggers immediate escalation and a night inspection. Thresholds are set from the site's own baseline and risk, documented in the pest management programme, and reviewed as the baseline shifts. The key discipline is that crossing a threshold is not a judgement call made later; it automatically opens a recorded corrective action with an owner and a deadline.
Feeding trends into HACCP
Pest control is a prerequisite programme, and its performance is an input to the hazard analysis. Trend data closes that loop. A sustained rise in a zone feeding an open-product step is information the HACCP team needs when reviewing the effectiveness of prerequisites and deciding whether existing controls remain adequate. Trending that sits in the pest file and never reaches the food safety team is a wasted signal. In a well-run system the pest trend review is a standing item, and any threshold breach or adverse trend is visible to the HACCP team, not buried in a contractor's report.
What auditors expect to see
BRCGS Food Safety requires that pest records include an analysis of trends and that the analysis informs the programme and the hazard analysis. In practice, an auditor opening your file expects to find:
| They look for | What good looks like |
|---|---|
| Catch counts trended, not just filed | Line graphs by pest type and zone across 12+ months |
| Defined action levels | Documented thresholds per pest and zone |
| Response to spikes | Every breach linked to a dated corrective action with close-out |
| Loop into HACCP | Evidence the trend review reached the food safety team |
| Trends driving decisions | Frequency or layout changes traced back to the trend |
You can download a catch-count trend log and action-level worksheet from our free checklists and forms page, and our food and beverage programme builds the trending in from day one.
Frequently asked questions
What is pest control trend analysis and why does it matter?
It is the aggregation of service data over time to reveal patterns a single visit cannot show: rising rodent activity in one zone, a seasonal insect-light-trap spike, a slow climb in beetle catches. It turns pest control into an early-warning system, letting you act before a low-level problem becomes an infestation, and it is explicitly expected by BRCGS and other schemes.
What does BRCGS expect for pest control trend analysis?
BRCGS Food Safety requires pest records to include an analysis of trends, with the results used to inform the programme and the hazard analysis. Auditors expect catch counts trended by pest type and zone over at least twelve months, defined action levels, and evidence that spikes triggered documented corrective action.
How do you set threshold triggers for pest activity?
Threshold triggers or action levels are pre-agreed catch counts that require a defined response when reached. They are set per pest and zone from the site's baseline and risk, documented in the pest management programme, and reviewed as the baseline changes. Exceeding a threshold should automatically trigger a recorded corrective action.
