Fundamentals of Construction Engineering

Chapter 3
Construction Drawings, Specifications and Technical Communication

Bachelors Program in Construction Technology
Fundamentals of Construction Engineering   •   Bachelor

Construction Drawings, Specifications and Technical Communication

Introduction and Context

Construction is delivered through coordinated information. Drawings communicate geometry and relationships; specifications communicate materials, workmanship, performance and quality; schedules organize repeated or tabulated information; and technical correspondence records decisions, responsibilities and changes. These documents form the information basis for estimating, procurement, construction, inspection, commissioning and maintenance.

A construction professional must do more than recognize symbols. The professional must interpret a document set as an integrated system, identify which information governs a particular decision, detect inconsistencies, communicate uncertainty without speculation, and maintain an auditable record. Errors in interpretation can produce rework, delay, unsafe conditions, claims and defective performance.

This chapter develops the skills required to read plans, sections, elevations, details and schedules; understand scales and conventions; coordinate drawings with specifications; and prepare calculations, reports, requests for information (RFIs) and site records.

Learning Objectives

After studying this chapter, a student should be able to:

  1. Explain the purpose and relationships of plans, sections, elevations, details and schedules.
  2. Use drawing scales, dimensions, grids, levels, symbols and keynotes correctly.
  3. Interpret a drawing set through title blocks, revision histories and document hierarchies.
  4. Coordinate drawings with specifications, schedules and contract requirements.
  5. Prepare clear technical calculations, inspection records, daily reports and RFIs.
  6. Identify ambiguity, inconsistency and incomplete information without making unauthorized assumptions.
  7. Apply professional, ethical and digital information-management practices.

1. Construction Documents as an Information System

A drawing is a graphical representation of a proposed facility. It is not normally a complete description by itself. Drawings show location, shape, dimensions, interfaces and relationships. Specifications describe qualities and procedures that are difficult to represent graphically, such as concrete strength, coating thickness, testing requirements, installation tolerances and accepted products.

The principal document types are:

DocumentMain purposeTypical information
PlanHorizontal view, usually looking downwardRoom layout, walls, openings, equipment and dimensions
SectionVertical cut through the buildingFloor-to-floor relationships, assemblies, levels and construction sequence
ElevationView of a surface or façadeAppearance, openings, finishes, heights and façade materials
DetailEnlarged representation of a specific conditionInterfaces, fixings, waterproofing, reinforcement and tolerances
ScheduleTabulated repeated informationDoor, window, finish, equipment or room data
SpecificationWritten technical requirementsMaterials, execution, testing, quality and acceptance
Addendum or revisionChange issued before or during authorization, according to contract proceduresModified requirements and affected documents
Record or as-built drawingInformation describing the constructed conditionField-verified locations, changes and final configuration

A document set should be read as a coordinated whole. For example, a wall may be located in plan, its height and floor relationship may be shown in section, its external finish may be shown in elevation, its base and head may be shown in details, and its material and installation requirements may be stated in the specification.

1.1 Drawing identification and document control

Every controlled drawing should be identifiable through its title block. Important fields include project name, client, drawing title, drawing number, discipline, scale, date, status, revision, author, checker and approver. The revision block should describe what changed and when.

A drawing marked “For Construction,” “Issued for Tender,” “Preliminary” or “For Information” has a different status. Users must not assume that an older drawing remains valid merely because it is physically available. Superseded documents should be removed from active work areas or clearly marked as superseded.

A practical document-control check is:

  1. Confirm project and discipline.
  2. Confirm drawing number and title.
  3. Confirm issue status and revision.
  4. Confirm that referenced drawings are the current revisions.
  5. Check whether an addendum, clarification, site instruction or change order modifies the information.
  6. Record the source used for any measurement or decision.

2. Reading Plans, Sections, Elevations and Details

2.1 Plans

A plan is produced by imagining a horizontal cut through a building and viewing downward, commonly at a level selected to reveal walls, doors and windows. A plan can show structural grids, room names, dimensions, furniture, equipment, finishes, floor slopes and service locations.

The cutting plane is important. Elements cut by the plane are usually represented with heavier linework, while elements beyond the plane may use lighter lines. A door swing indicates direction and approximate movement, not necessarily the complete manufacturer’s hardware requirement. A dimension string should be read from its extension lines and terminators rather than from apparent distances measured on the page.

