Interpretation of Plans

Learning Objectives

  • Establish the current controlled document set before interpreting geometry or quantities.
  • Navigate callouts, schedules, details, sections, risers, specifications, revisions, and discipline references as one information network.
  • Separate document evidence from project authority and avoid inventing a universal precedence rule.
  • Classify discrepancies and select a controlled response such as hold, RFI, submittal review, or approved change.
  • Produce quantity takeoffs with explicit source, revision, measurement basis, deductions, waste, units, and scope boundaries.
  • Audit interpretation and takeoff work so another reviewer can reproduce the result.

Construction documents are not a collection of independent pictures. They are a controlled information system. A reliable interpretation starts with issue status and revision, follows references between general and enlarged views, checks schedules and specifications, and records unresolved conditions before work proceeds.

Contract-Specific Authority

The executed contract defines document status, precedence, change control, and communication procedures. Common interpretation practices—such as preferring written dimensions over scaled measurements—do not authorize undocumented changes or create a universal legal hierarchy.

1. Controlled-Set Navigation

Start with Document Control

  • Drawing index and issue register.
  • Current revision and issue purpose.
  • Addenda, bulletins, sketches, and approved changes.
  • Specifications and schedules referenced by the drawing.
  • Superseded sheets retained only for traceability.
  • Holds, delegated-design packages, and pending submittals.

Follow an Information Chain

  1. Identify the element mark and exact plan location.
  2. Read adjacent written dimensions, grids, levels, and notes.
  3. Follow section, elevation, detail, and schedule callouts.
  4. Check the same element in related disciplines.
  5. Confirm every source is current and compatible.
  6. Record the navigation trace and unresolved differences.
  7. Return to the original plan to confirm the complete instruction.

Callout

A controlled reference from one drawing location to another view, detail, section, schedule, or sheet. A callout is useful only when the target exists, is current, and resolves the required information.

Revision-Aware Plan-Set Navigator

Trace current callouts, identify holds and superseded sheets, and leave a reproducible navigation path.

A-101 · REV 5

Ground-floor plan

Locates spaces, openings, grids, dimensions, tags, and references.

Current for this exercise
A-101Ground-floor planREV 5 · currentA-601Check opening, frame, fire-rating, hardware, and detail references.A-301Verify vertical relationship, ceiling, structure, and services.S-201Coordinate the architectural enclosure with the structural column.
Navigation trace: A-101Controlled-set issues visible: 2

Navigation Audit

2. Document Conflicts and RFIs

Discrepancy

A mismatch, omission, ambiguity, revision difference, or coordination condition that prevents a reliable interpretation of the intended work.

Useful Conflict Classifications

  • Revision conflict: current and superseded information are mixed or a referenced revision is missing.
  • Geometry conflict: dimensions, levels, locations, or physical envelopes cannot coexist.
  • Scope conflict: two documents assign different material, system, or responsibility.
  • Performance conflict: ratings, capacities, or required properties disagree.
  • Missing information: the documents do not define enough information to proceed.

Evidence-Based Resolution Workflow

  1. Mark the exact location and affected work.
  2. Collect current drawings, details, schedules, specifications, submittals, and change documents.
  3. Separate current evidence from superseded background.
  4. Classify the discrepancy and assess downstream effects.
  5. Decide whether unaffected work may proceed or the area requires a hold.
  6. Draft a concise question that requests a coordinated, buildable response.
  7. Attach marked-up evidence and identify affected dimensions, cost, schedule, and trades.
  8. Record the response and update every affected document.

Evidence-Based Conflict and RFI Workflow

Verify source status, classify the discrepancy, choose a controlled response, and frame a reproducible clarification request.

Duct depth conflicts with ceiling section

The mechanical plan routes a 500 mm-deep duct through a corridor where the architectural section shows only 420 mm from structure to ceiling, before supports and finishes.

1. Classify the discrepancy
2. Select the immediate action
Review every evidence source, including superseded material used only to explain history.

The executed contract, current revisions, addenda, approved submittals, delegated-design boundaries, and written design-team responses govern the project. This training lab does not establish legal precedence.

