For building owners, accountable teams & managing agents

Know where the evidence belongs.

When drawings, asset records and inspection reports sit in different places, even a simple building question can take hours to resolve. Scope a spatial view that helps your team find the source and see what still needs checking.

A proposed sector pilot, scoped around your information and reviewers.

Illustrative evidence journey

Find the location A floor, riser, space or asset
Open the supporting record Source reference, revision and owner
Identify what needs review Missing information and unresolved questions

A proposed information workflow, not a building-safety certification.

A building record should help someone answer a building question.

01 / The task

Find the right location

Asset names, drawing references and everyday descriptions do not always match.

Our approach: Connect the agreed spaces and assets to recognisable model context.

02 / The task

Check the source

A file can look current even when its revision, owner or review status is unclear.

Our approach: Expose the agreed source reference and revision beside the relevant location.

03 / The task

Make gaps visible

Missing evidence is easy to lose in a long document list.

Our approach: Record missing sources and review questions for the responsible team to resolve.

Start with one building area and one evidence question.

Inputs

What we review together

An available model or suitable drawings, a sample of the relevant records, an agreed asset list and someone authorised to review the information.

Deliverables

What the pilot produces

A navigable example linking selected spaces and assets to source records, plus a list of gaps and review decisions for your team.

Measures

How we judge usefulness

Time to find the correct source, whether the reference and revision can be identified, and how many information gaps the review exposes.

The pilot helps organise and retrieve information. It does not certify the building, verify an installation, provide a safety-case sign-off or establish regulatory compliance.

Timing, cost, approved hosting, access controls, review responsibilities and ongoing updates are agreed after the source review. No project files are needed for the first conversation.

Questions to settle before starting

Who checks the information?

Your appointed reviewers remain responsible for approving source content and resolving technical questions. The proposal should identify who reviews each source, how decisions are recorded and what remains outside scope.

Can this become our whole building record?

A pilot starts with a defined information question. Portfolio coverage, ongoing document control and integration with existing systems require a separate scope and maintenance plan.

Have you demonstrated this workflow in our sector?

The public worked example on this site is a data-centre demonstration. The sector workflow described here is a proposed pilot. We will discuss relevant project experience, the evidence you need and the limits of the scope before any commitment.

What does your team need to know?

Tell us a little about your site. We’ll discuss the problem, the information you have and whether a focused pilot would help.

A sentence is enough. Please don’t include sensitive site or personal information.

Name, email and organisation are required. We’ll use these details to respond to your enquiry. No newsletter signup. Privacy & terms.