Prevention & safety
Liv · Product specialist · 37 s
A working day with Prevention & safety · illustrative scenario
You do your work.
The context stays with you.
Track risks, measures and inspection evidence in different places. Explore how the intended workflow keeps the work together. This is an explanatory scenario, not a functioning customer environment.
01Assess the riskPlanned
YOUR ACTION
The authorised role records the risk and location.
THE SOFTWARE HELPS
The planned file links the relevant context.
WHAT THIS DELIVERS
One identifiable starting point.
02Follow up on the measurePlanned
YOUR ACTION
A responsible person and deadline are recorded.
THE SOFTWARE HELPS
The intended planning supports reminders and follow-up.
WHAT THIS DELIVERS
Visibility into what remains open.
03Verify the effectPlanned · expert assessment
YOUR ACTION
An expert reviews the evidence and reassesses the risk.
THE SOFTWARE HELPS
The planned history retains the link to the original risk.
WHAT THIS DELIVERS
No automatic declaration that it is safe.
04Finish with a clear resultYour review
YOUR ACTION
You review the recorded data and decide what is complete and what still requires follow-up.
THE SOFTWARE HELPS
The decision refers to the same source, task or file context; there is no silent copy to another workspace.
WHAT THIS DELIVERS
A clear status and a traceable next step.
Intended outcome: fewer separate risk lists and less follow-up administration.
Automation remains dependent on configuration and available features. No real message, document or instruction is processed here.
Meet Liv
Prevention & safety
Concerns and follow-up stay connected to the building.
Explore a practical example
Liv
Prevention & safety
Product specialist
Calls and live chat are not available yet. Contact us for more information.
Contact usWatch 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.