A Strong RFI States

  • precise location, grids, level, and element marks;
  • current documents and revisions reviewed;
  • exact conflicting statements or geometry;
  • affected scope and immediate construction status;
  • a specific question rather than a vague request;
  • attachments or markups that allow rapid coordination.

Do Not Convert Assumptions into Instructions

A reviewer may identify a likely intent, but construction authority must come from the approved project process. Field adjustments, substitutions, and inferred precedence can create structural, life-safety, waterproofing, cost, and warranty consequences.

Discrepancy Evidence and Controlled Response

Turn a drawing discrepancy into a documented clarification or approved revision while tracking affected scope and current source evidence.

Compare the executed contract, current controlled documents, issue purpose, and approved project procedure. Identify the exact mismatch, source revision, location, impact, and affected work. Apply any hold, notice, or proceed rules through the contract and authorized project process; this chart does not establish a universal document-precedence hierarchy. Do not treat an unanswered RFI or an assumption as design authorization. Close the issue only after affected records and drawings reflect the approved response.

Discrepancy Evidence and Controlled ResponseTurn a drawing discrepancy into a documented clarification or approved revision while tracking affected scope and current source evidence.. Compare the executed contract, current controlled documents, issue purpose, and approved project procedure. Identify the exact mismatch, source revision, location, impact, and affected work. Apply any hold, notice, or proceed rules through the contract and authorized project process; this chart does not establish a universal document-precedence hierarchy. Do not treat an unanswered RFI or an assumption as design authorization. Close the issue only after affected records and drawings reflect the approved response.. Identify a drawing discrepancy → Contract, current issue set, scope, and authorized RFI process; Contract, current issue set, scope, and authorized RFI process → Verify location, source revisions, and affected work; Verify location, source revisions, and affected work → Is the difference unresolved or material to scope?; Is the difference unresolved or material to scope? — No → Record evidence and close as nonconflicting; Is the difference unresolved or material to scope? — Yes → Classify conflict and identify affected scope; Classify conflict and identify affected scope → Apply contract hold, notice, or proceed controls; Apply contract hold, notice, or proceed controls → Submit evidence-based RFI with specific question; Submit evidence-based RFI with specific question → Is an authorized written response received?; Is an authorized written response received? — Yes → Update all affected drawings and coordination records; Is an authorized written response received? — No → Track open RFI under project controls; Track open RFI under project controls → Is an authorized written response received?; Update all affected drawings and coordination records → Do affected scopes and current documents agree?; Do affected scopes and current documents agree? — Yes → Record response, revision, and closed issue trail; Do affected scopes and current documents agree? — No → Record open conflict for project-controlled resolution

Identify a drawing discrepancy → Contract, current issue set, scope, and authorized RFI process; Contract, current issue set, scope, and authorized RFI process → Verify location, source revisions, and affected work; Verify location, source revisions, and affected work → Is the difference unresolved or material to scope?; Is the difference unresolved or material to scope? — No → Record evidence and close as nonconflicting; Is the difference unresolved or material to scope? — Yes → Classify conflict and identify affected scope; Classify conflict and identify affected scope → Apply contract hold, notice, or proceed controls; Apply contract hold, notice, or proceed controls → Submit evidence-based RFI with specific question; Submit evidence-based RFI with specific question → Is an authorized written response received?; Is an authorized written response received? — Yes → Update all affected drawings and coordination records; Is an authorized written response received? — No → Track open RFI under project controls; Track open RFI under project controls → Is an authorized written response received?; Update all affected drawings and coordination records → Do affected scopes and current documents agree?; Do affected scopes and current documents agree? — Yes → Record response, revision, and closed issue trail; Do affected scopes and current documents agree? — No → Record open conflict for project-controlled resolution

  • Identify a drawing discrepancy: terminator
  • Contract, current issue set, scope, and authorized RFI process: data
  • Verify location, source revisions, and affected work: process
  • Is the difference unresolved or material to scope?: decision
  • Record evidence and close as nonconflicting: document
  • Classify conflict and identify affected scope: process
  • Apply contract hold, notice, or proceed controls: process
  • Submit evidence-based RFI with specific question: document
  • Is an authorized written response received?: decision
  • Track open RFI under project controls: document
  • Update all affected drawings and coordination records: process
  • Do affected scopes and current documents agree?: decision
  • Record open conflict for project-controlled resolution: document
  • Record response, revision, and closed issue trail: document

