Comparing Commercial Pest Contracts: Scope, Visits, and Exclusions

Two pest control proposals land on your desk. Both offer regular visits, both mention monitoring, and they look much the same on paper. So how do you tell which one actually covers your site, and which one will leave you debating exclusions the first time something goes wrong? The answer sits in the written scope, not in the headline visit number.

This guide is for facilities managers, procurement teams, and site managers comparing commercial pest contracts at tender or renewal. It sets out the questions we’d ask in your position, so each proposal is judged on the same terms. It isn’t legal advice on contract wording, and it won’t pick a provider for you.

Brief every provider the same way

Proposals can only be compared fairly if each provider starts from the same information. Put together a short site brief: the buildings and yards in question, operating hours, storage and waste arrangements, how deliveries arrive, and any pest history you know about. If one provider walked the site on a quiet Sunday and another saw it mid-shift, their programmes may differ for reasons that have nothing to do with quality.

Include the activities that shape pest risk. Food handling, open loading bays, sensitive equipment, public access, and rooms that are rarely opened all raise different questions. A floor area on its own doesn’t describe your operation, and a programme built from square metres alone may miss what matters most.

Our commercial pest control programmes start from that site context: how the building is used, where the risk sits, and what your auditors expect to see. Tell each provider about changes you already have planned, such as a new storage area or longer opening hours, so the proposal fits the site you’ll have next year as well as the one you have now.

Share recent reports and be open about anything unresolved. Leaving a recurring issue out of the brief might produce a tidier-looking proposal, but the gap will show up on the first visit. It’s better for everyone if the starting position is realistic, including any areas that are hard to reach.

What’s in scope

“Pest control” is a broad label. Ask each provider to list the pests covered by the routine programme, and don’t assume it includes every insect, bird, rodent, or wildlife issue. Bird proofing, wasp nest treatments, and wildlife work may be scoped separately because they need their own survey and method.

Check the physical boundary too. Does the proposal include the yard, the bin store, roof spaces, detached stores, and shared service corridors? A marked-up site plan answers that far more clearly than a phrase like “full site coverage” with no defined limits.

The BPCA’s advice for commercial premises gives useful background on choosing professional pest management for a business. Use it alongside the proposals in front of you, then ask each provider to explain the practical edges of its own service. A trade association page is a good starting point, but it can’t define what your contract includes.

Here’s an illustrative example. A warehouse contract covers internal rodent monitoring, then pigeons start roosting above the loading bay. If bird work was never in scope, it’ll need its own survey and specification. Neither arrangement is wrong. The trouble starts when the buyer assumed it was included and only finds out once the issue is already urgent.

What a routine visit delivers

Visit frequency is the easiest number to compare and the least informative on its own. Ask what each routine inspection covers, what report you’ll receive, and how findings turn into recommendations. More dates in the calendar don’t automatically mean a better-designed programme.

The BPCA’s guide to procuring pest control treats buying pest management as a cycle: define your needs, set requirements, select a supplier, and keep reviewing performance. That’s a helpful way to look at it. Signing the contract is one step, and managing what it delivers carries on for the life of the agreement.

Ask how each provider arrived at its proposed frequency and when it’ll be reviewed. A change in activity, layout, or site use may justify a different pattern. A standard schedule copied from another site shouldn’t stay in place for years without anyone checking it still fits.

Where a proposal lists different kinds of visit, separate them out so you can compare like with like:

1. Routine inspections. The scheduled checks of monitoring points, proofing, and housekeeping, with a written report each time.
2. Follow-up visits. Return visits after a finding or treatment, to check whether the action has worked.
3. Reactive call-outs. Attendance when your team reports activity between scheduled visits.
4. Specialist surveys and projects. Work such as bird proofing or major exclusion, which is usually specified and agreed on its own terms.

Call-outs between visits

