What Is COBie?

COBie facility data is a standardized way to organize building information so it can be handed from design and construction teams to owners and facility managers in a usable format. Instead of burying equipment details, room names, warranty notes, and maintenance data inside many separate files, COBie puts key handover information into a structured dataset that can be reviewed, imported, and managed over time.

If you are planning a project, reviewing as-built deliverables, or trying to understand what should come at closeout, COBie is worth knowing because it sits between drawings, BIM models, and facility operations. In California, that matters on everything from tenant improvements and commercial renovations to multifamily upgrades, campus work, and public projects where owners want cleaner turnover data. FastAsBuilt focuses on field-measured as-built drawings and measured floor plans, but many clients also need to understand how those drawing packages connect to broader data and BIM requirements.

What COBie means in practice

COBie stands for Construction-Operations Building information exchange. In plain English, it is a method for delivering facility information in a consistent structure so owners do not have to retype everything after construction is complete. The goal is not just to provide drawings or a model, but to provide organized information about spaces, systems, and assets that operations teams can actually use.

A COBie deliverable commonly includes details such as:

• Facility and floor names
• Room or space identifiers
• Equipment and component lists
• Manufacturer and model information
• Serial numbers where applicable
• Installation and warranty information
• Maintenance-related attributes
• Documents linked to assets or spaces

Think of COBie as a data framework, not a visual drawing type. A floor plan shows walls, doors, and dimensions. A COBie file helps answer questions like: What air handler is installed in this building? Which room does it serve? What is its model number? Where is the O&M manual? When does the warranty expire? That is why COBie facility data is often discussed alongside BIM handover, digital twins, and owner closeout requirements.

Why owners ask for COBie facility data

Owners ask for COBie because turnover information is often fragmented. One consultant may provide CAD plans, another may issue product binders, and a contractor may submit separate closeout PDFs. Without a structured handover, facility teams spend significant time hunting for information or recreating asset lists manually.

COBie gives owners a more usable bridge from project delivery to operations. It can support:

• Facility management software setup
• Asset tracking and preventive maintenance
• Space management
• Capital planning
• Warranty and replacement planning
• Portfolio-level standardization across multiple sites

For California property owners, this can be especially useful when managing geographically spread facilities, mixed building types, or phased renovations. For example, a school, healthcare group, municipality, or multifamily owner may have recurring turnover needs across many buildings. Standardized COBie facility data makes those handoffs more consistent, even if the underlying design teams change from project to project.

It also helps separate two deliverable questions that owners sometimes blend together: what the building looks like, and what the building contains. Visual records often come from measured plans, point clouds, or BIM. Operational records come from structured data. Both matter, but they are not the same thing.

How COBie relates to BIM, CAD, and as-built deliverables

COBie is often associated with BIM, but it is not the same as a BIM model. A BIM model is a digital representation of building geometry and related information. COBie is a subset of building information organized for handover and operations. You can think of BIM as the richer container and COBie as one structured output focused on usable owner data.

This distinction matters when reviewing scope. A client may ask for “BIM” when what they really need is a set of dependable as-built deliverables plus asset and space data. Another client may ask for COBie when they also need accurate plans, elevations, and sections to support future renovations. Before ordering work, it helps to understand the difference between what as-built drawings are and what a data handover includes.

COBie also differs from typical CAD deliverables. CAD files such as DWG and DXF are drawing formats used to draft and edit geometry. If you are comparing DXF vs. DWG or trying to sort through common as-built file formats, you are dealing with drawing exchange, not necessarily facility management data structure.

At FastAsBuilt, our core service is field measurement followed by permit-ready CAD files in PDF and DWG. For some projects, that is the full need. For others, those plans become a foundation for additional BIM or owner data workflows handled by the wider project team. If you need measured plans, you can review options on our packages page.

What information COBie usually contains

Although requirements vary by owner and contract, COBie typically organizes information into repeatable categories. Exact field names and level of completeness may differ, but the structure usually covers the building from high level to component level.

Facility and floor information

This includes the overall building identity and how floors are named and organized. It gives an owner a consistent framework for locating information inside the property.

Spaces and rooms

Rooms, units, suites, common areas, and service spaces may be identified with names, numbers, and classifications. This matters for maintenance routing, occupancy planning, and future renovations. In an existing building, space accuracy often depends on reliable field verification and current as-built documentation.

Systems, types, and components

