A colleague covering a pest control visit should be able to open the site history and understand where to start. The previous report needs to identify the areas checked, explain the findings and show which recommendations still need attention. “Routine visit completed” leaves most of that work to the next technician.
The client needs the record too. A site manager arranging a repair or gathering documents for an audit needs specific findings, dates and evidence. The technician’s notes may become part of that report, so agree what information is needed before designing separate forms for the same visit.
We make Fieldmotion, which supports mobile job records and site information. This article covers record-keeping and office handovers. Treatment decisions, product requirements and technical assessments remain with appropriately competent people.
Record enough detail for someone unfamiliar with the visit to understand what happened. Use the following as an operational starting point, then add the fields required by the product, contract, scheme and jurisdiction involved. It is not a universal statutory checklist.
Visit details: Client, site, precise area, visit date, technician and job reference.
Scope and limitations: Areas inspected, purpose of attendance and anything inaccessible or outside scope.
Findings: Observed activity, location and supporting evidence, kept distinct from customer-reported sightings.
Work completed: Actions taken, relevant results and any treatment details required for the products used, including applicable product references, quantities and locations.
Monitoring: Device references, inspection results and changes to the site plan.
Follow-up: Recommendations, responsible person, agreed timing and outstanding decisions.
A job card can hold the visit details and link to supporting documents. Check that attachments identify the correct site and inspection point; a photograph labelled only “image 4” may be hard to interpret later.
Write for the person who needs to do something with the findings. “Proofing required” gives a maintenance manager little to work with. Identify the location and explain the issue, then state the next action agreed with the appropriate people.
The example below is hypothetical. It illustrates reporting detail, not a treatment recommendation or evidence from a customer site.
Site P-014, loading bay 2: A gap was observed beneath the closed external door; photograph P-014-07 attached. The site contact reported sightings nearby. The source of those sightings was not established during this visit. Access behind the stored pallets was unavailable, so that area remains uninspected.
Follow-up: Site maintenance lead to arrange a competent review of the door gap and confirm access for the outstanding inspection. Timing and any interim measures to be agreed with the pest professional according to the assessed risk.
The client can now locate the finding and arrange the next step. For larger contracts, agree report recipients and delivery arrangements at mobilisation, as covered in our facilities management reporting article.
Use stable references for monitoring points and inspected areas. If a device is moved or removed, record the change and update the plan. Otherwise, a comparison can treat two different locations as though they were the same point.
Keep the meaning of each result clear. “Not inspected because access was blocked” belongs in a different category from “inspected, no activity observed”. Filling both with zero can make a summary look more reassuring than the inspection supports.
When reviewing a change, check the visits being compared: their spacing, inspection coverage, monitoring arrangements and any changes to the premises. Record the technician’s interpretation and its limitations. A lower total alone does not establish that the underlying problem has been resolved.
For clients with several premises, multi-site scheduling can help organise visits against the correct site references. Keep site-specific findings visible when preparing a portfolio summary.
Give a recurring finding one reference so its history follows it. Copying the same recommendation into each visit report can obscure when it was first raised, who agreed to act and why it remains outstanding.
Record the named owner, next action and agreed deadline. Where a repair needs checking, retain the completion evidence and verification outcome before closing the finding. If access, funding or another dependency delays the work, record the decision and any required escalation.
Our article on pest control recommendations covers this process in more detail.
During the customer handover, confirm who has accepted the next task. The principles in our customer service guide help keep the verbal explanation consistent with the written report.
Separate the source of each requirement when reviewing your forms. A legal duty, stewardship condition, membership standard and customer’s audit specification may all affect the same job, but they should not be described as interchangeable rules.
Confirm the current authorisation and conditions for the products and uses involved. In the Republic of Ireland, DAFM’s biocides guidance explains that products must be notified to or authorised by the Irish competent authority before distribution or use. UK purchase conditions do not establish the Irish position.
Identify the applicable user-registration, documentation and retention requirements with the relevant authority or adviser. Keep your reporting template aligned to those requirements without presenting a general checklist as a complete compliance assessment.
Ask which standard applies to the site and obtain the relevant reporting requirements. Agree the plan references, visit reports, trend summaries and follow-up evidence your service must supply. Good records support a review; they cannot guarantee an audit result.
BPCA’s Codes of Best Practice set expectations for its member companies. BPCA also makes clear that its Codes do not remove legal requirements or the need for technical judgement. Check the relevant current Code rather than assuming association membership defines every client’s reporting specification.
CRRU UK’s proof-of-competence changes took effect on 1 January 2026. They concern the purchase and subsequent use of professional-use rodenticides under UK stewardship arrangements. Keep this requirement distinct from your general visit-reporting checklist.
CRRU UK’s training guidance sets out two accepted routes at the point of sale:
Certification from a CRRU UK-approved training course within the previous five years; or
Certification from an approved course more than five years ago, together with current membership of a CRRU UK-approved CPD scheme.
CPD membership alone is not the second route: it accompanies approved certification. Avoid a permanent “2021 or later” rule in your records. The certificate’s age changes, and CRRU tells users to check it regularly.
Record the person’s approved qualification and date, the certificate copy, any approved CPD scheme and current membership evidence. Track the next review date and whoever is responsible for checking it. A spreadsheet entry saying “trained” is difficult to verify when a supplier requests proof.
CRRU’s approved schemes require three points, hours or credits of qualifying rodent-control content annually as part of their membership requirements. Its guidance also says first-time joiners must complete the membership criteria in the current year to be ready for the following year. Confirm the person’s position with the scheme rather than assuming enrolment immediately resolves a gap.
These are UK stewardship requirements. For work in the Republic of Ireland, check the applicable Irish arrangements separately. Keep the scope of each training or competence check visible in your staff records.
Choose a completed visit and ask a colleague who did not attend to retrieve its report, monitoring results and open recommendations. Note where they need to search elsewhere or phone the technician. Those gaps tell you which references or handovers need attention.
Give someone responsibility for checking the site, required fields, attachments, limitations and recipients. Set a delivery time that matches the contract. Preserve corrections with enough history to identify what changed; never invent findings to fill an old gap.
Retention needs its own review. Identify the requirement for each record type, jurisdiction, product and contract. Health-related staff records may need different handling from client visit reports. Confirm uncertain periods with the appropriate adviser before applying automated deletion.
Fieldmotion supports mobile forms, photographs and job information. Technicians can record visit details using the Fieldmotion mobile app, including offline capture. Newly captured offline information needs to synchronise before the office can see it. Use an agreed direct contact route for urgent findings.
A consistent form can prompt useful detail, but review the issued report too. Check the customer receives the complete output, including attachments. Software cannot confirm that an inspection happened or replace the technician’s assessment of what was found.
If you change systems, include site plans, historical reports and unresolved recommendations in the transfer checks. Our guide to switching job management software covers testing access to archived records before retiring the old system.
No. The record should explain the inspected areas, findings and any limitations. An inaccessible area remains uninspected. Follow-up work or further monitoring may still be needed after the booked visit is complete, so keep those actions visible against the site.
Match your template to the work, product requirements, jurisdiction and contract. Consistent core fields help colleagues compare visits, but additional documents or client-specific reports may be needed. Review the output with the person responsible for the relevant technical or contractual requirements.
Under CRRU UK’s route for certification older than five years, current approved CPD membership accompanies approved training certification. It does not replace that certification. Check the current approved lists and the individual’s supporting evidence before relying on the route.
Set retention by record type and applicable requirements. Review product conditions, client contracts, relevant schemes and legal obligations, then document the basis for the period chosen. Do not assume one period covers treatment records, site plans and staff-related documentation.
Search for authentic evidence and establish what is missing. Record any retrospective addition accurately, including its preparation date and basis. Explain gaps to the appropriate person and agree the next action. Never backdate a record or create inspection findings from assumption.