Multiple Symptoms, Which Investigate First: Triage Decision Tree

Why this matters

A foundation inspection that opens with the owner listing five symptoms (sticking doors, a wall crack, a wet basement corner, a sloping floor, and a sagging porch) is the rule, not the exception. Without disciplined triage, the inspector chases the symptom the owner mentioned loudest, writes a scope around it, and either misses the upstream cause or addresses a downstream consequence at the price of the real driver. Reading which symptom is the root cause and which are downstream effects, which symptom is most urgent for safety, and which symptom is most defensible to document first, determines whether the diagnosis converges on the right scope. Four triage axes drive the sequencing: safety, root-cause-upstream, signal-to-noise on diagnosis, and owner expectation management.

Symptom presentation

Safety-first symptoms present as immediate hazards: visible wall bow with horizontal cracking and active deflection, large step cracks with offset on a bearing wall, slab cracks with vertical offset under load-bearing partitions, or any sign of imminent structural failure. Root-cause-upstream symptoms present as the soil, water, or load condition driving everything downstream: an active leak under a slab, surface drainage running at the wall, expansive clay heaving seasonally, a tree drawing moisture, or a load change such as an addition. Downstream-effect symptoms present as the visible result of the upstream cause: sticking doors, telegraphed drywall cracks, finish damage, all of which improve only when the upstream cause is addressed. Signal-rich symptoms present as ones that map cleanly to a single cause with low ambiguity (a horizontal crack at mid-height of a basement wall, a specific door binding in a specific orientation), while signal-poor symptoms present as ambiguous (slight floor slope that could be settling, heave, original construction, or all three).

Quick checks

Walk the perimeter exterior first and document every observable defect: cracks, grade, drainage, vegetation, hardscape, and recent owner work. Walk the interior and run a manometer survey across the whole footprint, not just the complaint area. Photograph every symptom with reference scale and tie to a numbered scope-of-symptoms list. Sort the symptoms by safety urgency first (any structural concern goes to the top), then by signal-richness (which symptom most narrowly identifies one cause). Note seasonality, weather context, and any recent owner work or building changes. Pull any prior repair history and warranty boundaries. Identify the symptom the owner most cares about; even if it is downstream, the conversation cannot ignore it.

Isolation tree

Branch first on safety. Any symptom with potential for sudden structural failure (bowing wall over 1 inch deflection, large stair-step crack with offset, slab crack with vertical displacement under load) jumps the queue and gets engineering review now; investigation continues but the safety symptom is addressed first regardless of root-cause analysis. Do not let a triage sequence delay an evaluation that affects life safety.

If no immediate safety concern, branch on whether one symptom is clearly upstream of the others. An active water source (under-slab leak, regraded perimeter, ponding water) drives moisture-related movement, finish damage, and crack reopening; address the water first or every downstream investigation will read polluted. A new load (addition, removed wall, new heavy equipment) drives settlement and crack patterns near the load change; investigate the load before chasing the cracks. Expansive clay heave under a slab drives sticking doors and finish cracks across multiple rooms; document the soil and the moisture cycle before scoping any cosmetic repair. A failed prior pier drives settlement at and around the piered area; review the original repair before adding new work.

If no clear upstream cause emerges from a perimeter walk and a manometer survey, branch on signal-richness. The symptom that most narrowly maps to a single cause (a horizontal crack at mid-height on a basement wall mapping to lateral pressure, a manometer drop over one specific bay mapping to a soft soil zone) gets investigated first because its conclusion narrows the remaining ambiguity. Signal-poor symptoms (a barely-noticeable slope, a hairline that may be original construction) wait until the signal-rich symptoms have driven the diagnosis.

Confirming diagnosis

Confirm the sequence with a written scope-of-symptoms list, ordered by safety, upstream-cause, and signal-richness, with the owner's signature acknowledging the planned investigation sequence. Confirm safety symptoms with an engineering inspection now; do not defer. Confirm upstream-cause symptoms with the test that closes the cause (static plumbing test under the slab, hose test on grade, soil moisture sampling for expansive clay per ASTM D4318, load review against the original design). Confirm signal-rich symptoms with the standard cause-specific workup (manometer survey, crack monitor installation, perimeter inspection). The triage document itself becomes the file's defensible record of why one symptom was investigated before another, which matters when the eventual scope addresses the real cause and the owner asks why the symptom they mentioned loudest was not first.

Remediation

Match the action to the triaged cause, not to the loudest symptom. For a safety-flagged condition, engage a structural engineer and stabilize first; investigation continues in parallel. For an upstream-cause confirmation (water, load, soil), address the cause before any downstream cosmetic or structural repair; injection of a crack while the wall is still being driven by lateral water pressure will fail. For signal-rich symptoms that confirm a specific cause, scope the repair against the cause and document the downstream symptoms expected to resolve. Set the owner's expectation that addressing the cause may take weeks or months to fully resolve the downstream symptoms (sticking doors after a leak repair improve as the soil dries and consolidates, not overnight). In every case, the triage document drives the conversation; without it, the company chases the loudest symptom and the owner blames the company for the next symptom that surfaces.

References

• IRC R401, General Requirements for Foundations
• IRC R403, Footings (bearing on undisturbed/competent soil)
• ASTM D4318, Test Methods for Liquid Limit, Plastic Limit, and Plasticity Index of Soils
• ACI 224.1R, Causes, Evaluation, and Repair of Cracks in Concrete Structures
• ICC-ES AC358, Acceptance Criteria for Helical Foundation Systems