Post-Repair Settlement Recurrence: Response

Purpose

The post-repair monitoring SOP ends its escalation path with two sentences: tell the supervisor the same day, and re-engage the engineer where the design was sealed. This procedure is what happens after those two sentences, and it is where a confirmed recurrence either closes as a covered warranty repair with a documented cause, or turns into the exact argument the monitoring program was built to prevent.

A confirmed recurrence is not automatically a workmanship failure, and it is not automatically excluded from warranty either. A pier can meet its torque and depth criteria and the ground can still find a new way to move around it; a lift can hold and a downspout the customer never reconnected can put water against the wall all winter. Which of those happened determines everything downstream, so this procedure's first job is establishing cause before anyone promises a fix, and its second job is keeping the promise and the cause consistent with each other in writing.

Scope

Covers the response once the post-repair monitoring program's escalation criteria are met: root-cause classification, warranty determination, engineer re-engagement, customer disclosure of the finding, remedial work authorization, and re-baselining monitoring after the fix.

Does not cover the monitoring visit itself, the threshold, or the escalation decision, which the post-repair monitoring SOP owns in full. Does not cover the diagnostic method for determining cause, which routes to the applicable troubleshooting card for the observed pattern of movement. Does not cover the remedial repair work itself, such as a re-lift or an added pier, which runs under the SOP that governs that work once this procedure authorizes it.

Roles and responsibilities

Procedure

Step 1: Freeze customer commitments the moment the escalation lands

The supervisor takes the escalation from the tech and does not authorize anyone to tell the customer a cause, a cost, or a timeline before the reading is independently confirmed and the cause is classified. Acceptance: no commitment made beyond acknowledging the reading and the next step. Wrong looks like a well-meaning supervisor telling a worried customer "it's probably just the piers settling a little more, we'll add depth" on the phone the same afternoon, before anyone has looked at the data twice. Stop rule: any commitment made before step 3 closes gets walked back in writing, which costs more trust than waiting a day would have.

Step 2: Independently re-verify the reading before treating it as real

A second technician re-shoots the flagged grid point and re-reads the flagged crack gauge, using the same benchmark, instrument and method the monitoring SOP specifies, without being told the first reading's value in advance. Acceptance: the second reading matches the first within the monitoring program's own stated repeatability spread. Wrong looks like accepting a single reading from a tech who may have mis-set the instrument or misread a gauge in poor light. Stop rule: where the two readings disagree by more than the repeatability spread, re-shoot a third time and treat the instrument and setup as suspect before treating the structure as suspect.

Step 3: Classify the root cause using the existing diagnostic method

Route the confirmed reading, the crack pattern, and the site conditions to the applicable troubleshooting card for the observed symptom to determine which of the recognized causes fits: continued soil consolidation below the original pier depth, a new load added since the repair, a plumbing or drainage condition introducing water the original design did not account for, or an installation criterion that was in fact not met. Acceptance: a written classification citing the diagnostic path that led to it. Wrong looks like guessing at a cause from experience without running the actual diagnostic steps; a guess that happens to match the eventual finding still leaves no record showing how it was reached, and the warranty administrator has nothing to point to later.

Step 4: Determine warranty scope from the classification, not from the customer relationship

Where the classification finds an original installation criterion was not met, such as a pier that logged below its design torque or depth, or a lift bracket that was never re-verified after lock-off, the remedial work is covered under warranty regardless of how the recurrence looks to the customer. Where the classification finds a new external condition, such as a downspout disconnected by the homeowner or a new addition adding load the original design never priced, the remedial scope is a new job. Acceptance: a written determination stating covered or new-scope, with the classification from step 3 cited as its basis. Wrong looks like a determination that varies by how upset the customer sounds on the phone rather than by what step 3 found; and if the classification and the determination do not agree, the determination is wrong, not the classification.

Step 5: Re-engage the engineer where the original design was sealed

Send the confirmed reading, the classification and the proposed determination to the engineer of record for review before any remedial design is finalized, since a sealed design's limitations paragraph typically does not cover a condition discovered after the fact. Acceptance: written engineer sign-off on the remedial approach, or a revised sealed design where the original criteria genuinely need to change. Wrong looks like the shop designing an added pier or an extra anchor on its own experience when the original job carried a stamp; that stamp does not transfer to work nobody sealed.

Step 6: Present the finding and the remedy to the customer in one written document

