ArchHubBABOOMDownload

Rooms, Areas and Model Quality Control

BBM-STD-32 · V0.2 · Finish a useful existing-condition baseline across the assigned buildings before design relies on it.

Download WordAll standards

Office BIM Workshops · Presenter: Ahmed Fargaly · Recorded session: 4 December 2024 · BBM-STD-32 · V0.2 · 14 October 2026 · WIP training revision; office approval pending

Purpose & scope#

Finish a useful existing-condition baseline across the assigned buildings before design relies on it. Keep the workshop's practical review: exterior, site context, entrances, openings, parapets and circulation, then space data and clean dimensions. Review everything in scope rather than polishing one building while the others have no baseline.

This guide distinguishes verified measurements from assumptions and shows how rooms, area schemes, area plans and tags support brief checks and finish planning. The author records objects and evidence; the discipline lead accepts design/measurement assumptions; the survey/coordinate owner accepts measured reference data; the BIM coordinator checks model/document/exchange quality. Calling a browser view Published does not authorise an exchange.

Standards basis#

  • ISO 19650-1:2018 and ISO 19650-2:2018 support agreed purposes, responsibilities and controlled delivery. Office Manual BBM-STD-01 V0.1 §§7.2, 8.2, 9, 11 and 12 and BEP BBM-STD-10 V0.2 §§6.5–6.6, 8.2, 8.6, 8.10 and 10 define the applicable model/data checks.
  • ISO 19650-4:2022 supplies the exchange-quality basis; metadata, content and the received result are checked separately. UK BIM Framework Guidance C, edition 1 (2020), supplies CDE transition guidance.
  • ISO 7817-1:2024 supports recording geometric, alphanumeric and documentary information needs by purpose. Accuracy must be stated; “approximately right” is not an acceptance condition for a surveyed output.
  • Autodesk A13/A14/A21 describe room calculation, phases and schedules. GSA BIM Guide Series 01 — Overview (2007, B02) is a historic spatial-programme reconciliation benchmark, not an adopted measurement code.
  • buildingSMART IFC guidance (S12) and IDS 1.0 (2024, S20) support agreed property/receiving tests. IDS does not establish geometric accuracy, accessibility or full design compliance.

V0.2 corrections#

Recorded shortcutCorrect instruction / why
Areas are like detail lines and exist only in one viewAn area is a scheme-based spatial object, with measurable data; an area plan is its view and an area tag is its annotation. They are separate components (C19/X02)
Deleting a wall never affects an areaDrawn boundaries can remain independent; picked/associated boundaries and area rules may react. Test wall move/deletion and actual associations
Site level = number of steps × 150 mmThis is an assumed study datum only. Survey actual risers, landings and site controls before measured/as-built or access use (C10)
Plot wall approximately 2 m high from a mapA schematic context aid needs a clear assumed-height/boundary label. Maps/photos do not verify legal boundaries or surveyed height
Fractions are errorsUnexpected fractions trigger investigation; verified oblique geometry and measured conditions can legitimately contain fractions. Do not round away evidence
Never use native/downloaded familiesOffice templates remain the default. Native/manufacturer/external content requires guide 35 quarantine, rights, compatibility, cleaning and approval (C17)
Only Published browser views go on sheetsUse the office's approved sheet-view template/status convention; actual CDE publication still requires checks and exchange decisions (C04)

Correction verification: Autodesk, Area Analysis, Revit 2026 (schemes, plans, boundaries, areas and tags); Create Area Boundaries, Revit 2026 (drawn/picked boundaries and area rules).

Define the measurement before modelling#

Calculation recordComplete / agree
Use and scopeBrief comparison, gross area, scope zoning or finishes; included levels/objects and exclusions
Measurement conventionNamed adopted method/edition or documented project rule; room/area boundary faces, openings, shafts, voids and deductions
Accuracy and unitsSource accuracy, allowable project variance, m² or agreed unit, reporting precision separate from underlying calculation
Room settingsBoundary-location setting, room-bounding categories/links, level computation height, lower/upper limits/offsets, phase
Area settingsScheme name/revision, level/area plan, boundary rules, drawn/picked/associated line behaviour, area type
VolumesOff if not required; on only with an agreed purpose and tested enclosure/height/performance
Review authorityMeasurement owner, design lead, survey/coordinate owner and exchange checker; decision IDs

Do not mix room finish-face net areas with gross/rentable/scope areas and expect equal totals. Revit's default scheme rules must be checked against the adopted convention; they do not automatically certify that convention. Rooms can be placed as soon as valid enclosure/data is needed and updated as design develops; they need not wait for the last layout. Area schemes can support early zoning independently of final room layout.

Room, area, view and tag relationships#

