If everyone around you is throwing around acronyms like BEP, LOD, CDE, and IFC like they're basic vocabulary - you're in the right place. 540 terms, from foundational concepts to the full BIM dimension stack, cross-linked between related ideas. ← Articles
Want to put these concepts into practice?
Explore our Revit courses →Start typing to search a term, or pick a category above.
Geometry
BIM "dimensions" describe what layer of information is added on top of the 3D model. Think of 3D as the base - each additional dimension enriches the model with a new type of data.
The base model. Walls, floors, roofs, columns, ducts, pipes - all modeled as intelligent 3D objects in space. This is what most people think of when they hear "Revit model."
The BIM dimension stack (3D–10D)
Autodesk 3ds Max
Where Enscape or Twinmotion prioritize speed and live interactivity, 3ds Max is usually the choice when a project needs the extra control and polish of a fully offline-rendered still.
Time
The model linked to a construction schedule. Each element is tied to a task and a date, so you can animate the building sequence, catch scheduling conflicts before breaking ground, and communicate the build plan to all stakeholders visually.
Cost
The model linked to cost data. Quantities are extracted directly from modeled elements and multiplied by unit rates, giving real-time budget tracking as the design evolves. Changes to the model automatically update the cost estimate.
Sustainability
The model used for energy and environmental analysis. 6D BIM evaluates daylight levels, heating and cooling loads, carbon footprint, and lifecycle environmental impact - all from early design stages, when changes are still cheap to make.
Facility Management
The model handed over to building operators after construction. Asset data - equipment specs, warranty periods, maintenance schedules, replacement cycles - is embedded in the model and used by the facility management team throughout the building's operational life.
Safety
Safety information integrated into the model. 8D BIM identifies construction site hazards, simulates risk scenarios, and embeds safety procedures into the building sequence. It helps contractors plan safer sites before anyone sets foot on them.
Lean Construction
The model used to optimize workflows and reduce waste. 9D BIM applies lean construction principles - minimizing idle time, sequencing work efficiently, reducing material waste - and feeds those improvements back into the construction plan.
Industrialization & Digital Twins
The most advanced dimension. 10D BIM integrates prefabrication and modular construction data (off-site manufacturing tolerances, delivery logistics, assembly sequences) and feeds into a Digital Twin - a live virtual replica of the building that continues to receive real-world data from sensors long after construction is complete.
Note: 3D through 7D are widely adopted and standardized. 8D–10D are increasingly used but not yet uniformly defined across all standards bodies.
Aconex fills a similar role to Newforma or Procore's document-control side - a single, auditable record of every drawing revision, submittal, and approval on a project - but has particularly strong adoption on large international infrastructure and mega-projects outside North America.
A special family type whose placement points are not fixed - they adapt to conform to a host, like a divided surface, a curved curtain wall panel grid, or a path defined by a Dynamo graph. Instead of one rigid shape, an Adaptive Component flexes its geometry to fit wherever its points land, which is what makes complex, non-repetitive facade panels or canopy structures possible without manually modeling each unique piece.
They are the standard technique for panelizing a curved or freeform surface: place one adaptive family, apply it across a whole divided surface, and each instance automatically reshapes to fit its own unique panel location.
Some add-ins run through the Revit API directly and require real programming; others, like Dynamo, offer a visual layer on top of that same API so non-programmers can automate tasks too.
It exists specifically because construction disputes can't wait years to resolve without stalling an entire project - a decision is binding immediately, even if either side can still challenge it later through arbitration or litigation.
Approved For Construction Drawings
The final status a drawing reaches once the design team, and often the client or approving authority, has signed off on it - work can now legally start on site from that revision. AFC is the last stop in a drawing's CDE status lifecycle (Work in Progress, Shared, Published/AFC), and any change after this point requires a formal revision, not a quiet edit.
Confusingly, some firms use AFC and IFC Drawings almost interchangeably; others draw a sharper line - IFC marks the moment drawings are issued to the site team, while AFC confirms they have been formally approved, which may happen slightly earlier or later depending on the project's issue tracking workflow. Either way, once a drawing set is superseded by a newer AFC revision, the old one should be clearly marked void to avoid the classic, and expensive, mistake of a contractor building from an outdated sheet.
AIA Document A201 - General Conditions of the Contract for Construction
Where the broader "AIA Contract Documents" entry covers the whole family, A201 is the specific one most US construction professionals actually mean when they just say "the AIA general conditions."
American Institute of Architects Contract Documents
AIA's E203/G202 documents specifically govern BIM and digital data protocols on US projects, playing a similar role to a BEP in an ISO 19650 project - defining model authorship, LOD expectations, and data ownership within the broader AIA contract framework.
Asset Information Model
The other half of the pair. The AIM is the information model used to operate and maintain the building after handover: asset registers, equipment data, maintenance schedules, warranties, and as-built models.
If the PIM answers "how do we build it?", the AIM answers "how do we run it?" - and COBie is one of the common vehicles for moving data from one to the other.
Asset Information Requirements
The operational twin of the EIR. Where the EIR defines what information a client needs during design and construction, the AIR defines what information the client needs to operate the building once it is handed over - maintenance schedules, warranty data, equipment manuals, spare-parts lists.
The AIR feeds directly into the AIM: it is essentially the specification for what the Asset Information Model must contain. A well-written AIR early in a project makes the eventual handover to facilities management dramatically smoother, because everyone knows from day one exactly what data needs to be collected.
Locking an alignment after using it keeps the two elements tied together going forward - move the reference later, and the aligned element follows it automatically.
It sits in the same Nemetschek family as Vectorworks, another data point in how fragmented the BIM authoring market actually is once you look past the Revit-centric English-speaking market.
It's the counterpart to a model family: a door tag, a level head, and a north-point symbol are all annotation families, scaling with the view rather than existing at real-world size in 3D space.
One of ISO 19650's defined roles: the Appointing Party is the organization commissioning the work - usually the client - responsible for setting the EIR and ultimately deciding what information it needs. Every other role in the standard's terminology is defined relative to this one: the Appointing Party appoints a Lead Appointed Party, who in turn may appoint further Task Teams.
Knowing these role names matters mainly when reading an ISO 19650-compliant contract or BEP directly - the standard uses them precisely and consistently, and the terminology can otherwise read as needlessly formal for what is, in plain language, simply "the client."'
Approved Document B: Fire Safety (UK Building Regulations)
Fire-rating parameters on Revit wall and door families, travel-distance checks on escape routes, and compartment boundaries on plans all exist specifically to demonstrate Approved Document B compliance - it's one of the most common reasons a design gets sent back for revision late in a project.
Approved Document F - Ventilation
As buildings are built increasingly airtight to meet Part L's energy targets, Part F's ventilation requirements become the counterbalance that keeps them healthy to actually live in.
Approved Document L - Conservation of fuel and power
It's the regulatory floor a project's operational carbon and net-zero ambitions get measured against - meeting Part L is the legal minimum, and many projects now set their own targets well beyond it.
Approved Document M - Access to and use of buildings
It sits alongside Approved Documents B and L as one of the three most frequently checked parts of the regulations on almost any building project.
Autodesk Platform Services (formerly Forge)
Autodesk's suite of cloud APIs - formerly branded Forge, renamed Autodesk Platform Services - that lets developers build custom applications on top of BIM data without needing Revit installed: viewing models in a browser, automating model checks, extracting data at scale, or connecting a project's BIM data into a company's own internal software.
Where Dynamo automates inside one open Revit session, APS operates at a platform level - server-side, cloud-hosted, capable of processing many projects' models without a person sitting at a desktop. It is the layer that custom, in-house BIM tooling and larger construction-tech products are typically built on.
Where adjudication is fast and interim, arbitration is slower but final - many international construction contracts, including FIDIC, specify arbitration as the ultimate route if earlier dispute mechanisms fail.
It's the tool most commonly sitting on the GIS side of GIS-BIM integration, receiving federated model data exported or streamed from the Autodesk/Bentley side.
It shares the same object-based-modeling philosophy as Revit but comes from an entirely separate lineage - Teamwork is its own worksharing system, and IFC is usually the practical bridge when an ArchiCAD-based architect coordinates with a Revit-based engineer.
Where room-vs-space usually comes up in the context of MEP coordination, area plans serve a different purpose entirely - gross floor area and rentable area calculations for planning approval or leasing, drawn with their own area boundary lines rather than room tags.
A row of evenly spaced parking bollards or a radial pattern of columns around a curved building are the kind of repetitive layouts Array handles in seconds instead of placing each one by hand.
As Built Model
The model that reflects what was actually built - not what was designed. Construction always brings changes: a pipe route moves, a beam is raised, a wall shifts. The as-built model captures all of them, often verified against laser scans of the finished building (Scan to BIM).
It is the basis for the AIM and facility management - you cannot maintain a building from a model that does not tell the truth.
As Designed Model
The third point in the design-to-construction trio, alongside As Made and As Built. The As Designed model is the design team's original intent - what should be built, based on the design decisions made before construction started. It is the baseline everything else gets measured against: As Made captures what was actually installed on site, As Built is the coordinated record of the completed building, and the gap between As Designed and As Built is, in effect, a map of every change that happened during construction.
Keeping the As Designed model intact, rather than overwriting it with site changes, matters for exactly this reason - without it, there is no way to see how much the finished building actually diverged from the original plan.
In DfMA and modular construction, elements are built in a factory to precise tolerances before ever reaching site - "as fabricated" captures that manufactured state, which can then be compared against both the design intent and, later, the as-installed reality to catch discrepancies early, while they're still cheap to fix.
As Made Model
A record - often at component or connection level - of exactly what was installed or constructed on site, usually captured by the installing team directly from site measurements or scans. As-Made data is typically more granular and immediate than an As-Built model: it is produced discipline-by-discipline as work happens, before it gets consolidated.
The as-made record then feeds into the broader As-Built model - the design team updates the design-intent model with the as-made data (plus any further verification) to produce the single coordinated record of the completed building. In short: As-Made is the raw site truth; As-Built is the coordinated model built from it.
As-Occupied Model
The fourth, least-discussed point in the design-to-operation timeline, alongside As Designed, As Made, and As Built. The As Occupied state captures a building after tenants and operators actually move in and start changing things - rearranging partitions, adding equipment, modifying finishes - changes that happen entirely outside the original project team's control or awareness.
Keeping an As Occupied record current is genuinely hard, which is exactly why it matters: an AIM that was accurate on handover day slowly drifts from reality as occupants make their own changes, and a facilities team working from a stale model is planning maintenance and renovations against a building that no longer quite exists.
"As planned" is the baseline everyone measures against - construction progress, schedule slippage (4D BIM), and eventual as-built deviations are all compared back to this original plan. It sits alongside as-designed, as-made, as-built, and as-occupied as one of the recognized project-state terms.
It's the quality-control step behind the whole scan-to-BIM and as-built process: a point cloud is overlaid on the as-built model, and any deviation beyond an agreed tolerance gets flagged before the model is signed off and handed over.
It sits at the start of the as-* family, before as-designed even begins - a condition survey or a scan-to-BIM model is usually how an as-existing state actually gets captured and modeled.
A CDE's status workflow exists precisely to separate work-in-progress from as-issued information - only the second one is safe for another party to actually rely on and build from.
An as-built model freezes the moment of handover; an as-maintained record keeps moving after it, capturing the boiler swapped in year three or the roof re-covered in year eight - exactly what an FM team needs to trust the AIM years later.
On a retrofit project it's checked before the first wall is even opened - missing or out-of-date entries are one of the most common causes of a construction-phase health-and-safety stoppage.
American Society of Heating, Refrigerating and Air-Conditioning Engineers
ASHRAE 90.1 (energy efficiency) and ASHRAE 62.1 (ventilation) are the two standards MEP engineers reference constantly when sizing systems in Revit - building performance simulation tools check a design against these same benchmarks long before a mechanical system is ever fully modeled.
Instead of exporting a static schedule out of Revit, an estimator can connect Assemble directly to the live model and slice quantities by any condition needed for a specific bid package - a faster, more flexible layer on top of the same underlying model data Revit's own schedules use.
A precast concrete panel or a prefabricated bathroom pod is a natural fit for an Assembly - it needs its own detail views and a shop-drawing-style sheet for the fabricator, which is exactly what an Assembly generates automatically, unlike a plain Group which has no view/sheet infrastructure of its own.
It's the field that lets a schedule roll up quantities by building system - all exterior wall assemblies together, say - rather than only by Revit's own built-in category.
A condition survey is the one-off assessment that produces it; the rating itself is what actually feeds a facilities management team's decision about which roof to replace this year versus which one can wait.
It's the formal bookend to an asset's lifecycle - without it, a decommissioned boiler can keep sitting in the asset register as if it's still something facilities management needs to maintain.
The broader discipline that BIM's 7D and AIM exist to support: the ongoing, whole-lifecycle work of operating, maintaining, and eventually replacing a building's systems and components, long after construction ends. Asset management thinks in decades, not project milestones - maintenance schedules, replacement cycles, energy performance, compliance inspections, all tracked against the actual physical assets a facilities team is responsible for.
Where BIM traditionally focused on getting a building built, the growing overlap between BIM and asset management (through the AIM and standards like ISO 19650's part 3) is what turns a one-time model into a long-term operational tool instead of a file that gets archived the day the building opens.
Where an EIR and AIM are about the information a building carries, the asset management plan is about the decisions that information is meant to support - when to replace a plant item, how to budget for lifecycle costs, which parts of the estate to invest in next. ISO 55000 sets the international standard it's usually built against.
It's the practical spine an FM system runs on - every work order, maintenance schedule, and asset-tagging effort ultimately points back to a single row in the asset register.
A facilities manager scanning a tag on a rooftop air handling unit should land directly on that exact asset's model data - warranty status, maintenance history, spec sheet - closing the gap between the physical building and its digital record that a handover package alone doesn't solve.
A deeper, slower file-health check than Purge - Revit's Audit command scans the entire project database for low-level corruption and inconsistencies that build up over long project lifespans, especially in heavily workshared models, and repairs what it can. It is typically run when a file starts behaving strangely (unexplained crashes, elements that won't delete cleanly) or as periodic preventative maintenance on large, long-running projects.
Audit and Purge solve different problems - Purge removes unused content, Audit repairs unhealthy file structure - and a well-maintained large project usually runs both on a regular schedule rather than waiting for something to visibly break.
The core mental shift moving from AutoCAD to Revit is that CAD draws independent lines representing a wall, while Revit models an actual parametric wall object that generates those lines (and every schedule, section, and quantity) automatically - which is why "AutoCAD habits" like manually drafting details from scratch are the most common source of friction for new Revit users.
It's where issue tracking and progress monitoring actually happen day to day on site - the tablet app a site manager opens, not the design coordination BIM 360 was originally known for.
Forma combines fast, cloud-based environmental and massing analysis (sun, wind, noise) for early design decisions with the document management, file transmittal, and issue-tracking modules that used to sit under the BIM 360/ACC name - Revit connects to it directly for cloud model sharing and coordination.
Check health.autodesk.com the moment cloud worksharing, sync, or an ACC upload suddenly stops behaving - it is usually the fastest way to tell whether the problem is on your end or Autodesk's before spending an hour troubleshooting locally. The dashboard tracks status for well over a hundred individual services, so it is worth searching for the specific one you use (Revit Cloud Worksharing, BIM 360 Docs, APS) rather than reading through the whole list.
Insight pulls geometry and location data straight out of the Revit model to run whole-building energy analysis without needing a separate dedicated simulation model - useful for the quick, iterative "what if we changed the window ratio" questions that come up constantly in early design.
A cost baseline set at design freeze is what every later change order gets measured against - without it, "how much did this project actually grow" has no fixed starting point to answer from.
BIM Collaboration Format
The open format for exchanging model issues - not the model itself. A BCF file carries a comment, a screenshot, a camera position, and references to the exact elements involved, so whoever receives it can open their own model, jump straight to the problem, and fix it.
BCF is maintained by buildingSMART (like IFC) and is supported by Navisworks, Solibri, Revit add-ins, and most issue-tracking platforms. It is how clash detection results actually travel between teams.
It's an American-contract concept that runs parallel to practical completion in UK contracts - the moment risk and use effectively transfer to the client, snag list or not.
BIM Execution Plan
The project team's response to the EIR. The BEP is written by the lead designer or BIM manager and explains how the team will deliver the information the client has asked for.
There are two types:
Every serious BIM project runs on a BEP.
A contractor's tender documents, cost plan, and proposed programme all get pulled together under bid management - a rushed one is a common early source of the risk a later risk register ends up tracking.
Building Information Modeling
The starting point. BIM is not a software - it's a process. It means creating and managing a building's information digitally throughout its entire lifecycle: design, documentation, construction, and operation.
At the center of a BIM workflow is a 3D model where every element carries data - not just geometry. A wall isn't just a shape; it has a material, a fire rating, a cost, and a thermal value. That data travels with the model from the architect's desk to the contractor's site to the facility manager's dashboard.
Autodesk Construction Cloud
Autodesk's cloud construction-management platform - originally launched as BIM 360, now the foundation of Autodesk Construction Cloud (ACC) - covering document management, model coordination, cloud worksharing, field issue tracking, and more, all in one connected environment. For many teams, it is the actual, practical CDE: the place where WIP, Shared, Published, and Archive information genuinely lives, rather than just a theoretical concept from ISO 19650.
Cloud worksharing through this platform has increasingly replaced Revit Server for teams collaborating across multiple offices, since it needs no dedicated server hardware and works from anywhere with an internet connection.
A BIM Champion doesn't necessarily hold a job title with "BIM" in it - often it's simply the most enthusiastic, capable person on a team who ends up training colleagues, pushing for better standards, and advocating for tools and workflows, long before the firm formalizes that role into an actual BIM Manager position.
The role that runs the day-to-day, hands-on coordination work on a single project: setting up the federated model, running clash detection, tracking and closing out issues, checking that discipline models are meeting the agreed LOD at each milestone, and keeping the model organized between coordination meetings.
Where the BIM Manager sets the standards and strategy, the BIM Coordinator is the one actually inside the model every day making sure the project follows them - the two roles work closely together, with the coordinator escalating problems the manager needs to solve at a higher level: a contract issue, a persistent process failure, a client pushing back on requirements.
The role responsible for how BIM actually gets delivered - writing and enforcing the BEP, defining office and project templates and standards, training staff, and making sure the model data a project produces actually satisfies the client's EIR. A BIM Manager operates at a strategic level: firm-wide standards, software rollout, process improvement, sometimes managing a team of BIM coordinators across several projects.
It is a genuinely different job from a BIM Coordinator, who works inside one project's day-to-day model coordination - though on smaller firms and projects, one person often ends up wearing both hats.
BIM Maturity Levels 0-3
A simple 0-to-3 scale (from the UK BIM Task Group) describing how far a project has moved from isolated 2D drawing toward fully collaborative, data-rich BIM:
Most real projects today operate at Level 2 - which is exactly what ISO 19650 was written to standardize.
Whether it's called a Family in Revit, a Component in ArchiCAD, or a Block-with-data in another tool, all of these are BIM objects: geometry plus structured, parametric data (dimensions, material, performance, manufacturer specs) bundled together so it behaves consistently wherever it's placed. Manufacturers increasingly publish their own BIM objects so their real products can be specified directly inside a model.
CIC BIM Protocol
A legal supplement (the best-known version published by the UK's Construction Industry Council) attached to a standard construction contract to make BIM deliverables legally enforceable. On its own, an EIR or BEP is a technical document - it does not carry contractual weight unless something ties it to the actual contract. A BIM Protocol is that tie: it references the EIR/BEP, defines who owns model data, sets out liability if information is wrong or late, and makes model delivery a contractual obligation rather than a best-effort request.
Every serious client who wants BIM deliverables that can actually be enforced needs a protocol like this sitting alongside the technical documents.
A catch-all term for outsourced BIM expertise: model managers, BIM trainers, BIM consultants, BIM facilitators, and modeling/auditing bureaus all fall under it. Firms bring in a BIM Service Provider when they need specialist capability or capacity they don't have in-house, rather than hiring a permanent BIM Manager or BIM Coordinator.
Rather than asking "do we need BIM," a project team asks "which BIM uses do we need" - because a model built for design visualization isn't automatically ready for 4D scheduling or quantity takeoff. Planning BIM uses upfront (a concept popularized by Penn State's BIM Planning Guide) is how a BEP decides what level of development each element actually needs.
It's a common first stop for checking that an exported IFC file actually opened correctly and looks right, before sending it on to a client or a coordination tool like Solibri or Navisworks.
A coordination platform built specifically around BCF issue exchange - rather than a full model-checking tool like Solibri or Navisworks, BIMcollab focuses on making the issue-tracking side of coordination smooth: creating, assigning, discussing, and closing BCF issues in a shared, structured workspace that plugs into Revit, Navisworks, Solibri, and most other major BIM tools.
It is a good example of how openBIM actually plays out day to day: a team can use completely different modeling software from each other and still coordinate cleanly, because the issue itself travels as a standard BCF file rather than being locked to one vendor's platform.
The label usually gets applied to marketing that claims "BIM Level 2" or "full BIM" compliance while the actual delivery is still 2D drawings with a token 3D model, or a firm that owns Revit licenses but never adopted the collaborative CDE, standards, and information-management processes that make BIM actually work.
Biodiversity Net Gain (BNG)
It's now mandatory for most new developments in England, using a standardized metric to score habitat value before and after - a young standard, but already as unavoidable in a planning application as an energy assessment.
On its own it knows nothing about walls or fire ratings - it's a general 3D tool, not a BIM authoring platform - which is exactly why an add-on like BonsaiBIM exists to bridge that gap.
Bluebeam Revu
Long before a design ever reaches the model in detail, plan reviewers, contractors, and clients mark up exported PDF sheets in Bluebeam with comments, clouds, and measurements - it's become the industry-standard review layer that sits on top of, not inside, the BIM authoring tools themselves.
Building Management System
The computer control system that actually operates a building's mechanical and electrical equipment day to day - HVAC, lighting, access control, sometimes fire and security systems - monitoring sensors and adjusting equipment automatically to keep the building running efficiently. Also called a BAS (Building Automation System) in some regions.
The BMS is where a building's 7D and AIM data becomes genuinely operational: equipment tags and system data captured in the model during design and handed over through COBie are exactly what a BMS needs configured correctly to actually control the right piece of equipment - a poorly handed-over model means a facilities team reprogramming and relabeling everything manually after move-in.
BonsaiBIM (formerly BlenderBIM)
Unlike Revit or ArchiCAD, which export to IFC as an afterthought, BonsaiBIM stores its data as IFC natively from the start - a genuinely different approach to what "open BIM" can mean in practice.
Bill of Quantities
Where QTO is the process of measuring quantities from a model, the Bill of Quantities is the resulting priced document contractors use to submit tenders and clients use to value work completed - BIM-derived BOQs update automatically as the design changes, instead of requiring a full manual re-measure.
Building Research Establishment Environmental Assessment Method
The UK-originated equivalent to LEED - a green-building assessment method (from BRE) covering energy, health and wellbeing, materials, waste, and land use, with ratings from Pass up to Outstanding. BREEAM dominates UK and many international projects the way LEED dominates North American ones, and the two are frequently mentioned together as the two most recognized systems worldwide.
Like LEED, BREEAM does not mandate BIM, but a well-modeled, data-rich project makes assembling the evidence a BREEAM assessment requires far faster than compiling it from scattered spreadsheets and drawings after the fact.
On a large project with hundreds of views, a well-set-up browser organization (grouped by discipline then phase, for example) is often the difference between finding the right view in seconds or scrolling through an unsorted list for a minute.
BS 1192:2007
The British Standard that predates even PAS 1192 - BS 1192:2007 introduced the collaborative, disciplined file-naming and layering conventions that later BIM standards inherited: a consistent naming code (project-originator-volume-level-type-role-number), and the idea of a shared, structured folder environment for a project team.
Most of what BS 1192 pioneered is now folded into ISO 19650's naming and CDE requirements, but the standard is still occasionally referenced directly, especially for its file-naming convention, which many UK and international offices still use as a base template.
BS 7671: Requirements for Electrical Installations (IET Wiring Regulations)
Cable sizing, circuit protection, and containment routing in an electrical Revit model all trace back to BS 7671 requirements - a model can look complete and still fail inspection if the underlying electrical design doesn't actually comply.
BS 8536: Design and Construction of Buildings and Infrastructure - Code of Practice for Facilities Management
BS 8536 pushes the facilities-management team's needs into the brief from day one - room adjacencies, maintenance access, and expected equipment lifespans are captured before design starts, rather than discovered as problems after the building is handed over.
Library objects for architecture, engineering and construction - Part 1: Identification and classification
It's the standard behind the idea of a permanent, structured object code - exactly the kind of naming discipline a well-run family library, including this site's own Revit family library, is built on.
buildingSMART Data Dictionary
It's the practical answer to the data dictionary problem at industry scale - rather than every country or software vendor defining "fire rating" its own way, bSDD gives IFC-based workflows a shared, queryable source for what a property actually means.
The full span a building exists across: brief and feasibility, design, construction, handover, operation - typically the longest phase by far - and eventually renovation, retrofit, or demolition. BIM's whole value proposition rests on this timeline: information created cheaply during design (changing a wall is trivial on screen) becomes exponentially more expensive to create or correct the later in the lifecycle you leave it, which is exactly why front-loading data quality is worth the extra effort.
The dimension stack (3D through 10D) essentially maps onto this lifecycle in order - geometry, time, and cost during delivery, then energy, facility management, and safety data carrying the project through decades of operation afterward.
Unlike a static O&M Manual delivered once at handover, a log book is meant to be a living document that gets updated as equipment is replaced or operating strategies change - a Soft Landings requirement that treats the building's documentation as something that ages with the building itself, not a one-time deliverable.
Building Performance Simulation (BPS)
Dedicated simulation tools pull geometry, materials, and location data out of Revit to test "what if" scenarios - window-to-wall ratio, shading depth, HVAC sizing - long before a single wall is built, and increasingly tie directly into embodied and operational carbon reporting.
Building Safety Act 2022
It's the legal source behind the golden thread and the building safety case requirements - not just recommended good practice, but a statutory duty with real legal consequences for getting it wrong.
A safety case has to be actively maintained and updated throughout occupation, not filed away once at completion - it relies directly on the Golden Thread of accurate, up-to-date building information staying connected to the physical asset for as long as the building exists.
It's a core soft landings deliverable - a building can be technically perfect and still perform badly if nobody who actually works in it understands how the heating controls or blinds are meant to be used.
"Built asset" is the vocabulary ISO 19650 uses for the actual structure once it exists, as distinct from the information models describing it. The term shows up throughout asset-management and handover discussions specifically to keep "the building" and "the model of the building" from being confused with each other.
A callout stays linked to its parent view - move a wall in the plan, and the callout's cropped detail view updates with it - which is what makes it the right tool for a wall-section detail or a stair detail, instead of drafting a disconnected duplicate view that would silently go out of sync.
It's the starting point for a walkthrough - a single static camera view is one frame; a walkthrough is a whole path of them animated together.
It's the practice of measurement that embodied carbon and whole-life carbon are the subjects of - without carbon accounting built into the model and the procurement process, a net-zero target stays a stated ambition rather than a tracked, verifiable number.
It's deliberately the last resort in most net-zero strategies - carbon accounting exists precisely to prove how much genuine reduction happened first, before offsetting is used to cover whatever's left.
A project can be profitable overall and still run out of cash mid-way through if payments and costs aren't timed properly - which is exactly the gap cash flow forecasting exists to catch before it becomes a crisis.
Category A and Category B Fit-Out
A landlord's model typically stops at Cat A, and the tenant's fit-out contractor picks up from there in their own Cat B model - meaning the two models need clean, well-defined interfaces (a shared coordinate system and a clear scope boundary) even though they're built at completely different times by completely different teams.
Revit Category
The highest level of Revit's element hierarchy: Category to Family to Type to Instance. Every element in a project belongs to exactly one category - Walls, Doors, Windows, Structural Columns, Mechanical Equipment - and the category controls fundamental behavior: which parameters are available, how the element schedules, what line weights and graphics it gets by default, and which views it shows up in.
Categories are fixed by Revit itself (you cannot invent a new one), which is exactly why they map so cleanly onto external classification systems like Uniclass or MasterFormat - they are the stable anchor point that makes automated classification and scheduling possible.
Common Data Environment
The single shared platform where all project information is stored, managed, and distributed. Instead of files flying around by email, everything lives in the CDE - models, drawings, documents, correspondence.
A CDE divides project information into four key zones:
| Zone | Who has access | What it contains |
|---|---|---|
| WIP (Work in Progress) | Creator only | Unfinished work not yet ready to share |
| Shared | Project team | Information approved for coordination |
| Published | Client & stakeholders | Formally issued deliverables |
| Archive | All | Superseded versions, kept for record |
The CDE is the backbone of ISO 19650-compliant BIM workflows.
Construction (Design and Management) Regulations
CDM shifts safety responsibility upstream - designers must actively design out foreseeable hazards (a difficult access route, a maintenance task requiring work at height) rather than leaving all risk mitigation to the contractor on site, and the Health and Safety File is the document that carries this information into operation.
When a Revit project uses worksets, one file is designated the central model - the authoritative version everyone's changes eventually flow into via Synchronize with Central. It should never be opened and edited directly; everyone works from their own local file instead.
It's the formal close-out of the defects liability period - the contractor's last remaining obligation before retention money is released in full. Without it, a client has no documented confirmation that the snagging list was actually cleared rather than just quietly ignored.
Civil Engineering Standard Method of Measurement, 4th edition
A quantity surveyor pricing a road or a bridge measures it against CESMM4; the same surveyor pricing a building measures it against NRM instead.
The formal process for handling a design change once a project is underway: proposing it, assessing its impact on cost, schedule, and other disciplines, getting it formally approved, and making sure everyone working from the model actually knows it happened. Without disciplined Change Management, a "small" change made by one team can silently break another team's coordinated work, since nothing forced the change to be reviewed or communicated before it landed in the shared model.
A well-run CDE supports change management directly: moving a changed element through WIP to Shared is itself a form of controlled, visible change, rather than an edit that just quietly appears in someone else's next model sync.
Where Change Management is the ongoing process of controlling and evaluating proposed changes, a Change Order is the specific, signed document that actually authorizes one - often triggered by a coordination clash or an RFI response that reveals the original design can't be built as documented.
Where V-Ray is built for high-quality offline stills, Vantage trades some of that fidelity for instant interactivity - closer in spirit to Enscape or Twinmotion than to its own sibling product.
Chartered Institution of Building Services Engineers
Its guides are to MEP engineers roughly what NRM is to quantity surveyors - a reference so widely adopted that a design brief referencing "CIBSE guidance" is usually understood without further explanation.
A design and construction philosophy focused on keeping materials in use for as long as possible - designing for disassembly rather than demolition, specifying reclaimed or recyclable materials, and treating a building's components as a future resource rather than eventual waste. It sits alongside embodied carbon reduction as one of the main levers for cutting a building's environmental footprint.
BIM supports circular-economy thinking in a very concrete way: a model with accurate material data becomes a material passport for the building - a record of exactly what is in the structure and where, making future disassembly, reuse, or recycling actually feasible instead of guesswork decades later.
Where IFC models a single building in rich detail, CityGML models an entire city more shallowly - the two meet in GIS-BIM integration work, each covering the scale the other doesn't.
Autodesk Civil 3D
Where Revit models the building, Civil 3D models everything around it - roads, drainage, earthworks, and utility networks - and the two share data (often via a shared coordinate system) so a building's foundation and grading design stay coordinated with the surrounding site plan.
The process of automatically identifying conflicts between elements in different discipline models. When the MEP engineer's duct runs through the structural engineer's beam, clash detection flags it - digitally, in the model - before it becomes a costly problem on site.
Clash detection is run in tools like Autodesk Navisworks or Solibri. There are three types:
Uniclass / OmniClass
For information to be usable across organizations, elements need a shared cataloguing language. Uniclass (UK) and OmniClass (North America) are hierarchical classification systems that give every component, system and activity a standard code - from a single door to an entire project stage.
The codes live as parameters on elements and enable consistent quantities, specifications and information requirements across all parties. You will meet them mostly on international projects and in the EIRs of large clients.
It replaces the old requirement of a Revit Server or shared office network with the same synchronize-with-central workflow teams already know - the meaningful difference is where the central model physically lives, not how users actually work with it day to day.
It's a common feature of integrated project delivery and other collaborative delivery models - a clash resolved in a five-minute conversation across a shared desk instead of a week of emails between separate offices is exactly the benefit co-location is meant to capture.
Construction Operations Building Information Exchange
A structured data format for handing over asset information from the construction team to the facility management team at project completion. COBie is typically delivered as a spreadsheet and contains every piece of information a building operator needs: spaces, systems, equipment, maintenance schedules, warranties, and spare parts.
COBie is how the 7D dimension actually gets delivered in practice.
Digital permitting is this idea taken all the way to the regulator's own desk; most projects still run a version of it privately first, using IDS-style rules to catch violations before submission.
Where a BIM protocol is a standard template of clauses, a collaboration agreement is the actual signed document for a specific project, naming the real parties and their real obligations.
Without a collateral warranty, a building's future owner or lender would have no direct contractual right to sue the original architect or contractor if a defect appears - this is the legal document that gives them standing, separate from the main construction contract and separate from a product Warranty covering physical materials.
It's a distinct feature from a general legend view - the color scheme is defined once against a parameter (like department name) and every room tagged with that value picks up its color and its entry in the legend automatically.
A commissioning agent runs HVAC, electrical, and life-safety systems through their real operating conditions - not just checking they're installed, but that they perform to spec - and the results feed directly into the O&M Manual and the facilities-management team's baseline for what "working correctly" looks like.
It's what a client should actually expect to see before switching on a building's systems for real occupants - not just a contractor's word that testing happened.
It schedules which system gets tested when and by whom, feeding directly into the commissioning certificate issued once every test has actually passed.
NEC contracts list exactly which events qualify (a change instructed by the client, an unforeseen physical condition, and others), and require them to be assessed and priced quickly - a structured alternative to the more open-ended change order and claim processes used elsewhere.
Editing a wall type's compound structure is how a modeler defines what it's actually made of layer by layer - which is what drives its fire rating, thermal performance, and the material quantities that flow into schedules, rather than the wall just being a single generic slab with no real construction logic behind it.
Massing
A simplified, freeform 3D shape used in Revit's conceptual design environment to explore a building's overall form and massing - footprint, height, setbacks - before committing to real walls, floors, or roofs. Faces of a mass can be converted directly into actual building elements once the form is settled, so early massing work is not thrown away, it becomes the starting geometry for the real model.
Massing is also where a lot of early 6D analysis happens - solar studies, floor-area calculations, shadow studies - because it lets a design team test many volumetric options quickly, before the cost of full detailed modeling makes changes expensive.
It's one of the most litigated topics in construction contract disputes - an extension of time claim gets genuinely complicated when both sides can point to a real delay happening on the exact same days.
BIM's shared model and worksharing make concurrent engineering practical: architects, structural engineers, and MEP teams can develop their own disciplines simultaneously on linked or worksets-based models, catching conflicts early through regular clash detection instead of discovering them at the end of a traditional, sequential handoff chain.
It's often the first real step on a retrofit or refurbishment project - and increasingly done via a laser scan feeding straight into a scan-to-BIM model rather than a hand-drawn sketch.
It's what lets Revit auto-route a duct or pipe run and validate that a system is actually continuous - two elements that look connected in a view but don't share an actual connector aren't really joined at all.
It scores things a building's own quality plan doesn't cover at all - noise, site tidiness, how workers are treated - a reputational layer sitting alongside the purely technical compliance checks.
Constructability Review
How practical and buildable a design actually is in the real world - whether a detail can physically be assembled in the sequence intended, whether a component can fit through the access route it needs to reach its final position, whether the design assumes tolerances the trades on site can actually achieve. A formal Constructability Review brings contractor and trade expertise into the design process early, specifically to catch these problems on screen instead of on site.
Clash detection catches whether two elements physically overlap; constructability review catches the broader, harder question of whether a design that has zero geometric clashes can still actually, practically be built the way it was drawn.
Constructability itself is the general quality a design either has or lacks; a constructability review is the specific, scheduled meeting where someone actually checks for it before it's too late to change.
Housing Grants, Construction and Regeneration Act 1996
It's the legal foundation adjudication actually rests on - without it, the fast, statutory dispute route construction relies on so heavily wouldn't exist as a legal right at all.
Written by the principal contractor before work starts and kept live throughout the build, it covers site rules, welfare arrangements, and how specific risks identified in the design will actually be controlled in practice. It's a legal requirement on UK projects of any real size, not an optional add-on.
Without it, a lump-sum contract is a single number with no way to check progress payments against actual work completed - the contract sum analysis is what a quantity surveyor values interim certificates against.
Contractor's Design Portion (CDP)
It's a common middle ground between the two extremes - the client's team retains design control over most of the building, while handing the specialist parts to whoever is actually best placed to design them.
A structural engineer commonly uses Copy/Monitor to bring the architect's grids and levels into their own model rather than redrawing them by hand - and if the architect later shifts a level's elevation, Revit flags the discrepancy automatically instead of the two models silently drifting apart.
It's Chaos's more approachable sibling to V-Ray - fewer settings to tune, at some cost to the fine-grained control V-Ray offers to experienced visualization artists.
An early-stage cost plan might be a single per-square-meter figure; by the time it reaches a contract sum analysis it's broken down element by element - the same document maturing alongside the design.
A quantity surveyor links CostX directly to the Revit model (or an exported IFC file) so measured quantities update automatically as the design changes, instead of manually re-measuring drawings every time a revision comes through - the same underlying goal as Assemble Systems, from a cost-estimating-first rather than model-coordination-first tool.
Critical Path Method (CPM)
Everything on the critical path matters for the finish date; everything off it has some slack - which is exactly why a good project manager watches the critical path far more closely than the rest of the schedule.
Shrinking a floor plan's crop region to just the area a sheet needs, rather than showing the entire model at that scale, is one of the most basic ways a Revit user controls what actually prints on a drawing sheet.
Construction Skills Certification Scheme
It's a practical, everyday gatekeeper - a site's security gate checks it before anyone gets in, regardless of how good their actual work is.
Instead of a uniform wall assembly, a Curtain Wall is defined by a grid pattern that divides it into panels (usually glass, but swappable to solid or louvered), with mullions running along the grid lines - making it the go-to system for anything from a single shopfront to a full glazed office tower facade.
It's the counterpart to Join Geometry for elements that need to pass through each other rather than merge - without it, a duct routed through a wall would just show as a solid block colliding with it.
Set it too low on a floor plan and a low window sill won't show as cut; set it too high and it might cut through a door head instead of the wall below it - it's the specific value inside view range most plan-reading confusion actually traces back to.
It competes directly in the same space as Enscape, Lumion, and Twinmotion - real-time visualization tools built to sit alongside an authoring model rather than replace it.
Without a shared data dictionary, one tool's "FireRating" and another's "Fire_Rating_Class" describe the same property under two different names, breaking any automated check or handover. buildingSMART's own bSDD is the best-known public example, mapping classification systems like Uniclass and OmniClass to a single online reference.
A term from the PAS 1192 / ISO 19650 world for a scheduled point in a project where a specific, pre-agreed set of information must be delivered into the CDE - not a vague "send it when it's ready," but a fixed milestone tied to the project's MIDP. Missing a data drop is treated the same as missing any other contractual deadline.
Data drops are what make the MIDP and TIDP more than a theoretical schedule - they are the concrete checkpoints a project team is actually held to, usually aligned with major project stages like the end of a design phase or a construction milestone.
The right granularity depends on who's asking - an FM team tracking filter changes needs duct-level detail, while a portfolio cost report is better served by a system-level rollup. LOD is granularity applied to geometry; this is the same idea applied to data.
If a room's fire rating changes three times across design, construction, and handover, data lineage is what lets someone trace it back to figure out which change was correct and who made it.
Switching FM software, or moving a legacy asset register into a new AIM, is a data migration project in its own right - and exactly where poor data quality upstream turns into a very expensive cleanup job.
Without clear contract language, a client can be left legally unable to update or even fully access the model they paid for, which is exactly why modern appointment documents (like a BEP) spell out data ownership and licensing terms as explicitly as they spell out fees and deliverables.
A perfectly modeled door with a blank fire-rating field has excellent geometry and poor data quality - exactly the kind of gap model quality review and data validation checks exist to catch.
A data dictionary or a shared classification system like Uniclass are the tools; data standardization is the ongoing discipline of actually enforcing them project after project, not just publishing them once.
Instead of every manufacturer or modeler inventing their own property names for, say, a fire door, a data template (like the UK's NBS BIM object standard) fixes the exact parameters, units, and value types expected - which is what makes data genuinely interoperable and searchable across projects and software, not just geometrically compatible.
Instead of a human manually checking that every door in a submission has a fire-rating parameter filled in, a validation tool applies an IDS ruleset (or a similar checker) automatically, rejecting or flagging any element that doesn't meet the agreed information requirements before it ever reaches the shared model.
It runs on the same model geometry sun-path studies use, but focuses on interior comfort metrics rather than just tracking where shadows fall outside.
It's demolition planning's circular-economy-minded sibling - slower and more expensive up front, but exactly what makes material passporting and reverse logistics worthwhile downstream.
Snags logged during this period get tracked the same way as pre-handover issues - often against the same model elements - and clearing them all is usually the condition for releasing retention money withheld from the contractor's final payment.
An asbestos register and a condition survey both usually come before demolition planning starts, since what's actually in a building changes how it can safely be taken apart.
A plain "Duplicate" copy is a completely independent view; a dependent view stays tied to its parent, which is exactly what's needed when the same large floor plan has to appear split across matchlines on multiple sheets.
It's the narrative that justifies the drawings - explaining why a building looks and sits the way it does, not just showing that it does.
Because one party controls both design and construction, Design and Build tends to concentrate BIM decision-making and risk with the contractor - a sharp contrast to Design-Bid-Build, where the client's own design team and a separately-appointed contractor have to coordinate across an organizational boundary that Design and Build largely removes.
A generous floor-to-floor height and a structural grid that doesn't fight future partition walls are both design-for-adaptability decisions - cheap to make at design stage, expensive to retrofit later.
It's the design-stage half of the CDM Regulations' logic - a designer choosing a lighter cladding panel that two people can lift safely, instead of one requiring a crane and a higher-risk lift, is design for safety in practice.
Without a design freeze, downstream teams - fabricators, cost estimators, structural engineers running analysis - are always working against a moving target. Freezing a defined package (say, the building envelope) at an agreed LOD lets those teams commit resources without redoing work every time someone tweaks a wall.
Revit's built-in tool for exploring several design alternatives - different lobby layouts, different facade treatments - inside a single project file, without duplicating the whole model. Elements get assigned to an Option Set (a group of mutually exclusive choices) and a specific Option within it; the rest of the model, outside any option set, stays the shared "main model" that every option shares.
This is genuinely different from comparing full design alternatives in generative or computational workflows - Design Options is specifically Revit's own, file-internal mechanism, mainly used for short-lived, small-scale comparisons during design development rather than large parallel-scheme studies.
Increasingly run inside a common data environment or a viewer like Navisworks or BIM 360/ACC rather than around a printed drawing, a design review lets every discipline see the same federated model at once and log issues (often as BCF files) directly against the elements causing them.
Because the design and construction teams are separate organizations under Design-Bid-Build, model handover between them has to be explicit and well-documented (clear EIR/BEP requirements matter more here) rather than assumed - unlike Design and Build, where design and construction responsibility already sit inside one contract.
Where a Filled Region just fills a shape with a hatch pattern, a Detail Component is a genuine reusable family with its own geometry and behavior (it can flex, array, and carry parameters) - the right tool for anything that needs to repeat identically across many detail drawings, like a run of insulation or a standard flashing profile.
A repeated typical detail - dimensions, tags, and 2D linework around a recurring construction condition - is a natural fit for a detail group, kept separate from the 3D model groups used for repeated physical assemblies.
Coarse, Medium, Fine
One of the most commonly confused terms for anyone who has also learned LOD - and they are genuinely different things. Detail Level (Coarse, Medium, or Fine) is a per-view Revit display setting that controls how much graphical detail an element shows: a wall at Coarse might draw as a single line, the same wall at Fine shows every layer of its construction.
LOD describes how reliable and developed the underlying model data is - a real, project-wide, cross-software concept. Detail Level is purely about how that same element is drawn on screen in one particular view, and has no bearing on the model's actual information content. A wall can carry full LOD 350 data and still display at Coarse detail in a small-scale site plan.
Design for Manufacture & Assembly
The approach behind the 10D dimension. Instead of designing a building and then figuring out how to build it, you design for off-site manufacturing from the start: modular elements, prefabricated MEP racks, ready-made bathroom pods - factory-produced to high precision and rapidly assembled on site.
BIM is a precondition here: the model must reach fabrication-level accuracy (LOD 400) so the factory can work directly from it.
Design (MicroStation native format)
On infrastructure-heavy projects (rail, highways, utilities) it's common to find DGN files alongside RVT and DWG ones, since Bentley's tools are especially strong in that sector - IFC is usually the neutral bridge between the two ecosystems.
A CDE is the practical tool that implements digital asset management on a project; the discipline itself is broader, covering everything from naming conventions to who's allowed to overwrite which file.
It's the practical, project-delivery-focused follow-up to policy documents like the Golden Thread requirements - less a technical standard like ISO 19650 and more a playbook of recommended practices (twin models, platform approaches, manufacturing-led design) that public clients increasingly reference in their own requirements.
Interoperability solves "can Software A read Software B's file today," while digital continuity solves the harder problem of "will this asset information still be usable in 20 years, after the software that created it is gone." It's why long-lived asset owners increasingly prefer open, well-documented formats (IFC, COBie) over proprietary ones for anything meant to outlive the current toolchain.
It's the broader philosophy ISO 19650, the AIM, and the golden thread all serve - a building's information staying accurate, structured, and accessible for decades, not just accurate enough to get through handover.
Common in infrastructure and government contexts (especially Australia, the UK, and increasingly used alongside BIM in buildings too), Digital Engineering treats the model as just one part of a wider digital ecosystem that includes GIS, sensor data, simulation, and analytics. In practice, most organizations use "Digital Engineering" and "BIM" close to interchangeably, with DE emphasizing the engineering-data pipeline over the modeling software.
It's what makes DfMA actually work in practice - the model has to be accurate enough (typically LOD 400) that a factory machine can cut, mill, or print directly from it with no human re-drawing step in between.
Singapore's CORENET and several US and EU pilot programs already automate parts of plan checking this way - reading rule-based checks (like fire egress distances or accessibility clearances) straight out of the model's own data instead of a human reviewer measuring a PDF by hand.
A 4D sequence walkthrough, a crane-lift simulation, or a virtual commissioning run-through are all forms of digital rehearsal - catching a clash of trades, a blocked access route, or a startup-sequence error on screen instead of on site, where fixing it costs far more.
It matters most when a dispute happens months later - a searchable, time-stamped digital record is far harder to challenge than someone's memory of what a handwritten diary said.
A digital thread means every piece of information - from an early design decision to a sensor reading on an installed asset years later - stays linked and traceable back to its source, instead of getting recreated or lost at each project handover. It's the connective tissue that lets a digital twin actually reflect reality, rather than being a one-off snapshot.
A live virtual replica of a physical building, continuously updated with real-world data from IoT sensors and building management systems. Unlike a static BIM model, a Digital Twin evolves after handover - tracking energy use, equipment health, occupancy patterns, and maintenance needs in real time.
Digital Twins are the endpoint of the BIM lifecycle: the model doesn't get archived when the building opens. It becomes the operational intelligence platform for the building's entire lifespan.
A model or survey documenting the space's condition at lease start versus lease end is the practical evidence behind a dilapidations claim - the same reality-capture and scan-to-BIM techniques used for new-building as-built surveys apply here too, just at the other end of the tenancy.
Adding or removing a witness line from an existing dimension string automatically keeps every other segment aligned - manually placing the same number of separate dimensions almost never lines up as cleanly.
Digital Plan of Work
Where a traditional plan of work is a document, a Digital Plan of Work is structured data - it ties each project stage (see RIBA Plan of Work) to defined data drops, responsibilities, and classification, so software tools can track what's due, from whom, and when, rather than a project team tracking it manually in a spreadsheet.
A standard flashing detail that applies the same way on every project is a natural fit here - unlike a callout view, it never updates from the model because it was never linked to it in the first place.
It's often the fastest way to feed photogrammetry with the volume of overlapping images it needs, especially across a large or hard-to-access site.
Design Web Format XPS
It's Autodesk's answer to a universal, view-and-markup-only export - much smaller than a native RVT or DWG, viewable in free tools, and unable to be edited back into the source model. Useful for review packages sent to people who don't need (or shouldn't have) editing access.
The native binary file format of AutoCAD, and by extension one of the most common formats for exchanging 2D drawing information in construction, even in a BIM-heavy project. Revit can export sheets and views to DWG for consultants who still work in 2D CAD, or to satisfy a contract requirement for DWG deliverables.
DWG is not a BIM format - it carries lines, arcs, and blocks, not parametric elements or rich data - so exporting to DWG is effectively a step down in information richness. It remains essential in practice because plenty of contractors, authorities, and sub-consultants still expect drawings in DWG rather than IFC.
Drawing Exchange Format
Because DXF's structure is openly published and text-readable, it's the safer choice when exchanging 2D drawing data with software that may not perfectly support DWG's proprietary binary format - at the cost of larger file sizes and occasional loss of some DWG-specific formatting.
Computational Design
Stop doing by hand what a computer does better. Computational design defines geometry and data through logic and rules instead of clicks - Dynamo is the visual-programming tool of the Revit world (with Python or C# via the API for advanced users). Everyday uses: renaming hundreds of sheets at once, automated QA/QC checks, filling parameters from an Excel table.
Generative design takes it one step further - the computer proposes and evaluates dozens of alternatives against goals you define.
It sits at roughly the same level as Grasshopper does for Rhino - dragging and connecting nodes instead of writing scripts - and can read and write Revit parameters directly, making it a common bridge between generative design workflows and a live Revit model.
Before E57, every scanner manufacturer had its own proprietary point cloud format, making it hard to move a scan between different reality capture and BIM tools. It's now the closest thing the scan-to-BIM workflow has to a common exchange standard, alongside LAS for airborne and mobile LiDAR data.
Early Contractor Involvement (ECI)
ECI tries to capture some of Design and Build's early buildability input while keeping the client's own design team in control - the contractor reviews the developing model, flags constructability issues (see Constructability) early, and often firms up pricing before the client commits to a fixed-price contract.
It's built into the NEC contract's collaborative philosophy - flagging a problem the moment it's spotted, before it becomes a compensation event, gives both parties a chance to jointly manage it down instead of arguing about it after the fact.
Earned Value Management (EVM)
It answers a sharper question than "are we on budget" - by comparing planned value, earned value, and actual cost together, it shows whether a project is both on schedule and on budget, or drifting on one while looking fine on the other.
If a modeler needs to edit an element someone else already owns, Revit sends that person an editing request they can grant or deny - a lightweight negotiation layer that lets a large team work on the same central model simultaneously without constantly locking each other out.
Employer's Information Requirements
The document that starts every BIM project. The EIR is written by the client (employer) and defines exactly what information they need from the project team - in what format, to what level of detail, and at which project milestones.
Think of it as the client's BIM brief. It covers:
Everything in the BIM workflow flows from the EIR.
Without assigning devices to a circuit, Revit has no way to generate a panel schedule - it's the invisible link that turns a scattered set of light fixtures into an actual electrical system on paper.
The carbon emissions associated with a building's materials and construction process - extracting raw materials, manufacturing products, transporting them, and the construction work itself - as distinct from operational carbon, which comes from running the finished building. For a highly efficient modern building, embodied carbon can represent a larger share of lifetime emissions than operational carbon, simply because operational energy use has fallen so much.
A BIM model with accurate material quantities and types is the practical foundation for calculating embodied carbon: multiply each material's quantity (extracted the same way as any QTO) by its published carbon factor, and the total becomes a genuine design decision input rather than a guess made after the fact.
Execution of steel structures and aluminium structures
A steel fabricator without EN 1090 certification simply can't legally supply structural steel into the European market - it's a hard compliance gate, not a voluntary quality mark.
Sustainability of construction works - Assessment of environmental performance of buildings
It's the formal methodology behind a life cycle assessment - the standard that defines exactly which life cycle stages and impact categories a whole-life carbon figure actually has to account for.
Energy performance of buildings - Ventilation for buildings
CIBSE guidance in the UK and EN 16798 across Europe cover much of the same indoor-environmental-quality ground, from two different institutional directions.
It feeds directly into building performance simulation tools like IES-VE or Autodesk Insight - a full architectural model has far more geometric detail than an energy simulation actually needs or can efficiently process.
Energy Performance Certificate (EPC)
Unlike BREEAM, LEED, or Passivhaus, which are voluntary certifications a client chooses to pursue, an EPC is often a hard legal requirement - and the same energy model or building performance simulation data used to chase a voluntary certification typically produces the EPC rating as a byproduct.
A real-time rendering plugin that runs directly inside Revit (and several other BIM tools), turning the model into a walkable, photorealistic 3D scene almost instantly - no separate export, no waiting for a render to finish. As you edit the model, the Enscape view updates live alongside it.
Its main value is communication: a client or contractor who cannot read a floor plan can walk through an Enscape view of the same design and understand it immediately. It has become close to a default expectation on client-facing Revit projects, the same way a rendered visual used to be a special, separately-commissioned deliverable.
It sits alongside the site waste management plan as one of the two environmental documents most planning approvals now condition on.
Environmental, Social, and Governance Reporting
A property company reporting embodied and operational carbon across dozens of buildings to investors or regulators increasingly pulls that data straight from each building's Asset Information Model rather than commissioning a separate audit - another reason accurate, structured model data keeps paying off long after handover.
Eurocodes - European structural design standards
Eurocode 1 defines the loads, Eurocode 8 covers seismic design, and so on - a structural engineer sets up load combinations in a tool like Robot Structural Analysis according to whichever code governs the project's jurisdiction, Eurocode being the most common outside North America.
Extension of Time (EOT)
A well-documented model and schedule history is exactly what an EOT claim needs to prove its case - showing precisely when a design change or a late information delivery actually pushed back the construction sequence, rather than the delay being the contractor's own fault.
A generic duct family is fine for design coordination; fabrication parts carry the real manufacturer data needed for digital fabrication, feeding straight into a factory's cutting and assembly process.
BIM's usefulness doesn't end at handover - a well-structured Asset Information Model, populated via COBie or similar, feeds directly into facilities management software so building owners can track assets, plan maintenance, and manage space without re-surveying the building. It's the single biggest reason large owners mandate BIM on their projects in the first place.
Revit Families
Not an industry-wide BIM term, but the one every Revit user lives inside. A family is a parametric component definition - a door, a column, a light fixture - with types (predefined size and property combinations) and instances (the actual placed elements).
Revit has three kinds: system families (walls, floors, roofs - built into the project), loadable families (.rfa files you create or download), and in-place families (one-off elements modeled directly in the project). Mastering families is the single biggest step from "using Revit" to "controlling Revit".
The separate modeling environment inside Revit - opened by editing a family rather than a project - where Families actually get built: reference planes and lines first, then parametric geometry, types, and formulas layered on top. It looks similar to the main project environment but behaves differently in important ways, most notably that a family file has no worksharing and is designed to be flexed and tested in isolation before being loaded into a real project.
Comfort in the Family Editor is usually the clearest dividing line between someone who "uses" Revit and someone who can genuinely solve problems in it - most everyday frustrations with a missing or wrong component get fixed here, not in the project file.
It's the family-editor-level counterpart to project and shared parameters - a door family's own "panel width" formula is a family parameter, and it stays invisible to schedules and tags outside that family until it's promoted to a shared one.
Picking "Door" as a family template pre-wires wall-hosting behavior and standard door parameters, while picking "Generic Model face-based" sets up something that can attach to any surface - choosing the wrong family template at the start is one of the most common reasons a custom family behaves unexpectedly later.
Which one a survey team uses usually just comes down to which brand of scanner they bought - the two ecosystems solve the same registration problem in largely the same way.
Filmbox (FBX) file format
Revit can export directly to FBX, which is the format most visualization and game-engine tools (like Unreal Engine or Twinmotion in some pipelines) expect as input - useful when a model needs to go beyond a still rendering into an interactive walkthrough or VR experience.
A combined model made up of separate discipline models linked together - the architect's model, the structural engineer's model, and the MEP engineer's model all viewed simultaneously. Nobody works in the same file; instead, each team works in their own model and the federated model is assembled for coordination reviews.
Federated models are used to run clash detection and to give all stakeholders a complete picture of the building.
Also called a volume strategy, it sets out how models are segregated - typically by building, zone, and discipline - so multiple teams can model simultaneously without file-size or coordination problems, and then defines the hierarchy for linking those pieces back into federated models, up to a single master federated model for the whole project. Usually documented as part of the BIM Execution Plan.
International Federation of Consulting Engineers - standard contract forms
Each FIDIC "book" fits a different procurement model - the Red Book suits traditional Design-Bid-Build with an employer-designed project, the Yellow Book suits Design and Build, and the Silver Book suits EPC/turnkey projects - so which one a contract references says a lot about who carries design risk before a single clause is even read.
FIDIC Conditions of Contract for Construction
It's the FIDIC equivalent of a traditional design-bid-build split - the Yellow Book, by contrast, is FIDIC's form for design-and-build-style contracts where the contractor designs too.
A filled region only exists in the view it was drawn in - it has no real-world thickness or 3D presence - which makes it the right tool for things like poché, paving patterns on a plan, or a highlighted zone that shouldn't affect quantities or schedules the way an actual model element would.
Agreeing the final account is often the slowest part of closing a project out - every change order, extension of time, and loss-and-expense claim has to be reconciled against the original contract sum before either party signs off.
Finite Element Analysis (FEA)
A structural engineer takes the analytical model (see Structural Analytical Model) out of Revit into a dedicated FEA tool like Robot Structural Analysis, which subdivides members into a mesh of small elements and solves the physics for each one - the standard method behind every modern load case, deflection, and code-compliance check.
It's a live, building-specific document rather than a one-off design check - and for higher-risk buildings, it now has to stay current as part of the golden thread.
For higher-risk buildings this feeds directly into the golden thread and the building safety case - fire safety information can't be a static PDF handed over once, it has to stay accurate as the building changes over its whole life.
Regulatory Reform (Fire Safety) Order 2005
It's the legal requirement that makes a fire risk assessment mandatory rather than optional - the Building Safety Act added a further layer of duties on top of it specifically for higher-risk buildings.
It's positioned as the more accessible alternative to WELL - less exhaustive documentation, but covering much of the same ground around light, air, and occupant comfort.
A door family's frame width might be written as a formula referencing the door's overall width plus a fixed offset, so changing one dimension automatically updates the other - the mechanism that makes a well-built parametric family flex correctly instead of breaking when a user changes an unexpected value.
Common in public-sector work, a framework establishes standard rates and BIM/information requirements once, then individual projects ("call-offs") are awarded quickly against it - meaning a firm's BIM standards and templates need to be consistent enough to serve many different projects drawn from the same framework, not tailored to just one.
It's a smaller, less mature project than Revit or ArchiCAD, but it's a real, actively developed part of the same open-source push toward openBIM as BonsaiBIM.
Fuzor sits at the intersection of visualization and scheduling - a project team can walk through the model in VR while simultaneously scrubbing through the construction timeline, which makes it a popular choice for site logistics planning and stakeholder presentations that need to show both "what it looks like" and "when it happens" together.
You define the inputs (say, a site boundary and a program of rooms), the goals (maximize daylight, minimize travel distance), and the constraints, and generative design produces a range of viable layouts ranked against those goals - letting a team explore far more options than manual iteration would allow. It builds on the same underlying computational-design engine as Dynamo, but is packaged as a guided, goal-driven workflow rather than open-ended visual scripting.
Shared Site
Setting a project's true real-world position - latitude, longitude, and true north - so the model sits correctly on a map and its solar and shadow studies calculate accurately for its actual location. Revit's Shared Site feature lets multiple linked projects agree on one common real-world anchor, which matters on large multi-building sites or infrastructure projects spanning a wide area.
Geolocation and shared coordinates solve related but different problems: shared coordinates get models to agree with each other, geolocation gets the whole project to agree with the real planet - both need to be right for a model's sun studies, site context, and GIS integration to actually mean anything.
Every BIM element carries two kinds of information side by side: geometric data (its 3D shape and location) and non-geometric data (everything else - manufacturer, fire rating, cost code). A model can look complete geometrically while its non-geometric data is still empty, which is exactly the gap an EIR is written to close.
Greenhouse Gas Protocol
Its Scope 1/2/3 split is what most net-zero targets and carbon accounting systems in construction are actually built around, even when the project itself never names the protocol directly.
A single building's BIM model is precise but zoomed-in; a city's GIS layer is broad but shallow on detail - integrating the two lets a utility company, for instance, see exactly which pipe inside which building connects to which street-level main.
Named, reusable values (a length, an angle, a number, a yes or no) that live at the project level rather than inside a single family, and can be used to drive dimensions, constraints, and formulas anywhere in the model. Setting a "Standard Corridor Width" as a Global Parameter and tying every corridor dimension to it means changing the office standard once updates every corridor in the project instantly, instead of hunting down each one manually.
They are a lightweight entry point into the same "define it once, drive everything from it" thinking that parametric modeling and shared parameters are built on, without needing a Dynamo graph to set up.
GL Transmission Format
An open, royalty-free 3D file format (maintained by the Khronos Group) designed specifically to load fast in web browsers, game engines, and AR/VR applications - which IFC was never built for. glTF strips a model down to lightweight geometry, materials, and textures, dropping the rich parametric and classification data that IFC carries.
In a BIM workflow, glTF is typically an export target at the end of the pipeline: a coordinated federated model gets converted to glTF so a client or site team can view it smoothly on a phone or in a VR headset, without needing heavyweight BIM software.
A term that entered BIM vocabulary through UK building-safety reform (following the Grenfell Tower inquiry): the Golden Thread is the requirement that safety-critical information about a building - fire strategy, structural design, materials, later changes - stays accurate, accessible, and unbroken from design through construction and for the entire life of the building.
It is less a specific document than a principle: information created during design must not get lost or become out of date by the time a building is occupied. BIM and a well-run CDE are the practical tools that make a Golden Thread achievable - a spreadsheet in someone's inbox is not.
Like Dynamo for Revit, Grasshopper lets designers wire together nodes instead of writing code to generate and control complex geometry - facades, structural optimization, form-finding - parametrically. It's especially dominant in early-stage conceptual design and competition work, where Rhino's freeform modeling is often preferred to Revit's more constrained tools.
Like a level, it's a datum that only needs to be placed once and stays consistent everywhere - structural engineers in particular navigate a drawing set almost entirely by grid references rather than by room names.
Guaranteed Maximum Price (GMP)
It shifts cost-overrun risk onto the contractor while still letting the client benefit if the actual cost comes in under the ceiling - a middle ground between a fixed lump sum and open-book cost-reimbursable contracts.
Handback is essentially the mirror image of the original handover - instead of a new asset moving from contractor to client, an already-occupied one moves from tenant back to landlord, and disputes over the space's condition at that point are exactly what Dilapidations claims are about.
The point where a project stops being a construction job and becomes an operating building: possession, and the associated information, formally transfers from the delivery team to the client or operator. In a BIM-driven project, handover is not just keys and a certificate - it is when the relevant parts of the PIM get filtered and delivered as the AIM, often packaged as COBie data, alongside warranties, manuals, and as-built records.
A handover that goes badly usually traces back to a poorly defined AIR at the start of the project - if nobody specified early on exactly what data the operator needed, there is no reliable way to assemble it under deadline pressure at the end.
It's the last line of defense against the common failure mode where a client discovers, months later, that some promised document was never actually handed over.
The checklist is the verification tool; the handover pack is the physical or digital thing being verified - an O&M manual, a building user guide, and a commissioning certificate are typical contents.
A building user guide is the reference document; handover training is the live session that actually makes sure someone read and understood it before the design team walks away.
Hazards that were designed out get recorded here too - if a structural element contains asbestos, or a roof has no permanent fall-arrest anchor points, this is the document that has to say so, following that information from design through the entire operational life of the building.
A door family is host-based on a wall (delete the wall and the door goes with it), while a face-based family can attach to any suitable surface, and a stand-alone family - like most furniture - needs no host at all. Choosing the right hosting behavior when building a custom family in the Family Editor determines how forgiving it is to place and move later.
Health and Safety Executive
It's the body that can actually stop work on a site or prosecute a contractor over a health-and-safety breach - the CDM Regulations are the rules; the HSE is who enforces them.
Editing hundreds of door numbers or room names one by one inside Revit is slow and error-prone - Ideate BIMLink pulls that data into a familiar spreadsheet, where find-and-replace and formulas make bulk changes fast, then pushes the results back without anyone touching the model elements directly.
Information Delivery Specification
buildingSMART's youngest standard, turning information requirements from Word documents into a machine-readable file. Instead of writing "every door must have a fire rating", an IDS file defines the requirement in a form software can check automatically against the IFC model - flagging every element that fails.
In practice: fewer arguments about "what was required", and quality control that becomes an automated report instead of a manual review.
Integrated Environmental Solutions Virtual Environment
Where a quick Revit-native check answers "roughly how much energy will this use," IES-VE is built for the detailed, standards-compliant modeling a certification body or building regulator actually requires - geometry usually gets exported or linked from Revit rather than modeled a second time from scratch.
Industry Foundation Classes
The open standard file format for exchanging BIM data between different software platforms. IFC allows an architect working in Revit to send a model to a structural engineer working in Tekla or a contractor working in Navisworks - without losing information.
IFC is maintained by buildingSMART International and is the backbone of open BIM - the principle that BIM workflows should not be locked to any single vendor's software ecosystem.
Industry Foundation Classes 4.3
Before 4.3, exchanging infrastructure data as open BIM meant stretching a buildings-focused schema to fit a road or a bridge; 4.3 gives alignments, road, rail, and other infrastructure disciplines their own proper IFC entities instead.
Issued For Construction Drawings
The formal issue status marking a drawing as released to the contractor and site team as the authoritative version to build from - as opposed to earlier statuses like For Review or For Coordination, which are for internal checking only and were never meant to leave the design team's hands.
IFC drawings move through the same CDE approval gate as AFC Drawings, and on many projects the two labels describe the same milestone from two angles - IFC is what the site team sees stamped on the sheet, AFC is what the design team's issue tracking log calls the approval event. When a later revision supersedes an IFC set, the superseded drawings must be marked void immediately, since a subcontractor working from a stale IFC sheet is one of the most common, and costly, coordination failures on site.
The current major release of IFC, superseding the long-dominant IFC2x3 version. IFC4 added support for richer parametric relationships, better structural analysis data, infrastructure elements, and tighter alignment with openBIM workflows. In practice, IFC2x3 is still widely requested on many projects simply out of software-compatibility habit, so it is common to see an EIR specify exactly which IFC version - 2x3 or 4 - a project must use, since the two are not fully interchangeable.
Knowing to ask "which IFC version?" rather than assuming "IFC" means one single thing is a small detail that saves real coordination headaches.
Most users never touch it directly - it's the underlying library developers build on, the same way a website's code depends on libraries a visitor never sees.
An imported DWG or model is frozen the moment it's brought in - if the source file changes, nothing updates - while a Linked Model stays connected and refreshes automatically, which is why Linked Models are the standard for ongoing multi-discipline coordination, and importing is generally reserved for one-off reference geometry that will never need to update.
In-Place Family / Model In-Place
An in-place model is quick to create but comes with real costs: it can't be shared or reused across projects, it tends to bloat file size more than an equivalent Family, and it doesn't flex the same way through Family Editor parameters - appropriate for a genuinely one-off sculptural element, but a common sign of a rushed workflow when used for anything repeatable.
Rather than talking about "files" or "drawings" specifically, ISO 19650 uses "information container" as a vendor- and format-neutral label for any single piece of managed project information, so the same rules (naming, status, revision, approval) apply consistently whether the container is a Revit model, a PDF, or a spreadsheet.
A tender submission, a stage-gate deliverable, and a final handover package are all information exchanges - not casual file-sharing, but a defined, checked, and recorded event. ISO 19650's whole CDE workflow exists to make each exchange auditable: who submitted what, when, and whether it passed the required checks.
The umbrella discipline that ISO 19650 exists to codify: planning, producing, reviewing, and securely sharing information throughout a built asset's life, using consistent processes rather than ad hoc habits that vary team to team. It is broader than "using BIM software" - information management covers the naming conventions, approval workflows, security classifications, and roles and responsibilities that make a CDE actually function as intended, rather than just being a shared folder with a fancier name.
Most of the acronyms in this glossary - EIR, BEP, AIR, PIM, AIM, LOIN - are all specific pieces of the information management framework that ISO 19650 defines.
Defined in ISO 19650, the Information Manager is a procedural role - not a design or coordination one - that governs the Common Data Environment (CDE), ensures information is exchanged according to the agreed protocol, and confirms deliverables meet the project's Exchange Information Requirements before they move between CDE states. The role has no responsibility for clash detection or design decisions; it exists purely to keep information management disciplined and auditable.
"Information model" is the umbrella term ISO 19650 actually uses - a federated model is one way to build it, but the information model also includes documents, schedules, and data that never appear in the 3D view. During delivery it's called a PIM; once handed over, it becomes the AIM.
Every "information requirements" document answers the same three questions - what, how detailed, and by when - just from a different vantage point: organizational (OIR), asset (AIR), project (PIR), or exchange with a specific supplier (EIR). Understanding the family as a whole makes each individual acronym much easier to place.
An MEP consultant's spreadsheet of equipment data that never makes it into the shared model is a classic information silo - precisely the failure mode a CDE and a single source of truth are designed to eliminate.
Insurance-Backed Guarantee (IBG)
A standard warranty is only as good as the company that issued it; an IBG solves the exact failure case where that company no longer exists to honor its own promise.
Integrated Project Delivery
Popularized by the AIA in the US, IPD is the delivery-method end state that target value design and co-location both support - the multi-party contract is what actually removes the incentive for any one party to protect its own margin at the project's expense.
The Interface Manager identifies where one task team's information depends on another's (for example, where structure and MEP models must align) and coordinates the exchange so nothing falls through the gaps between disciplines. It is a communication-heavy role, sitting alongside the Task Team Manager and Task Information Manager in a typical BIM task team structure.
Interference Check is a quick, in-app sanity test - "does this duct hit this beam, within this one file" - while full Clash Detection in Navisworks or Solibri federates multiple linked models from every discipline and manages the resulting issues at project scale; most teams use both, at different stages.
The broad goal that IFC, openBIM, and formats like glTF all serve: the ability for different software tools - made by different vendors, used by different disciplines - to exchange model data without losing or corrupting its meaning along the way. Perfect interoperability is genuinely hard: geometry usually survives a round-trip between programs, but rich data (parameters, classifications, relationships) is exactly what tends to get lost or mangled in translation.
It is worth treating as a spectrum rather than a yes-or-no property - "how interoperable" a given exchange actually is depends heavily on which specific software pair, which format, and which data you are asking about.
Internet of Things
Networked sensors and connected devices embedded throughout a building - occupancy sensors, temperature monitors, energy meters, smart lighting - that continuously feed real-world data back into digital systems. In a BIM context, IoT is what turns a static handover model into a live Digital Twin: instead of a one-time snapshot from handover day, the model keeps receiving real operational data for the rest of the building's life.
The practical value shows up in facilities management: an IoT-connected BMS can flag a failing piece of equipment before it breaks, or an energy manager can compare a building's real IoT-measured performance against the energy targets modeled during 6D design.
ISO 9001: Quality Management Systems - Requirements
A client's tender documents often ask bidders to demonstrate ISO 9001 certification alongside their BIM capability - it's a baseline signal that an organization has documented, repeatable processes, which a BIM Execution Plan then builds project-specific information-management procedures on top of.
ISO 14001: Environmental Management Systems
Where LEED or BREEAM certify the completed building's environmental performance, ISO 14001 certifies the contractor or design firm's own environmental management processes - waste handling, resource use, pollution prevention on site - a different, organization-level layer of the same broader sustainability picture.
Greenhouse gases - quantification and reporting
Where the GHG Protocol is the widely adopted practical framework most organizations actually follow, ISO 14064 is the formal international standard version of the same underlying idea.
The international standard for managing information over the whole life cycle of a built asset using BIM. ISO 19650 defines the principles and requirements for:
ISO 19650 is now the global reference standard for BIM, replacing earlier national standards like the UK's PAS 1192 series.
ISO 19650-1: Concepts and Principles
ISO 19650-1 doesn't specify procedures itself - it's the shared glossary and conceptual framework the rest of the series depends on, covering ideas like the information container, the Common Data Environment's four states, and the general principle of managing information across an asset's whole lifecycle rather than just its design and construction phases.
Information management using BIM - Part 2: Delivery phase of assets
Part 2 is the section of ISO 19650 most teams work with day to day - it defines the appointment process, EIR, BEP, MIDP/TIDP, and the CDE workflow that governs how information moves from tender through to handover. Part 3 picks up where it leaves off, covering the building's operational life.
Information management using BIM - Part 3: Operational phase of assets
Part 3 applies the same information-management discipline as Part 2 - appointments, information requirements, a CDE - but to facilities management, refurbishment, and day-to-day operation instead of design and construction, closing the loop between a project's Asset Information Model and its real operational life.
Information management using BIM - Part 5: Security-minded approach to information management
It applies to projects where the information itself could be a security risk if it leaked - critical infrastructure, defense sites, high-profile buildings - requiring a documented sensitivity assessment before deciding how openly a CDE can actually be shared.
ISO 45001: Occupational Health and Safety Management Systems
A contractor's ISO 45001 certification demonstrates a systematic approach to identifying hazards and reducing risk - the organizational counterpart to the design-side hazard elimination CDM Regulations require, closing the loop between safe design and safe execution.
ISO 55000: Asset Management - Overview, Principles and Terminology
Where ISO 19650 governs how information is managed during design and construction, ISO 55000 governs the much longer asset-management phase that follows - aligning budgets, risk, and performance targets across an entire portfolio of buildings, not just a single project. A well-structured Asset Information Model (AIM) handed over at the end of a project is what lets an ISO 55000-compliant organization actually use that data operationally.
The discipline of turning a coordination problem - a clash, a missing piece of information, a design conflict - into a tracked item with an owner, a status, and a resolution, instead of letting it live only in someone's meeting notes or memory. Issues are typically exchanged between teams as BCF files, or managed directly inside a CDE platform, and a well-run project reviews open issues on a fixed cadence until the count trends to zero.
The whole point of running clash detection and model coordination is worthless without disciplined issue tracking behind it - finding a hundred problems means nothing if forty of them quietly never get fixed.
Joint Contracts Tribunal
Where NEC contracts are built around proactive, collaborative risk management, JCT contracts are the more traditional, still-dominant default most UK building projects actually use.
Wall joins are the automatic, walls-only version of this at corners; Join Geometry is the manual tool for everything else - a column meeting a floor, a beam meeting a wall.
It's the mindset underneath the whole lean construction movement - the same logic the Last Planner System applies week to week, just named at its most general.
Where an individual keynote tag on a drawing just shows a short code, the keynote legend is the key that spells out what each code actually means - required on almost every construction drawing set that uses keynoting at all.
A documentation system where drawing notes reference a numbered code from a master keynote list (often tied to a classification system like MasterFormat) instead of writing free text directly on every sheet. A tag on a drawing shows just the code; the full note text lives in one central, editable list, so correcting a note's wording once updates it everywhere that keynote appears across the entire project.
It is essentially the annotation-level equivalent of shared parameters: one authoritative source of text, referenced everywhere, instead of the same phrase retyped independently on forty different sheets with forty chances to go slightly out of sync.
Keyhole Markup Language
It's a lightweight way to share "where is this site" with someone who has no GIS software at all - just Google Earth - unlike the richer, more structured data LandXML or CityGML carry.
It's the practical bridge between site-survey data and civil design tools like Civil 3D, doing for terrain and alignments roughly what IFC does for building elements.
LASer file format
Maintained by the American Society for Photogrammetry and Remote Sensing, LAS is the format most site-survey and topographic LiDAR data arrives in before it's brought into a BIM or civil design tool - E57 covers much of the same ground for terrestrial laser scanning specifically.
Last Planner System
Developed by the Lean Construction Institute, it works backward from milestone dates to weekly work plans that foremen and subcontractors actually commit to, then tracks a "percent plan complete" metric to catch unreliable commitments early rather than discovering a slipped schedule at the end.
The organization appointed by the Appointing Party to lead delivery of the project - often the lead designer or the main contractor, depending on the procurement route. The Lead Appointed Party is responsible for producing the BEP in response to the client's EIR, and for coordinating the work of any Task Teams it appoints beneath it.
In a typical design-led project this role usually sits with the architect or lead consultant; on a design-and-build or contractor-led project it more often sits with the main contractor - the term itself is deliberately procurement-route-neutral, which is exactly why ISO 19650 uses it instead of a more specific job title.
Techniques like the Last Planner System and target value design both come out of the lean construction movement, which reframes "waste" as anything that doesn't add value for the client - rework, waiting, and unreliable handoffs between trades, not just leftover material.
Leadership in Energy and Environmental Design
A point-based green-building rating system (from the US Green Building Council) that certifies a project across categories like energy performance, water use, materials, and indoor air quality, awarding a level from Certified up to Platinum. LEED does not require BIM, but in practice BIM makes pursuing it dramatically easier: energy analysis, daylight studies, and material quantities that LEED documentation demands can be extracted or simulated directly from the model instead of calculated by hand.
This is essentially what 6D BIM is for in practice - LEED (or its regional equivalents like BREEAM) is often the actual target that 6D energy and environmental analysis is being done to satisfy.
A Legend view can be placed on multiple sheets at once (unlike almost any other view type), which makes it the standard way to build a door/window schedule key, a wall-type legend, or a symbols key that needs to repeat identically across a whole drawing set.
It exists purely for the legend view showing it - placing a chair as a legend component doesn't add a real chair anywhere else in the model or in any schedule.
A raw laser scan doesn't arrive ready to use - Cyclone is where multiple individual scans get aligned into one clean, registered point cloud before it's exported to E57 or brought into a scan-to-BIM workflow.
It's the single most commonly skipped document on this list - everyone agrees it's valuable, and it's still the first thing dropped when a project team moves straight on to the next job.
It lets long-lead procurement or early site work start without waiting for every contract clause to be finalized - useful for keeping a schedule moving, but risky if it's used to avoid agreeing terms rather than genuinely speed things up.
Levels are one of the very first things set up in any Revit project, and almost everything else depends on them: worksets, phasing, schedules, and family placement all reference a level, directly or indirectly. Getting levels wrong early on is one of the most common causes of frustrating rework later.
Life Cycle Assessment (LCA)
LCA is the calculation framework itself (defined by standards like EN 15978), while embodied carbon and whole-life carbon are the specific numbers it produces - a Revit model's quantities and material assignments are what actually feed an LCA tool, making accurate material data entry a sustainability task, not just a documentation one.
A wall's cut line needs to read heavier than a hidden line behind it at every scale a drawing might print at - line weights are what make that graphic hierarchy consistent across a whole set of sheets instead of being adjusted view by view.
Revit Links
The mechanism for bringing a whole separate model - another discipline's Revit file, a site survey, a consultant's model - into a project as a live reference, without merging the actual data together. Unlike worksets, which divide ownership within one shared central model, Linked Models are entirely separate files: the architect links the structural engineer's model to coordinate against it, but each team still owns and edits their own file independently.
Getting links positioned correctly depends entirely on shared coordinates being set up right - a link with the wrong coordinate system will look fine in isolation and be meters off once brought into the host model.
Liquidated Damages are the financial mirror of an Extension of Time - if a delay is the contractor's fault, damages start accruing; if a valid EOT is granted instead, the completion date itself moves and damages don't apply, which is exactly why the underlying schedule and change documentation matters so much to both sides.
Level of Accuracy
Defined by the U.S. Institute of Building Documentation, Level of Accuracy grades reality-capture data (like scan-to-BIM output) by measured tolerance - how close the model geometry is to as-built reality - which is a genuinely different question from Level of Development's "how much information does this element carry." A highly detailed element can still have low positional accuracy, and vice versa.
A structural model rarely fails under any single load type alone - the dangerous scenarios are combinations, like peak wind load coinciding with full occupancy live load - which is exactly why building codes mandate checking dozens of specific load combinations rather than each load type in isolation, a process modern Revit-to-Robot workflows can automate.
Every team member on a workshared project works inside their own local file rather than the shared central model directly - this keeps the file responsive and lets each person edit their own worksets without waiting on others, syncing changes back and forth via Synchronize with Central.
Level of Development
LOD defines how detailed and reliable an element in the BIM model is at a given stage. It answers the question: "How much can I trust this model element, and what information does it contain?"
The standard LOD scale runs from 100 to 500:
| LOD | Stage | What it means |
|---|---|---|
| 100 | Concept | Element exists as a symbol or mass. Size and location are approximate. |
| 200 | Schematic Design | Generic element with approximate geometry and size. |
| 300 | Design Development | Specific geometry, exact dimensions, location, and orientation. |
| 350 | Construction Documents | Includes connections to adjacent elements. Ready for coordination. |
| 400 | Fabrication | Detailed enough for manufacturing and assembly. |
| 500 | As-Built | Verified in the field. Represents the building as actually constructed. |
LOD is used in the BEP to specify what level each model element must reach at each project milestone.
LOD 100–500 at a glance
LOD 100 Conceptual - generic massing or symbol
LOD 200 Approximate geometry - rough size, shape, location
LOD 300 Precise geometry - accurate size, shape, location, quantity
LOD 350 Like 300, plus interfaces with other building systems
LOD 400 Fabrication-ready - detailed for construction & installation
LOD 500 As-built - field-verified actual size, shape, location
Level of Information
Often paired with LOD. While LOD describes geometric detail, LOI describes the non-graphic data attached to an element - properties, specifications, material data, performance values.
A door at LOD 300 has accurate geometry. The same door with high LOI also has a fire rating, acoustic rating, hardware specification, and manufacturer's product code. Both dimensions matter for handover and facility management.
Level of Information Need
The newer, ISO 19650-era term that is gradually replacing the LOD/LOI pair in specifications. LOIN flips the question around: instead of asking "what LOD should this element reach?", it asks who needs which information, for what purpose, at which milestone - and requires exactly that, no more.
LOIN is defined in the European standard EN 17412-1 and covers three kinds of content:
The goal is to stop over-modeling: information nobody asked for costs time and money to produce and maintain.
Compared to Enscape or Twinmotion, Lumion is used more often for final marketing-quality stills and animations than live design-review walkthroughs - a common workflow is modeling in Revit, then exporting to Lumion specifically for the polished renders a client presentation needs.
Master data is what keeps a room number or asset tag consistent across the BIM model, the CDE, the FM system, and every schedule derived from them. Without a clear master data source, the same asset ends up with three slightly different IDs in three different places - exactly the inconsistency a single source of truth is meant to prevent.
The North American counterpart to Uniclass - MasterFormat (published by CSI, the Construction Specifications Institute) organizes construction information into numbered divisions, like Division 08 for Openings or Division 23 for HVAC. It is primarily a specifications-writing standard rather than a full BIM classification system, but it shows up constantly in US and Canadian projects as the backbone for organizing specification sections, and its division numbers often get mapped onto model parameters for consistency between the drawings and the specs.
Where Uniclass dominates UK/international projects, MasterFormat is what you will meet on North American ones.
On a large building where one floor doesn't fit on a single sheet at a usable scale, it's the annotation that keeps someone reading sheet 3 from getting lost about where sheet 4 picks up.
It's what turns deconstruction from a hopeful idea into a practical one - a demolition crew can't easily reuse a beam whose material grade and history nobody actually recorded.
Where a door schedule counts doors, a material takeoff can report the total area of a specific paint finish across every room that uses it - directly feeding a bill of quantities without a separate manual measurement pass.
Compared to a survey-grade laser scanner, a Matterport camera is faster and cheaper to operate but less precise - a common workflow for smaller renovation projects is a quick Matterport scan for a visual walkthrough and rough measurements, reserving a full laser scan for anything requiring true as-built modeling accuracy.
Model Element Author
On a coordinated, multi-discipline project, it's not always obvious who "owns" a given wall or duct in the federated model - the Model Element Author designation (often a code or abbreviation on the element itself) removes the ambiguity, tying every element back to the specific task team responsible for its geometry and data.
It's the least formal of the three main dispute routes - cheaper and faster than adjudication or arbitration, but only works if both sides genuinely want to reach an agreement rather than win an argument.
Mechanical, Electrical & Plumbing
The engineering disciplines that handle a building's services: HVAC systems, electrical distribution, plumbing, fire protection, and more. MEP models are among the most complex in a federated BIM workflow because the systems they contain must be coordinated against the structure and against each other.
In Revit, MEP work is done in Revit MEP - a discipline-specific configuration of the same platform used by architects and structural engineers.
A door family's geometry is data; the fact that it was last modified on a specific date, by a specific person, tagged with a specific Uniclass code, is metadata - exactly what a CDE's audit trail and a data dictionary manage.
Where a schedule (like a 4D sequence) says when work happens, a Method Statement explains how - the actual steps, plant, and safety measures a crew will follow for a task like a crane lift or a concrete pour, often reviewed alongside the model to confirm the sequence is physically achievable.
Where Autodesk's tools dominate buildings, Bentley's MicroStation and its OpenX applications (OpenRoads, OpenBridge) are especially common in civil infrastructure - the two ecosystems meet on the same project through IFC exchange rather than either one replacing the other.
Information Delivery Plans
Two documents from the ISO 19650 world that live alongside the BEP. A TIDP (Task Information Delivery Plan) is one team's delivery plan: which files and models that team provides, when, and at what level of information. The MIDP (Master Information Delivery Plan) combines all TIDPs into a single project-wide delivery plan - the schedule of the information, not of the construction.
If the EIR says "what", the MIDP says "who and when".
Revit, ArchiCAD, and Tekla Structures are authoring tools; Navisworks and Solibri are not - they federate and review what authoring tools already built. Knowing which category a piece of software falls into explains why a clash report from Navisworks still has to be fixed back in the authoring model, not in Navisworks itself.
The ongoing, cyclical process that clash detection is just one part of: regularly merging discipline models into a federated model, reviewing it (visually and through automated checks), logging every problem found as a tracked issue, assigning it to whoever needs to fix it, and confirming the fix in the next cycle. A single clash-detection run is a snapshot; Model Coordination is the repeating weekly or biweekly rhythm that keeps a project's models converging toward a buildable, conflict-free design instead of diverging further apart.
Issues are typically tracked with BCF files so every team can open exactly the same problem in their own software, at the exact camera angle and element it was found.
Walls, doors, ducts, and rooms are all model elements - the basic building blocks that carry both geometry and data inside an information model. Understanding "model element" as the generic unit is what makes concepts like Level of Development and Model Element Author meaningful, since both are defined per-element, not per-model.
Unlike a Family, which is a single reusable component, a Group bundles multiple existing elements (say, a hotel room's walls, door, and furniture) into one placeable unit - editing one instance of the group can propagate to every copy, which makes it a fast way to repeat identical layouts across a floor or a whole tower.
A model can be brilliantly designed and still be unhealthy - hundreds of unresolved warnings, bloated by years of unpurged families, slow to open for everyone on the team. Regular audit and purge passes are the routine maintenance it actually depends on.
A model line drawn on a site plan to mark a property boundary shows up in a 3D view and a section too, since it's real model geometry - a detail line doing the same job would only ever appear in that one plan view.
It's usually run automatically through rule-checking software (Solibri, Navisworks, or a custom IDS check) rather than manually, catching things like missing parameters or elements on the wrong workset before they reach a federated model and cause a much more expensive problem downstream.
It's the practical outcome quantity surveyors are aiming for when they push for well-structured, LOD-appropriate models - the more reliable a model's quantities are, the less manual re-measurement an estimate needs.
Modern Methods of Construction (MMC)
Modular construction and DfMA are two specific approaches that sit under this wider umbrella - MMC is the category the UK government and industry actually use when discussing the shift away from traditional building methods as a whole.
A construction method where large sections of a building - entire rooms, bathroom pods, structural modules - are manufactured complete in a factory and transported to site for assembly, rather than built piece by piece on location. It is the physical, large-scale end of the DfMA spectrum: instead of individual prefabricated components, whole volumetric chunks of the building arrive ready or near-ready.
BIM is close to a prerequisite for modular construction at any real scale: the factory needs LOD 400 fabrication-level model accuracy to manufacture modules that will actually fit together correctly on site, since there is little room to "figure it out" once a module has already left the factory.
Model View Definition
The full IFC schema is huge - an MVD narrows it down to exactly what's needed for one workflow, such as "Coordination View" for clash detection or "Quantity Take-off View" for QTO, so software vendors can certify support for a specific, testable subset instead of all of IFC at once. buildingSMART maintains the official MVDs alongside the IFC standard itself.
Autodesk Navisworks
Autodesk's dedicated tool for reviewing large, federated BIM models from multiple disciplines and multiple software packages at once. Navisworks aggregates models (Revit, IFC, DWG, and more) into a single lightweight federated view, runs clash detection, drives 4D construction sequencing, and manages coordination issues, often exchanged as BCF files with the design team.
It is not a modeling tool - nothing gets designed in Navisworks - it is where coordination and construction planning happen once the discipline models exist. On many contractor-led projects, Navisworks (or a competitor like Solibri) is where the "real" coordination meeting actually happens.
National Building Specification
NBS specifications are traditionally the detailed written document that sits alongside drawings and the model, spelling out exactly which product, performance standard, or workmanship quality is required for each element. Modern NBS tools (like NBS Chorus) link that text directly to BIM objects by classification code, so a change to a spec section can be traced straight back to the model elements it governs.
New Engineering Contract, 4th edition
Early warning notices and compensation events are its two signature mechanisms - the whole contract is designed around surfacing problems while they're still small and cheap to fix.
A family loaded inside another family - a handle family nested inside a door family, a hinge nested inside a window - letting complex components be built out of smaller, independently maintained pieces rather than one monolithic geometry blob. The parent family can expose (or "shared") the nested family's parameters so they still appear and schedule correctly at the project level.
Nesting is what makes large, realistic families genuinely manageable: update the handle family once, and every door family that nests it picks up the change, rather than needing forty separate handles remodeled by hand.
Net Zero Carbon
A target where a building's carbon emissions - from both its operation (energy use) and its construction (embodied carbon) - are reduced as far as practically possible, with any unavoidable remainder balanced out through offsets or carbon removal, so the net contribution to atmospheric carbon is zero. "Net zero operational carbon" and "net zero whole-life carbon" are meaningfully different, narrower and broader claims, and the distinction matters when a client asks for one specifically.
BIM's role is mainly in the "reduce as far as possible" part: 6D energy analysis and embodied-carbon calculation from model quantities are what let a design team actually test how close to net zero a design gets, long before construction starts.
Rather than hunting through email threads to find who answered a specific RFI, Newforma indexes all project communication in one searchable place - a workflow layer that sits alongside, not inside, the BIM authoring tools.
A door's 3D geometry tells you almost nothing useful for facilities management or costing on its own; its non-geometric data - fire rating, hardware set, supplier, warranty period - is what actually gets used downstream by schedules, COBie exports, and FM systems. BIM's real value over plain 3D modeling comes almost entirely from this layer.
An architect appointed directly by the client during early design can get "novated" to the contractor once construction starts - the same firm keeps working on the same model, but their client relationship and reporting line legally switches, which can quietly change whose information requirements actually take priority.
It's what actually makes a design-and-build novation real - without a signed novation agreement, the consultant technically still answers only to the original client.
New Rules of Measurement
A suite of standards (from the RICS, the Royal Institution of Chartered Surveyors) that define exactly how to measure and cost construction work consistently, across three volumes covering cost planning, detailed measurement, and maintenance costs. NRM is the rulebook that makes QTO and 5D meaningful in practice - it defines what actually counts as "one unit" of a wall, a door, or an excavation, so quantities extracted from a BIM model can be compared and costed consistently between projects and quantity surveyors.
Without a measurement standard like NRM behind it, a model-derived quantity takeoff is just a number - NRM is what makes it a trustworthy one.
Operations and Maintenance Manual
Traditionally a mountain of PDFs handed over in a box at the end of a project, the O&M Manual's content is increasingly pulled directly from BIM model data - maintenance schedules, warranty periods, spare-parts lists - so facilities managers get structured, searchable information instead of a filing cabinet to dig through.
It's one of the oldest and most universally supported 3D formats, which is exactly why it's still used for moving simple mesh geometry into renderers, game engines, or 3D printing workflows where FBX or glTF might carry more than's needed.
BS 8541-1 is exactly the kind of standard a well-run object library is built against - without it, a library becomes a folder of files with inconsistent names nobody trusts enough to reuse.
It's the base layer underneath visibility/graphics overrides and view templates - change a category's line weight in Object Styles and it updates everywhere by default, unless a specific view has already overridden it.
A CAD line representing a wall is just geometry; a BIM wall object knows its own type, fire rating, and cost - and updates every plan, section, and schedule at once when it changes.
Organizational Information Requirements
The top of the ISO 19650 requirements pyramid. OIR describes the information an entire organization needs to make strategic and operational decisions across its whole property portfolio - not just one building. Think of it as the "why" behind everything else: the OIR shapes the AIR (what a specific asset needs), which shapes the EIR (what a specific project needs).
Most individual project teams never touch the OIR directly - it lives at the client organization's portfolio-management level - but it is worth knowing it exists, because it explains why some information requirements on a project can feel disconnected from that project's own scope.
OmniClass Construction Classification System
OmniClass is built from 15 numbered tables (Table 21 for Elements, Table 23 for Products, Table 33 for Disciplines, and so on), each usable independently or combined to classify a single object from multiple angles at once. It's the classification system most often paired with MasterFormat and referenced inside Revit family templates and keynote files for North American projects.
openBIM / closedBIM
Two approaches to sharing information. openBIM relies on open, vendor-neutral formats - IFC, BCF, IDS - so every party can work in the software they choose and the information is never locked to one vendor. closedBIM assumes everyone works in the same ecosystem ("everyone on Revit"), which simplifies day-to-day coordination but creates vendor lock-in and complicates long-term handover.
Public projects increasingly require openBIM deliverables.
Common on hospitals and major infrastructure, it covers staff training, moving-in logistics, and system testing under real operating conditions - the practical extension of soft landings past the construction finish line.
It updates automatically as electrical circuits are added or changed - an electrician on site relies on it being accurate far more than on the plan view itself.
A parametrically designed staircase defined by "total rise divided by riser height" recalculates its step count the moment the floor-to-floor height changes. Grasshopper and Dynamo exist to push this idea further than a single family's own parameters can.
The term that explains why Revit is not "AutoCAD in 3D". In parametric modeling every element is defined by parameters - dimensions, materials, rules and relationships - rather than frozen lines. Change one parameter and the element updates along with everything that depends on it: move a wall and the doors, dimensions and quantities follow.
This is what makes a BIM model smart rather than just drawn: geometry and data stay linked, and the model keeps itself consistent through every change.
It's a lighter-weight relative of a full framework agreement - less formal, but built on the same logic that repeat collaboration beats one-off competitive tendering for certain kinds of ongoing work.
It has to be in place before certain excavation or wall work starts - skipping it is a common, entirely avoidable source of neighbor disputes and delayed starts on site.
PAS 128: Specification for Underground Utility Detection, Verification and Location
PAS 128 defines quality levels (D through A, A being the most certain) for utility survey data, so a model showing an existing gas main can carry an explicit confidence rating - critical before excavation or foundation work begins near services nobody has physically verified.
Publicly Available Specification 1192
The PAS 1192 series (published by BSI, the British Standards Institution) was the UK's national suite of specifications for managing BIM information before ISO 19650 existed. PAS 1192-2 covered the capital delivery phase, PAS 1192-3 covered operational asset management, and PAS 1192-5 covered security-minded BIM.
ISO 19650 was built directly on top of PAS 1192 - the CDE zones (WIP, Shared, Published, Archive), the EIR/BEP pairing, and much of the terminology carried over almost unchanged. If you read an older UK BIM specification or contract, it likely still references PAS 1192 by name.
Passivhaus (Passive House) Standard
Unlike LEED or BREEAM, which award credits across many categories, Passivhaus certifies a building against a small set of hard, measurable performance thresholds - primarily heating/cooling demand and airtightness (measured via a blower-door test). Because the standard is so sensitive to construction detailing, Passivhaus projects typically demand tighter coordination between the Revit model and the actual as-built envelope than a typical green-building certification.
The percentage complete stated on a payment certificate is increasingly checked against real quantities pulled from the model itself (via QTO or a tool like Assemble) rather than a contractor's own estimate, making an accurate, up-to-date model a direct input into the project's cash flow.
A performance bond protects the client against outright contractor failure or insolvency, which is a different risk than Retention (protecting against defects in otherwise-completed work) or Liquidated Damages (compensating for lateness) - all three mechanisms often exist on the same contract, each covering a different failure mode.
Phasing sets which phase an element belongs to; the phase filter is what actually decides how a specific view chooses to display existing, demolished, and new work relative to that assignment.
Revit's system for modeling a building across time rather than as one static snapshot. Every element gets assigned a Phase Created and, if relevant, a Phase Demolished, and every view is set to show a specific phase (or a phase comparison, like "New Construction" showing new work highlighted against a greyed-out existing building). This is essential for renovation and retrofit projects: the same model can represent existing conditions, demolition, and new work simultaneously, with each view filtering to show only what is relevant.
Phase Filters control exactly how each phase state gets drawn - what line style demolished elements get, whether existing elements show at all - giving full control over how the story of the building's timeline gets told on paper.
Software matches common points across dozens or hundreds of overlapping photos (often taken from a drone) to triangulate real-world coordinates - cheaper and faster to capture than laser scanning for large sites, though typically less precise for tight interior detail, which is why the two methods are often combined on the same project.
Project Information Model
One half of ISO 19650's central pair. The PIM is the information model built up during design and construction: models, drawings, specifications, schedules, and documentation, all developed and approved through the CDE.
At handover, the relevant parts of the PIM are transferred to the owner and become the basis of the AIM.
Project Information Requirements
The third member of the OIR/AIR/PIR family. PIR captures the information a client needs during the life of one specific project - not to operate the finished asset (that's the AIR) and not for the whole organization (that's the OIR), but to make good decisions about this particular job: budget tracking, risk management, design approvals.
In practice, the EIR that a project team receives is usually assembled from a mix of the relevant AIR and PIR content - the client's way of saying "here is everything I need from you, for this project and for running the building afterward".
Biodiversity net gain assessments and a design and access statement are two of the supporting documents a planning application increasingly needs alongside the drawings themselves.
Scan to BIM
The bridge between existing buildings and BIM. A point cloud is the output of a 3D laser scan (or photogrammetry): millions of measured points that together form a precise digital snapshot of a physical space.
Scan to BIM is the workflow of importing that point cloud (in Revit: RCP/RCS files, linked like any other reference) and modeling the real building over it - walls, floors, structure, systems - to produce an accurate as-built model for renovation, retrofit, or documentation projects.
Post-Occupancy Evaluation (POE)
A POE compares the "As Designed" intent against the "As Occupied" reality - actual energy use versus the performance simulation's prediction, occupant comfort surveys, how spaces get used differently than planned - closing the loop that Soft Landings and BS 8536 are both designed to set up from the start.
It's the step between bid management and actually signing a contract - the point where an ambiguous line item in a bill of quantities usually gets resolved.
Issuing this certificate is what actually starts the clock on the Defects Liability Period and hands operational responsibility to the client - the model and documentation package delivered around this milestone is what the facilities-management team will live with for years afterward.
It's the client's half of the CDM information exchange, feeding directly into the contractor's own construction phase plan.
A digital twin connected to live equipment sensors can flag a failing pump or an HVAC unit trending toward breakdown weeks in advance, letting facilities teams schedule the fix on their own terms rather than responding to an emergency - the practical payoff of investing in accurate BIM data for the operations phase.
Where BIM 360/ACC and Autodesk Forma grew directly out of the design/model-coordination side of Autodesk's ecosystem, Procore is a construction-management-first platform - many general contractors run Procore for site operations while still coordinating the model itself through a separate BIM tool.
It's decided before almost anything else on a project, because it determines who's actually responsible for design risk once construction starts - a decision every other document on this list is written to reflect.
Professional Indemnity Insurance (PI)
It's the standard risk transfer mechanism behind almost every design consultant's appointment - a client will usually require proof of current PI cover before signing anyone on.
A drone or 360-camera pass captures the site on a regular cadence, and that reality-capture data is compared against the 4D schedule model to flag what's ahead, on track, or falling behind - turning "how's it going out there" into an objective, model-based answer instead of a subjective site-visit impression.
It's the simplest, oldest form of reality capture on a project - still valuable even after photogrammetry and point clouds became standard, because a dated photo is sometimes the fastest way to prove what existed on a given day.
Project Bank Account (PBA)
It's increasingly required on UK public sector projects specifically to fix a well-known failure mode - a subcontractor doing good work but never getting paid because the money stalled somewhere above them in the chain.
Earned value management and the critical path method are two of its core techniques - project controls is the discipline that puts them to use together rather than as standalone tools.
Where a BEP answers "how will information be managed," the project execution plan answers the wider question of how the whole project - budget, schedule, roles, risk - will actually be run.
Project Parameters are the simplest of Revit's three parameter types to set up - useful for a one-off tracking field on this project only - but because they're baked into that single file, they can't be tagged, scheduled across other projects, or exported to ODBC the way a Shared Parameter can.
An extension of time gives a contractor more days; prolongation costs are the separate, and often more contested, claim for what those extra days actually cost to keep the site running.
It's the same practice as snagging under a different name - useful to know both terms, since which one a project uses often just depends on whether it follows UK or US contract conventions.
A built-in Revit command that finds and removes elements loaded into a project but not actually placed anywhere - unused family types, line styles, materials, view templates - which quietly bloat file size and slow down performance over the life of a project without adding any value.
Purge Unused is one of the simplest, lowest-risk habits for keeping a model healthy: run it periodically (especially before a big milestone or handover), and a project that has picked up hundreds of unused, half-experimented-with elements over months of work gets noticeably lighter and faster with essentially no downside.
Where Dynamo's visual graphs are approachable for modelers without a coding background, pyRevit appeals to users who already know or want to learn Python - the two aren't mutually exclusive, and some studios use Dynamo for quick one-off graphs and pyRevit for maintaining a shared library of reusable custom tools across a whole office.
It reads and writes the same open geospatial formats (like KML and LandXML) as its commercial competitors, making it a common low-cost entry point into GIS-BIM integration.
Quantity Takeoff
The practical side of 5D. QTO means extracting quantities directly from the model - wall areas, duct lengths, concrete volumes, door counts - instead of measuring drawings by hand. In Revit this happens through Schedules; tools like Navisworks or Power BI let you slice quantities by level, zone or construction stage.
QTO quality depends directly on modeling quality: an element modeled wrong gets counted wrong.
It defines who checks what, how often, and against which standard - inspection and test plans, model quality checks, and sign-off procedures all sit underneath it. On a BIM project this usually includes explicit model quality review steps alongside the traditional physical inspections.
Quantity surveyors extract measured quantities from drawings or a BIM model - historically by hand, increasingly via QTO tools reading model data directly - to produce cost estimates, bills of quantities, and valuations as a project progresses. BIM's structured, parametric data makes this measurement faster and far less error-prone than working from 2D drawings alone.
The umbrella term for every technique used to record the real, physical condition of a site or building digitally: laser scanning that produces a point cloud, drone photography, 360-degree photo documentation, and photogrammetry (building 3D geometry from overlapping photographs instead of a laser). Scan to BIM is the specific workflow of turning reality capture data into a usable Revit model - reality capture is the broader category that workflow belongs to.
On a renovation project, good reality capture at the start is what makes an accurate as built model possible later; skipping it usually means a model built on guesswork and old, unreliable drawings instead.
Autodesk ReCap
Raw scanner output is usually far too heavy and noisy to work with directly, so ReCap indexes, cleans, and compresses it into its own .rcp/.rcs format before a modeler links it into Revit as an underlay for tracing walls, floors, and existing conditions at real-world scale - the practical first step in most Scan-to-BIM workflows.
Where "as-built" describes a category of information generally, record drawings are the specific 2D document set a client actually receives at handover - and increasingly, that set is generated directly from the as-built model rather than redrawn from scratch.
Reference planes are the invisible-in-3D guide lines a modeler adds inside a family editor or sketch (often locked with dimensions or parameters) to keep geometry aligned as it flexes - they're a sketch-time tool, while a Work Plane is the actual 3D surface hosting the whole sketch.
It became mainstream almost overnight during the pandemic, and stuck around afterward simply because it's faster for routine checks - a drone survey feeding straight into it for anything at height or hard to reach.
It's increasingly modeled alongside embodied and whole-life carbon rather than treated separately - a building designed for net-zero operation still needs a resilience plan for the climate conditions it will actually face over a 60-year life, not just the ones on file today.
Responsibility Matrix (RACI)
In an ISO 19650 workflow, a responsibility matrix is what actually assigns each piece of model content and information deliverable to a specific team or role, so a coordination clash or missed deliverable has a clear, agreed-upon owner rather than an ambiguous "someone should fix this."
A typical retention is 5% of each payment, with half released at Practical Completion and the rest at the end of the Defects Liability Period - a real financial incentive tied directly to how quickly and completely a contractor closes out the snag list.
Instead of the client physically holding back 5% of every payment, the contractor's bank or insurer issues a bond covering the same risk - the contractor keeps full cash flow through the project, and the client can still call on the bond if defects go unfixed at the end of the Defects Liability Period.
Retrofit projects almost always start with Scan-to-BIM (there's rarely an accurate existing model), and success is measured against Whole Life Costing and carbon targets rather than a fresh design brief - a fundamentally different modeling problem than new-build work, working around and constrained by what's already there.
Ordinary supply chain management moves materials from factory to site; reverse logistics is the same discipline running the other way, and it's usually the harder direction to make economically viable.
It's the visual half of a two-part system - the cloud shows where a change happened on the sheet, while the revision schedule records what the change was, when, and why.
It's usually placed right next to the title block, giving anyone reading a printed drawing an instant history of every change without needing to compare it against an older version.
Revit was originally developed by Charles River Software and acquired by Autodesk in 2002 - its name is short for "Revise Instantly," a nod to its core idea: every wall, door, and schedule is a live view of one shared model, so a single change updates everywhere else automatically. That is the parametric, database-backed approach the rest of this glossary keeps referring back to - families, worksets, schedules, and the Revit API all exist inside Revit specifically, not as generic BIM concepts. Three separate disciplines (architecture, structure, MEP) work inside the same core product, usually coordinating through linked models and worksharing rather than separate software.
Revit Application Programming Interface
Anything Revit can do manually, the API can usually do programmatically - bulk-editing parameters, generating custom reports, automating repetitive modeling tasks, or building entire custom tools. Dynamo and most third-party Revit plugins are themselves built on top of the Revit API; power users write directly against it in C# or Python (via pyRevit) when they need something beyond what visual scripting offers.
Revit LT covers the core modeling and documentation workflow at a fraction of full Revit's price, which makes it attractive to sole practitioners and small firms - but the missing worksharing and API support mean it can't participate in a multi-user central model or run Dynamo scripts, so growing firms typically outgrow it.
Autodesk's own solution for extending worksharing across multiple physical office locations without everyone connecting to the same local network. Instead of a single central model sitting on one office's server, Revit Server hosts the central model and lets each office's local Revit Server instance keep a synchronized copy, so a team in one city and a team in another can work on the same project through their own local, fast connection.
It has been increasingly overtaken by cloud worksharing (Autodesk Construction Cloud), which does the same job without dedicated server hardware in every office, but Revit Server is still common in larger firms with an existing IT infrastructure investment.
A coordination platform that combines federated model viewing, clash detection, and issue tracking into one real-time environment, aimed at making coordination meetings genuinely interactive - multiple people can navigate the same live 3D view together during a call, rather than one person sharing their screen while everyone else watches.
It competes directly with Navisworks and Solibri in the same coordination space, and like BIMcollab, leans on BCF to keep issues portable between different teams' software.
Request for Information
RFIs are the standard mechanism for resolving ambiguity during construction - when something on site doesn't match the documents, or two disciplines' information conflicts, an RFI captures the question, routes it to whoever can answer, and creates a written record of the resolution. Frequent RFIs on a project are often a sign of coordination problems that better BIM clash detection could have caught earlier.
Rhinoceros 3D
A double-curved facade panel or an organic canopy shape is often designed and rationalized in Rhino using Grasshopper's parametric tools, then brought into Revit as an imported form or adaptive component family for documentation and coordination with the rest of the building model.
A widely used UK framework (from the Royal Institute of British Architects) that divides a project into numbered stages - from 0 (Strategic Definition) through 7 (Use) - each with defined outputs and decision points. It is not a BIM standard on its own, but BIM specifications constantly reference it: an EIR will typically say what LOD is expected "by the end of Stage 3" or "by Stage 4," anchoring model detail to a stage everyone in the industry recognizes.
Other countries use their own equivalent staged frameworks, but the RIBA Plan of Work is the one referenced often enough internationally that it is worth knowing even outside the UK.
Royal Institution of Chartered Surveyors
NRM, the New Rules of Measurement quantity surveyors work to daily, is itself an RICS publication - membership and its professional standards sit behind much of how quantity surveying and valuation are practiced in the UK and internationally.
In a BIM context this usually takes the form of a live risk register cross-referenced against model elements and a responsibility matrix, so a genuinely serious coordination clash gets escalated ahead of a cosmetic one instead of both landing in the same undifferentiated issue list.
A design-stage risk register might flag an unresolved geotechnical uncertainty; a construction-stage one tracks a live weather delay. It's reviewed at every stage gate, and closing out an entry usually means either the risk was designed out or a mitigation genuinely worked - not that it was quietly forgotten.
A guaranteed maximum price is a form of risk transfer onto the contractor; professional indemnity insurance is a form of risk transfer onto an insurer - the same underlying idea applied to different parties.
Autodesk Robot Structural Analysis Professional
A structural engineer exports the analytical model (see Structural Analytical Model) from Revit into Robot, runs load cases and code checks there, then pushes reinforcement or member-size results back - keeping the physical Revit model and the engineering analysis in sync instead of maintained as two disconnected files.
A room that calculates the wrong area or refuses to fill with a color scheme almost always has a room-bounding mismatch nearby - a furniture family incorrectly set to room-bounding, or a partition wall incorrectly set to not room-bounding - making this one of the first properties to check when Room vs. Space calculations look wrong.
Common on healthcare, education, and hospitality projects with hundreds of similar-but-distinct rooms, a Room Data Sheet is typically generated straight from Revit room parameters and schedules rather than authored by hand - keeping it automatically in sync whenever a room's finishes or area change in the model.
A frequent point of confusion for anyone coordinating architecture with MEP in Revit: Rooms and Spaces are two separate element types that can occupy the exact same physical volume but belong to different disciplines and different Revit categories entirely. Architects place and schedule Rooms; MEP engineers place Spaces (used for HVAC load calculations and energy analysis) - and the two do not automatically stay in sync with each other.
Best practice is usually to let Spaces derive their boundaries directly from the architectural model's Rooms wherever possible, and to re-check that link whenever the architectural layout changes - otherwise an MEP team can end up doing load calculations against room boundaries that no longer match the actual design.
A cracked wall can be patched in an afternoon; root cause analysis is what tells you whether it'll just crack again because of a settlement issue nobody actually looked into.
Revit Project File (.rvt)
The native file extension of a Revit project - .rvt - which carries the complete model: geometry, parameters, views, sheets, and every loaded family, all in one proprietary binary file. Unlike exchange formats like IFC or DWG, an RVT file is not meant for cross-software exchange - it is Revit talking to Revit, preserving 100% of the model's native intelligence, which is exactly why it is the file format used for the central model in worksharing.
RVT files can grow large and, without regular maintenance (purging unused elements, auditing), gradually accumulate bloat that slows the whole team down - which is why file-health habits matter as much as modeling skill on a long-running project.
Where Scan-to-BIM creates a model FROM a scan (usually for existing buildings with no model), Scan vs. BIM compares a NEW scan of freshly built work against an ALREADY-EXISTING design model - flagging deviations before they become expensive problems, a quality-control step increasingly run at key construction milestones rather than only at final handover.
Surveyors capture an existing site or building with a laser scanner or photogrammetry to produce a point cloud, then modelers use that point cloud as an accurate reference to build walls, floors, and other elements in Revit (or another BIM tool) at real-world dimensions. It's the standard way to get reliable as-built models for renovation, retrofit, and facilities-management projects where no accurate existing model exists.
Revit Schedule
A table view in Revit that lists model elements and their parameters as rows and columns - a door schedule, a room finish schedule, a window schedule - built directly from live model data rather than typed in by hand. Because a Schedule is really just another view of the model, editing a value in the schedule changes the actual element, and editing the element updates the schedule instantly; the two are never out of sync the way a model and a separately-maintained spreadsheet always eventually are.
Schedules are also the most common practical output of QTO: a material takeoff schedule with a calculated quantity column is often the fastest way to get numbers out of a model and onto a cost plan.
Instead of typing "wall finish: paint, floor finish: tile, ceiling finish: acoustic panel" into every single room, a modeler assigns one key (say, "Finish Type 2") and the schedule key table fills in all three values automatically - built specifically to make a Room Data Sheet-style schedule fast to populate and consistent across hundreds of rooms.
On a large campus or multi-tower project, grids and levels would otherwise stretch across every view regardless of which building it belongs to; a scope box lets a modeler crop grid/level visibility to just the relevant building or zone in each view, without touching the extents of the actual grids and levels themselves.
It's a live, view-specific tool for exploring a model interactively - unlike a crop region, which limits what a 2D view shows, or a scope box, which limits what datum elements appear across several views at once.
Not every building's information can be freely shared - airports, government facilities, and critical infrastructure need controls on who can access what, at what resolution, and through which systems. Security-minded BIM builds a security triage process into the standard ISO 19650 workflow, assessing sensitivity before information gets published rather than after.
A modeler manually picks an odd, one-off combination of elements - say, every window on a single irregular elevation - saves it as a named selection set, and can reselect that exact same combination weeks later in one click, which neither a rule-based View Filter nor a geometry-sharing Group is built for.
The number-one reason models "don't sit" on each other in coordination. Every Revit model has a Project Base Point (internal reference) and a Survey Point (anchor to the surveyor's coordinate system). Shared coordinates are the agreement of all disciplines on the same real-world anchor - so when the structural model is linked into the architectural one, they meet in the right place, at the right elevation, at the right rotation.
Setting them correctly on day one of the project saves weeks of pain.
A firm typically maintains one central shared parameter file that every project and family template points to - split it across several inconsistent files, and the same parameter can end up with two different internal IDs in different projects.
Revit's way of letting one piece of data exist consistently across families, projects and schedules. A shared parameter is defined once in an external .txt file with a unique GUID, and every family or project using it refers to the exact same field - which is why it can appear in schedules, tags and IFC exports.
Without shared parameters, "FireRating" in one family and "Fire_Rating" in another are two strangers that will never meet in the same schedule.
It's a less commonly used path to the same destination shared coordinates reach - useful when several models need to agree on a real-world position but publishing coordinates directly between them isn't practical.
It solves a specific access problem - a client or reviewer who has no Revit license and shouldn't see the whole working model can still open one shared view in a browser to leave comments.
Since it's a live schedule, adding or removing a sheet updates the drawing index automatically - no more manually retyping a table of contents every time the sheet count changes.
Detailed, fabrication-ready drawings produced by a subcontractor, fabricator, or manufacturer - showing exactly how a component will be built or installed, at a level of precision the design team's own drawings do not attempt. In a BIM workflow, shop drawings are increasingly generated directly from the model rather than redrawn from scratch, once the model reaches LOD 400.
Shop drawings usually require formal approval from the design team before fabrication starts, which is exactly the kind of milestone tracked through a project's issue tracking and review workflow - an unapproved shop drawing that gets fabricated anyway is a common, expensive mistake on a poorly coordinated project.
It sounds like a technicality, but it's what makes a CDE actually work: if a drawing can also be emailed directly to a subcontractor, there are now two versions in circulation and no way to know which one is current. A single point of entry is what keeps the CDE the genuine single source of truth instead of just one more copy of the files.
It's the underlying logic behind design-and-build's appeal - instead of a client managing a design team and a contractor separately, and arguing about whose fault a problem is, there's only one door to knock on.
The foundational principle behind most of BIM's process discipline: information about a project should exist in exactly one authoritative place, with everything else - drawings, schedules, reports - generated from it, rather than maintained as separate, parallel copies that inevitably drift out of sync. A schedule pulled live from the model is a single source of truth in action; a spreadsheet someone maintains by hand alongside the model is the opposite.
The CDE is the organizational mechanism that makes a single source of truth possible at the project level - a defined, agreed place where the current, correct version of every piece of information lives, so nobody is ever working from an outdated copy without realizing it.
It's the physical execution of the site logistics plan - the plan on paper becoming hoarding, cabins, and a compound gate in the real world.
On a tight urban site it's often the single most argued-over document on the job - it's also exactly the kind of plan a digital rehearsal is used to test before committing to it on paper.
A site logistics model sits alongside the permanent building model and changes as construction progresses - a crane's reach and a material laydown zone that make sense in month two might need to move entirely by month eight, and planning that sequence in the model catches clashes a static 2D site plan would miss.
A precise physical survey of a site - boundaries, existing levels, utilities, existing structures - carried out by a licensed surveyor and used as the accurate ground-truth base a model is built on top of. A site survey is typically imported as a linked drawing or point file and tied to the project's shared coordinates, anchoring everything modeled afterward to the real world.
Skipping or rushing a proper site survey is one of the most common sources of expensive downstream problems: a building modeled against inaccurate site data can end up with the wrong finished floor level, misaligned property boundaries, or a design that does not actually fit the real topography once construction starts.
It tracks waste by type and destination - what gets recycled, what's reused on site, what actually ends up in landfill - and is increasingly tied to a project's circular economy and embodied carbon targets rather than treated as a standalone compliance document.
Many architecture students and small firms start a concept in SketchUp because its learning curve is far gentler than Revit's parametric approach - the tradeoff is that a SketchUp model carries no real building data (no wall types, no schedules), so it typically gets rebuilt as proper Revit families once the design is set, rather than imported wholesale.
It's the format behind the free 3D Warehouse library many SketchUp users pull furniture and site-context models from - useful for early massing and concept work, though it carries none of the parametric, data-rich structure a Revit family does.
A "snag list" (also called a punch list) is walked and photographed on site, then increasingly logged directly against BIM model elements using mobile apps or BCF issue files, so each defect is tied to the exact object, location, and responsible party rather than a loose spreadsheet row.
Clearing every item on the snagging list is what a certificate of making good defects formally confirms happened.
BSRIA Soft Landings
A framework (originally from BSRIA in the UK) for closing the gap between how a building was designed to perform and how it actually performs once people move in. Soft Landings keeps the design and construction team involved for a period after handover - typically a year or more - to fine-tune systems, answer the operator's questions, and compare real performance data against the original design intent.
It pairs naturally with BIM: the AIM and COBie data produced during the project become the baseline the Soft Landings team measures against, and lessons learned feed back into the next project's EIR.
Solibri Model Checker
A model-checking and coordination platform (now owned by Nemetschek) built specifically around openBIM and IFC, rather than any single authoring tool. Solibri's strength is rule-based checking: instead of just visually spotting clashes, it can automatically verify a model against a defined rule set - fire-escape distances, accessibility clearances, missing information, LOD compliance - and flag every violation in a structured report.
It is a common alternative or companion to Navisworks, especially on projects that lean heavily on openBIM workflows and want checking that goes beyond geometric clashes into actual information quality.
Clash detection is the automated check; spatial coordination is the broader discipline it serves, including things a clash test alone won't catch, like leaving enough clearance around a valve for a technician to actually reach it.
If drawings show what goes where, the specification says how good it has to be - which standard a material must meet, how it should be installed, and how it's tested or certified. On BIM projects, specification sections (often organized via MasterFormat or a national equivalent like NRM) are increasingly linked directly to model elements rather than living in a completely separate document.
Instead of exporting an IFC or Navisworks file and re-importing it whenever something changes, Speckle keeps live, versioned "streams" of model data that different tools can push to and pull from - closer to how a code repository works than a traditional file exchange. It's gained traction as a lighter, more automatable alternative to file-based interoperability, especially for teams already scripting with Dynamo or Grasshopper.
It's useful the moment two halves of what was one continuous wall need different properties - a different fire rating past a certain point, say - without redrawing anything from scratch.
Site and roof drainage plans depend heavily on it - a series of spot elevations across a sloped surface is how a reviewer confirms water will actually flow toward a drain rather than pool somewhere unintended.
The RIBA Plan of Work's numbered stages are a well-known example - each stage gate exists to stop a project sliding into detailed design before the client has actually approved the concept it's based on.
It replaced the older sketch-based stair tool as the default for a reason - each component stays independently editable, which handles awkward real-world stair geometry far more gracefully.
A responsibility matrix tells you who does what; stakeholder management is the broader, ongoing job of keeping everyone who cares about the outcome informed and aligned, whether or not they're formally assigned a task.
Standard for the Exchange of Product Model Data
When a Revit-modeled component needs to actually get manufactured - a custom curtain wall bracket or a piece of structural steel - STEP is often the format that hands its precise geometry off to CNC machines and manufacturing CAD software, since it was built for mechanical engineering precision rather than architectural documentation.
A simplified representation of the structure - beams and columns reduced to centerlines, walls reduced to planes - that structural analysis software actually calculates against, running alongside the full Physical Model (the real geometry everyone else sees and coordinates with) inside the same Revit structural elements.
The two models can drift apart if not managed carefully: moving a column's physical geometry does not always automatically move its analytical line the same way, and a structural engineer's calculations are only as trustworthy as how well the analytical model actually matches the real, physical design intent.
A finite element analysis or a structural optimization pass usually feeds directly into it - the calculations document is the formal, checkable record of what that analysis actually concluded.
It's finite element analysis put to a specific purpose - not just checking whether a design works, but iterating toward the leanest design that still works.
AIA contract documents define it precisely because so much else hangs on that date - warranty periods, retainage release, and the client's insurance obligations often all start counting from it.
A quick sun-path study inside Revit itself can catch an obvious overshadowing problem or confirm a shading device works at the summer solstice, without needing to export to a dedicated building performance simulation tool for every early design question.
A digital fabrication supplier is only as reliable as the supply chain feeding it materials on time - which is why a delayed shipment three tiers down can still blow a critical path months later.
It's the procurement-side counterpart to embodied carbon targets - a low-carbon design can still fail its sustainability goals if the materials behind it are sourced from whoever's cheapest regardless of their footprint.
Synchro Pro
Instead of a schedule and a model living as two disconnected documents, Synchro ties each schedule task to the specific elements it builds, so the whole team can visually watch the building "grow" over time and immediately spot sequencing conflicts a spreadsheet-based schedule alone would never reveal.
Where the project browser organizes a model by view, the system browser organizes it by system - the tool an MEP engineer reaches for to select every element on one specific duct run at once, wherever it appears.
It's the fundamental split every new Revit user has to learn: loadable families (like a door or a piece of furniture) live in RFA files and get loaded into a project, while system families are always project-hosted, copied between projects via transfer project standards instead of a family load.
Copying an element between two open projects, or quickly comparing a detail across a current job and a past reference project, becomes a simple tab-switch instead of alt-tabbing between two entirely separate Revit windows - a workflow convenience most new users only appreciate once they've felt the friction of the old way.
A tag isn't independent text - it's a live readout tied to a specific model element's parameter, so if that element's value changes (or the element gets deleted), the tag updates or disappears with it, which keeps drawing documentation from silently drifting out of sync with the model.
It puts the owner, designer, and contractor in the room together from the start, treating the target cost as a design constraint rather than an estimate produced after the design is already fixed - closer in spirit to integrated project delivery than to a traditional design-bid-build sequence.
Within a BIM task team (as set out in ISO 19650 and BS 1192), the Task Information Manager plans and directs the day-to-day production of information, ensures the team follows the project's naming conventions and standards, and reviews information before it is shared for coordination. Distinct from the wider Information Manager role, which operates at the whole-project level rather than within a single task team.
A single-discipline team - the structural engineers, the MEP consultants, the facade specialists - appointed to produce a specific portion of the project's information, working under the coordination of the Lead Appointed Party. Each Task Team is responsible for its own TIDP, and for delivering its discipline model to the agreed LOD at each milestone.
In everyday language this is simply "one of the consultant teams on the project" - ISO 19650's contribution is giving that relationship a precise name and a defined place in the overall information-delivery structure, rather than leaving it implicit.
Where Revit is a generalist across every discipline, Tekla goes deep on one - connection-level steel detail accurate enough to drive digital fabrication directly, which is why it's common to see a Tekla structural model federated with a Revit architectural one.
Template (.rte)
Every project's starting file - and the DNA of an office standard. A template (.rte in Revit) comes pre-loaded with view settings, view templates, families, line styles, sheets, parameters and naming conventions - so every new project starts organized and consistent.
An office with a good template produces uniform work fast; an office without one reinvents the wheel every project. Building an office template is one of the highest-return investments in BIM adoption.
They're a placement aid, not documentation - a small permanent-dimension icon appears next to them precisely so a user can promote a useful temporary reading into a real dimension string before it disappears.
It's a distinct engineering discipline from the permanent structural design, and a frequent source of on-site accidents when it's treated as an afterthought rather than designed and checked properly.
Under Design-Bid-Build, the quality of the tender package directly determines how comparable and reliable the bids that come back actually are - an incomplete or ambiguous model/specification at tender stage is one of the most common sources of costly change orders once construction starts.
It's a lighter-weight alternative to a collateral warranty, achieving a similar practical outcome with less separate paperwork for each new party who needs protection.
It's itself an annotation family, custom-built or edited per firm, and it's what every revision schedule and sheet list ultimately displays alongside.
A Toposurface was purely geometric - a shape with no material layers or quantity data - while a Toposolid behaves like a proper building element: it can host sub-elements, split into layers (topsoil over subgrade), and feed schedules the way a floor or wall assembly does, closing a long-standing gap between site modeling and building modeling.
On a tight urban site it works hand in hand with the site logistics plan, but focuses specifically on the public road network rather than the site boundary itself.
Since system families and view templates can't be loaded like an RFA family, this is the actual mechanism firms use to keep standards consistent across projects - typically run once against a firm's master template file rather than project-to-project.
A transmittal is the paper trail of information exchange - it names the sender, recipient, purpose (for information, for review, for construction), revision numbers, and a list of every file included, so both sides have a shared, auditable record of what was issued and when. On BIM projects it's usually generated automatically by the Common Data Environment when a set of documents changes CDE state.
It's one of the very first tools a new Revit user learns - clicking two walls that don't quite meet and having them snap together cleanly instead of manually dragging endpoints.
Trimble's cloud-based collaboration platform - a CDE-style environment for sharing, viewing, and coordinating models across teams, particularly common on projects using Tekla Structures or other Trimble tools, and widely used in infrastructure and heavy-civil work alongside building projects.
It plays a similar functional role to Autodesk Construction Cloud, but from a different vendor ecosystem - which project you will meet it on usually comes down to which authoring software the structural or infrastructure discipline is using.
A real-time architectural visualization tool from Epic Games (the makers of the Unreal Engine and Fortnite), offering the same "instant photorealistic walkthrough" value as Enscape, but built on genuine game-engine technology. Models come in from Revit and other BIM tools via Datasmith, Epic's dedicated import pipeline, preserving materials and hierarchy far better than a generic export would.
Twinmotion and Enscape occupy roughly the same niche and are frequently compared directly - the choice between them usually comes down to rendering style preference, VR support needs, and which one a firm's existing licenses already cover.
It brings the contractor's buildability input into the design earlier than a traditional single-stage tender would - closer in spirit to early contractor involvement than to a pure design-bid-build split.
One of the first genuinely confusing ideas for anyone new to Revit. A Type parameter is shared by every placed instance of that type - change the fire rating on one door of "Door Single 900mm" and every door of that exact type updates, because it is really one shared definition. An Instance parameter belongs to one specific placed element only - its Mark number, its Level, its exact height above the floor - and changing it affects nothing else.
Getting this distinction right is the difference between a model where a single correction fixes forty doors at once, and one where you are manually fixing forty doors one by one.
Rather than loading an entire family with every possible size (say, a door family with forty width/height combinations) and picking one, a type catalog lets a user pick just the specific type they need straight from the Insert dialog - keeping projects lighter and family management cleaner, especially for manufacturer content with many variants.
It's how a drafter checks that a wall on the second floor actually lines up with the wall supporting it below, without switching back and forth between two separate plan views.
Unified Classification for the Construction Industry
Uniclass groups information under tables like Systems, Products, Spaces/Locations, and Entities, and each item gets a short alphanumeric code (e.g. Ss_25_10 for a wall system) that stays consistent whether it's referenced in a drawing, a schedule, or a COBie handover file. It's most common on UK and Commonwealth projects, and pairs naturally with classification fields already built into Revit's family and material parameters.
Uniformat Classification for Building Elements
Where MasterFormat organizes information by trade (concrete, masonry, doors and windows), Uniformat groups the same building by what it physically is made of - substructure, shell, interiors, services - which makes it especially useful for early cost estimating and elemental quantity takeoffs, before trade-specific specifications even exist.
Twinmotion trades some of Unreal's raw flexibility for a much faster, AEC-tailored workflow - a studio that needs full creative control over lighting, materials, and interactivity beyond what Twinmotion's simplified interface offers will often go straight to Unreal itself instead.
Universal Scene Description
USD's ability to layer and merge huge scenes from multiple sources non-destructively is what makes it attractive for AEC beyond film - a Revit model can be converted to USD and combined with other data sources in a shared real-time environment without flattening everything into one fixed file the way older exchange formats do.
Unlike the real-time engines built for fast design-stage walkthroughs (Enscape, Twinmotion, Lumion), V-Ray renders take longer to compute in exchange for more physically accurate light bounces and materials - the tool of choice when the final image itself is the deliverable, like a competition board or a hero marketing shot.
A structured process for reviewing a design specifically to find ways to reduce cost while still meeting the project's required function and quality - substituting materials, simplifying a detail, questioning whether a specified system is actually necessary - as distinct from simply "cutting corners," which sacrifices quality to save money.
BIM makes value engineering far more informed: because a model carries live QTO and cost data, a proposed substitution's actual cost and quantity impact can be tested in the model directly, rather than estimated roughly on paper, and the impact of a change ripples visibly through every schedule and drawing that depends on it.
Where value engineering is usually a targeted exercise applied to a specific design once it exists, value management runs throughout the project lifecycle, shaping the brief and decisions from the very start rather than optimizing after the fact.
It's a diagnostic tool lean construction borrows directly from manufacturing - drawing out the actual flow of a process is often the fastest way to see where it's genuinely breaking down.
Virtual Design & Construction
A term you will meet constantly in job postings and large construction companies. VDC is the management approach that wraps around BIM: using virtual models to plan the construction itself - coordination, schedules, site logistics and budget - before anyone reaches the field.
If BIM is the information and the model, VDC is how the project team uses them to make execution decisions. In practice, a "BIM coordinator" role at a contractor is very close to VDC work.
Its landscape and entertainment-industry toolsets are unusually strong compared to Revit's, which is why it's the more common choice outside pure building-design work.
A CDE's own status/revision fields are its version control mechanism at the project level; Revit's central-and-local file system is the same idea at the single-file level.
Instead of manually recoloring every wall by hand, a view filter says "any wall where Fire Rating equals 2 Hours turns red in this view" - applied per view or view template, purely graphical, and completely reversible since it never touches the actual model data. Common uses include coding phases, disciplines, or fire ratings by color across a whole set of drawings at once.
A plan view showing a kitchen counter but not the upper cabinets above it, or missing a low beam that should appear as a dashed line, is almost always a View Range setting problem rather than a modeling error - one of the most common sources of confusion for anyone new to reading or producing Revit plan views.
A saved collection of view settings - visibility and graphics overrides, scale, detail level, phase, view range, and more - that can be applied to a view in a single click, and optionally locked so nobody can accidentally change it. View Templates are how an office keeps every floor plan, section, and elevation looking consistent across a project (and across every project, if the templates live in the office Template), instead of every team member configuring visibility settings by hand.
They are one of the highest-leverage tools in a well-run Revit office: a good set of view templates turns "make this drawing look right" from a 20-minute manual task into a two-second dropdown selection.
Visibility/Graphics Overrides (VG)
VG (opened with the shortcut VG or VV) is where a modeler tweaks a single view's line weights, hatch patterns, or category visibility on the fly - a View Template, by contrast, packages a whole set of VG and other view settings into one reusable, lockable preset applied across many views at once.
On a large project, one single Revit file becomes too heavy for anyone to work in efficiently, so the team agrees up front on how to split it - often by tower, floor band, or zone - and documents where each split's boundaries sit so linked models stay aligned and no scope falls between two volumes unowned.
It's a simpler, built-in alternative to exporting a model into Twinmotion or Lumion for a fully rendered flythrough - lower fidelity, but immediate, with no extra software involved.
It's one of the most common sources of confusing-looking corners in a plan - the automatic join usually gets it right, but disallowing or overriding it manually is a routine fix when it doesn't.
It follows the wall's own path automatically, including around corners and openings, instead of being drawn as separate straight segments that would need manual updating every time the wall changes.
The built-in alerts Revit raises when something in the model is geometrically or logically questionable - overlapping walls, elements at the wrong level, rooms that aren't fully enclosed - without actually blocking the user from continuing to work. A small number of warnings is normal on any active project; a model with thousands of accumulated, ignored Warnings is usually a sign of deeper, unaddressed coordination or quality problems.
Reviewing and triaging the warnings list periodically - fixing what is real, understanding and dismissing what is a false positive - is a standard part of the model-health checks a BIM Coordinator runs before a milestone or handover.
A roof membrane might carry a 20-year manufacturer warranty even though the general Defects Liability Period on the whole project ends after 12 months - tracking which specific product warranties apply to which model elements is exactly the kind of non-geometric data an Asset Information Model is built to carry into operation.
Where LEED and BREEAM focus mainly on a building's environmental footprint, the WELL Building Standard certifies how the building affects the health and wellbeing of its occupants - air and water quality, lighting, acoustics, thermal comfort, and mental health considerations. It is increasingly requested alongside LEED or BREEAM rather than instead of them, especially for workplace and residential projects where occupant experience is a selling point.
As with the other certifications, the data a WELL assessment needs - daylight levels, ventilation rates, material transparency - overlaps heavily with information a properly developed BIM model can already provide.
The complete carbon picture of a building across its entire lifecycle: embodied carbon from materials and construction, operational carbon from decades of energy use, and end-of-life carbon from eventual demolition or deconstruction, all added together. Assessing whole life carbon requires exactly the kind of rich, structured data BIM is built to hold - quantities, material types, expected service life, energy performance - pulled together from a single model rather than assembled by hand from separate reports.
It is increasingly what regulations and certifications like LEED and BREEAM are moving toward requiring, replacing older assessments that only looked at operational energy in isolation.
Whole Life Costing (WLC)
A cheaper HVAC system to build can easily cost more over 30 years of energy use and replacement parts than a pricier, more efficient one - Whole Life Costing is the discipline of comparing options on that full timeline instead of the upfront number, using the same quantities and system data already captured in the model.
Work in Progress
The private zone inside the CDE where each discipline works on their own model before sharing it with the wider team. WIP information has not been checked or approved - it is the raw working file.
Promoting information out of WIP and into the Shared zone is a formal step: it means the information has been reviewed and is ready for the rest of the team to coordinate against.
Work Breakdown Structure (WBS)
Uniformat and Omniclass are essentially standardized WBS structures for building elements - which is exactly why a well-built BIM model's own hierarchy so often lines up with the project's cost and schedule breakdown too.
The invisible flat reference surface Revit uses whenever you sketch or place something - by default it is tied to the current view or level, but it can be set explicitly to a face, a reference plane, or a specific grid to sketch somewhere other than flat and horizontal, like on a sloped roof or an angled wall.
Confusion about "why did that element go where I didn't expect" is very often a Work Plane problem in disguise - Revit placed the new geometry relative to whatever plane was active, not necessarily the one the user assumed. Understanding work planes explicitly is one of the fastest ways to stop fighting Revit's placement logic and start using it deliberately.
The mechanism inside worksharing that splits one central model into logical, independently-editable chunks - shell and core, interiors, site, MEP - so multiple people can work on the same file at once without constantly stepping on each other. Every element belongs to exactly one workset, and each user can choose which worksets are open and visible in their own session, which is also how a large, heavy model stays workable: closing worksets you don't need speeds up your local session considerably.
Worksets are about dividing ownership within one file; if you need to bring in a genuinely separate file, that is what Linked Models are for.
Central Model & Worksets
The terms every junior hears in week one on a real project. Worksharing is Revit's mode for letting a whole team work on one model at the same time: the project lives in a Central Model (on a server or in the cloud), each person works on a synced local copy, and changes flow back with "Synchronize with Central". Worksets split the model into logical chunks - shell, interiors, site - so ownership and visibility can be managed per team. If you ever wondered why file names end with "_Central" - this is why.
Instead of opening the Worksharing Monitor dialog to check who owns what, a modeler can toggle Worksharing Display directly in a 3D view or plan to see it painted across the actual geometry - useful for quickly spotting which parts of the model are actively being edited by teammates right now.
When a save-to-central is running slowly or a team member can't get an editing request granted, the Worksharing Monitor is the first place to check - it shows exactly who's connected, what they're borrowing, and whether the central model itself is under heavy load at that moment.