Maintenance
Nico · Product specialist · 33 s
Plan recurring maintenance, receive reports and follow up technicians or suppliers. Every intervention remains linked to the correct installation, manual, cost and history.
For property managers, technical services, owners and maintenance partners.
MaintenanceLess chasing and searching; better visibility into recurring problems and costs.
Design of the product explanation · not a live product demo. Features and package coverage must be confirmed before publication.
Meet Nico
From a reported issue to follow-up, starting with the building.
Explore a practical example
Maintenance
Product specialist
Calls and live chat are not available yet. Contact us for more information.
Contact usNico · Product specialist · 33 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: The resident, manager and supplier each have part of the story.
Your workflow: Link the report, lift record, work order and intervention.
The result: One traceable follow-up for the lift.
Today: Recurring dates are entered manually each time.
Your workflow: Set intervals and responsibilities for the installations concerned.
The result: Less calendar administration, with oversight of outstanding assignments.
Today: The inspector found a defect.
Your workflow: Link the approved repair assignment to the original finding.
The result: From finding to repair evidence without overwriting the initial condition.
The architect writes in Dutch. The contractor reads in Spanish. The reply and original stay with the same task.
Depends on configurationPhotos and spoken observations become a draft report with action points, roles and deadlines.
Planned AI enhancementYou: Record maintenance dates and intervals for each installation.
ObraPad helps: Recurring follow-up can use the configured schedule and reminders.
You: Record the problem, priority, photo and installation concerned.
ObraPad helps: The report remains linked to the installation and the building.
You: Bring the assignment, responsible person, instructions and deadline together.
ObraPad helps: Status and follow-up use the configured workflow.
You: Open the linked installation record and relevant documentation.
ObraPad helps: The same installation identity links the QR, documents and history.
You: Add the report, photos, parts used and relevant costs.
ObraPad helps: The installation record is supplemented with that information.
You: Set useful thresholds when a supported integration is available.
ObraPad helps: The roadmap provides for signals and proposed tasks in the correct building context.
You: Have the contractor link their intervention report and photos, and determine whether reinspection is required.
ObraPad helps: The work order can refer to a finding or inspection; acceptance and any reopening remain visible.
You: View recurring reports, parts, interventions and recorded costs together.
ObraPad helps: The asset overview brings the recorded events together; replacement advice still requires substantive assessment.
You: The manager describes the fault in their language; the technician reads the assignment and replies in theirs.
ObraPad helps: The original and translated view remain connected. Measurements, source references and important instructions are not silently changed.
You: Select the installation and work order, dictate the work carried out and link photos.
ObraPad helps: Planned AI assistance creates a draft with findings and proposed follow-up actions; the technician checks it before the assignment is closed.
Recurring maintenance dates, reminders and status overviews according to your settings.
With suitable AI: structure a fault description and prepare a work order.
Approve work, exceptions and costs within the permissions you define.
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.
Send the technician the location, manual and previous intervention separately.
Open one work order with the installation, documents and history.
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.
Installations · suppliers · documents · maintenance history. You continue with the same property context; you do not create a second record.
For example, dictate observations or have data extracted from an intervention report.
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 →The intention is to bring together the authorised assignment, installation data and relevant documents. They do not automatically see other properties or restricted information.
No. Execution, inspection and financial processing are separate steps. A status change is not a payment instruction.