Plans should be read systematically:

  • establish the orientation using the north arrow and project grid;
  • identify the drawing level and datum;
  • locate structural grids and major reference lines;
  • trace primary walls, columns and openings;
  • read dimensions from overall to intermediate to local dimensions;
  • locate section, elevation and detail callouts;
  • compare room, door, window, finish and equipment schedules;
  • inspect notes and keynotes associated with the area.

2.2 Sections

A section represents a vertical slice. It explains vertical continuity and is particularly useful for foundations, floor build-ups, roofs, stairs, shafts, ceiling zones, parapets and waterproofing. Levels may be expressed relative to a project datum. For example, “+3.600” may indicate an elevation 3.600 m above the designated reference datum, but the datum definition must be confirmed in the project documents.

A section callout on a plan identifies the viewing direction and the location of the cut. The same condition may be shown differently in architectural, structural and services sections; coordination requires comparing all relevant disciplines.

2.3 Elevations

An elevation shows the appearance or surface of a building from a stated direction. It may include façade grids, materials, joint lines, windows, doors, levels, signage and external equipment. Elevations are not substitutes for plans or details: they often omit concealed support, drainage paths and fixing arrangements.

2.4 Details

Details enlarge conditions that cannot be understood reliably at general drawing scale. A detail may show a sealant joint, flashing, damp-proof course, reinforcement anchorage, roof edge, movement joint or connection between different materials.

The reader should check whether the detail is typical or project-specific. A typical detail may require adaptation to the actual wall thickness, structural system or fire rating. The detail reference should be followed back to the parent plan or section, and the detail should be compared with the relevant specification clause.

3. Scale, Dimensions and Measurement

Scale expresses the relationship between a drawing distance and the corresponding real distance. For a ratio scale of 1:n:

Lreal = n × Ldrawing

where Lreal is the real length and Ldrawing is the measured drawing length, both expressed in the same unit, and n is the scale denominator. This relationship applies only when the drawing is reproduced at its stated scale and is not distorted.

For example, at 1:100, 35 mm on a correctly printed drawing represents:

Lreal = 100 × 35 mm = 3500 mm = 3.5 m

Conversely:

Ldrawing = Lreal ÷ n

A 4.2 m wall at 1:50 should appear as:

Ldrawing = 4200 mm ÷ 50 = 84 mm

The assumptions are that the drawing is printed without scaling, the scale applies to the view, and the measured line is not distorted by scanning or screen display. Dimensions written on the drawing generally take precedence over scaling from the paper. If a dimension conflicts with a scaled measurement, do not guess; raise the discrepancy.

Common scales include 1:500 or 1:1000 for site plans, 1:100 or 1:50 for general plans and elevations, and 1:20, 1:10, 1:5 or 1:2 for details. Scale alone does not determine construction accuracy. A 1:50 plan may show a wall location, while a 1:5 detail may govern the interface construction.

3.1 Dimensioning conventions

Dimensions should be read according to their defined units and reference points. Important conventions include chain dimensions, baseline dimensions, coordinate dimensions, centerline dimensions, level dimensions and tolerances. A dimension of 2.400 m may mean a nominal distance; it does not automatically establish a permissible construction tolerance.

Dimensions should not be accumulated carelessly. If a series of dimensions is independently rounded, its sum may differ from an overall dimension. The overall dimension and contractual tolerances must be checked before setting out.

3.2 Areas and quantities from drawings

For a rectangle:

A = L × W

where A is area, L is length and W is width. If dimensions are in metres, area is in square metres. For a rectangular concrete slab 8.0 m by 5.5 m and 0.15 m thick, volume is:

V = L × W × t = 8.0 × 5.5 × 0.15 = 6.60 m³

where t is thickness. This is a geometric quantity only. It may need adjustment for openings, laps, waste, construction joints, cambers, overbreak or specified ordering allowances. The student must distinguish a drawing-based estimate from an approved procurement quantity.

4. Symbols, Linework and Conventions

Graphic conventions make drawings readable, but conventions vary by discipline, jurisdiction and project standard. The project legend and notes take priority over general familiarity.