COBie may separate broad system types from individual installed assets. For example, similar pieces of equipment may share a type record, while each actual unit has its own component record with identifying details.

Documents and attributes

Supporting files can be associated with specific assets or spaces, such as cut sheets, manuals, commissioning records, and warranty material. Attributes may include installation dates, expected service life, capacity, or manufacturer details.

Because COBie is structured, it is easier to import into owner systems than a stack of disconnected PDFs. That does not mean every project includes every possible field. A good handover starts with a clear owner standard stating what must be captured, who is responsible for it, and how it will be validated.

What COBie is not

COBie is often misunderstood, especially by teams that are new to digital closeout requirements. It is not a substitute for every other deliverable on a project, and it does not automatically guarantee accurate information just because a spreadsheet or export exists.

COBie is not:

• A full 3D model by itself
• A replacement for permit-ready as-built plans
• A laser scan or point cloud format
• An automatic proof that all equipment data is correct
• A single universal file that solves every facilities workflow

It also should not be treated as a magic export button. If the underlying model, submittal data, or field verification is incomplete, the COBie output will reflect those gaps. That is why accurate source information matters. On existing buildings, reliable field measurement often comes first. On new construction, close coordination between designers, contractors, and owner teams matters just as much.

If your team is also looking at scan-based workflows, it helps to understand related concepts like scan-to-CAD or when a Revit as-built model makes sense. Those are production methods or model types, while COBie is a handover data standard.

How COBie shows up on real projects

In real-world projects, COBie facility data usually appears as a contract requirement or owner standard rather than a casual add-on. Public agencies, institutional owners, and sophisticated private owners are the most likely to require it, especially when they already use computerized maintenance or asset management systems.

Common situations include:

• New construction with formal digital closeout requirements
• Large renovations where equipment is being replaced or added
• Campus or portfolio work needing consistent asset records
• Healthcare, education, civic, or corporate facilities with in-house operations teams
• Projects where BIM execution plans define owner handover expectations

In California, the exact requirement usually comes from the owner, architect, agency, or project manual rather than from a blanket statewide rule requiring COBie for every building. Local public agencies and institutional owners may have their own standards. Private developers may request simpler closeout packages with plans and manuals only. That is why scope review matters early. If COBie is required, confirm the template, required fields, naming conventions, and acceptance process before production starts.

For existing buildings, one challenge is that installed conditions may not match old record drawings. That is where fresh field measurement and current as-built plans help establish the geometry and room framework before downstream data is organized.

How COBie connects to measured plans and field verification

Even though COBie is about data, it depends heavily on trustworthy building information. Space names, room numbers, floor layouts, and asset locations all become more useful when they are tied to accurate existing conditions. If the base plans are wrong, the owner inherits confusion in both drawings and data.

FastAsBuilt’s process is straightforward: local crews perform on-site laser measurement, then senior drafters produce permit-ready CAD files in PDF and DWG. That service is often the first practical step in documenting an existing California property. Our 2D As-Built Plans start at $900 for up to 1,500 square feet, then $0.50 per square foot, include one revision, and are typically delivered in 48–72 hours. Our 3D As-Built Plans start at $1,500, then $1.00 per square foot, include a 3D model plus 2D floor plans, elevations and sections, include two revisions, and are typically delivered in 3–5 business days.

Turnaround times are estimates and may vary based on project complexity and scheduling.

Those measured plans are not the same thing as COBie, but they often support the same owner goals. A clean set of current plans can help teams:

• Confirm room naming and numbering
• Locate assets within the right spaces
• Coordinate renovation design
• Build or validate BIM content later
• Reduce confusion at handover

If you are evaluating broader digital outputs, it can also help to review what 3D as-built deliverables usually include so you can separate geometric deliverables from operations data.

Common COBie challenges and how to avoid them

Most COBie problems are not software problems first. They are scope, responsibility, and data quality problems. Teams often discover too late that they never agreed on what had to be captured, who would supply it, or how it would be checked.

Unclear owner requirements

If the owner has not defined required fields, naming rules, or software import expectations, teams may produce a technically formatted file that still fails owner review. Start by confirming the owner standard.

Incomplete source data

Missing serial numbers, unverified room names, or inconsistent equipment tags can make a COBie export less useful than expected. The handover is only as strong as the information collected during design, procurement, installation, and closeout.

Confusing model detail with useful handover data

