Repair a cracked masonry wall using helical pin/crack-stitching reinforcement
domain: icc-es.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Diagnose the cause of the crack (differential settlement, thermal movement, corroding embedded metal, seismic) before selecting stitching, since stitching stabilizes a crack but does not fix an active movement source.
Select a helical-tie crack-stitching system with current code-recognition documentation (e.g., an ICC-ES evaluation report) appropriate to the masonry type and load, following that system's published bar spacing, embedment, and grout requirements.
Cut or rake horizontal bed-joint slots extending well past each side of the crack at the manufacturer's specified vertical spacing along the crack height.
Install the helical bar in a compatible grout per the manufacturer's data sheet, fully bonding the bar into the slot.
Repoint the disturbed bed joints to match the surrounding historic mortar color and profile so the repair is visually concealed.
Have a structural engineer confirm crack stitching alone is sufficient, or whether additional bracing, shoring, or foundation work is also required.
Known gotchas
Crack stitching stabilizes an existing crack; it doesn't address an ongoing structural cause -- a stitched crack can reopen elsewhere if the root cause isn't fixed.
There is no single US prescriptive code standard covering these proprietary systems -- verify current code-recognition for the specific product rather than assuming blanket acceptance.
On historic/landmark buildings, disturbing visible mortar joints to cut slots may require the same design-review approval as repointing.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?