Typical conventions include:

  • thick continuous lines for elements cut or emphasized;
  • thin continuous lines for visible elements beyond the cut;
  • dashed lines for hidden, overhead or proposed elements, as defined by the legend;
  • centerlines for axes and centers;
  • grid bubbles for structural or setting-out references;
  • section arrows for cut location and viewing direction;
  • elevation markers for façade views;
  • level symbols for vertical elevations;
  • revision clouds to identify changed areas;
  • keynote numbers linked to written notes;
  • material hatch patterns indicating, for example, concrete, masonry, insulation or earth.

Symbols must be interpreted in context. A triangle, arrow or abbreviation may have different meanings in architectural, structural, mechanical or electrical drawings. Abbreviations should be checked against the project abbreviation list rather than inferred from habit.

A useful distinction is between graphical information and written qualification. A symbol may locate a fire extinguisher, but the specification may govern its rating, mounting height and inspection requirement. A hatch may suggest insulation, but the specification determines thermal performance, thickness, density and installation method.

5. Schedules and Specifications

5.1 Schedules

Schedules consolidate repeated information and reduce clutter. A door schedule may include door mark, size, type, material, frame, hardware set, fire rating and finish. A window schedule may identify dimensions, glazing, frame, acoustic performance and safety requirements. Finish schedules connect rooms to floor, wall and ceiling finish codes.

A schedule must be coordinated with its graphic references. A door mark appearing in plan should match one and only one applicable schedule entry unless the schedule explicitly permits a type family. Missing marks, duplicated marks or inconsistent sizes are coordination issues.

5.2 Specifications

Specifications commonly contain general requirements, product requirements and execution requirements. They may define:

  • standards and codes;
  • approved or permitted materials;
  • required performance;
  • submittals and samples;
  • inspection and testing;
  • installation procedures;
  • tolerances;
  • protection and cleaning;
  • quality assurance;
  • measurement and payment, where applicable.

A performance specification defines the required result, while a prescriptive specification defines particular materials or methods. Many projects use a combination. The constructor must determine whether substitutions are permitted and what approval process applies.

Drawings generally communicate location and geometry; specifications generally communicate quality and execution. This is a practical principle, not a universal legal rule. The contract conditions, employer’s requirements and governing law establish the actual hierarchy and precedence.

5.3 Resolving apparent conflicts

When documents disagree, the correct response is controlled clarification, not silent selection. The following sequence is useful:

  1. Identify the exact conflict, including document numbers, revisions, locations and dimensions.
  2. Check whether one document explicitly states precedence.
  3. Check later revisions, addenda, instructions and approved submittals.
  4. Consider safety, code compliance and constructability.
  5. Issue an RFI or formal clarification through the authorized channel.
  6. Record the response and distribute the resulting change to affected parties.
  7. Update drawings, models, registers and field instructions as required.

An instruction from an unauthorized person may be technically sensible but contractually ineffective. Personnel should not rely on informal messages for changes affecting cost, time, safety or quality.

6. Coordination Across Disciplines

Coordination is the process of ensuring that architectural, structural, civil, mechanical, electrical, plumbing, fire-protection and specialist information can be built together. It includes spatial coordination, dimensional coordination, performance coordination and sequence coordination.

Common conflicts include a duct passing through a beam, a drainage outlet without sufficient fall, a door opening into equipment clearance, a ceiling too shallow for services, or a façade anchor conflicting with reinforcement. Coordination should occur before work reaches the affected location, but field verification remains essential because existing conditions may differ from drawings.

A coordination review should examine:

  • common grids and datums;
  • openings and penetrations;
  • structural zones and load paths;
  • service routes and access for maintenance;
  • fire, acoustic, thermal and moisture continuity;
  • equipment clearances;
  • construction sequence and temporary works;
  • interfaces between trades;
  • tolerances and dimensional accumulation.

Building information modelling (BIM) can support coordination through federated models, clash detection, object data and controlled issue workflows. A clash report is not automatically a design solution. It identifies a geometric or rule-based conflict; competent professionals must evaluate responsibility, performance, access, cost and sequence before approving a resolution.

7. Technical Calculations and Reports

