In a BIM project, completing the 3D model does not mean the BIM process has come to an end. The real value of BIM lies in the data and deliverables created, checked, and handed over throughout the project lifecycle.
A BIM project can generate various types of data, including Revit Models (RVT), IFC, DWG, PDF Drawings, Point Clouds, Schedules, QA/QC Notes, and more. Each serves a specific purpose, but all need to be linked to the Central BIM Model – the project’s single source of truth.

BIM Deliverables are the collection of models, drawings, data, and documents created and handed over throughout the BIM process.
Deliverables do not only appear at the final handover stage. Throughout the project lifecycle, they are continuously created and updated — from site surveying, design, BIM coordination, technical development, construction, and QA/QC to handover and operations.
The overall workflow can be summarized as: Capture Site → Build Model → Coordinate & QA → Create Deliverables → Share & Publish
The key is to manage all deliverables consistently to ensure they are in the right version, right status, and available to the right stakeholders.
RVT is typically the native BIM model developed in Revit. It can include architectural, structural, and MEP elements, along with the geometry, materials, and technical parameters of the building. The model also contains Families and properties associated with individual objects.
RVT is commonly used throughout the Design → Coordination → Clash Detection → Documentation workflow and serves as an important data source for generating other deliverables.
However, not all project stakeholders use Revit. Therefore, handing over only RVT files may not be sufficient to ensure data exchange and usability across different teams and software platforms.
IFC (Industry Foundation Classes) is an open data format used to exchange BIM information between different software applications.
For example: Revit → IFC → BIM Coordination Platform → Other BIM Software
IFC is particularly useful when a project involves multiple stakeholders using different software platforms.
Therefore, IFC is often an important deliverable for projects that require interoperability.
Although BIM focuses on models and data, PDF remains an important deliverable in many construction projects. A PDF drawing package may include floor plans, sections, elevations, technical details, construction drawings, and sheet sets.
PDFs are commonly used for Review → Approval → Construction → Print & Share, especially when drawings need to be shared or used outside the BIM environment.
An important requirement is that PDFs should be generated from the correct version of the model that has been checked and approved. If the model has been updated but the PDF still uses an older version, inconsistencies may occur between the Model and Drawing, potentially causing confusion during construction and coordination.
DWG continues to play an important role in many design and construction workflows. DWG files can be exported from BIM Models to support 2D drawings such as Layouts, Plans, Elevations, Details, and Sections, while also facilitating data exchange with teams using CAD.
In practice, many projects still operate with both BIM Models and CAD Drawings. Therefore, BIM does not necessarily have to replace CAD. The key is to keep data across different formats synchronized and consistently managed.
One of the major benefits of BIM is the ability to extract data directly from the model. Schedules can provide information such as Door Schedules, Window Schedules, Room Schedules, Equipment Schedules, Material Takeoffs, and Quantity Information.
Instead of manually compiling information from multiple drawings, data can be extracted directly from objects within the BIM Model, making the process faster and more consistent.
The workflow can be simplified as: BIM Model → Schedule → Quantity Takeoff → Cost / Procurement.
This helps reduce manual data entry and minimize errors during quantity takeoff and reporting.
QA/QC Information is an important part of BIM Deliverables, helping ensure that the model meets quality and consistency requirements before it is shared or published.
The checking process may include Clash Detection, Model Review, Data Validation, Naming Convention, Model Structure, as well as checks for missing or invalid information.
Issues identified during the checking process can be recorded as QA/QC Notes or Issues. For example, a Door may be missing its Fire Rating information, or an MEP Pipe may clash with a Structural Beam.
These Issues should be recorded, assigned to responsible parties, tracked, and updated until they are resolved and closed. This makes the QA/QC process more transparent and easier to manage.
For renovation, refurbishment, or Scan-to-BIM projects, Point Cloud can be an important deliverable, providing detailed and accurate visual data about existing building conditions.
Point Clouds can be generated using technologies such as Laser Scanning, LiDAR, Drone Scanning, or 3D Scanning.
The workflow can be summarized as: Existing Site → Laser Scan → Point Cloud → BIM Modeling → As-built Model.
Point Cloud serves as an input data source for the BIM Team, helping create more accurate existing-condition models while reducing reliance on manual measurements.
For existing buildings in particular, Point Cloud can become one of the most important deliverables and data sources from the early stages of the project.
Looking at each file type individually can make a project seem increasingly complex.
A project may contain multiple deliverables at the same time, including RVT + IFC + DWG + PDF + Point Cloud + Schedules + QA/QC.
The challenge is not the number of files, but rather: How can we ensure that all deliverables are generated from the correct data source and the correct version?
This is where the Central BIM Model plays an important role.
The Central Model can be considered the Single Source of Truth — the central data source used by project stakeholders to coordinate their work and generate different deliverables.
The overall concept can be illustrated as follows:
CENTRAL BIM MODEL
Single Source of Truth
│
┌─────────┬───────┼───────┬─────────┐
↓ ↓ ↓ ↓ ↓
RVT IFC DWG PDF Schedules
↓
QA / QC Notes
When the model is updated, the related deliverables should also be version-controlled and kept aligned with the corresponding model version.
A common mistake is to view BIM Deliverables simply as a list of files to be handed over, such as 01 RVT + 01 IFC + 20 PDFs + 05 DWGs. However, this approach does not fully reflect the value of BIM or its information management requirements.
Each deliverable should be associated with information such as the creator, checker, version, status, issue date, and intended use. It is also important to clearly define who has access and which version is the latest.
Therefore, BIM Deliverables are more than just files being handed over. They are a combination of data + processes + information control, ensuring that the right information, in the right version, reaches the right people at the right time.
A basic workflow can be implemented in four steps:
Collect existing-condition data using:
Laser Scan / Drone Scan / Point Cloud
Develop the BIM Model using Revit or other suitable BIM tools.
Perform:
Create and publish:
RVT → IFC → DWG → PDF → Schedules → QA/QC
This workflow helps ensure that deliverables are generated from a validated and controlled data source, rather than being issued as disconnected files.
As the number of files and project stakeholders increases, managing information through email, Google Drive, or personal folders becomes increasingly difficult to control. This is where a Common Data Environment (CDE) becomes important.
A CDE helps organize project information through a workflow such as: WIP → Shared → Published → Archived
For example:
WIP: The BIM team is developing and checking the model.
Shared: The model is shared with relevant stakeholders for coordination.
Published: The deliverable has been checked and officially issued.
Archived: Previous versions and historical project information are preserved.
As a result, users do not only know where a file is located, but also know: Which file is currently being used? Which file has been approved? Which file is an older version?
Proper management of BIM Deliverables can provide several key benefits:
Drawings, models, and schedules are managed and controlled based on a consistent data source.
Different disciplines can use IFC, RVT, and other appropriate formats to exchange information effectively.
Schedules and quantity data can be extracted directly from the model, reducing repetitive manual processes.
Helps prevent teams from accidentally using outdated drawings or models.
Well-structured BIM data can continue to support the As-built and Facility Management stages throughout the building lifecycle.
BIM Deliverables are more than just RVT, IFC, PDF, or DWG files. They represent the entire information system created, checked, shared, and issued throughout the BIM project lifecycle.
An effective BIM workflow should ensure a connected process from Capture → Model → Coordinate → QA/QC → Deliver → Manage. The Central BIM Model serves as the central data source, while the CDE helps control the storage, sharing, approval, and publication of project deliverables.
When BIM is viewed not simply as a 3D model, but as an information management system, BIM Deliverables can create real value across design, coordination, construction, and facility operations.
👉 BIMCAD Vietnam provides BIM/CAD and CDE solutions that help construction companies manage models, data, and deliverables in a centralized, consistent, and efficient environment.






