BLDG7021 Chap.10 BIM Coordination and Technical Documentation
BIM Coordination and Technical Documentation
Technical documentation is a connected information system of plans, sections, details and schedules. This chapter establishes controlled information sources, stable naming, drawing references and revision checks.
The final audit traces high-risk conditions across the complete set and verifies that the exported package matches the coordinated model.
Finish with a cold-read test after stepping away from the set. Open only the exported package, choose one sheet and follow every reference forward and backward. Confirm that view titles, scales, drawing numbers and revision information lead to the intended content.
Compare one scheduled type with its plan tag and enlarged detail. Record broken links or ambiguous names as issue items, correct the controlled source and export again. This exercise tests the delivered information rather than the familiarity of the person who produced it.
What this chapter covers
- 01
Set information sources
- 02
Coordinate drawing references
- 03
Trace critical conditions
- 04
Control revisions and issues
- 05
Verify the exported package
Worked example · free
Trace a slab-edge condition
- 1Confirm grids, levels and callouts agree.
- 1Match shade and mullion geometry to studies and structure.
- 1Check anchors, drainage, movement and fire stopping.
- 1Match type codes to glazing and finish schedules.
- 1Correct the controlled source and regenerate affected sheets.
Key terms
- Drawing register
- The controlled list of sheets, titles, revisions and issue status in a package.
- Model source
- The authoritative object or parameter from which dependent drawing information is generated.
- Revision control
- The process for identifying, issuing, replacing and verifying changed project information.
BIM Coordination and Technical Documentation FAQ
Does BIM guarantee coordinated documents?
No. Shared geometry helps, but assumptions, annotations, links, revisions and consultant information still require deliberate review across all plans, sections, details, schedules and final exports.
What should a final issue audit include?
Check the drawing register, references, dimensions, type codes, critical interfaces, revisions, linked models, sheet readability, file format, page count, delivery metadata and every reopened exported file.
Why correct the source instead of the PDF?
A local PDF edit can hide inconsistent model data and leave dependent views wrong, while correcting the controlled source allows regeneration and complete verification of the change.
What is the last useful issue check?
Open the exported package independently, follow one reference chain, compare one tag with its schedule and detail, and verify that the drawing register, file revision and issued content agree.
Assessment move
Study technical documentation as an information system with controlled sources and traceable outputs. Begin with a drawing register that lists number, title, scale or format, revision status and the model view or schedule that supplies the information. Use predictable, unique names for levels, grids, views, sheets, types and key details.
Ambiguous duplicates create coordination errors even when individual drawings look polished. Nominate where each repeated value is controlled so revisions do not require manual edits in several disconnected locations. Test the set through several high-risk conditions rather than inspecting sheets in isolation.
Good candidates include a core edge, facade-to-slab junction, plant or riser crossing, accessible entry, roof termination and ground discharge. Trace each condition from general arrangement plan to section, elevation, detail and schedule. Check that geometry, material names, dimensions, levels and references agree.
If a condition cannot be followed across the set, add or repair the necessary cross-reference instead of relying on an oral explanation. Apply a hierarchy audit to every sheet. Titles should identify purpose, view names should be consistent, line weights should distinguish cut and projection, and annotations should remain legible at the issued size.
Remove redundant notes and use keynotes or schedules where repetition would create maintenance risk. Confirm that dimensions are necessary, non-contradictory and referenced to stable elements. A dense sheet is not automatically informative; the reviewer should be able to find the primary decision, supporting detail and unresolved qualification in a clear sequence. Practise revision control with a deliberate model change.
Alter one coordinated element, then search the entire project for the obsolete value, type or reference. Update dependent plans, sections, schedules, details and diagrams, and record the revision. Spot-check the replacement in exported output rather than assuming the model propagated it correctly.
Where information comes from a linked consultant model or external schedule, note the exchange date and ownership so the team knows whether the source is current. A revision is complete only when the issued package and controlled model correspond. Run a pre-issue audit on the actual deliverables.
Reopen the exported PDF and inspect page order, sheet size, fonts, clipping, raster quality, line weights, hyperlinks if relevant and blank or duplicated pages. Compare sheet titles with the register and confirm that all required files use the intended revision.
Open the submitted model independently to check links, view templates, warnings relevant to output, file paths and the absence of unintended personal or obsolete content. This is a technical task, not merely presentation cleanup. For revision, create a small audit table with condition, source view, dependent outputs, status and evidence of closure.
Give a peer the package and ask them to trace three conditions without the live model or verbal guidance. Record where they become lost and repair titles, references or missing views. Finish with an issue note that states what is coordinated, what remains provisional and which external inputs were current at export. This method supports accuracy and legibility while making the submission resilient after it leaves the author.