Pest risk management, run as a programme.

A conventional contract proves that a technician attended. It does not prove the site is being managed. The two are routinely confused, and the gap only becomes visible when something is reviewed.

Stratton structures inspection, recommendations, corrective actions, escalation, and review through SEPOS, so the record shows not only what happened, but what changed because of it.

Before a programme is designed, the site is read properly: ingress points, proofing condition, waste and housekeeping pressures, monitoring suitability, and the activity history behind the risk.

• Building envelope and access points.
• Proofing defects and harbourage.
• Waste handling and housekeeping pressure.
• Monitoring placement and its justification.
• The history of activity at each location.

Findings become tracked actions, each with an owner and a priority, carried from visit to visit until closed. When risk or priority changes, it is raised before it drifts, rather than mentioned only once something has gone wrong.

Commercial pest control contracts are usually procured on visit frequency, because frequency is the one variable that compares cleanly across tenders. It describes how often somebody attends. It says nothing about what was examined, what was decided, or what changed as a result.

A contract worth holding should be legible on eight points. Read against them, most attendance-led agreements are quiet in precisely the places that carry consequence.

• Inspection quality: what is actually examined, by whom, and to what competence, rather than how long the visit takes.
• Documented risk: the site's pressures and vulnerabilities held as a standing assessment, not rediscovered at each attendance.
• Corrective actions: every finding raised as an owned item with a priority and a date, not a recommendation buried in a paragraph.
• Responsibility for closure: named ownership on both sides, so an open action cannot sit unresolved because it belonged to nobody.
• Escalation: a defined threshold at which an issue stops being routine, and a stated route it travels once it crosses that line.
• Monitoring strategy: where devices are justified, what their signals are taken to mean, and where they would only add noise.
• Trend review: activity read across time and across sites, so a recurring problem is visible as a pattern rather than a sequence of incidents.
• Audit evidence: the record assembled as a reviewer would want to read it, available without a scramble in the week before a visit.