Interactive practical example · simulation

From construction site to handover

An observation becomes useful information for the next phase. You explore how it works; no real data is processed and no actions are carried out.

01Observation

A note from the construction site gains context.

An architect notes that the finish in a space needs extra attention. The photo and note remain linked to the same project space.

Example: space W2 · finishing item.

02Document

Work from the correct source.

The relevant plan and its corresponding revision are associated with the item as its source. A new upload is not automatically an approved revision.

Source and revision remain separately visible.

03Follow-up

The person responsible knows what is needed.

An action item contains the relevant photo, space and document reference. Assessment remains with the authorised stakeholders.

This example does not create a real task or work order.

04Evidence

Keep a record of what was assessed.

Completed follow-up is documented with a report or photo. A completion screen does not replace substantive review.

Draft, assessed and verified are different states.

05Handover file

The story does not end with construction.

Selected, relevant project information is prepared for the building passport of the owner or manager.

Digital file transfer is not a legal transfer of ownership.

The same property, a different perspective.

These examples illustrate the intended connections. They are not proof of production functionality.

Help me continue

Meet Lucas

Construction

A plan becomes a building. Its information grows with it.

Explore a practical example

Lucas

Construction

Product specialist

Watch the practical example

Construction

Lucas · Product specialist · 36 s

Open the video

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.