Does a valid COBie workbook guarantee owner acceptance?

No. Structural and relationship checks are necessary, but the owner's asset scope, naming rules, receiving system, and contractual acceptance tests still determine whether a delivery is accepted.

Can BIMRelay validate project-specific requirements?

Yes. Teams can mark columns as required and configure workbook rules in addition to the COBie-specific validation behavior.

What happens to findings after the Revit models change?

BIMRelay creates a new workbook version from current model evidence, preserves matching manual edits, and evaluates the resulting workbook again.

COBie quality control

Validate COBie before handover.

Find missing values, broken references, invalid PickList values, and project-specific gaps before the COBie XLSX reaches the owner.

Join the waitlist

COBie validation findings in BIMRelay — Findings stay beside the workbook cells and current version that produced them.

In short

What does BIMRelay check?

BIMRelay checks required values, controlled values, unique identifiers, and relationships between COBie worksheets. Each validation finding stays beside the affected cell so the responsible collaborator can understand and resolve it in the shared workbook.

Check structure and completeness

BIMRelay generates the standard COBie 2.4 sheets and columns, then checks unique row identifiers, required values, dates, numbers, maximum lengths, and controlled PickList values. Findings stay in the same workspace where the team edits the data, removing the need to audit one spreadsheet and correct another.

COBie requirements also depend on the delivery milestone and contract. BIMRelay can distinguish baseline COBie behavior from fields a project chooses to mark as required, so blank values become actionable findings only under the rules that apply to that delivery.

Validate relationships across worksheets

COBie behaves like a relational dataset. A Component can look complete but still be unusable when its Type or Space does not exist. A CreatedBy value can fail when no matching Contact is present. BIMRelay checks these references and keeps each problem attached to the affected workbook location.

Relationship validation is particularly important after source models change. Regeneration refreshes model-backed rows, then the project can review any new or changed findings against the current workbook version.

Resolve findings collaboratively

Validation is a coordination workflow, not a final button click. BIMRelay gives editors a shared grid, model context, cell presence, comments, and issue status so the person who understands a value can correct or explain it without passing spreadsheet copies between teams.

A technically valid workbook can still fail an owner's operational test. BIMRelay supports the checking process, but the contract, asset scope, receiving system, and owner acceptance criteria remain authoritative.

Buyer questions

Frequently asked questions

Does a valid COBie workbook guarantee owner acceptance?: No. Structural and relationship checks are necessary, but the owner's asset scope, naming rules, receiving system, and contractual acceptance tests still determine whether a delivery is accepted.
Can BIMRelay validate project-specific requirements?: Yes. Teams can mark columns as required and configure workbook rules in addition to the COBie-specific validation behavior.
What happens to findings after the Revit models change?: BIMRelay creates a new workbook version from current model evidence, preserves matching manual edits, and evaluates the resulting workbook again.