Knowledge Base

Overview
Inspection & Test Plans

The AI Insights Panel

AI & Searchinsightsaibuilding codes
Carlos Greblo - Updated 10 Nov 2026

Where the project graph went

The node graph of requirements, ITP items, activities and BOM items is not part of an Insights document. It is the Basis diagram, at Project, then Basis, and it is on every plan including free: it is deterministic traceability over your own rows, so it must not go dark when an AI call fails or a subscription lapses. See "Reading the Basis Diagram".

Asking questions

The AI Insights panel alongside the graph answers free-text questions about the project (for example, "which BOM items are still backordered?") from that project's own Requirements, ITP, Programme, Cost and BOM text, plus the building code clauses described below. Every answer cites the specific rows it drew from as numbered sources, so you can verify the answer instead of taking it on faith. A source that is one of the project's own rows links back to that row; a building code clause links out to the issuing authority instead, and opens in a new tab so a streamed answer is not lost.

An answer in the AI Insights panel, with the project rows it drew from cited as numbered sources.

An answer in the AI Insights panel, with the project rows it drew from cited as numbered sources.

The panel also offers one-click suggestion buttons ("Find related requirements," "Find BOM items missing requirement/ITP/programme links") that surface candidate links to approve or dismiss, instead of requiring a typed question. Both the free-text answers and these suggestions are ranked so the most relevant rows surface first. See the "Finding Related Content" article for how that ranking shows up elsewhere in the app.

Building code clauses

An answer can also cite the building code, so a requirement can be read against the clause it is meant to satisfy rather than on its own.

Which codes are searched comes from the project's country, so an Australian project is answered against the NCC and a British one against the Approved Documents (a British project also gets the European clauses). Nothing about this is org-scoped: the clause corpus is shared reference data, like the Uniclass tables.

Clauses are capped and held to a minimum similarity, and they are added after the project's own rows have been ranked rather than competing with them. The intent is that an answer stays grounded in what the project says, with the code as the yardstick it is held against, so a well-worded clause cannot push out the requirement it is meant to be judging.

Two things a clause source does not do. It does not reproduce the clause text, because most codes cannot be republished: you get the clause reference, its title and a link to the authority that issues it. And it does not speak for the technical standards a clause references (AS, BS EN, ASTM): those are named, but their content is not available and the answer will not invent it.

Where a code states the distinction, a clause records whether it is a performance requirement or a deemed-to-satisfy provision, since meeting the second is one way of demonstrating the first.

Availability

Insights is a paid feature, available on both the Professional and Team plans. An org without it sees the other four document types as normal but won't have Insights documents to open.