Property manager pest response SOP: the 7-step protocol that keeps you RTB-safe

Why property managers need a documented SOP

Property managers face dual accountability: to the property owners they represent (minimize cost, minimize legal exposure) and to the tenants they interact with (RTA-compliant response, timely action). A pest report that is handled informally — logged in someone's email, mentioned on a call, delegated without confirmation — is a pest report that fails at RTB when it escalates. RTB arbitrators look for the gap between tenant report date and landlord action date. A property manager who cannot produce a documented timeline of their response loses disputes they would win with proper documentation. The SOP below converts best-practice behavior into a documented system.

The 7-step pest response SOP

How to

Property manager pest response SOP

The 7-step protocol for BC property managers from pest report receipt to file closure — designed for RTB compliance and consistent portfolio-wide execution.

1
Step 1: Log the report within 2 hours of receipt
Enter into your property management system (or a dedicated log): date and time received; property address and unit; tenant name; pest type as described; report method (email, text, voicemail); evidence provided (yes/no; if yes, attach). Assign a reference number. This timestamp is your documented response start.
2
Step 2: Acknowledge in writing within 24 hours
Send a written acknowledgment: 'I have received your pest report for [unit] dated [date]. I am arranging an inspection within [X] business days. You will hear from [pest contractor name] to schedule. Your report reference is [#].' This acknowledgment establishes your response date in the documentation trail.
3
Step 3: Contact pest contractor and schedule inspection within 7 days
Contact your pest contractor immediately. Provide address, unit, pest type, and any evidence the tenant provided. Request a written inspection report. For multi-unit buildings, request the inspector advise on adjacent-unit scope assessment. Confirm the inspection date and communicate it to the tenant.
4
Step 4: Issue RTA-compliant entry notice to tenant
Issue Section 29 notice: minimum 24 hours, in writing, specifying date, time window (e.g., 10 AM–12 PM), and purpose ('pest inspection and potential treatment'). Best practice: 48 hours. Include tenant prep instructions if chemical treatment is likely. Keep a copy with delivery confirmation.
5
Step 5: Receive inspection report and authorize treatment within 24 hours
On receipt of the inspection report, review the scope recommendation. Authorize the recommended scope — do not reduce scope to save cost without documented justification. For multi-unit scope, confirm with the property owner that you have authorization to approve the expenditure (or verify your contract authority). Communicate authorization to the pest contractor in writing.
6
Step 6: Coordinate treatment access and receive photo report
Issue treatment-day entry notice (48-hour minimum). Confirm access logistics (key with building manager, buzzer code, key box). After treatment: request photo report delivery within 30 minutes of completion. File the photo report by property, unit, and date in your property management system. Forward to property owner if required by your management agreement.
7
Step 7: Monitor and close the file
Set a 21-day follow-up reminder. If the pest contractor recommends a monitoring inspection, schedule it. At day 21, confirm with the tenant: any new observations? If yes, initiate the protocol from Step 3 with the new report. If no: close the file with a documented clearance note. Total file duration target: 21–35 days from initial report to clearance.

Adapting the SOP for building-wide issues

When a building-wide infestation is confirmed (multiple units, migration-type pest), the SOP expands: Step 3 includes scope assessment of the full migration corridor (not just the reporting unit); Step 4 involves notices to all affected units; Step 5 authorization may require escalation to the strata council or property owner for larger expenditures; and Step 7 includes building-wide monitoring rather than single-unit monitoring. The timeline may extend to 30–45 days for building-wide treatment completion. Document each step for each affected unit separately.

SOP compliance and RTB risk: where deviations cause problems.

SOP deviation	RTB consequence	Risk level
No written acknowledgment within 24 hours	Response date unclear; arbitrator may use tenant's claimed date	Medium
Inspection not arranged within 7 days	RTB may order rent reduction from report date	High
No RTA-compliant entry notice	Entry may be invalid; tenant may have grounds to refuse	High
Single-unit treatment when building-wide recommended	High recurrence; tenant re-claims; property owner exposure	High
No photo report filed	No documentation of treatment completion date	Medium
File not closed with clearance note	Ongoing open period; unclear end date for any compensation period	Medium

Frequently asked questions

What if the property owner instructs me to delay treatment to save cost?+

Document the instruction in writing and advise the owner of the RTB timeline obligations. Delay beyond 21 days without legitimate reason creates liability for the owner and may involve the property manager if you execute the delay without objection. A brief email noting your advice and the owner's instruction protects you.

Should the SOP vary based on pest type?+

The documentation and timeline are the same for all pest types. The scope of treatment varies — bed bugs and cockroaches in multi-unit buildings trigger expanded adjacent-unit protocols; single-unit infestations follow a simpler path. The SOP framework is pest-type-agnostic.

What software should I use to track this?+

Any property management software with maintenance ticket functionality works: Buildium, AppFolio, Yardi, PropertyMe. If you're not using PM software, a shared spreadsheet with the 7 SOP fields per ticket is the minimum viable system. The requirement is date-stamped documentation; the tool is secondary.