ComponentPurpose / dataRequired contextChange / deletion effect to verify
RoomSpace identifier, name, calculated area and room propertiesLevel, phase, room-bounding enclosure/separation lines, calculation settingsMoves with its valid spatial context; unplacing retains record; permanent deletion removes data
Room tagAnnotation reading a room's dataAnnotatable view and referenced roomDelete tag: room remains; retag to restore annotation
Area schemeAlternative spatial/measurement organisationApproved purpose, rules and scheme identityDifferent schemes are separate analyses; no unqualified addition across schemes
Area planView of the scheme/level spatial relationshipsScheme and level; supported display settingsView operations are distinct from changing the area's data or boundaries
Area boundary / areaBoundary encloses an area record carrying scheme-specific dataDrawn/picked lines, selected rules and placed areaWall-associated changes require a test; unplaced/unenclosed records need audit
Area tagAnnotation reading the area's dataArea-plan view and referenced areaDelete tag: area data persists; selecting tag is not selecting the area

Room extent/volume is spatial, but visibility and annotation depend on the chosen view and category capability; the workshop's “every view including 3D” is not a guarantee of graphical visibility. Within one intended scheme, audit gaps, overlapping scope and redundant records. Overlap across different schemes may represent valid alternative analysis, not duplicated physical area to add together.

Step-by-step procedure#

  1. Classify the existing-condition evidence. Register surveys, drawings, photos, maps and scans with revision/date/source and use limits. Mark measured, inferred or assumed geometry. Do not label the whole model as-built when only appearance was checked. Obtain a measured baseline before changes to structure, services or access depend on it; an anticipated contractor survey is an assigned outstanding dependency, not present evidence.
  2. Model context to the agreed need. Show surrounding out-of-scope buildings as simple blocks with a context-only property/legend. Model verified boundaries with their source and uncertainty; label schematic boundaries and guessed heights. Check exterior openings, landmarks, parapets, stairs, ramps and entrances against the scope. Reference guide 30 for survey/site coordinates. Keep the provisional zero datum explicitly separate from accepted site elevations.
  3. Agree the space convention. Complete the calculation record above. Set project units/precision, room boundary calculation and level computation height under owner approval. On sloped walls or unusual heights, inspect the section where area is computed. Add room separation lines only where needed; do not use them to hide a wrong room-bounding wall. Validate room height/upper limit when volumes are required.
  4. Place rooms in the correct context. Confirm view level/phase and each bounding element's phase. Place unique room IDs/names; inspect enclosed, redundant, Not Placed and Unenclosed conditions in the schedule. Use Tag All where appropriate, then inspect missing/duplicate annotations. Test room-bounding linked-model behaviour with a representative enclosure, link instance setting and phase mapping. Reload the approved link revision and verify the recalculated result; do not assume every visible linked wall bounds a room.
  5. Build area analyses deliberately. Create the required scheme first, then its area plan by level. Create boundaries using the adopted rules, place area objects, assign unique IDs and area types and tag them. Decide whether boundaries are independent or associated with picked walls. In a controlled copy move and then delete one wall; record whether the area boundary/result changes and repair the intended enclosure. Never infer the rule from a tag alone. Apply colour schemes by approved department/scope/name and confirm colours match data; colour is not measurement evidence.
  6. Control families and graphics. Prefer the office category templates. For old or external content, follow guide 35: selected standards only, parameter/GUID preservation, flex, tag/schedule and exchange tests, library release. A foreign line pattern raises a review request; it does not prove that all required manufacturer data should be deleted. Record which family reload option is selected and compare intended existing values before/after. For design plans duplicate using the selected view operation, apply the stage template, and check filters, annotations, phase and sheet references; duplication behaviour differs by operation.
  7. Use dimensions to investigate geometry. Start with verified grids, then wall location lines/core/finish faces and offsets. The office Check dimension style may expose finer precision than issue drawings. Compare raw measured geometry with the approved tolerance and source rather than forcing whole millimetres. Use selection/category filters or agreed worksets to inspect the intended elements without changing phase semantics. Record approved exceptions for sloped/rotated geometry or surveyed fractions.
  8. Audit all space records. Create itemised room and per-scheme area schedules including ID/number, name, level, phase where supported, scheme, area, upper-limit data and required finish/brief keys. Keep a separate unfiltered QA/exception view for missing/duplicate IDs, Not Placed, Unenclosed, redundant rooms and abnormal zero/negative/unexpected areas. Do not filter all blanks out of the only schedule. Categorise failure, affected ID, owner, action, due date and retest evidence.
  9. Reconcile to the brief. Join model records to brief IDs, compare like-for-like convention and phase, and account for included/excluded circulation, walls, voids and out-of-scope space. Record target/actual/variance and reason. The design/measurement owner accepts a justified exception; required failures remain open until corrected. Never add gross and net totals or different scheme totals as if they were disjoint.
  10. Check and exchange the reviewed revision. Preserve the exact model, calculation settings, linked revisions, schedules and sheet pack. Check filenames/revision/status/access metadata separately from contents. Export with the agreed IFC schema/profile and required space/object/property mapping. Use applicable IDS 1.0 requirements only within their supported scope; retain requirement/checker versions and reports. In the receiving system, inspect spaces/units/identities, sample boundaries, elevations and schedule totals; visually review spatial/doc outputs as well as automated properties. Review warnings/performance with ownership and disposition. Correct failures in WIP and resubmit a new revision through appointed check/share/authorise/accept decisions; archive superseded evidence.

