Evaluate and classify a coating failure in the field using standardized ASTM visual rating methods
domain: astm.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the failure mode observed (rusting, blistering, checking/cracking, or loss of adhesion at a scribe) before selecting a test method
For rust breakthrough on painted steel, apply ASTM D610, 'Standard Practice for Evaluating Degree of Rusting on Painted Steel Surfaces' (0-10 scale by percent rusted area and distribution pattern)
For blistering, apply ASTM D714, 'Standard Test Method for Evaluating Degree of Blistering of Paints' (photographic reference for blister size/density)
For checking/cracking, apply ASTM D660 (checking) or the related D661/D1654 series as appropriate, and for scribed-panel corrosion creep from an artificial defect use ASTM D1654
Photograph the failure alongside a scale reference and record the numeric/letter rating from the applicable standard rather than a purely subjective description, then correlate against exposure time, environment, and known coating system to build a root-cause hypothesis
Known gotchas
These are all visual/photographic comparator methods, not laboratory analytical methods — for a defensible failure-analysis report attributing a specific root cause (e.g., contamination, under-cure, incompatible topcoat), destructive cross-section analysis or lab testing is usually still needed in addition to the visual rating
Confirm current editions on store.astm.org before citing a year — several of these standards (e.g., D660) have been reapproved with unchanged technical content, so a reapproval date does not necessarily mean new criteria
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?