Pest notes
Garden pest log template for clearer follow-up decisions.
A pest log helps you remember what appeared, where it appeared, when it mattered, and what you want to watch earlier next season.
Describe damage before naming the pest
When you first notice a problem, record the damage pattern before jumping to a name. Chewed leaves, holes in fruit, sticky residue, wilting stems, missing seedlings, or skeletonized leaves each point to different follow-up checks.
Add crop, bed, date, affected plant part, and severity. If you are unsure, write 'unknown' and take a clear photo for later comparison. Guessing too confidently can make next year's notes less useful.
The log should support observation and follow-up, not panic.
Track timing and location
Pest notes become much more useful when they include timing and location. A problem that appears every June in the same bed is different from one random damaged leaf in September.
Record the first date noticed, nearby crops, bed conditions, weather pattern, and whether the issue spread. These details help you decide where to inspect earlier next season.
Use the frost and weather page beside pest notes because cold, heat, rain, and drought often change plant stress and pest pressure.
Keep response notes practical
Write what you actually did: removed leaves, used covers, hand-picked, changed watering, improved spacing, added supports, cleaned debris, waited and watched, or removed a plant. Avoid vague notes like 'treated garden' because they do not help later.
Also record the result. Did the issue stop, slow, spread, or become irrelevant when the crop finished? A response is only useful if you know whether it mattered.
Do not use the notebook as a substitute for reading product labels or local guidance when using any garden product.
Add a next-season watch list
At the end of the month or season, turn pest observations into a watch list. Include crop, likely timing, bed, signs to inspect, and supplies to prepare. This moves pest notes from memory to action.
A watch list might say: check brassicas weekly after transplanting, inspect squash leaves in early summer, cover young greens before flea beetle damage appears, or avoid leaving fallen fruit under the plant.
Keep it short enough that you will actually use it.
Separate one-time damage from patterns
Not every damaged leaf deserves a major plan change. Mark each issue as one-time, recurring, spreading, severe, or unknown. This prevents a dramatic-looking but harmless event from taking over the garden plan.
Recurring and severe problems deserve more attention. One-time damage can simply be noted. Unknown issues should be watched, photographed, and reviewed before next season.
The pattern label is often more important than the exact pest name.
Link pest notes to crop verdicts
At harvest or cleanup, decide whether pest pressure changed the crop verdict. Some crops are still worth growing with better timing or covers. Others may need a different bed, spacing, variety, or season.
Write the decision next to the crop in your harvest log and your seed inventory. This prevents pest notes from sitting in a separate section where they are forgotten during planning.
A good pest log ends with a practical next step, not a dramatic conclusion.
Use photos as evidence, not clutter
Photos are helpful when the damage pattern is hard to describe. Take one close photo and one wider photo that shows the plant, bed, or surrounding crops. Then label the photo in the notebook with date, crop, bed, and the question you want to answer.
A labeled photo can help you compare the problem later, but it should not replace written notes. The written note tells you timing, spread, response, and result. The photo shows what the symptom looked like.
At the end of the month, keep only the photos that answer a future decision. Delete or ignore the rest so the notebook does not become a photo dump.
Prepare inspection routines for repeat crops
Some crops deserve a standing inspection routine because they are important to your garden or have shown repeat issues. Add a weekly check line for squash leaves, brassica undersides, young bean seedlings, tomato foliage, or ripening fruit if those areas matter in your beds.
A routine does not need to be complicated. Choose a day, walk the beds in the same order, check the same plant parts, and write one line if something changed. Consistency makes small problems easier to notice.
If a crop stays clean all season, write that down too. Negative evidence is useful because it tells you where not to spend extra attention next year.
Avoid mixing diagnosis notes with product instructions
If you use any garden product, keep the notebook focused on what you observed and what you did, while product labels and local guidance remain the authority for application details. This keeps the log honest and reduces the chance of repeating a vague or unsafe instruction later.
For notebook purposes, record the product category, date, crop, reason, and result. Do not rely on memory for rates, timing restrictions, or safety details. Those belong on the label or in local extension guidance.
The pest log should help you decide what to inspect earlier, what to cover, what to remove, and what to research before acting.
Worksheet fields to include
FAQ
Do I need to identify every pest?
No. Damage pattern, timing, and location can be more useful than a guessed name.
Should I include beneficial insects?
Yes, if they affect your decisions. Record observations that help you understand the garden, not just problems.
Can I include photos?
Yes. Label photos with date, crop, bed, and reason so they remain useful later.