The Cockroach Treatment Report: What a Technician Has to Document (Canada)

A cockroach job is not a one-visit job, and that single fact changes what your paperwork has to do. You can knock a bed-bug or wasp problem out in a visit or two and close the file. German cockroaches — the ones that turn up in apartment kitchens and never the woods — are a program: bait, monitor, re-inspect, re-bait, rotate. The report isn't a record of one treatment; it's the running log of a campaign. If it can't show the trend, it can't do its job.

This guide assumes you already know the general shape of a pest-control report — the fields every job needs, the PCP registration number, the difference between the record you keep and the notice you leave. If you don't, start with the pest control intervention report guide, which covers the whole regulatory frame for Canada. Here we stay narrow: what's specific about documenting cockroaches, and where those jobs go wrong on paper.

Why cockroach documentation is its own thing

Two features of German cockroach control break the one-visit report model that works fine for most pests.

• It's a multi-visit program. Bait takes time to cycle through the population, and an IGR works on the ones you can't see yet. A single visit that isn't followed up is a visit that failed — and a report that stops at visit one can't show the treatment ever worked.
• It's a multi-unit problem. In an apartment or condo building, cockroaches travel through shared walls, plumbing chases, and voids. Treating one unit and ignoring the neighbours is how you get a callback in a month. The report has to record what you did about the units next door, not just the one on the ticket.

What the cockroach report has to capture

On top of the standard fields — date, address, target pest, product, PCP number, quantity, certified applicator, signature — a cockroach job needs the following, and these are the ones home-made forms tend to miss.

Units and rooms treated

"Apt 4" is not enough. German cockroaches live where it's warm, humid, and close to food, so the report should pin down the rooms and harbourages actually treated: kitchen (under and behind appliances, sink void, cabinet hinges), bathroom (vanity, plumbing penetrations), and any other food-handling area. In a multi-unit building, name the specific unit and record every unit inspected — including the ones you couldn't get into.

Product, PCP number, and method

Record not just what you used but how you used it, because the method drives the re-entry rules. German cockroach programs lean on gel bait placed in cracks and voids and an insect growth regulator (IGR); some jobs add a residual or flushing product. Each product needs its commercial name and its PCP registration number — Health Canada's identifier under the Pest Control Products Act — and a note of the application method (crack-and-crevice gel, IGR point-source, spot spray). If you rotate to a different active ingredient on a later visit to manage bait aversion, that's a new line with its own PCP number, not an edit to the old one.

Monitor placement and counts over time

Sticky traps are how you measure a cockroach program, so they belong in the report as data, not as a vague "placed monitors." Record where each monitor went (labelled by location) and the count at each visit. The trend across visits is the whole point: a count dropping toward zero is your evidence the program worked; a count that won't fall is your signal to rotate the bait, chase a missed harbourage, or look at the unit next door.

Sanitation recommendations to the occupant

Cockroach control fails when the kitchen keeps feeding them, so sanitation advice isn't a nicety — it's part of the treatment, and documenting that you gave it protects you when a client blames the product. Record the specific recommendations left with the occupant: eliminate food debris and grease, fix leaks and reduce moisture, store food in sealed containers, remove cardboard and clutter harbourage. Note whether the occupant was home to receive them.

Follow-up schedule and adjacent-unit inspection

• Follow-up date. When the next visit is due, so the program has a defined next step and the file doesn't silently go cold.
• Adjacent units inspected. Which neighbouring units you checked, what you found, and — critically — which ones you couldn't access. In a multi-unit building, an untreated neighbour is the reason infestations come back; the record of who denied or wasn't home for access is what protects you.
• Access and cooperation. Whether the occupant prepared the unit as asked (cleared cabinets, emptied under the sink). A job done in an unprepared unit is worth flagging in writing.

Bed bugs raise the same adjacent-unit question in a different form; if you also do that work, our bed bug treatment report guide covers the documentation for the other classic multi-unit pest.

When cockroach work triggers the occupant notice

The record-vs-notice split is covered in full in the pillar, but cockroaches have a wrinkle worth calling out, because the method you choose changes your obligations. Most German cockroach work is gel bait — small placements in cracks and voids. The moment you move to a sprayed or liquid application inside a dwelling, indoor-treatment re-entry rules and the written occupant notice come into play in the provinces that require them.

For cockroaches the report isn't a snapshot of one visit — it's the timeline of a program. Build it so each visit adds a row: products used, monitor counts, units inspected, next date.

Building the cockroach report as a form

Everything above is easier to capture as a structured form than as a scribbled page, and cockroach work especially rewards a form because it's repeated visits to the same address. The trend only exists if each visit is logged the same way.

• Rooms and harbourages as checkboxes — kitchen, bathroom, food-prep area — so the technician taps rather than types at the end of a long day.
• A repeatable product line pairing commercial name, PCP number, and method, so a rotation across visits reads as a clean history.
• A monitor-count field per location, captured every visit, so the falling (or flat) trend is visible at a glance.
• Adjacent-unit inspection fields — unit, result, access granted yes/no — because that's the field that protects you in multi-unit buildings.
• A required follow-up date, so no cockroach file ever ends without a defined next step.

That's the shape of our free pest control intervention report form template — a field-ready starting point you can adapt for cockroach programs by leaning on the monitoring and follow-up fields. Every visit is stored in a dashboard, so the address history — and your legal record — builds itself instead of living on loose paper in a truck.