For pest control
No report goes out until the treatment is recorded
A pest control job is only as good as what was written down about it. Which areas were treated, what was used, what was found, and whether the follow-up was ever done. When those live on a paper sheet in the van, the answer to a callback is a guess.
Treatment recorded first
The fields your process requires are filled in before a report can go out.
Callbacks on the original job
Each follow-up or warranty visit its own record, raised against the treatment it relates to.
Photos on the job
Damage, stations and labels kept on the record, scanned in Sydney.
Follow-ups that happen
Target days per stage, flagged on the record and emailed to whoever owns it.
Booked, inspected, treated, reported
Write the process down once: booked, inspection, treatment, report sent, follow-up, invoiced. Every job moves through those stages, with the customer, the property and the pest captured at the start.
Each stage carries your own written instructions, sitting on the step where the work happens, so a new technician reads what your business does at that point while they are doing it.
Record what your process requires
Make the fields your process needs required on the stage they belong to: the areas inspected, what was found, the areas treated, the product and quantity used, the technician's name. A job cannot move on to the report until they have values. Try, and it stays where it is, with the missing field named.
Use dropdowns for the pest and the treatment type so the records agree with each other and can be counted. What the record should contain is your call; Streams makes sure it is filled in every time.
Photograph the damage, the bait station or a product label and keep it on the job. Scanned text is read on our own service in Sydney, so the document does not leave the country.
Follow-ups and callbacks against the original job
Mark a follow-ups stream as a sub-stream of your jobs, and each return visit or warranty callback becomes its own record raised against the original treatment. Six months later, the history of that property is on one job rather than across three sheets.
Give the follow-up stage a target number of days. A follow-up past its target is flagged, listed in the weekly summary, and emailed to whoever owns it the morning after it goes over.
Customers told, then billed
Put an email on the report stage and it sends itself when a job reaches it, with the customer's details filled in. When the customer replies, the reply comes back onto the job with anything they attached saved on it.
Raise the invoice off the job with GST worked out per line, send it with the PDF attached, and connect Xero or QuickBooks so it goes across too.
A starting point: the Site Safety Inspections template
Run site safety inspections the same way every time: scheduled, inspected, every hazard actioned, then signed off. 4 stages and 14 fields, with written instructions on every stage. Change any of it, because it is your process.
Questions
- Can I stop a report going out before the treatment is recorded?
- Yes. Make the treatment fields required on the treatment stage. The job will not reach the report stage until they have values, and the technician is told which fields are missing.
- Does using this keep us compliant with pest control regulations?
- No software does that on its own. Streams makes sure the fields your process requires are filled in every time and keeps a record of who entered what and when. What those records must contain under your licence is still your call.
- Can it schedule technicians and service rounds?
- No. There is no scheduling, dispatch, calendar, recurring job or GPS tracking built in. Planned dates can be shown on a timeline.
- Can customers pay by card from the invoice?
- Not today. Invoices go out with the PDF attached and sync to Xero or QuickBooks, and payment is taken however you take it now.
Weighing it up against
Other trades doing the same thing
Start with the free plan
Two users, 500 records and every feature switched on. No credit card, and your data stays in Australia.
Get started free