A file, not an argument
Every treatment ends with dated counts a client can see. Callbacks are caught early and disputed jobs are settled by the number.
Insect GateProof of treatment
A treatment is paid for on the day. Proof comes later.
A unit left in place after heat, steam or bait keeps counting through the weeks that follow. Zero is evidence. A count on night three is a callback you caught before the client did.
Example console readings for one room after a heat treatment: zero counts on days 1, 7, 14, 21 and 42.
What proof looks like
Bed bug eggs hatch over two to three weeks and survivors can go a month without feeding. A treatment that looked complete on the day can start again on day twenty. A monitor at the bed legs counts through the whole window, and the console shows the run of zeros with dates.
The same applies to a kitchen after bait. Counts should fall to zero within a fortnight. If they do not, the bait, the sanitation or the harbourage search needs revisiting, and the count says so before the client does.
Sold per job, not per site
The lure lasts a year and the unit needs no visits, so leaving one behind costs little. Priced into the treatment, it changes what the client is buying.
Evidence they can forward
A read-only console login shows the room, the count and the date. Nothing to interpret, and something to show a guest, a tenant or an auditor.
A reason to stay
The unit stays after the job and the contractor stays with it. The next incident is caught by the monitor already in the room.
How to run it
Place the unit at the end of the treatment, name it for the room, and clear the count. Leave it for at least six weeks. Send the client the console link. When the run of zeros is long enough, the job is closed with a file behind it.