Separate room and area contexts, then validate their boundaries, records, brief totals and received outputs.

QA record — a fill-in check register#

Object / checkMethodOwnerAcceptance conditionEvidence / failure action
Existing-condition accuracySurvey/control and dimension comparisonSurvey/coordinate ownerMeets approved use-specific accuracy; no unlabeled assumptionsSource revisions, controls, discrepancy ID and resolution
Room enclosure/heightPlan + section at computation heightModel author / checkerAll required rooms enclosed, uniquely identified, correct level/phaseCalculation settings and room exception report
Area scheme/boundaryRule review + wall move/delete sampleMeasurement ownerMatches adopted method and recorded behaviourScheme/rule revision, before/after results
Brief totalsStable-key join and variance analysisDesign leadRequired spaces accounted for; allowed variance/exception approvedBrief/model revisions and variance table
Metadata / accessIdentifier/revision/status/recipient checkInformation-management roleCorrect approved project metadata and custodyTransmittal and decision record
Delivery contentSpace/property/profile check; IDS where applicableExchange checkerEvery mandatory applicable requirement passesExport/IDS/checker versions and failed-object report
Geometry / documents / receiverPlans, sections, sheet QA and independent importCoordinator / discipline reviewerPosition and displayed/reported data match approved baselineScreenshots, dimension/quantity reconciliation and disposition
Warnings / performanceWarning classification, open/regenerate tests on approved hardwareBIM coordinatorNo unresolved critical failures; project performance criterion metModel revision, warning list, timings and approved exceptions

Automated data checks cannot replace a section review or detect every incorrect assumption. Each failed row needs an issue, correction or explicit authorised exception, and retest. “Looks clean” is not evidence of the calculation method.

Worked exercise — three rooms and two areas#

Create three rectangular test rooms measured to the agreed internal finish-face boundaries: R01 = 4 × 3 m (12.00 m²), R02 = 5 × 4 m (20.00 m²), R03 = 6 × 3 m (18.00 m²). This synthetic net-area total is 50.00 m². In a separate SCOPE scheme use independently defined disjoint rectangles A01 = 30.00 m² and A02 = 25.00 m², total 55.00 m². The 5.00 m² difference is intentional under these different definitions; do not combine them to report 105.00 m².

  1. Set a recorded computation height, room boundary setting and phase; tag each object. Delete only the R01 tag: the room remains and the room total stays 50.00 m². Restore the tag.
  2. Unplace R03 deliberately: its retained record becomes Not Placed and the placed-room area total becomes 32.00 m². The brief/exception check fails until R03 is re-placed and returns the total to 50.00 m². Do not delete the record to hide the issue.
  3. Make R02's enclosure depend on a test linked bounding wall; record link revision, room-bounding setting and phase mapping. Move that wall by 0.200 m across a 4.000 m span in a controlled copy. The intended rectangular test changes area by 0.800 m²; inspect actual calculation and repair unexpected behaviour.
  4. Repeat a wall move/deletion for one drawn and one associated area boundary. Record the actual scheme behaviour; restore 30.00/25.00 m² and explain the difference. Add a blank ID and duplicate ID temporarily to prove the exception report finds them, then correct.
  5. Submit schedules, key-plan/section, measured/assumed evidence register, brief reconciliation, failure/retest log and received space/property check. Assessed pass requires correct identities/totals and an explanation of each context/exception, not attendance.

Acceptance criteria / self-check list#

  • Existing-condition source/accuracy and provisional limits are explicit; survey verification precedes reliance or an as-built claim.
  • Measurement convention, units, computation height, limits, phase, scheme/rules and reviewer are recorded.
  • Room/area objects, their views and tags are distinguished; linked-boundary/phase and wall-change tests are demonstrated.
  • All required records have unique identifiers; unplaced/unenclosed/redundant/abnormal conditions remain visible in the exception schedule.
  • Totals reconcile to the brief under the same approved convention and scope; assumptions and exceptions have decisions.
  • Fractions are investigated against source/tolerance; required measured geometry is not rounded away.
  • External/old families use guide 35 controlled admission; required identities/values survive reload.
  • QA records identify object, method, owner, acceptance and evidence; failures and retests are traceable.
  • Metadata/content, IFC/IDS where applicable, geometry/document/receiver, warning and performance checks reference the preserved model revision.