3. Quantity Takeoff as a Traceable Measurement Process

Quantity Takeoff

A structured measurement of counts, lengths, areas, volumes, or assemblies from controlled project sources, with a documented scope and calculation basis.

Every Takeoff Row Needs

  • item description and scope boundary;
  • source sheet, detail, schedule, specification, and revision;
  • measurement type and unit;
  • written dimensions or approved model quantity;
  • formula or count basis;
  • inclusions and exclusions;
  • deductions and additions;
  • waste, laps, cuts, or procurement allowance assumptions;
  • reviewer status and revision history.

Net Quantity with Deductions

A generic measurement ledger separates additions and deductions before applying an allowance.

Qg=(Qadd−Qdeduct)(1+w)Q_g=(Q_{add}-Q_{deduct})(1+w)

Variables

SymbolDescriptionUnit
QgQ_gGross procurement or study quantityproject unit
QaddQ_{add}Measured additionsproject unit
QdeductQ_{deduct}Measured deductionsproject unit
wwExplicit allowance or waste factordecimal

Plan-Linked Quantity Takeoff Ledger

Tie every quantity to a controlled source, formula, inclusion decision, allowance, and revision delta.

Source audit: 0/6 included rows checked.
Revision A→B magnitude: 4.3 combined source-unit change.

Measurement trace

A-101 Rev B / grids 1–4 & A–C

2(12.0 + 8.0) = 40 m

Net m
56.95 m
Net m²
94.08 m²
Net m³
8.11 m³
Net ea
9.00 ea
Study cost
₱312,452
A-101 REV B · highlighted scope: walls
Editable takeoff audit ledger
IncludeItem / sourceQtyWasteUnit rateExtended
200 mm external wall centrelineA-101 Rev B / grids 1–4 & A–C · 2(12.0 + 8.0) m%₱74,160
100 mm internal partitionsA-101 Rev B / dimensions · 6.0 + 4.0 + 5.0 m%₱19,688
Floor tile areaA-101 Rev B / room dimensions · 12.0 × 8.0 m²%₱98,496
Stair opening deductionA-101 Rev B / opening tag O-1 · 2.4 × 4.0 m²%₱-9,120
Strip footing concreteS-101 Rev 3 / detail 3-S501 · 40.0 × 0.65 × 0.30 m³%₱52,728
Door count D-01A-101 + A-601 Rev B · count tags ea%₱76,500

A takeoff is only as reliable as its controlled source, scope boundary, dimension basis, deductions, waste assumptions, and revision handling. Unit rates are editable classroom placeholders, not market quotations.

Takeoff Review

  1. Freeze the revision and issue used for measurement.
  2. Define the scope before measuring.
  3. Highlight or tag each measured element once.
  4. Record the formula and source for every row.
  5. Separate deductions from waste factors.
  6. Reconcile plan quantities with schedules and details.
  7. Compare revisions and quantify changes rather than replacing prior work without trace.
  8. Perform an independent check and retain the audit trail.
Traceable Quantity Takeoff Review

Control the takeoff scope and revision, preserve quantity and material-state bases, reconcile discrepancies, and retain an independent audit trail.

Use the executed contract, BOQ, measurement specification, approved drawings, schedules, and project method for the applicable quantity. Record source, revision, units, scope, formula, additions, deductions, and any expressly authorized allowance. Keep bank, loose, compacted, installed, and other material states separate. Do not infer a universal waste, conversion, or payment rule. A change requires traceability to the superseded calculation and current approved source.

