Explain why drive-in/drive-through racks carry elevated impact risk: the forklift must physically enter the rack structure (drive between rails) to place/retrieve every pallet, unlike selective rack where the truck stays in the aisle
List key inspection points: front columns/entry areas (bent, twisted, scraped, cracked welds from entry/exit/turning), side rails (bent, loose, or showing drag marks from improperly placed loads), uprights and cross-bracing (dents, bends, out-of-plumb sections, focus on the lower portion where forklift contact is most common)
Include baseplates/anchors (lifted or bent baseplates, loose/missing anchors, cracked surrounding concrete, shifted shims) and beams/connectors (twisting, sagging, missing safety clips, dislodged beam-to-column connections)
Include pallet condition and fit within the lane as a specific drive-in hazard: undersized, oversized, or damaged pallets can hang up on rails or fail to seat properly between rails, given the tighter tolerances of drive-in lanes
Confirm ANSI MH16.1 (2023 edition) explicitly excludes drive-in and drive-through racks from its scope, along with cantilever, portable, and non-steel racks — do not cite MH16.1 as the design/testing basis for these systems; rely on the specific rack manufacturer's own engineering documentation and rated capacities as the governing reference for a given installation instead
Recommend inspection frequency be increased relative to selective rack given higher impact exposure, with mandatory post-impact inspection after any reported forklift contact in the lane
Known gotchas
Drive-in racks depend on rail alignment tolerances that are easy to overlook visually — a rail that looks fine from the aisle end may be misaligned deeper into the lane
Because only the entry-facing frame is easily visible, damage to rear/interior frames of a deep drive-in lane can go undetected without entering the lane or using an inspection mirror/camera — don't assume a visual walk-by from the aisle is sufficient
ANSI MH16.1 does NOT cover drive-in/drive-through racks — they are explicitly excluded from its scope; don't cite MH16.1 clauses for these systems' structural design or testing, and confirm the applicable engineering basis directly with the rack manufacturer rather than assuming a single named companion standard applies
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?