Building passport

A record that keeps growing.

The digital building passport brings building information, documents and history together. What is created during construction, management and maintenance remains recognisably linked to the property.

What does this mean for your work?

Documents, maintenance and inspections stay in context.

The examples show the product setup. Planned features, package coverage and real connections remain labelled separately.

Meet Sofia

Buildings & building passport

All the information about a building in one familiar place.

Explore a practical example
Sofia

Sofia

Buildings & building passport

Product specialist

Contact us

Watch the practical example

Pilot direction: start with one workspace and expand later.

ObraPad is designed to keep Obra Core as the shared foundation while you add capabilities over time.

Building-specific activation and restricted installer access are being prepared for the pilot and verified end to end. Ask which scopes can currently be tested.

Intended starting point

The pilot direction is to begin with one workspace and add more later.

Planned per-building expansion

The planned flow activates Construction only for the building being renovated; other buildings stay unchanged.

Planned access model

The access model is being developed so an installer or partner can use only the selected building, installation or task.

Intended example: heat pump maintenance

In the intended scenario, the installer only accesses the heat pump, its documents and assigned maintenance tasks in one building. Other buildings, financial information and private documents remain outside the scope. View, change, duration and revocation controls must be proven server-side before availability.

The design keeps an additional workspace and partner access as separate choices, with the building passport as the shared foundation.

Help me choose