Prevention & safety
Liv · Product specialist · 37 s
Organise risks, inspections and improvement actions, as well as emergency plans, work procedures, training and drills. Everyone finds the correct reviewed instruction, in the correct language and for the correct building. This Prevention implementation is planned.
For prevention advisers, safety managers and building or site managers.
Prevention & safetyIntended outcome: fewer separate risk lists and less follow-up administration.
Product explanation design · no live product demo. Features and package coverage must be confirmed before publication. This workspace is planned and not yet available.
Meet Liv
Concerns and follow-up stay connected to the building.
Explore a practical example
Prevention & safety
Product specialist
Calls and live chat are not available yet. Contact us for more information.
Contact usLiv · Product specialist · 37 s
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.
The pilot direction is to begin with one workspace and add more later.
The planned flow activates Construction only for the building being renovated; other buildings stay unchanged.
The access model is being developed so an installer or partner can use only the selected building, installation or task.
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.
Today: A hazard is reported, but the measure remains unclear.
Your workflow: Link the location, risk, owner of the measure and required inspection.
The result: The planned workflow makes the follow-up request specific.
Today: A measure is marked complete without verifiable evidence.
Your workflow: Refer to the inspection and have the authorised person assess the evidence.
The result: Completed action and verified result remain distinct.
Today: Emergency plans, contact roles and instructions are scattered and not all current.
Your workflow: Link the approved procedure to the building, schedule a drill and assign reviewed improvement items.
The result: A traceable cycle of preparation, drill, follow-up and update. Planned product flow.
The architect writes in Dutch. The contractor reads in Spanish. The reply and original stay with the same task.
Depends on configurationKeep approved plans, instructions, drills and follow-up linked to the same building.
Planned Prevention developmentYou: Describe the risk, location, people involved and assessment.
ObraPad helps: The planned structure links the risk to the property and work context.
You: Link actions and inspection points to the risk.
ObraPad helps: The intended follow-up follows recorded rules and schedules.
You: Use a targeted inspection of the building, workplace or site.
ObraPad helps: Findings must be able to flow into measures and evidence.
You: Record deadlines and recurring inspection times.
ObraPad helps: Reminders are intended to follow those configured times.
You: Link plans, instructions, reports and relevant evidence.
ObraPad helps: The same source documents remain linked to their context.
You: Assess the evidence and reassess the risk after the measure.
ObraPad helps: The intended loop keeps risk, inspection, action and verification together.
You: Record the parties involved, work zones and agreed measures, and refer to the correct execution or inspection flow.
ObraPad helps: The planned layer coordinates risk, action and evidence; it does not replace separate inspection execution or technical authority.
You: Record an event, observation and follow-up request, and have the authorised person reassess the risk picture.
ObraPad helps: The event must refer to the risk, measure and evidence without automatically establishing causes or blame.
You: Discuss a risk or inspection point with contractors in their own language, using the approved instruction as the source.
ObraPad helps: The original and translated view remain connected. Measurements, source references and important instructions are not silently changed.
You: Link the emergency plan, building, current plan version, contact roles and approved instructions.
ObraPad helps: The planned product flow shows the source version and relevant information by role; AI can prepare a draft, not approve an emergency plan itself.
You: Manage steps, evidence requirements, applicable installations, authorised operators and review times.
ObraPad helps: The shared procedure building blocks support version management and role-based execution; publication requires content review.
You: Manage the approved layers for routes, exits, assembly points and emergency equipment.
ObraPad helps: The planned plan layer refers to the same building objects and associated inspections. AI does not invent a route during an incident.
You: Schedule an instruction session or drill and record participants, observations and follow-up.
ObraPad helps: Reminders and reviewed action items can be followed up according to authorised rules. Participation is not automatically a declaration of competence.
You: An authorised coordinator opens the correct procedure and follows the roles, confirmations and actions involved.
ObraPad helps: Planned notifications, role assignments and logging follow the explicit mandate. Received, read and executed remain different statuses.
Intended: scheduled inspections and follow-up of measures according to configured rules.
Intended: AI helps structure observations and prepare possible measures.
Risk assessment, suitability of measures and formal safety review remain with authorised experts.
You define your workflow and boundaries. Routine can follow those rules; AI helps with preparation; exceptions remain visible. The capabilities you use depend on the available features and your plan.
Maintaining risks, measures and inspection evidence in different places.
In the planned model, follow one loop: risk → measure → inspection → evidence → reassessment.
Formula: number of tasks × (minutes now − minutes after the change) ÷ 60.
20 tasks × (15 − 10 minutes) = 100 minutes, or 1 hour and 40 minutes per month.
This is fictitious input, not a predicted product saving. Include checks and any additional actions. A negative result means additional time.
The editable calculation is available when this presentation is opened with JavaScript. Time freed up does not automatically represent a realised cost saving.
Risks · inspections · actions · verification evidence. Continue with the same property context; do not create a second file.
Any extensions follow workspace availability. A planned feature does not become available automatically through an add-on.
An add-on already included in your plan is not offered again. The exact features, limits and any additional price are shown with your configuration.
Workspaces and add-ons explained →No. In this presentation, Prevention & Safety is explicitly planned. The explanation describes the direction, not an already released or certified product.
No. The planned prevention layer connects risks, measures and evidence. Inspection execution and authorised technical or safety assessment remain separate responsibilities.
AI may help structure a draft using controlled sources. The content must be assessed by authorised experts for the building and country. The software provides no general legal approval guarantee.
No. The design requires accessible, current and reviewed instructions. Offline or paper availability and alarm arrangements are organised and tested separately; the preview does not provide a real emergency facility.