Compliance Dashboard

Tracking observed reality against project expectations.

Expectation vs. Reality

Verified Pending Missing

Asset Requirement (Expectation)	Claimed Reality (Uploaded)	Status

Active Findings

0

Remediation loops for missing and non-conforming data.

Project Setup

Who this project is, and when it is due. The handover date is what gives every expectation a delivery date.

Project header

Project name

Taken from the register on a pull, if the register names a building.

Owner / appointing party

Project number

Target handover date

Space numbering authority

Whose room numbers win when two parties disagree.

What this changes

Setting a handover date dates the ledger. Until there is one, expectations are tracked but nothing can be reported as late — a deadline nobody agreed is not a deadline.

Expectations—

Without a delivery date—

Spaces in the register—

Of those, rooms—

Data Exchange Map (EXC)

Define what data is owed, by whom, and when across the project lifecycle.

Expectations

Exchange	Artifact Owed	Responsible Party	Delivery Phase	Format	Due	Status

Systems Inventory (SYS)

Every system holding project data, spreadsheets included. Ranked by connector priority — the API column decides whether a connector is even possible, and the closeout column decides whether the owner keeps their data.

Rank	System	Vendor	Category	Owned By	API	Access Ends at Closeout	Exchanges

Ingestion Inbox

Drop any deliverable. It is checked on arrival against locatability, classification, identity and relationship rules, and itemized results come back in seconds.

Itemized Conformance Findings

0 findings

Severity	Rule	Entity	Finding & Remediation
Upload a deliverable to see findings.

Assertion Log

Entity	Property	Value	Source Surface	Suitability
Assertion log empty.

Document Register

Everything delivered, and what it is about. A document attached to nothing cannot answer a question about a room or a machine, which is the point of keeping it.

Documents

Document	Div	Category	Filed against	About

Documentation Coverage

What the register holds against what was delivered — in both directions. Equipment with no documents behind it, and documents for work that was never registered.

By CSI division

Div	Expected	Components	Documents	O&M	Warranty	Gap

COBie Readiness

COBie is the spreadsheet an owner hands to their facilities team at the end of a job. This is how much of yours could be filled in today, and what stands in the way of the rest.

Missing, and not on anyone's list

0

COBie needs these to hand over a complete record, and nothing in your Data Exchange Map asks a contractor to provide them. So nobody is late and nobody can be chased — these stay blank until somebody is made responsible for them. Add one to a requirement and it moves to the list below, with a name against it.

Sheet	Field	Blank on	Would come from

Missing, and somebody owes it

0

A requirement asks for these and they have not arrived. There is somebody to go back to.

Sheet	Field	Blank on	Would come from

Every sheet

Sheet	Rows	Fields COBie needs	State

Document Resolution

Which asset is this document about? Model checkers validate what is in a model and delivery trackers record that a file arrived. Neither can say which pump a warranty covers.

Work by division

Div	Left	Progress

Select a division

Pick a division on the left. Divisions with no components are register gaps, not resolution work — there is nothing there to attach to.

Conflict Resolution Queue

The system never decides who is right. An Information Authority declares precedence, and the superseded claims stay readable.

The Asset Record

Verified, structured data ready for operations. Outlives the appointment.

Spatial Hierarchy

—

Provenance Inspector

Select an asset to see every claim made about it and where each came from.