Mushroom Pest Library

Quick recognition

Use mushroom pest library to identify, monitor and exclude pests through integrated pest management. Recognition begins the investigation; it does not confirm a cause.

• Identify the organism or group
• Separate adults from larvae and damage
• Use repeated trap counts
• Map entry and breeding routes

What to record

Capture crop stage, crop day, room, rack, layer, pattern, first observation, progression, compost and casing batches, watering, chemistry, pests and timestamped environmental readings.

Could it be something else?

Compare visual appearance with spatial pattern, progression, environmental history, process history and missing expected signs. Colour or one photograph is weak evidence.

Evidence still needed

State the unanswered questions and next measurement. Useful evidence can be visual, environmental, spatial, temporal, microscopic, laboratory, molecular, trap-based or process-history based.

Immediate safe direction

Document the affected area, avoid unnecessary disturbance or cross-room movement, isolate suspect tools, inspect adjacent areas and preserve representative evidence. Do not spray automatically.

Root-cause review

Trace the visible problem through water, evaporation, airflow, sensor placement, compost, casing, staff movement, flies, tools or room design where evidence supports the connection.

Chemical and regulatory boundary

Historical management literature is separated from current practice. No crop-protection dose is published unless the exact product, formulation, mushroom crop label, target, method, harvest interval, worker-safety information and current Indian status are verified.

When remote guidance is inadequate

Seek technical inspection or laboratory support for rapid unexplained loss, repeated outbreaks, suspected virus, unknown mould, severe pests, chemical injury, multiple affected rooms or unresolved contradictions.