Why IPM starts with a written record
Integrated Pest Management is defined by the EPA as "an effective and environmentally sensitive approach to pest management that relies on a combination of common-sense practices" — one that manages damage "by the most economical means, and with the least possible hazard to people, property, and the environment" (EPA IPM Principles). Notice what that definition asks of you: it is not "spray less," it is "decide from information." Every IPM program — farm, greenhouse, or a single tomato bed — runs on monitoring data, and a log is simply monitoring you can actually remember.
The stakes of guessing are higher than most gardeners think. UC IPM points out that only about 1% of all insects and mites are harmful, and that most pest species are simultaneously attacked by multiple natural enemies. A no-data treatment decision doesn't just waste money — it kills the free labor force already working in your garden, which is exactly how small pest problems get worse (UC IPM).
What to write down (and what to skip)
A useful pest log is six fields long. Anything fancier stops getting filled in by week three:
| Field | Example entry | The decision it drives |
|---|---|---|
| Date + time of day | Jul 14, 7:15 AM | Links the sighting to a life stage and season — the same count means different things in May vs. August |
| Pest + stage + count | Aphids, ~40, all wingless, on new growth | Wingless means the colony has not started dispersing — timing for intervention |
| Location | Bean bed, undersides of top leaves | Where to scout next, and where any treatment must actually reach |
| Action taken (or deliberately not) | Nothing yet — counting again in 3 days | An honest "wait and watch" is a data point too; it builds your threshold intuition |
| Conditions | Third dry day above 90°F | Connects outbreaks to weather patterns you can see coming next year |
| Outcome at 7 and 14 days | Day 7: ~15. Day 14: fewer than 5 | The only real evidence a treatment worked — or did not |
The three patterns your log will reveal
- A treatment that doesn't move the count. If two applications of the same product leave counts flat, the problem is wrong identification, wrong coverage, or resistance — not "you didn't spray enough." The fix is rotating to a product with a different active ingredient class, and the log is what stops you from buying the same chemistry under a new label. (Extension services warn that differently-named products frequently contain the same active ingredient — always read the label, not the brand.)
- Repeat seasonal windows. Most garden pests arrive on a schedule — the log converts one year of observations into next year's prevention calendar. The seasonal defense calendar covers what's typically active when; your own records make the timing local and precise.
- Escalation creep. If each year your log shows more spraying for the same pest, the cause was never removed — usually habitat, food waste, or a plant that should be moved. The damage checker helps separate pests you must act on from damage you can tolerate.
Thresholds: when a count becomes a decision
The money-saving core of IPM is the action threshold: the count at which the expected damage costs more than the intervention. In a home garden your threshold can be as simple as "I act when counts grow for two straight check-ins" or "I act if tomatoes are being lost, not when I spot the first aphid." Writing counts down is what makes that line visible — and it is the difference between treating a problem and treating your own anxiety. Every spray is also a decision about the predators in the bed: check what you might be killing first in the beneficial bug matchmaker, and time any necessary spray to protect pollinators with the pollinator-safe spray guide.
Sources: EPA (Integrated Pest Management Principles) and UC IPM (Biological Control and Natural Enemies of Invertebrates).