Pest risk management for construction and infrastructure.

Excavation, demolition and drainage work displace established rodent populations rather than ending them. Burrows are opened, sewer runs are broken into, and the harbourage a colony has used for years stops being available in a single afternoon.

That population goes somewhere. Usually it goes to the nearest stable food and shelter, which is the occupied premises on the other side of the hoarding. The first anyone hears of it is a complaint from a neighbour, an environmental health visit, or a claim, and by then the connection back to the works is obvious to everyone except the record.

A programme that starts before the ground is opened treats displacement as a predictable consequence of a known activity. Baseline the site and its boundary, anticipate where pressure will move, and the works stop generating liabilities they were never scoped to carry.

Welfare units, canteens, and waste compounds produce exactly the conditions a rodent population needs, in temporary arrangements that change location every few weeks. No single trade owns them, so an observation gets mentioned, noted somewhere, and lost between packages.

The duty does not move with it. It stays with the principal contractor, who is answerable for site conditions whether or not a subcontractor passed the information on.

Findings are therefore written to be actionable by the person who can act: named location, named condition, named owner, and a closure position that is either met or visibly outstanding.

• Welfare units, canteens and waste compounds reviewed as they move.
• Boundary and neighbouring occupiers assessed before groundworks.
• Findings routed to the contractor who owns the condition.
• Protected-species duties raised before they become a stop.

Badgers, bats, and nesting birds carry statutory protection, and encountering them mid-programme is not a pest problem. It is a legal one, with the power to halt an activity until the position is resolved properly.

Stratton's field biology capability is the reason this sits on the same programme rather than becoming an emergency call to a separate consultant. A survey that identifies a sett, a roost, or active nesting before the plant arrives costs a conversation. The same finding on the day costs the week.

Where a protected species is present, the route is documented: what was found, what the duty is, and what has to happen before work proceeds. Nothing here is treated informally, because nothing here can be.

The same finding costs very different amounts on either side of practical completion. While the site is still a site, there is plant on it, ground is already open, service voids and ceilings are still accessible, and the work sits inside a contingency that exists for exactly this kind of thing.

After handover it is a finished, occupied building. Access has to be arranged around an operator, finishes have to come up and go back, and what would have been a line in the programme becomes a defect, a liability conversation, or a retention argument. The technical problem has not changed. Everything around it has.

This is the whole argument for treating pest risk as a construction-phase activity rather than something the eventual occupier inherits. It is also why the baseline matters: a condition identified before the ground is opened is the cheapest it will ever be to resolve.

Infrastructure and major build programmes are reviewed long after practical completion. What the client's team eventually holds is the documentation, and a pest position that was managed but never evidenced reads exactly like one that was ignored.

The programme produces a continuous record across the phases: what the site condition was at baseline, what changed as the works progressed, what was raised, and what was closed. It is written to be read by an employer's agent, not only by the site team who were there.