Rental
Aisha · Product specialist · 35 s
A working day with Rental · illustrative scenario
You do your work.
The context stays with you.
Store the contract, arrival photos, meter readings and complaints in different places. Explore how the intended workflow keeps the work together. This is an explanatory scenario, not a functioning customer environment.
01Prepare for arrivalAccording to configured rules
YOUR ACTION
You open the rental period and checklist.
THE SOFTWARE HELPS
The property and tenant data form the same context.
WHAT THIS DELIVERS
Clear preparation.
02Record the check-inAccording to configured rules
YOUR ACTION
You open the linked condition report and record the condition, inventory, meters and keys.
THE SOFTWARE HELPS
Inspection retains the record; Rental continues to refer to the same unit, rental period and report version.
WHAT THIS DELIVERS
No duplicate initial condition in two workspaces.
03Follow up on departureAccording to configured rules
YOUR ACTION
You compare the data and assess open items.
THE SOFTWARE HELPS
Any maintenance notification refers to the same property.
WHAT THIS DELIVERS
Targeted follow-up without rebuilding the file.
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.
Less administration per rental and less missing information during handover.
Automation remains dependent on configuration and available features. No real message, document or instruction is processed here.
Aisha
Rental
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.
