Interpreting Drawings, Specifications and Work Instructions
Reading the document set correctly
A plasterer works from a set of documents that only make sense together: architectural and reflected ceiling plans, elevations, sections, detail drawings, the specification, the schedule of finishes, and the builder's work instructions or site instructions. Questions in this domain test whether you read the right document for the question asked, and whether you can extract a dimension or a specification without being misled.
Core concepts to know
- Scale and dimensions: never scale a drawing when a written dimension exists; written dimensions govern. Note the stated scale and check it against a known dimension.
- Projections and views: first-angle versus third-angle projection, plan, elevation, section, and reflected ceiling plan (viewed from below, so left and right appear reversed relative to a floor plan).
- Symbols and abbreviations: hatching for finishes, levels and datum, RL (reduced level), FFL (finished floor level), and abbreviations for plaster types and thicknesses.
- Specification and schedules: the finish schedule tells you the system, coat thicknesses, mix and substrate; the specification controls quality and standards. Where drawings and specification conflict, raise a request for information rather than guessing.
- Setting-out information: grid lines, centrelines and datum points are the reference for measuring and setting out.
- Work instructions: written or verbal directions from the supervisor; confirm in writing if there is any ambiguity, especially for variations.
Traps
Common distractors include scaling a drawing to find a dimension, reading a reflected ceiling plan as if it were a floor plan, or treating a detail drawing as the general arrangement. Another trap is assuming a schedule applies to a different room type.
Worked rule of thumb
When asked which document governs, apply this order: written dimensions beat scaled ones; specification beats a generic note; a specific detail beats a general note; and any conflict triggers an RFI, not an assumption.