National field manual

Dead patches: separate symptom from cause

Investigate whether plants failed to emerge, declined after emergence or were damaged later before choosing a repair.

A brown patch is not automatically dead, and a dead patch is not automatically a disease. The most useful first question is what happened over time. Did the area never emerge, did young plants decline, or did established-looking growth change after a later event? This HAUSE investigation guide helps an owner prepare a useful record for competent advice. It does not diagnose an insect, pathogen, chemical injury or soil problem from colour alone, and it does not recommend a fungicide or other treatment without identification.

Establish the sequence of change

Find the earliest photograph or observation of the affected area. Record emergence, mowing, watering changes, traffic, product applications and unusual weather in order. Ask whether the patch appeared suddenly or expanded gradually. A current photograph can show the symptom but cannot reconstruct that sequence by itself. If dates are uncertain, label them as approximate rather than inventing a precise history.

Separate areas that never established from areas that grew then declined. The investigation may take different directions. The University of Maryland Extension — diagnosing lawn problems resource explains that several causes can produce overlapping lawn symptoms. Its Maryland examples are not a diagnostic key for every Canadian planting. Use the principle of competing explanations and seek local expertise where the evidence points to a biological or specialized soil issue.

Map shape, location and reference areas

Measure or estimate the patch boundary using a clearly stated method. Note relationships to paving, sprinkler patterns, pet routes, mower turns, building shade, snow storage and previous construction. Include a healthy reference area with a similar intended treatment. Photograph the entire pattern and selected close views with scale. A close-up without location can hide a straight application band or a repeated equipment route.

Do not interpret a circular shape as proof of a specific cause. Several mechanisms can create similar outlines. Likewise, a dark green edge is information to record, not a sufficient basis for a diagnosis. Retain the images before raking, reseeding or adding products. If investigation requires a plant or soil sample, ask the advisor how to collect and preserve it appropriately rather than sending an unsuitable dried handful.

Check water and physical conditions first

Observe whether water actually reaches the patch and whether the ground is persistently wet, dry, compressed or disturbed. A functioning controller does not prove even distribution. Review the condition beneath the visible symptom through safe, authorized assessment where needed. University of Minnesota Turfgrass Science — diagnosing struggling lawns discusses multiple site factors associated with weak turf. It supports considering the growing environment rather than treating every decline as a product problem.

Look for changes after the first mowing or another maintenance visit. Record scalping, wheel marks, clippings and the machine used. Review any fertilizer or pesticide history with actual labels and dates. These checks do not exclude disease or insects, but they help the reviewer avoid prescribing a biological treatment for a physical or management issue. Keep observations factual and avoid assigning responsibility before the cause is examined.

Use a structured diagnostic request

InformationUseful detailWhy it matters
PlantingSeed mixture, application date and objectiveEstablishes the expected vegetation and stage
PatternMapped extent and comparable photographsConnects symptoms with site features
Care historyActual watering, mowing and productsShows changes before decline
Field conditionWetness, damage and soil observationsHelps distinguish competing explanations

Ask the reviewer what further evidence would change the conclusion. A useful diagnostic response should state its confidence and limitations. “Possibly disease; sample needed” is different from a confirmed identification. Record that distinction so a tentative suggestion does not become an unsupported treatment order when passed between people.

Treat disease as an identification task

University of Maryland Extension — lawn diseases describes lawn diseases and conditions that can favour them. It should not be used to match a single photograph and immediately select a fungicide. Young seedlings, mixed species and local weather can complicate interpretation. If disease is suspected, obtain appropriate identification and advice on whether an intervention is needed. Any pesticide decision must follow the actual Canadian label and local rules, not a foreign treatment example.

Imagine an illustrative 25 m² patch that declined after both a mower visit and a watering change. Changing the irrigation again, applying fertilizer and adding a disease product simultaneously would make the next observation difficult to interpret. Document the sequence, check the physical evidence and obtain a focused review. The scenario does not imply that either event caused the decline; it shows why chronology and controlled decisions matter.

Repair after the cause is addressed

Agree on whether plants may recover, whether dead material needs management and whether reseeding is appropriate. Define the repair boundary and any preparation needed. If the cause remains active, a fresh application may fail in the same pattern. Keep the repair's establishment date and care plan separate from the surrounding older lawn. A later mowing or traffic decision may need to protect the patch independently.

Mark whether each patch appeared suddenly or developed gradually, and whether its boundary is expanding. Compare a dated overview with a close view rather than relying on memory of colour. A caretaker change, equipment leak or altered watering arrangement belongs in the chronology even when its relevance is uncertain. Record those events as possible context, keeping the observation separate from any unconfirmed explanation of cause.

Photograph the repair baseline and review the response at agreed locations. If the problem repeats, revisit the evidence rather than treating repetition as proof that a stronger product is required. Continue with patchy-emergence diagnosis, fertility decisions and mowing readiness.

Sources and further reading

Read each source in its own product, jurisdiction and project context. Local requirements and the actual project documents govern the work.

Bring the chapter into your project

Keep the relevant measurements, documents, observations and unresolved questions together. Your enquiry brief remains editable before you choose to send it.

Prepare your project enquiry ↗

A clearer next step

Bring your questions.
Leave with a better brief.

Tell HAUSE what you are planning, what you have observed and the decision you need help with.

Start a service request