Traceable Quantity Takeoff ReviewControl the takeoff scope and revision, preserve quantity and material-state bases, reconcile discrepancies, and retain an independent audit trail.. Use the executed contract, BOQ, measurement specification, approved drawings, schedules, and project method for the applicable quantity. Record source, revision, units, scope, formula, additions, deductions, and any expressly authorized allowance. Keep bank, loose, compacted, installed, and other material states separate. Do not infer a universal waste, conversion, or payment rule. A change requires traceability to the superseded calculation and current approved source.. Set up a quantity takeoff → Defined scope, issue purpose, BOQ basis, and units; Defined scope, issue purpose, BOQ basis, and units → Are controlled sources current and compatible?; Are controlled sources current and compatible? — Yes → Measure each element once from its controlling source; Are controlled sources current and compatible? — No → Hold affected row and obtain current source; Hold affected row and obtain current source → Are controlled sources current and compatible?; Measure each element once from its controlling source → Record formula, additions, deductions, and material state; Record formula, additions, deductions, and material state → Do plans, schedules, details, and totals reconcile?; Do plans, schedules, details, and totals reconcile? — Yes → Perform an independent scope and calculation check; Do plans, schedules, details, and totals reconcile? — No → Investigate difference without hiding its source; Investigate difference without hiding its source → Record formula, additions, deductions, and material state; Perform an independent scope and calculation check → Is the quantity basis accepted by the project process?; Is the quantity basis accepted by the project process? — Yes → Archive reviewed quantity with source and revision trail; Is the quantity basis accepted by the project process? — No → Record basis rejection and preserve change history

Set up a quantity takeoff → Defined scope, issue purpose, BOQ basis, and units; Defined scope, issue purpose, BOQ basis, and units → Are controlled sources current and compatible?; Are controlled sources current and compatible? — Yes → Measure each element once from its controlling source; Are controlled sources current and compatible? — No → Hold affected row and obtain current source; Hold affected row and obtain current source → Are controlled sources current and compatible?; Measure each element once from its controlling source → Record formula, additions, deductions, and material state; Record formula, additions, deductions, and material state → Do plans, schedules, details, and totals reconcile?; Do plans, schedules, details, and totals reconcile? — Yes → Perform an independent scope and calculation check; Do plans, schedules, details, and totals reconcile? — No → Investigate difference without hiding its source; Investigate difference without hiding its source → Record formula, additions, deductions, and material state; Perform an independent scope and calculation check → Is the quantity basis accepted by the project process?; Is the quantity basis accepted by the project process? — Yes → Archive reviewed quantity with source and revision trail; Is the quantity basis accepted by the project process? — No → Record basis rejection and preserve change history

  • Set up a quantity takeoff: terminator
  • Defined scope, issue purpose, BOQ basis, and units: data
  • Are controlled sources current and compatible?: decision
  • Hold affected row and obtain current source: document
  • Measure each element once from its controlling source: process
  • Record formula, additions, deductions, and material state: process
  • Do plans, schedules, details, and totals reconcile?: decision
  • Investigate difference without hiding its source: process
  • Perform an independent scope and calculation check: process
  • Is the quantity basis accepted by the project process?: decision
  • Record basis rejection and preserve change history: document
  • Archive reviewed quantity with source and revision trail: document

Common Takeoff Failure Modes

  • measuring a superseded sheet;
  • scaling a distorted PDF when written dimensions exist;
  • mixing gross, net, bank, loose, compacted, or installed quantities;
  • double-counting intersections or repeated schedule items;
  • omitting openings or adding inappropriate deductions;
  • applying a waste factor without explaining its basis;
  • using unverified unit rates as though they were current quotations;
  • failing to capture revision changes.

4. Reading Linework, Dimensions, and References

Graphic Hierarchy

Heavy lines commonly indicate cut or primary boundaries; lighter lines show visible secondary information; dashed or special linetypes indicate hidden, overhead, centerline, property, demolition, or other defined conditions. The project legend controls the exact meaning.

Final Interpretation Checklist

Key Takeaways
  • Navigation is a traceable path through controlled information, not random sheet browsing.
  • Superseded documents explain history but do not authorize work.
  • Conflict resolution begins with evidence and ends with a recorded coordinated response.
  • A takeoff without source, revision, formula, and scope is not auditable.
  • No universal precedence rule replaces the executed contract and approved project process.

References

The executed contract, approved RFI and change process, BOQ, and project measurement specification establish document authority and quantity basis.