A highly detailed model does not automatically produce good facility data. Many owners care more about complete, consistent, searchable asset records than they do about visually rich geometry.

Late coordination

When COBie is treated as an end-of-project paperwork task, important information is often hard to recover. It is better to plan capture responsibilities from the start, especially on large or phased jobs.

For existing buildings, another common issue is trying to attach structured data to outdated drawings. If the geometry is stale, the handover framework may need to be rebuilt from current field conditions before the data becomes dependable.

COBie, compliance, and California project planning

COBie itself is not the same as California code compliance. It does not replace plan requirements for permits, life safety coordination, accessibility review, or energy compliance. You may still need separate documentation for Title 24, local building department review, or project-specific approvals. If your work involves ADUs, SB 9 lot split development, tenant improvements, or multifamily upgrades, always confirm documentation expectations with the local jurisdiction and the project professionals handling permits.

That same caution applies when owners are dealing with broader property obligations such as balcony or exterior elevated element inspection laws like SB 721 and SB 326, or with local historic and tax-related considerations like the Mills Act. Those frameworks may influence documentation needs, but they do not turn COBie into a universal compliance document. It is best understood as an operations-focused handover structure.

In practice, California owners often need several layers of documentation at once:

• Measured existing-condition plans for design and permit work
• CAD or BIM files for consultant coordination
• Construction closeout records for installed products and systems
• Structured facility data if the owner’s operations platform requires it

Understanding that stack helps prevent scope gaps. COBie supports operations. Permit-ready plans support design review and construction documentation. BIM may support coordination, visualization, and data hosting. They are related, but not interchangeable.

How to ask for COBie and related deliverables clearly

If you think your project may need COBie, the best move is to define the outcome instead of just naming the acronym. Different teams use the term loosely, and that can lead to mismatched expectations.

When scoping the work, ask questions such as:

• Is COBie actually required by the owner contract or agency standard?
• What template or format must be used?
• Which spaces and assets must be included?
• What attributes are mandatory?
• Who is responsible for collecting and validating each data field?
• Will the owner import the file into a facility management platform?
• Are current measured plans or a BIM model needed first?
• What are the required as-built deliverables in addition to COBie?

This last point is important. Owners should state whether they expect PDFs, DWGs, model files, elevations, sections, asset schedules, linked documents, or point cloud references. Teams sometimes use “as-builts” as a catch-all phrase, but the actual package can vary widely by project type and budget.

If you are comparing data handover to model exchange, you may also want to read about what an IFC file is. IFC is another concept people often encounter in BIM discussions, but it serves a different purpose from COBie.

Frequently asked questions

Is COBie a file format?

Not exactly in the everyday sense of a drawing format like DWG or PDF. COBie is better understood as a standardized data structure for facility handover. Teams may exchange it through spreadsheets or software exports, but the key idea is the organization of the data, not just the file extension.

Do all as-built drawings include COBie facility data?

No. Most as-built drawing packages do not automatically include COBie. Standard measured as-builts usually focus on geometry and documentation of existing conditions, such as floor plans, elevations, sections, and CAD files. COBie is a separate operations-focused deliverable that must usually be requested and defined in the project scope.

Can COBie be created from existing buildings?

Yes, but the quality of the result depends on the available information. For existing properties, teams often need current field-verified plans, room data, and asset information before structured handover data can be assembled reliably. If older record drawings are inaccurate, fresh measurement may be needed first.

Is COBie the same as BIM?

No. BIM is a broader digital building information approach that can include geometry, data, relationships, and coordination logic. COBie is a specific way of organizing certain owner-relevant data for handover and operations. A BIM model may be one source of COBie information, but the two terms are not interchangeable.

When should a project ask for COBie?

Usually when the owner has a clear plan to use structured asset and space data after turnover. That is most common on institutional, public, campus, healthcare, corporate, and other professionally managed facilities. If the owner only needs permit-ready measured plans or standard closeout documents, a full COBie requirement may be unnecessary.

Bottom line

COBie facility data is a practical handover standard that helps owners receive organized information about spaces, assets, and maintenance-related records instead of disconnected closeout files. It is not a substitute for measured as-built drawings, CAD file formats, or BIM models, but it works alongside them. If your California project needs dependable existing-condition documentation first, FastAsBuilt provides field-measured as-built drawings and measured floor plans across Southern California, the Bay Area, and San Diego, giving your team a solid base for whatever the next deliverable needs to be.