The Rodent Control Report: What to Document for a Mouse or Rat Program in Canada

Rodents are a different kind of job from a bed-bug blitz or a wasp nest. You don't show up, treat, and leave. You install a system — bait stations and traps around a building — and then you come back, again and again, to read it. Mice (souris) and rats (rats, or surmulots for the brown Norway rat) are managed as an ongoing monitoring program, and the paperwork has to match that shape. The report isn't a snapshot of one visit; it's a ledger that grows.

This is a companion to our main guide on the pest control intervention report, which covers the full regulatory picture — licensing, the pesticide-use record, retention, and the record-vs-notice distinction across Canada. Read that one for the legal frame. This piece assumes you know it, and stays on what's specific to rodents: the station map, what you log at each one, and why the log itself is the deliverable.

Why the station log is the whole game

A rodent program lives or dies on one artifact: a numbered map of every device on site, with a history of what happened at each one. Not "we baited the building." Station 7, north wall of the loading dock, bait block, all taken since the last visit — replaced, and flagged for follow-up. That granularity is what separates a program from a guess.

It's also what an auditor, a client, and your own technician on the next rotation all need. The regulator wants to see product used and traced. The client wants proof the pressure is dropping. And whoever services the site next month needs to know what station 7 looked like this month. One well-kept log answers all three.

What a rodent report has to capture

Layer the rodent-specific detail on top of the standard pesticide-use record. Beyond the usual date, client, address, target pest, certified applicator, and signature, a defensible rodent report documents each of the following — per station, per visit.

1. 1A station map and numbering. Every bait station and trap has a permanent number and a fixed location, drawn or listed so anyone can find it. The map is the backbone; without it, the rest of the log is just floating notes.
2. 2Each station's location. Where device 7 actually is — "exterior north wall, loading dock, 3 m east of the door." Specific enough that a new technician finds it without you.
3. 3Bait or trap type, and the product. Whether the device holds a solid rodenticide block, a snap trap, a glue board, or a multi-catch trap — and, for any rodenticide, the product name paired with its PCP registration number (the Health Canada identifier, more below).
4. 4Consumption or activity, this visit. The reading that makes it monitoring: bait untouched / partially taken / all taken, trap sprung or empty, droppings or gnaw marks nearby, a catch recorded. This is the data point you compare across visits.
5. 5Servicing done. What you did at the station — rebaited, reset, cleaned, relocated, removed — so the log shows action, not just observation.
6. 6Identified entry points. Gaps, cracks, unsealed penetrations, door sweeps missing — the routes rodents are actually using. Documenting them is half the value you deliver.
7. 7Exclusion and sanitation recommendations. What the client has to fix — seal that gap, clear that clutter, fix the dumpster lid. In writing, so "you never told us" isn't available six months later.
8. 8Quantity and the certified applicator, signed. Same as any pesticide-use entry: how much product, who did the work with their certificate number, and a signature on the visit.

The PCP number still applies — even for a bait block

It's easy to think of a station full of solid bait as somehow lighter than a spray application. It isn't, on paper. A rodenticide is a registered pest-control product like any other: no product may be used in Canada unless it's registered with Health Canada's Pest Management Regulatory Agency (PMRA) under the federal Pest Control Products Act, and every registered product carries a PCP registration number on its label. Record it against the product on the station log, used per label. It's the same field an inspector scans for on any pesticide-use record — bait blocks don't get a pass.

The Québec twist: no notice, so the register carries it

Here's the nuance that makes rodent documentation different, and it's worth stating plainly because it cuts the other way from what you'd expect. After most indoor treatments, several provinces make you leave a written re-entry notice with occupants. In Québec that's the after-treatment notice under the Code de gestion des pesticides — with prescribed content and a Poison Control number.

But solid bait placed inside tamper-proof stations is an exception to that notice. A sealed, locked bait station isn't the same exposure risk as a sprayed baseboard, so it doesn't trigger the same occupant-notice obligation. Which sounds like less paperwork — until you see what it actually means: there's no posted notice standing in as a record of what you did. The only durable trace of that station, that product, that PCP number, that date, is your own register. The register isn't a backup here. It's the whole record.

For a bait station, the notice exception doesn't lighten your documentation — it concentrates it. Nothing on the wall is recording the job. Your station log is.

The provincial specifics of that notice, its exceptions, and the register's required content are covered in the pillar guide. The takeaway for rodents: don't let "no notice required" quietly become "nothing written down." The exception raises the stakes on your log, it doesn't lower them.

Building the rodent report as a form

A rodent log is punishing on paper. You're recording the same handful of fields for a dozen or more stations, every visit, forever — and comparing this visit to the last one. Handwriting that on a pad means illegible entries, skipped stations, and a history nobody can search. A structured form is the natural fit.

• A repeatable station block. One set of fields — number, location, device type, activity, servicing — repeated per station, so a route of fifteen stations is fifteen quick entries, not a wall of free text.
• Activity as a tap, not a paragraph. Untouched / partial / all taken / catch / trap sprung as preset options, so the reading is consistent and comparable across visits.
• Product and PCP number paired and required wherever a rodenticide is in play — neither submittable without the other.
• Entry points and recommendations as their own fields, so the exclusion advice you gave the client is captured, not buried.
• A signature field for the certified applicator, on the same visit.

That's the shape of our free pest control intervention report form template — a field-ready starting point you can extend with a repeatable station section for rodent routes. Every visit is stored in a dashboard, so the station-by-station history builds itself: the running log that makes the program defensible is a by-product of just doing the visits.

And because rodent work is recurring by nature — the same sites, on a rotation — the other half of the job is scheduling and assigning those station-servicing visits so none of them slip. Our look at pairing an intake form with a field-service dispatch tool covers how the capture form and the recurring-visit scheduling fit together.