Find out exactly what happens when someone on site reports a sighting between routine visits. Who do they contact, how is the report assessed, and what decides whether a technician attends? Acknowledging a message, arriving on site, and completing the work are three different things, so check which one any stated response time refers to.

If a response time is written into the proposal, ask what conditions apply. Operating hours, access, the type of pest, and specialist equipment can all affect it. Don’t read “prompt response” as a fixed attendance promise if the agreement doesn’t actually say that.

For estates with several locations, escalation matters just as much. Our guide to multi-site and FM pest control looks at how reporting and escalation can stay consistent across a portfolio, so a sighting at one site reaches the right person quickly.

Agree in advance who can authorise work outside the routine scope. A shift supervisor should be able to report a problem straight away, even if they can’t sign off a separate project. Settling that now saves time when an urgent finding lands late on a Friday.

Who does what on site

A pest contract doesn’t hand every building and housekeeping task to the provider. Repairs, waste management, storage, cleaning, and access usually stay with your business, your landlord, or another contractor. Ask for the boundary in writing, so recommendations don’t sit unowned between organisations.

The HSE’s guidance on using contractors stresses cooperation and sharing information about the work and its risks. For pest management, that means you tell the technician about hazards and site rules, and the technician explains the work and the controls it needs. Neither side should assume the other already knows about a change.

Agree how recommendations are prioritised, received, and closed. A useful record shows the issue, the action, the person responsible, and any follow-up check. A recommendation marked “sent” isn’t the same as a gap proofed or a door repaired.

Think about access failures as well. If the technician can’t get into a locked room or reach devices behind stock, the report should say so. Decide who arranges access and how missed areas are revisited, so a completed visit isn’t mistaken for a complete inspection.

Records and equipment

Ask what documentation you’ll receive and how authorised staff can get to it. Expect visit reports, a current site plan showing device positions, product information where it applies, and a recommendations log. For food sites, check the records will support what an auditor or EHO expects to see; our audit-ready EHO inspection guide covers what that looks like in practice.

Confirm how each provider handles the safety paperwork for work on your premises, including COSHH assessments and method statements. Our article on COSHH, RAMS, and the ERA explains how those documents fit together, which helps when you’re comparing what each proposal actually supplies.

Clarify who owns the monitoring equipment, who maintains it, and what happens when the contract ends. The outgoing provider should manage the removal or handover of devices and any products, rather than leaving site staff to clear them out.

Keep the final specification and any agreed changes together. If a phone call clarified an inclusion, make sure the accepted version says so in writing.

Questions about pest contracts

Should every site in our portfolio have the same contract?

A consistent reporting standard helps, but identical visit patterns or equipment may not suit buildings with different uses. Ask for the common standard and each site’s variations to be set out clearly. Consistency shouldn’t hide the reason one location needs a different programme.

How do we check a provider’s trade membership?

Use the relevant organisation’s current member directory or confirmation route. A logo on a proposal isn’t the same as a live check. Apply the same care to other credentials, and don’t assume one certificate covers every specialist task in the scope.

Will a pest contract get us through an audit?

No contract can promise an audit result. Auditors and inspectors look at your own controls, records, and actions alongside the contractor’s work. Ask what documentation the service provides, then make sure your team completes its side and checks the standard that applies to your operation.

What if our operation changes after the contract starts?

Tell your provider about changes to layout, stock, hours, or access, and ask whether the specification needs reviewing. Record any agreed variation. A programme shouldn’t quietly drift away from the site it was designed for while the paperwork stays the same.

Can we compare proposals without a site survey?

An early conversation can outline the options, but a final programme needs a proper look at the premises and the risks. Ask what assessment sits behind each proposal and which parts are still provisional. A scope written without seeing the site shouldn’t be treated as a fully assessed specification.

When should we review the contract once it’s running?

Agree a review point in the contract itself, and bring it forward if the site changes or findings shift. Use the visit reports and the recommendations log as the basis for that review, so you’re judging the service on evidence rather than on how often someone turned up.