The customer calls after you leave and asks what was applied beside the kitchen door. If your pest controller treatment records cannot answer that question, the visit is still open.
Close each visit with one dated entry. Record what you saw, what you did, what you could not do and what you told the customer. Link it all to the same job reference.
Check the label and UK regulator before fixing your record fields
Do not copy a pesticide form from another business and assume it covers your work. The fields can depend on the product, operator, premises, treatment, work setting and part of the UK.
Read the product label first. Identify whether you are using a biocidal product or a plant protection product. Do not decide from the pest alone. Use the product authorisation and label.
For biocidal products in Great Britain, check the current authorisation and guidance from the Health and Safety Executive (opens in a new tab). Its biocides pages also explain the separate arrangements for Northern Ireland. Follow the instructions for the territory where the product will be used.
For plant protection products in England, Scotland or Wales, use the pesticide authorisation and label information from the Health and Safety Executive (opens in a new tab). For plant protection products in Northern Ireland, start with the current pesticide guidance from the Department of Agriculture, Environment and Rural Affairs (opens in a new tab).
Use the authorised product information for the correct territory. If it does not answer a recordkeeping question, ask the named regulator and save its answer. There is no single pest-controller licensing body to use for every product and site.
Keep an owner-controlled product-field register
The owner or competent person checks and approves the application fields before issuing the template. The pest controller gets a finished form, not an unresolved legal question.
| Control | Approved entry |
|---|---|
| UK territory | [England, Scotland, Wales or Northern Ireland] |
| Product or work category | [Enter the category checked] |
| Label, authorisation and official guidance checked | [Record the controlled reference] |
| Approved application fields | [List the prompts to place on the visit form] |
| Approved by | [Name] |
| Checked and next review | [Dates or review trigger] |
Keep this register with the controlled template. Do not put source checks and review dates on every visit record. When the approved fields change, issue a new template and withdraw the old one.
Separate approved application fields from site notes
Put only the approved product and application prompts on the visit form. The pest controller completes them from the work actually done.
Use site notes for the facts your office and crew need. Customer details. Areas inspected. Evidence found. Access problems. Work completed. Customer instructions. Next action.
This split stops useful pest site notes from being mistaken for product or application entries. It also keeps the on-site form short enough to finish before leaving.
Build pest controller treatment records around one visit
One attendance gets one entry. A return visit gets a new entry. Never open the old record and replace what happened last time.
Every entry should identify the customer, premises, service area, job reference, visit date and pest controller. If a managing agent instructed the work but an occupier received the handoff, record both people.
Use a written month or another unambiguous UK date format. Include the postcode and any unit, floor, room or exterior area needed to identify the work.
The incoming work order and the completed visit record do different jobs. The work order says what was authorised before attendance. The visit record says what happened on site. Use the work order explainer for a clear pre-visit brief if those documents currently run together.
The invoice is separate again. It asks for payment for the completed and authorised scope. Do not turn the treatment record into an invoice or rewrite the site facts to match a billing line.
Copy-ready pest treatment log
The owner or competent person must approve the product and application prompts in the controlled register before issuing this form. Pest controllers should use only the current approved version.
| Field | Entry |
|---|---|
| Customer or account | [Name] |
| Instructing contact | [Name and role] |
| Site contact | [Name and role] |
| Premises | [Address, unit and postcode] |
| Job or work order reference | [Reference] |
| Visit date | [Date] |
| Pest controller | [Name or identifier] |
| Service type | [Inspection, planned treatment, return visit or other] |
| Reported problem | [What was reported and where] |
| Areas inspected | [Name each room, unit, cabinet, entry point or exterior area checked] |
| Findings observed | [Describe the sign or condition and its exact location] |
| Suspected cause or route | [State the basis and mark it unconfirmed] |
| Blocked or unsafe areas | [Name the exact area, obstruction or hazard, and whether it was inspected or treated] |
| Authorised treatment area | [Scope before work starts] |
| Treatment decision | [Treat, postpone, no treatment or request approval] |
| Approved product identity | [Copy the product detail from the work actually completed] |
| Target pest | [Enter the target pest] |
| Application points | [List each room, device, entry point, elevation or treated surface] |
| Application method | [Enter the method actually used] |
| Other approved application fields | [Complete the prompts issued in the current template] |
| Work completed | [What was done and where] |
| Work not completed | [What stopped and why] |
| Changed conditions | [Difference from the work order or earlier visit] |
| Variation approval | [Scope, person, method and approval reference] |
| Customer instructions | [Action, location and timing taken from the approved job information] |
| Information supplied | [Product information or document reference supplied] |
| Customer handoff | [Recipient, role, delivery method and date] |
| Photos and attachments | [File reference plus location label] |
| Next action | [Return, monitoring, quote, proofing action or closure] |
| Office review | [Reviewer and correction reference] |
Before invoicing, the office reviewer should take one completed record and check whether another pest controller could identify the area, findings, treatment, exceptions, customer instructions and next action without making a phone call. Repair unclear prompts while the visit is still fresh.
Record the inspection before choosing the treatment
Start with the problem reported by the customer. Treat it as a report, not a confirmed finding.
Then list the areas you actually inspected. Name the cabinet, room, service duct, entry point, exterior face, bait point or treated surface. “Checked premises” tells the next pest controller nothing.
Write observable facts. Describe the evidence and its location. If you suspect a cause or access route, put that in a separate field and state why you suspect it.
Fact: “Droppings observed beneath the rear storeroom shelf.” Suspected route: “Gap below the rear door may be an entry route; not confirmed.” Keep the entries separate. Facts first. Assessment second.
If an area is unsafe to enter, stop and record the condition. In England, Scotland and Wales, check the workplace safety and hazardous-substance guidance from the Health and Safety Executive (opens in a new tab). In Northern Ireland, use the guidance from the Health and Safety Executive for Northern Ireland (opens in a new tab). Record the control used or the reason the work stopped.
Fix the authorised area before preparing the treatment
Compare the reported problem, inspection findings and authorised work before you prepare an application.
The pest may be active in a different room or exterior area from the work order. Record the new finding first. Then check whether the authorised scope covers that area.
If it does not, stop. Ask the customer or office to approve a variation. Record what changed, the proposed extra work, who approved it and how approval was given.
Do not bury extra work in a broad line such as “treated throughout”. A clear variation protects the customer from a surprise invoice and protects your business from unpaid work.
If approval is refused or unavailable, record the declined or postponed work and leave the new area untreated. Write down the next action.
Complete the pesticide application record from the work done
Complete the approved current template from the work done, not the plan or the previous visit.
Copy product information from the product actually used. Enter the target pest, precise application location and method in separate fields. Complete the other approved prompts shown on the current template.
Location detail matters. Name the room, unit, cabinet, entry point, bait point, exterior elevation or surface. “Treated site” is too broad to answer the customer asking what was applied beside the kitchen door.
Label every photo
A photo without a location note becomes a loose image in the job file.
Give each image a short reference. State what it shows and where it was taken. Link it to the inspection finding, application point or access problem it supports.
Keep product documents and other attachments under the same job reference. Do not rely on a pest controller’s personal phone as the only copy.
Close blocked, changed and no-treatment visits on site
Exceptions need better notes than straightforward treatments. Finish them before leaving the premises.
An inspected area with no evidence is not the same as an area you could not inspect. Record the exact room, cabinet, service area or exterior point and why you could not reach it.
Stored goods may block the cabinet named on the work order. Record the obstruction and whether inspection or treatment was affected. State who was told to clear it and what should happen next.
Do not use “access issue” as the whole note. Another pest controller must be able to stand at the premises and find the blocked area without phoning you.
For changed conditions, state what differed from the work order. Record whether the work stopped, proceeded under the existing scope or became an approved variation.
For declined work, name the work offered, the area involved and the next agreed action. Do not write a judgement about the customer.
Record a no-treatment visit
No product applied does not mean no job record.
Complete the inspection findings. State why treatment did not proceed. Record the areas left untreated, the customer handoff and the next action.
Site conditions may stop an application after the inspection. The record should still show the work done before the stop. It should also stop the office from invoicing for an application that never happened.
Use blunt wording:
- Area inspected; no product applied.
- Planned area blocked; not inspected or treated.
- Finding outside authorised scope; approval requested.
- Site condition stopped application; customer told what must happen next.
Give the customer a usable handoff
Tell the customer what area was treated, what instructions apply there and what happens next. Use the approved product and job information. Do not make up precautions or intervals from memory.
Record exactly what you supplied. Name the product information, document or instruction reference. Add the recipient, role, delivery method and date so the office can answer a later question without guessing.
Make the next action concrete. Clear the named cabinet. Monitor the stated point. Give access to the locked unit. Approve the quoted proofing work. Book the return after the recorded condition has been corrected.
Keep recurring pest site notes as a visit history
Start a fresh entry for every inspection, treatment and return visit. Keep the original entry. If it needs correction, add a dated note showing what changed, why it changed and who made the correction.
Preserve the original entry and append the dated correction. Check whether the official rules that apply to the work require anything further.
Compare today’s evidence with the earlier locations. State whether activity remains at the same point, appears elsewhere or was not observed in the areas inspected.
Carry unresolved actions forward as prompts, not as completed work. A cabinet that was blocked last time stays unresolved until somebody records that access was available and the inspection happened.
Pest controller treatment records should let a different tradesperson take the next visit. They need the earlier locations, access limits, treatment history, customer instructions and open actions without depending on a verbal handover.
The pest control industry page shows how customer details, jobs and site records can stay tied to the same piece of work without flattening several visits into one note.
Pass the completed visit into billing and cost tracking
The office needs the actual visit outcome. Send the job reference, completed scope, variation approval, labour used, materials used and next action from the closed record.
Match invoice lines to authorised work that was completed. If an area was not treated, do not let a planned treatment line pass into billing unchanged. Use the invoice-writing guide to turn the approved outcome into a clear customer document.
Keep the quote, site record, variation and invoice separate. They answer different questions.
Worked example — all figures are sample currency units. The house electrical example shows the document chain. At 14 Oak Street, quote Q-1847 was 1,105 for a bathroom exhaust fan and four LED downlights. The ceiling was lined, and the quote excluded chasing. Extra cable and chasing became an approved 160 variation, so invoice INV-1847 was 1,265.
The site record explains why the invoice changed. It does not replace the quote or variation.
For cost tracking in this worked example, the original quote of 1,105 is compared with job cost of 850. Profit is 255, margin is about 23% and markup is 30%. Do not calculate profit from the 1,265 invoice because the cost of the variation is not given. Before sending your invoice, use the completed pest controller treatment records to enter your own labour and material costs with the shared job-costing guide.