Give the customer the classification, the warranty determination, the proposed remedial work, and, where the scope is new, the reason it falls outside the original repair, all in one document rather than a sequence of phone calls. Acceptance: a written summary delivered before remedial work is scheduled. Wrong looks like a verbal explanation followed by a separate invoice with no document connecting the two; a customer reading only the invoice sees a bill with no reasoning attached to it.

Step 7: Execute the remedial work under its own governing procedure

Route the actual repair, whether an added pier, a re-lift, a drainage correction or an anchor adjustment, through the SOP that already governs that work, rather than treating this incident as license to improvise a new method. Acceptance: the remedial work's own record, produced under its own SOP, attached to this incident file. Wrong looks like a crew skipping the standard pier installation log because "this is just a warranty fix," which leaves the second repair with less documentation than the first one had.

Step 8: Re-baseline monitoring after the remedial work closes

Do not continue the old monitoring series as if the recurrence never happened. Set a new benchmark and a new zero reading the day the remedial work demobilizes, following the post-repair monitoring SOP's own commissioning step, and note on the record that this is a restarted series with a stated reason. Acceptance: new baseline survey, new crack gauge zeros, and the restart reason on the record. Wrong looks like plotting the new readings against the pre-recurrence baseline, which buries the recurrence inside a series that no longer means what it did before the remedial work.

The record this produces

One recurrence incident file: the original escalation, the independent re-verification reading, the classification with its diagnostic path cited, the warranty determination and its reasoning, the engineer's sign-off or revised sealed design, the customer summary, the remedial work's own record, and the restarted monitoring baseline.

The warranty administrator reads the classification-to-determination link first on any dispute, because the whole file exists to show that the determination followed from a finding rather than from how the conversation went. The estimator reads the classification when the same street or the same soil condition produces a second call.

One worked pass

Nine helical piers, installed fourteen months earlier, escalate under the monitoring program's rule at a rear grid point reading 0.29 in against a 0.15 in threshold, confirmed on two consecutive readings. Step 1 holds: the supervisor tells the customer a technician will re-verify before anyone says anything about cause.

Step 2's re-verification, run by a technician who was not told the first figure, reads 0.27 in, inside the program's own repeatability spread of the original reading. The reading stands. Step 3 routes it to the applicable settlement-recurrence troubleshooting card, which walks the crew through checking the as-built installation log against current conditions rather than assuming either soil or workmanship.

The as-built log shows pier 4, nearest the flagged point, logged final torque of 4,650 ft-lb against a 4,400 ft-lb criterion and a depth of 26 ft against a 24 ft minimum, both criteria met with margin. That rules out an unmet installation criterion at the nearby pier. The crawl space inspection that follows finds a hose bib on the exterior wall directly above the flagged grid point, dripping steadily at its packing, saturating the soil against the footing through a full winter and spring.

Step 3's classification: a new water condition introduced after the original repair, not a pier or soil deficiency. Step 4's determination follows directly: this is new-scope work, a hose bib repair and a drainage correction, not a warranty claim against the pier installation, and the record states the criteria met at pier 4 as the basis. Step 5 is where this pass has its failure in the direction of caution rather than convenience: the supervisor initially treats the finding as clear enough to skip engineer review, since no pier work is proposed. Under step 5's rule that a sealed design's limitations do not cover a condition discovered after the fact, that skip is itself wrong, because the original design's assumptions about drainage at that corner are exactly what the new water condition calls into question. The file is sent to the engineer of record, who confirms the piers remain adequate and the fix is limited to the drainage correction, in writing, before the customer document goes out.

Step 6 delivers one summary: the classification, the met installation criteria at pier 4, the engineer's confirmation, and the proposed hose bib and grading fix as new-scope work with its own estimate. Step 8 sets a fresh baseline the day the drainage fix closes, and the restart reason on the record reads exactly what step 3 found, so the next person reading the file in three years does not have to reconstruct it from memory.

References

• ASTM D4719 and the pier system's ICC-ES evaluation report, for the installation criteria the as-built log is checked against during classification.
• International Residential Code Section R401.3, for the grade and drainage standard a new water-related cause is measured against.
• See related: post-repair monitoring and follow-up, whose escalation criteria trigger this procedure; engineer involvement and sign-off, for the field-change and reconciliation pattern this procedure follows when the design is sealed.