Skip to content
AUAustralia

Pest Controller Treatment Records: Log Every Site Visit

Build a treatment record that links the authorised scope, site inspection, product application, variations, customer handover and next visit.

Yes Foreman · 4 October 2026 · Running the work

The tradie leaves, then the customer asks what was applied beside the entry door. If your pest controller treatment records cannot answer from an exact site entry, the visit is not closed.

Use one record for one visit. Write what you inspected, what you could not reach, what you applied, what changed and what the customer must do next.

One form, two Australian regulator checks

Do not download a generic form and call it compliant. Confirm product approval, permitted use, applicator credentials, business licensing, required records and retention with the official body responsible for each question in the jurisdiction where you work.

Check the registered product and approved label using the Australian Pesticides and Veterinary Medicines Authority product search (opens in a new tab). Read the label for the actual product and treatment setting before deciding which application fields belong on your form.

Then ask the official pesticide or pest-management body for the state or territory where the site sits about permitted use, applicator credentials, record fields, correction methods and retention. Ask the state or territory licensing regulator about any separate business or contractor licence question. Write down the body contacted, the question, the answer and the date checked.

Use this list to reach the official pesticide-use starting point for the job’s jurisdiction:

Do not assume the same form covers every state and territory. Put the jurisdiction on every visit record. If your business crosses a border, check the form again before dispatching the job.

Ask the official body responsible in that jurisdiction who controls each question. Workplace safety questions go to your state or territory WHS regulator.

Tag each field by source and use

Give every application field one or more source tags:

  • Approved product label
  • State or territory regulator
  • Company operating field

Then mark whether the field applies to every visit or only to a particular product, treatment, site or jurisdiction. “Conditional” describes when you use the field. It does not identify the source.

Beside each source tag, record the label or regulator reference and the date checked. One field may carry both an approved-label tag and a state or territory regulator tag.

Do not present company notes as legal requirements. Do not drop checked entries because the office does not use them for billing. Keep both groups visible and give conditional fields a clear “not applicable” option.

Your next job: tag every field on your current form by source, record the reference and mark when it applies. Any field you cannot classify needs checking before the form goes back into the van.

Build pest controller treatment records around one visit

The work order records what the customer authorised before the visit. The treatment record records what happened at the property. They share a job reference, but they are not the same document.

Start the chain during customer intake. Capture the reported pest, location, access conditions and site contact before dispatch with a pest controller enquiry checklist. Turn the accepted scope into the work order.

Then open a blank visit record. Do not duplicate the last treatment and edit a few lines. Old application details can survive unnoticed and become a false account of the new visit.

Identify the account, service address, suburb, state or territory, postcode and exact unit or treatment area. Add the work order reference, purchase order where used, site contact, tradie and visit date. Commercial and strata sites also need the common-property area or unit named precisely.

Separate these three facts:

  1. The problem reported before attendance.
  2. The scope authorised on the work order.
  3. The work actually completed on site.

If they differ, explain the break in the chain. Never make the final note look as though the completed work was authorised from the start.

Copy-ready visit record template

Adapt this blank form only after checking the product label and the official bodies responsible for pesticide use, licensing and records in the state or territory where you work.

#### Application-field verification worksheet

Source tagsApplies whenFieldEntryReference and date checked
[Approved label / state or territory regulator / company][Every visit / conditional]Product details[Enter the label name, registration identifier or other checked identity][Label or regulator reference and date]
[Source tags][When it applies]Target pest[Enter the target pest][Reference and date]
[Source tags][When it applies]Exact application site[Room, unit, doorway, crack, device, exterior face or landscape area][Reference and date]
[Source tags][When it applies]Application method[Enter the method actually used][Reference and date]
[Source tags][When it applies]Amount or dilution[Enter the amount, concentration, dilution or mixture checked for the job][Reference and date]
[Source tags][When it applies]Applicator details[Enter the identity, credential or supervision detail checked for the work][Reference and date]
[Source tags][When it applies]Date or time[Complete when required or mark not applicable][Reference and date]
[Source tags][When it applies]Equipment or site condition[Complete when required or mark not applicable][Reference and date]
[Source tags][When it applies]Other checked field[Name the field and enter the detail][Reference and date]