A technical calculation should be transparent and reproducible. It should identify the purpose, input data, assumptions, governing reference, method, units, result, check and conclusion.

A concise calculation format is:

Problem: Determine concrete volume for a slab.

Data: L = 8.0 m, W = 5.5 m, t = 0.15 m.

Assumption: The slab is rectangular and no openings are deducted.

Calculation: V = L × W × t = 6.60 m3.

Check: Length × width gives area in m2; multiplying by thickness gives m3.

Conclusion: The geometric slab volume is 6.60 m³; ordering quantity requires project-specific allowance and approval.

Reports should distinguish observed facts from interpretations and recommendations. A strong site report states who attended, when and where the observation occurred, what was inspected, what evidence was reviewed, what was found, what action is required, who is responsible and when closure is expected. Photographs should include location, direction, date and a clear reference to the issue.

8. Requests for Information and Site Records

8.1 Requests for Information

An RFI is a controlled request for clarification. It should not be used to transfer design responsibility casually or to conceal an avoidable failure to review documents.

A useful RFI includes:

  • unique identification number;
  • date, originator and responsible recipient;
  • subject and precise location;
  • references to drawings, specifications and revisions;
  • description of the discrepancy or missing information;
  • the effect on work, safety, cost or programme;
  • a clearly framed question;
  • proposed solution, if appropriate, identified as a proposal rather than an instruction;
  • required response date;
  • attachments and marked-up extracts.

Poor wording: “The drawings are unclear. What should we do?”

Better wording: “On drawing A-204 Rev. 3, detail 5/A-512 shows a 100 mm cavity, while wall type W-07 in the wall schedule indicates 125 mm. At grid B/4, the structural column leaves 110 mm available. Please confirm the required cavity width and whether the associated insulation and flashing detail are to be revised before wall installation.”

8.2 Site records

Daily reports, inspection requests, nonconformance reports, delivery records, test reports and meeting minutes create the project record. Entries should be contemporaneous, factual and legible. Corrections should preserve the original entry according to the project’s record-control procedure; backdating or deleting inconvenient information is unethical and may be unlawful.

A daily report commonly records weather, workforce, plant, work locations, deliveries, inspections, tests, disruptions, visitors, instructions, safety events and photographs. “Work progressed normally” is less useful than “Blockwork to Level 02, grid C–F, proceeded from 08:00 to 16:30; 42 m² completed; inspection request IR-017 submitted at 15:45.”

9. Applied Case: Coordination of a Wet-Room Floor Build-Up

The following is an illustrative case, not a report of an actual project.

Background

A student accommodation project contains repeated accessible bathrooms. The architectural plan identifies a floor drain, the finish schedule specifies tiles, and a section shows a level threshold. The plumbing drawing locates the drain branch, while the specification requires waterproofing turned up at walls and a tested floor membrane.

Problem

During pre-installation review, the contractor observes that the structural slab is level with the adjacent corridor slab. The proposed tile build-up and required drainage fall would raise the bathroom floor above the corridor, contradicting the accessible threshold shown in the section. In addition, the plumbing drawing and architectural plan show slightly different drain positions.

Analysis

The team records the exact drawing numbers and revisions, verifies the datum and checks the finish schedule. It calculates the available vertical zone. Suppose the drain is 2.4 m from the outlet and the required design fall is 1:80. The vertical fall is:

∆h = L ÷ 80 = 2.4 m ÷ 80 = 0.030 m = 30 mm

where ∆h is the vertical difference and L is the horizontal drainage length. This calculation applies only if the specified fall is 1:80 and the route is approximately uniform. It does not establish the complete floor build-up or replace hydraulic design.

The available zone is insufficient if the tile, adhesive, screed, membrane protection and 30 mm fall together exceed the permitted threshold. The team also identifies a potential waterproofing continuity issue at the wall junction.

Approach and solution

The contractor submits an RFI with marked-up plan and section extracts, the calculated fall, photographs of the slab and three questions: which drain location governs, what finished floor level is required, and whether the designer approves a revised screed profile or relocated outlet. Work is held only in the affected area, while unaffected preparatory work continues.

The design team issues a coordinated sketch and revised detail. The approved solution relocates the branch connection, confirms a shallow sloped screed, maintains the accessibility requirement and adds a tested waterproofing upstand. The revision is entered in the drawing register, briefed to the trades and verified through an inspection request before tiling.