Common mistakes#

  • Treating a colourful plan as a correct measurement, or treating area tags as area objects.
  • Assuming every wall change updates every boundary, or every linked wall bounds rooms.
  • Using an area scheme name as proof that its calculation is compliant with the adopted convention.
  • Assuming a photographed facade or step-derived elevation is surveyed as-built information.
  • Clearing Not Placed rooms or imported family properties without impact review.
  • Rounding verified fractional dimensions to make the QA view look tidy.
  • 25 and 30: approved scope, survey, levels and coordinates.
  • 28: controlled view templates and sheet checks; 31: room actions and data-edit recovery.
  • 33: finish keys, quantities and phases; 35: family admission policy; 36: complete and exception schedules.

Editorial coverage record#

R10.1–R10.5: calculation record, component relationships, procedure 3–5/8–9 and known-total exercise. T06.1–T06.5: QA register and procedure 10 cover ownership, metadata/content failures, IFC/IDS scope, visual/receiving checks, warning/performance and retained revisions. C04/C09/C10/C17/C19 resolved; P1 1/1 and P2 1/1 fixed, P3 known-total exercise included. Training exercises require execution and review in the office-approved release.

References#

Source IDs refer to the supplied RESEARCH.md register. Autodesk Help describes the listed release; verify commands in the project-approved build. Public ISO abstracts establish scope and edition, not clause-level compliance.

  • S01 — ISO 19650-1 — Concepts and principles. ISO, 2018, ed.1. https://www.iso.org/standard/68078.html?browse=tc
  • S02 — ISO 19650-2 — Delivery phase of the assets. ISO, 2018, ed.1. https://www.iso.org/fr/standard/68080.html
  • S04 — ISO 19650-4 — Information exchange. ISO, 2022, ed.1. https://www.iso.org/cms/live/live/en/sites/isoorg/contents/data/standard/07/82/78246.html?browse=tc
  • S07 — ISO 7817-1 — Level of information need: concepts and principles. ISO, 2024, ed.1. https://www.iso.org/standard/82914.html?browse=tc
  • G-C — Guidance C — Facilitating the CDE workflow and technical solutions. UK BIM Framework, ed.1, September 2020. https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-C_Facilitating-the-common-data-environment-workflow-and-technical-solutions_Edition-1.pdf
  • A13 — About Room Area. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-ArchDesign/files/GUID-9348929C-18CA-40AC-BB64-71D01CC52F2B.htm
  • A14 — Project Phasing. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-DocumentPresent/files/GUID-2E104AB8-68B9-46F2-9BE2-B54E767429E5.htm
  • A21 — Schedules; About Schedules. Autodesk Revit Help, 2026 / 2024. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-DocumentPresent/files/GUID-F50D6FF4-859E-43A2-A2F6-81C84A1BA0EB.htm; https://help.autodesk.com/cloudhelp/2024/ENU/Revit-DocumentPresent/files/GUID-73090B70-8A13-4E12-909C-F25D724D5BA7.htm
  • A10 — How to set up Shared Coordinates using one Revit model as the Site or Base file. Autodesk Support, 15 August 2026. https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-set-up-Shared-Coordinates-using-one-Revit-model-as-the-site-or-base-file.html
  • A06 — Create Shared Project Parameters. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Model/files/GUID-114C68A9-FF2B-4D4C-A2DF-3AE7E1F174C8.htm
  • A18 — Create a Family from a Template. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Customize/files/GUID-228D213B-9497-48A6-AAE1-4E54F7834931.htm
  • A19 — Model Efficiently. Autodesk Revit Help, Revit 2024. https://help.autodesk.com/cloudhelp/2024/ENU/Revit-Customize/files/GUID-8287BB99-B15F-4809-B6AF-3DA26B8CD027.htm
  • S12 — Industry Foundation Classes (IFC). buildingSMART International, Undated live page; 2024 ISO edition. https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/?lang=en
  • S20 — Information Delivery Specification (IDS). buildingSMART International, 1.0, approved 2024. https://www.buildingsmart.org/standards/bsi-standards/information-delivery-specification-ids/?trk=article-ssr-frontend-pulse_little-text-block
  • B02 — GSA BIM Guide Series 01 — Overview. US General Services Administration, 2007. https://www.gsa.gov/cdnstatic/GSA_BIM_Guide_v0_60_Series01_Overview_05_14_07.pdf (historic spatial-programme benchmark).