#### Company operating fields

FieldEntry
Customer or account[Name]
Service address[Street, unit, suburb, state or territory, postcode]
Jurisdiction[State or territory]
Work order or job reference[Reference]
Purchase order[Reference or not used]
Visit date[Date]
Tradie[Name or identifier]
Site contact[Name and role]
Reported problem[Problem and reported location]
Authorised scope[Areas and work approved before attendance]
Areas inspected[Exact rooms, units, structures or exterior areas]
Evidence observed[Evidence and exact location]
Access limits[Exact area, reason and not-inspected status]
Treatment decision[Treat, do not treat, postpone or seek approval]
Work completed[Action and exact location]
Work not completed[Item, location and reason]
Changed condition[New finding and effect on scope]
Variation approval[Person, method, date and approved work]
Customer instructions[Action, location, precaution and next step]
Handover[Recipient and delivery method]
Photos and attachments[File reference, visit and exact location]
Next action[Return, monitor, quote or no further action]
Tradie sign-off[Name and completion entry]
Office review[Reviewer and correction reference]

Use “not inspected”, “not applied” and “not applicable” deliberately. A blank box tells the office nothing.

Test your pest controller treatment records against your last completed job. Check whether a supervisor who never attended can tell what was authorised, seen, applied and left unresolved.

Record the inspection before deciding to treat

Write the site account before the application entry. The inspection explains why you made the treatment decision.

Name every inspected location. “Kitchen” may still be too broad. Use the cabinet below the kitchen sink, the eastern wall behind the refrigerator or the external doorway beside the loading area when that is what you inspected.

Keep observed evidence separate from an assumed cause. Write what you saw and where you saw it. If you did not confirm the entry route or source, do not state it as fact.

Use the pest site notes for useful context. Record damaged seals, disturbed monitors, moisture, food residue or another condition only when you observed it. Tie each note to a place.

Mark inaccessible and unsafe areas

Stored goods block access below a sink. Do not mark the kitchen inspected and move on.

Name the blocked cabinet. Mark it not inspected and not treated. Record why access failed, who was told and what must change before the return visit.

An inaccessible area is not an inspected area with no activity. Keep those statuses separate so the next tradie does not read “nothing found” into a blank field.

If a condition raises a workplace safety question, stop and follow the direction of your state or territory WHS regulator. Record the area, the condition, the decision not to proceed and the next action. Do not use the treatment record as a substitute for required safety documents.

Complete the record when no treatment occurs

A no-treatment visit still needs a proper pest treatment log entry. Record the areas inspected, evidence found, access limits and reason no product was applied.

Then state what the customer must do and whether the job needs a return visit, a new quote or no further action. Select “not applied” in the application section rather than leaving it empty.

Before leaving the next site, read the inspection entry once. Could another tradie find the same spot without calling you? If not, make the location more precise.

Complete the pesticide application record from actual work

Fill in the pesticide application record after the work. Never copy the planned treatment from the work order and present it as completed.

Enter the product details checked for the job. Record the target pest, exact application site and method actually used. Add the amount or dilution, applicator, equipment, time or site-condition fields that your label and regulator checks require.

“Applied outside” is useless. Name the elevation, door, crack, device, surface or landscape area. If the product was applied at several points around a commercial property, create separate location entries or a clear site map reference.

Keep three separate fields:

  • Inspection finding: what you observed before treatment.
  • Treatment decision: why you treated, postponed or did not treat.
  • Application entry: what product use actually occurred.

This separation lets the office answer a direct customer question. It also lets a supervisor spot an application entry with no matching inspection or authorised scope.

Do not prefill the previous product, amount, dilution or method on a recurring visit. The earlier record is history, not an instruction for the next application.

Check the next completed pesticide application record against the container label and your checked form fields before the tradie leaves the site.

Stop when the authorised scope changes

