Distinguish interior veneer plaster over gypsum base (blueboard) from conventional three-coat interior plaster for scope and licensing
domain: astm.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For veneer plaster, install a gypsum base product compliant with current gypsum board standards (the historical dedicated veneer-base standard, C588, was withdrawn and superseded by gypsum board standard C1396) per ASTM C844 application requirements
Apply veneer plaster in one or two thin coats per ASTM C843, using the scratch-and-double-back technique where a single-coat product is used
For conventional three-coat interior plaster, use a full-thickness scratch/brown/finish build over lath per the applicable plaster application standard, similar in principle to exterior C926 but for interior gypsum-based plaster
Confirm which trade license classification covers the work being bid, since interior lathing/plastering scope can fall under the same classification as exterior stucco in some jurisdictions (e.g., California's C-35) rather than a separate drywall license
Communicate schedule differences to the GC: veneer plaster is typically a fast, low-dust, one- to two-day process versus the multi-day dry time of conventional three-coat plaster
Known gotchas
The older dedicated veneer-base standard (C588) is withdrawn; current veneer plaster jobs specify a gypsum base compliant with the gypsum board standard (C1396), applied per C844 — citing the withdrawn C588 in a spec is a red flag
Veneer plaster and conventional three-coat plaster are not interchangeable systems; substituting one for the other changes wall thickness, trim reveals, and cure/dry schedules
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?