Property management
Amara · Product specialist · 32 s
A working day with Syndic · illustrative scenario
You do your work.
The context stays with you.
A report in an email, the quotation elsewhere and the decision only in separate minutes. Explore how the intended workflow keeps the work together. This is an explanatory scenario, not a functioning customer environment.
01Record the reportAccording to configured rules
YOUR ACTION
An owner reports a fault with the garage door.
THE SOFTWARE HELPS
The door and common areas define the context.
WHAT THIS DELIVERS
One traceable item.
02Prepare the decisionAccording to configured rules
YOUR ACTION
You link the quotation and agenda item.
THE SOFTWARE HELPS
Existing documents remain linked to the same building.
WHAT THIS DELIVERS
Fewer documents to reconstruct.
03Follow up on the decisionAccording to configured rules
YOUR ACTION
Authorised people decide; you assign the follow-up.
THE SOFTWARE HELPS
The action and subsequent evidence remain linked to the decision.
WHAT THIS DELIVERS
A decision becomes visible work.
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.
Fewer repeated questions and less manual follow-up of building agreements.
Automation remains dependent on configuration and available features. No real message, document or instruction is processed here.
Meet Amara
Co-ownership management
Co-ownership, stakeholders and building information brought together.
Explore a practical example
Amara
Co-ownership management
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.
