Determine whether a bolted joint requires snug-tight or pretensioned installation per the RCSC Specification, and inspect turn-of-nut installation accordingly
domain: boltcouncil.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check the contract/erection drawings for the joint designation: snug-tight, or pretensioned (including slip-critical joints, which require pretensioning).
For snug-tight joints, bring plies into firm contact, confirm required washers are present, and verify bolts are tightened enough to prevent turning without a wrench — no torque or turn measurement is required.
For pretensioned joints using the turn-of-nut method, first bring the assembly to the snug-tight condition, then apply the additional rotation specified in the RCSC turn-of-nut tables (which vary by bolt length and diameter), using match-marking to track rotation.
Perform pre-installation verification testing on sample bolt assemblies, using the actual lot/tools/components intended for the work, before production installation begins.
Conduct inspection appropriate to the joint type per the RCSC Specification's inspection provisions — visual/procedural checks for snug-tight joints, and rotation/torque verification methods for pretensioned joints.
Known gotchas
Snug-tight joints require no further torque or turn verification once turning-without-a-wrench is confirmed — over-inspecting them as if they were slip-critical wastes time and isn't what the specification calls for.
Turn-of-nut rotation amounts vary by bolt length/diameter combination in the RCSC tables; applying one flat rotation rule for every bolt without checking the applicable table row is a common field error.
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?