Pest control software for Melbourne operators

The Victorian record schema is the most granular in Australia, and it is the reason a form built for another state will not do in Melbourne. Under the Public Health and Wellbeing Regulations 2019 a Victorian record carries fields that simply do not appear elsewhere.

The batch number is the clearest example. No other state we cover asks for it, and it cannot be reconstructed after the fact — once the drum is empty and gone, the number is gone with it. Capturing it means capturing it at the moment of mixing, which is a field-app problem, not an office problem.

Victoria is explicit that a third-party form must match the Department of Health template section for section. That single rule rules out a lot of general trades software, because a job app with a bag of custom fields produces a document shaped like the software, not shaped like the template.

The Department also states plainly that electronic and smartphone records are acceptable, that a job-site analysis is expected before every job, and that falsifying a record is an offence. Put those together and the compliant workflow is obvious: the assessment happens on arrival, the record is filled in on the phone while the work is in front of you, and it is signed at the end — not rewritten on Monday from a text message.

Because Victoria requires records to be kept at the business address for at least three years, an operator with technicians running their own paperwork has a structural problem. Records scattered across five phones are not held at the business address in any meaningful sense.

Melbourne’s housing age changes what the work is. A city of stumped weatherboards, brick veneer on suspended floors and accessible subfloors produces a high volume of pre-purchase and regular timber pest inspections, and those reports have their own document requirements under AS 4349.3 — inspector credentials, the pre-engagement agreement reference, findings split between live activity, past evidence, visible damage and conditions conducive, the areas that could not be accessed, a risk rating, and the next inspection interval.

Where a management system is installed or a treatment carried out under AS 3660, the certificate and the durable notice are separate artefacts with their own retention. In practice a Melbourne operator is producing three document families — the statutory application record, the inspection report, and the certificate or notice — and they all have to reference the same job.

Hunter treats the Victorian schema as the superset it is. Batch number, precautions, method, quantity and rate, applicator and supervisor licence numbers and the signature are all first-class fields, so a Melbourne application record validates against the Victorian profile and cannot be closed half-filled. Weather captures with a time stamp, so a change mid-job is a second reading rather than an overwrite. Records live in one place — the business’ account — not on five technicians’ phones.

Alongside that, Hunter runs the recurring inspection cycles that Melbourne timber pest work depends on, tracks the warranties that lapse when an inspection is missed, keeps technician licences and their expiries, maintains the hazardous chemicals register with current SDS, and puts an AI agent on the phone calls, quotes and follow-ups.

For the field-by-field detail, see our guides to VIC pesticide record requirements, to pesticide application records across Australia, and to AS 3660 termite management.

This page is general information, not legal advice. Requirements change; confirm your current obligations with the Victorian Department of Health.