The work order covers the kitchen. On site, you find activity around a separate storeroom. Record the storeroom finding first. Then check whether the authorised scope includes that area.

If it does not, stop. Describe the extra work, get the customer’s approval and write a variation before treating the added area. Record who approved it, how approval was given and what extra work was accepted.

Do not hide the change in “treated premises”. That breaks the link between authority, treatment and billing. If the customer declines, record the declined work and the untreated location.

Worked example: approval before extra work

All figures in this house electrical example are sample currency units.

R. Chen at 14 Oak Street accepted quote Q-1847 for 1,105. The bathroom exhaust fan and four LED downlights were quoted, but chasing was excluded. The ceiling was lined, so extra cable and chasing became an approved 160 variation. Invoice INV-1847 was then 1,265.

The point is the approval chain. The excluded work became necessary, the change was written down, approval came before the extra work, and the invoice followed the approved variation.

Use the same control on a pest job. Record the new site finding. Define the added treatment area. Get a yes. Then do and bill the extra work.

Review your current variation form now. It needs the linked work order, changed condition, added scope, customer approval and resulting billable work.

Close the visit with instructions and pest site notes

Do not finish with “advice given”. Write the instruction, the location it covers and the next action.

Tell the customer what to prepare, avoid, monitor, clear or repair. Use the product label and your regulator-confirmed process for treatment precautions. Do not turn a standard office script into product-specific directions without checking it.

Record who received the handover. Add whether it was spoken on site, sent electronically or left through another approved method. If the site contact was absent, state how the instructions were delivered.

Label every photo with the visit and exact location. “IMG final” will not help when the office is answering a question later. Use entries such as the unit, room, doorway or exterior face shown.

A photo supports the written record. It does not replace a location, finding, treatment decision or application entry.

Before you leave, ask the site contact to repeat any action that must happen before the next service. Correct misunderstandings in the handover entry while you are both still there.

Preserve the history of recurring visits

Add new pest controller treatment records for every attendance. Never open the old pest treatment log entry and rewrite it as the current visit.

Link the visits through the customer, site and recurring job. Carry forward unresolved access issues and promised follow-up actions, but confirm them again on site. Do not carry forward old application details as defaults.

The next tradie should be able to see this sequence: what was found before, what was done, what remained inaccessible and what needed checking today. Each visit must still stand on its own.

If a record needs correction, keep a correction trail. Record the corrected field, the new entry, who made the correction and when. Do not silently replace the original site account.

Connect the checked visit to the invoice by job reference. The record proves what happened; the invoice requests payment. For the billing step, use the pest control invoice guide for recurring treatments.

Recurring service billing should start from the completed scope and approved variations, not from a copied schedule alone. Keep GST, ABN, BAS and tax-invoice questions with the Australian Taxation Office (opens in a new tab). Accounting corrections must not rewrite the treatment history.

On your next recurring visit, open a new entry and bring forward only the unresolved action as a prompt to inspect. Leave the previous application untouched.

Run the office close-out before billing

The office should check the record before marking the visit complete. Do not wait for a call-back or customer question to expose the gaps.

Return the record when:

  • A finding or application has no exact location.
  • An inaccessible area looks inspected.
  • Product details, amount or dilution, or other checked application fields are incomplete.
  • Extra work has no recorded variation approval.
  • The customer instructions or next action are missing.

Send the record back to the tradie as a correction. Do not let office staff silently invent a location, product detail or approval from memory.

Keep the treatment record separate from the invoice even when both sit under one job. The invoice can carry the service description, approved variation and accounting details. The site record keeps the inspection, pesticide application record, exceptions and handover.

A job system can hold the work order, site record, attachments and invoice under one reference. Yes Foreman’s pest control job workflow can keep that chain together without turning a broad invoice line into the treatment history.

Give one supervisor a set of completed pest controller treatment records today. Ask them to identify what was authorised, what was inspected, what was applied where, what changed, who approved it and what happens next. Return the record if any answer depends on a phone call.

Put the next job in one place

Yes Foreman connects quotes, schedules, crews, timesheets and invoices for small field-service teams.