Determine which architectural woodwork standard(s) actually govern a project when the spec mixes AWI and AWMAC/WI references
domain: awinet.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify whether the spec cites AWI's own ANSI-accredited standards (the 0100/0200/0300/0600/1200-series, developed independently after 2015) or the jointly-published North American Architectural Woodwork Standards (NAAWS) used by AWMAC and Woodwork Institute.
Recognize these are two distinct standards lineages since the 2015 dissolution of the AWI/AWMAC/WI joint standards committee — they are not interchangeable even where terminology overlaps.
For Canadian work, expect NAAWS/AWMAC GIS to govern; for U.S. work referencing 'AWI,' confirm which specific numbered standard(s) apply.
Flag any spec that ambiguously cites 'AWS' or 'Architectural Woodwork Standards' without specifying edition or publisher, since this likely references the pre-2016 joint standard and needs clarification via RFI.
Confirm the current edition/status of whichever standard is actually cited directly on the publisher's site (awinet.org for AWI; naaws.com, awmac.com, or woodworkinstitute.com for NAAWS) before bidding, since AWI standards are actively under revision.
Known gotchas
Older specs (pre-2019) may still reference the joint 'Architectural Woodwork Standards' (AWS) Edition 1 or 2 — that joint document has been superseded on the AWI side by newer independent standards and, on the AWMAC/WI side, by NAAWS; neither party still maintains 'AWS' as its current standard.
Bidding to the wrong standards lineage (e.g., pricing to AWI 0641 when the spec actually intends NAAWS-based WI CCP inspection) can create a significant cost/scope mismatch discovered only at submittal review.
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?