Outcome

The project avoids installing a noncompliant threshold and prevents later demolition. The record demonstrates that the conflict was identified, analyzed quantitatively, referred to the authorized designer and closed through a controlled revision.

Learning points

  1. A plan, section, schedule, specification and services drawing must be read together.
  2. A simple calculation can expose a constructability problem early.
  3. A proposed solution is not an approved instruction.
  4. Waterproofing, accessibility and drainage are interface requirements, not isolated trade concerns.
  5. The final record must identify the approved revision and field verification.

10. Ethics, Governance and Contemporary Practice

Technical communication has ethical consequences. Professionals must report unsafe conditions, avoid misleading precision, protect confidential information and disclose uncertainty. A person should not certify work that was not inspected or represent an unverified drawing as an as-built record.

Regulatory requirements vary by jurisdiction, but typical governance concerns include building codes, fire and life safety, accessibility, occupational health and safety, environmental requirements, records retention and professional licensing. The project contract and applicable standards must be consulted directly; a textbook cannot replace them.

Digital tools introduce additional responsibilities. Cloud platforms, common data environments and BIM improve accessibility and traceability when permissions, naming conventions, approval states and revision controls are disciplined. Artificial intelligence may assist with document classification, drawing comparison, quantity extraction or draft summaries. However, AI can misread symbols, omit qualifications, use superseded information or produce confident but unsupported interpretations. Human review by a competent person remains essential, particularly for safety, compliance, cost and contractual decisions.

Good practice includes a single controlled source for current documents, clear status codes, standardized file names, revision registers, access control, backup procedures and an audit trail. Markups should be unambiguous, dated and attributable. Before issuing information, the author should verify references, units, revision status and affected disciplines.

Best-Practice Checklist

Before using a drawing or specification:

  • verify title, number, revision, status and date;
  • confirm the applicable scale and units;
  • read legends, general notes and abbreviations;
  • locate the relevant plan, section, elevation, detail and schedule;
  • check related disciplines and specifications;
  • distinguish dimensions from tolerances;
  • identify assumptions and unresolved interfaces;
  • seek formal clarification where required;
  • record the source and approved response;
  • communicate changes to everyone affected.

Chapter Summary

Construction drawings, specifications, schedules and records operate as a coordinated information system. Plans communicate horizontal arrangement; sections explain vertical relationships; elevations describe surfaces and appearance; details explain interfaces; schedules organize repeated data; and specifications define materials, performance and execution. Correct interpretation depends on title blocks, revision status, legends, dimensions, scales, datums, symbols and cross-references.

Scale calculations are useful only when the stated scale has been preserved, while written dimensions normally take precedence over measurement from paper. Technical calculations must show data, assumptions, units, method, result and limitations. RFIs should identify a precise issue and request an authorized clarification rather than invite informal guessing. Site records should be factual, contemporaneous, traceable and sufficiently detailed for later technical and contractual review.

Coordination is both a design and construction responsibility. BIM and AI can improve information management, but neither replaces professional judgment, field verification, code compliance or controlled authorization. Clear technical communication reduces rework, protects safety and supports defensible decisions.

Key Terms

Drawing scale: Ratio between a drawing measurement and the corresponding real measurement.

Plan: Horizontal projected view of a building or site.

Section: Vertical cut showing internal construction and levels.

Elevation: View of a building surface or façade.

Detail: Enlarged drawing of a specific construction condition.

Schedule: Tabulated information associated with repeated elements.

Specification: Written requirements for materials, performance and execution.

Title block: Identification and control area of a drawing.

Revision: Controlled change to a document after an earlier issue.

Datum: Reference level or coordinate from which measurements are established.

Grid: Reference system used for locating building elements.

Keynote: Number or symbol linked to explanatory written information.

Tolerance: Permitted variation from a specified dimension or condition.

RFI: Controlled request for clarification of incomplete or conflicting information.

Submittal: Information provided for review, such as samples, shop drawings or product data.

Shop drawing: Detailed drawing prepared by a contractor, supplier or specialist.

As-built drawing: Record representing the constructed or installed condition.

