What is a pest control service report?

It is the document a technician produces after a visit. It records the site, the date, the devices checked, the findings, the products used and the actions to take. The customer keeps it as proof that the work was carried out.

How long should a pest control report be kept?

Retention periods depend on your country, your customer's sector and any standard they follow. Ask the customer or the competent authority which period applies to you. Whatever the period, keep reports in a form you can find and export when asked.

Should the customer sign the report?

Yes, it is good practice. A signature on site shows that the customer received the report on that day. It also reduces later disputes about what was found or done.

Can a technician write the report on a phone?

Yes. Recording device checks, photos and findings on the phone during the visit avoids rewriting notes in the evening. NaviR Field works this way: everything happens on the technician's phone, and the report is generated from what was recorded.

Does pest control software make a company compliant?

No software can promise compliance with a given standard by itself. It records what was done, in a consistent and retrievable way. Whether that meets a particular requirement depends on the rules that apply to you.

How do you write a pest control service report a customer can show an auditor?

Published on 2026-11-03, NaviR Field

In shortA pest control report an auditor can read on its own states who intervened, where, when and on which devices, what was found, which products were used and what must happen next, and it is signed by the customer. The report should be produced on site, from data recorded during the visit, not rewritten from memory at the office. NaviR Field, pest management software, builds the report from the technician's checks, photos, findings and the customer's signature, then saves it and sends it with the service certificate.

Key points

An auditor reads a report to check that the work was done, that problems were noticed and that action followed.
Every report should identify the site, the date, the technician, the devices checked and the products used.
Findings are only convincing when they are specific: a device reference, a count, a level of infestation, a photo.
A customer signature on site turns a technician's notes into a document both parties have seen.
The fastest way to avoid gaps is to record everything on the phone during the visit, not at the office in the evening.
Software records what was done; it does not by itself make a company compliant with any given standard.

What does an auditor look for in a pest control report?

An auditor looks for proof that a control programme exists, that it is followed and that problems lead to action. The report is rarely read for its wording. It is read to answer simple questions: was the site visited when planned, were all devices checked, was anything found, and what was done about it?

In practice, an auditor will often compare several reports over time. They look for a regular rhythm of visits, consistent device references from one visit to the next, and a trail showing that a finding on one date led to a corrective action on the next. A single beautiful report matters less than a coherent series.

This is why the customer, not only the pest control company, cares about the document. When the customer's own site is inspected, your report becomes part of their evidence.

What should a service report contain, visit after visit?

A usable report contains the same core elements every time, so that anyone can compare one visit with another. The exact requirements depend on your country, your customer's sector and the standard they follow, so check them with the customer or the relevant authority. The following list is a sound baseline for most field visits.

Site identification: customer name, address and, where relevant, the area or room concerned.
Date, arrival and departure times, and the name of the technician.
The devices checked, each with its own reference, and the result for each one.
Findings: activity observed, catches counted, damage or entry points noticed, and an infestation level.
Products used: name, quantity and where they were applied, so that biocidal products can be traced.
Actions taken during the visit and actions recommended to the customer, with a date if one is expected.
The customer's signature, or the name of the person who received the report.

How do you record findings on site without rewriting them later?

Record them on the technician's phone during the visit, device by device, and generate the report from that data. Rewriting notes at the office is where details are lost: a count is rounded, a device is forgotten, a photo ends up in the wrong folder.

Three habits make findings reliable. First, check devices in a fixed order, so nothing is skipped. Second, write down numbers, not impressions: "12 catches" is more useful than "quite a lot of activity". Third, take photos at the place of the finding, so the image shows the location and not just the problem. Dictating a comment is often faster than typing with gloves on, and it keeps the wording close to what the technician actually saw.

NaviR Field is built around this routine. The technician checks every device on the phone, for example a light trap PL-01 with 12 catches and a UV tube replaced, and the date of the next tube change is recalculated automatically. Photos are located on site, findings can be written or dictated, and an infestation level is recorded.

How do you show which products were used and what equipment was checked?

Record the product at the moment it is used, and keep the supporting records (stock, vehicles, certifications) in one place. An auditor who asks about a rodenticide, an insecticide or a biocidal product expects to see what was applied, where and by whom. If that answer requires searching through paper delivery notes, the report loses its value.

Equipment and people matter too. Depending on the sector, an inspection may ask you to prove that a technician holds the right certification, that the vehicle carrying the products is accounted for, or that stock levels match what was used. Keeping these records next to the visit data means one search instead of three.

NaviR Field keeps the traceability of biocidal products with the visit, and groups stock, vehicles and certifications in one place, so that what an inspection may ask you to prove is not scattered across folders. It records what was done; whether that satisfies a given standard remains for you and your customer to confirm.

How do you deliver the report so the customer can actually use it?

Have the customer sign on site, save the report immediately and send it before the technician has left the area. A report that arrives days later is easily lost, and a report that nobody signed is harder to defend if there is a disagreement about what was done.

A service certificate is a useful companion: it is the short document a customer can show quickly, while the full report holds the detail. Sending both together means the customer has the summary for the reception desk and the evidence for the auditor.

With NaviR Field, the customer signs on the technician's phone, the report is saved and sent to the customer along with the service certificate. The software runs in the browser, on a computer or a phone, so there is nothing to install. It was written by Halte Nuisibles, a pest management company whose teams use it every day, in the office and in the van. The interface is currently shown in French and the English version is being prepared, so ask for the availability date if that matters to you.

Write to the NaviR Field team

Frequently asked questions

What is a pest control service report?: It is the document a technician produces after a visit. It records the site, the date, the devices checked, the findings, the products used and the actions to take. The customer keeps it as proof that the work was carried out.
How long should a pest control report be kept?: Retention periods depend on your country, your customer's sector and any standard they follow. Ask the customer or the competent authority which period applies to you. Whatever the period, keep reports in a form you can find and export when asked.
Should the customer sign the report?: Yes, it is good practice. A signature on site shows that the customer received the report on that day. It also reduces later disputes about what was found or done.
Can a technician write the report on a phone?: Yes. Recording device checks, photos and findings on the phone during the visit avoids rewriting notes in the evening. NaviR Field works this way: everything happens on the technician's phone, and the report is generated from what was recorded.
Does pest control software make a company compliant?: No software can promise compliance with a given standard by itself. It records what was done, in a consistent and retrievable way. Whether that meets a particular requirement depends on the rules that apply to you.