Inspection
Kai · Product specialist · 29 s
A working day with Inspections & condition reports · illustrative scenario
You do your work.
The context stays with you.
At every handover, describe the spaces again, store photos separately and later gather meter readings, keys and comments. Explore how the intended workflow keeps the work together. This is an explanatory scenario, not a functioning customer environment.
01Prepare the check-inAccording to configured rules
YOUR ACTION
You select the rental unit, inspection date and people involved.
THE SOFTWARE HELPS
The permitted property and contract data form the starting point.
WHAT THIS DELIVERS
No second rental or building file.
02Record each space in turnAccording to configured rules
YOUR ACTION
You select existing spaces or add to the structure; you record condition, inventory and photos.
THE SOFTWARE HELPS
Each new finding remains linked to the correct item. Anything not checked remains identifiable.
WHAT THIS DELIVERS
An organised initial condition, without presenting old photos or statuses as a new inspection.
03Record the handoverPreparation + your assessment
YOUR ACTION
You record meter readings, keys and responses and review the draft version.
THE SOFTWARE HELPS
The information is linked to this inspection. The report and signature status follow their own version.
WHAT THIS DELIVERS
It is clear what is recorded, what is still missing and who still needs to respond.
04Compare at check-outAccording to configured rules
YOUR ACTION
You create a new inspection and compare the same spaces and inventory.
THE SOFTWARE HELPS
The initial condition remains alongside the final condition; missing evidence remains visible.
WHAT THIS DELIVERS
Identify differences without assigning blame or costs in advance.
05Connect repairs and reinspectionYour decision + configured follow-up
YOUR ACTION
You decide which item is followed up and who reviews the repair.
THE SOFTWARE HELPS
The task, repair evidence and reinspection refer back to the original finding.
WHAT THIS DELIVERS
Separate moments, one traceable history.
Less duplicate entry, less sorting through photos afterwards and less rebuilding reports.
Automation remains dependent on configuration and available features. No real message, document or instruction is processed here.
Kai
Inspections
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.