Common data environment: Controlled digital system for managing project information.

Clash detection: Identification of conflicts between modelled or documented elements.

Nonconformance report: Controlled record of work or material that fails to meet a requirement.

Review Questions

Short Answer Questions

  1. What is the principal difference between a plan and a section?
  2. Why should written dimensions generally be preferred to scaling a printed drawing?
  3. Name four items commonly found in a drawing title block.
  4. What information should an RFI contain?
  5. Why must a detail be checked against its parent drawing and the specification?

Long Answer Questions

  1. Explain how plans, sections, elevations, details, schedules and specifications work together to describe a building element.
  2. Describe a systematic procedure for reviewing a multidisciplinary drawing package before construction begins.
  3. Explain the difference between a performance specification and a prescriptive specification, including advantages and limitations of each.
  4. Discuss the qualities of a reliable daily site report and explain how it supports quality, safety and contractual administration.
  5. Evaluate the benefits and risks of BIM and artificial intelligence in construction document management.

Analytical / Application Questions

  1. A drawing at 1:50 shows a wall measuring 68 mm, but the written dimension is 3.400 m. Analyze the discrepancy and state what should be checked before construction.
  2. An architectural plan places a column within a door swing, while the structural plan confirms the column location. Identify the coordination issues, documents to review and formal actions required.
  3. A roof detail shows insulation continuity, but the specification requires a different insulation performance and thickness. Develop a step-by-step method for resolving the conflict and documenting the approved outcome.

Multiple Choice Questions with Answers

Question 1

Which document primarily communicates vertical relationships such as floor-to-floor heights and roof construction?

A. Plan

B. Section

C. Door schedule

D. Site diary

Correct Answer: B. Section

Question 2

At a scale of 1:100, a correctly printed drawing length of 35 mm represents:

A. 0.035 m

B. 0.35 m

C. 3.5 m

D. 35 m

Correct Answer: C. 3.5 m

Question 3

What should a professional do when two current documents contain conflicting dimensions?

A. Use the smaller dimension without consultation

B. Scale both drawings and select the average

C. Ignore the conflict if construction is urgent

D. Identify the conflict and seek controlled clarification

Correct Answer: D. Identify the conflict and seek controlled clarification

Question 4

Which document most commonly specifies testing, installation procedures and material performance?

A. Specification

B. North arrow

C. Elevation marker

D. Grid bubble

Correct Answer: A. Specification

Question 5

For a rectangular slab 8.0 m long, 5.5 m wide and 0.15 m thick, the geometric volume is:

A. 6.60 m³

B. 8.25 m³

C. 13.50 m³

D. 44.00 m³

Correct Answer: A. 6.60 m³

Question 6

Which RFI wording is most technically useful?

A. The drawings are confusing. Advise.

B. Please fix everything shown on the attached drawing.

C. Drawing A-204 shows 100 mm while wall schedule W-07 shows 125 mm at grid B/4; please confirm the governing cavity width.

D. The subcontractor refuses to continue.

Correct Answer: C. Drawing A-204 shows 100 mm while wall schedule W-07 shows 125 mm at grid B/4; please confirm the governing cavity width.

Question 7

What is the primary function of a revision block?

A. To list workers on site

B. To identify document changes and their issue information

C. To calculate concrete volume

D. To replace the specification

Correct Answer: B. To identify document changes and their issue information

Question 8

A drainage route is 2.4 m long and requires a fall of 1:80. The vertical fall is:

A. 3 mm

B. 24 mm

C. 30 mm

D. 192 mm

Correct Answer: C. 30 mm

Question 9

Which statement about a proposed solution in an RFI is correct?

A. It automatically becomes a contract instruction

B. It should be identified as a proposal until authorized

C. It replaces the designer’s responsibility in every case

D. It need not be recorded if discussed verbally

Correct Answer: B. It should be identified as a proposal until authorized

Question 10

Why is field verification still necessary when BIM coordination has been completed?

A. Models always contain deliberate errors

B. Field conditions may differ from documented or modelled conditions

C. BIM cannot represent any dimensions

D. Specifications are not relevant to models

Correct Answer: B. Field conditions may differ from documented or modelled conditions

Fundamentals of Construction Engineering
Chapter 3 of 15