Obra Core · The shared foundation

Set up your property once. Keep working with it everywhere.

Manage your property list, contacts, documents and access rights in one place. Other workspaces use the same data, so you do not have to enter it again.

For owners, managers and teams that want to move from separate records to one clear structure.

Property structureContacts & rolesShared documents
Illustrative practical context for Obra CoreObra Core
Practical reference · not a customer case
What makes your work easier?

Less duplicate data entry and less searching across separate files.

Design of the product explanation · not a live product demo. Features and package coverage must be confirmed before publication.

Meet Paul

Obra Core

Obra Core connects your buildings, documents, tasks and partners. Every workspace builds on the same building passport.

Explore a practical example
Paul

Paul

Obra Core

Product specialist

Contact us

Watch the practical example

From the office to the site.

ObraPad brings property management together in an online platform, with a mobile app for iOS and Android being prepared for the pilot.

An overview in your browser

Bring building information and documents together, follow up tasks and maintenance, and work with your team and partners from the same record.

The ObraPad app for iOS and Android

The app is being developed for work on site: open a building or installation via QR, record inspections and add evidence photos to the right record.

The mobile apps are being prepared for the pilot. Ask about current testing options and access.

Ask about the app and pilot access

One building passport for office and field work, keeping information connected to the right building.

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.

Recognise your situation

When do you use this?

Three practical applications. Open the one that suits you.
01Set up the first home

Today: Addresses, contact details and plans are scattered.

Your workflow: Create the property, add its spaces and link the first documents.

The result: The other workspaces can refer to the same property.

02Enable the management team to collaborate

Today: Each colleague maintains a separate list.

Your workflow: Record responsibilities and access on the shared record.

The result: Less uncertainty about who may use which information.

03New manager or supplier

Today: A change risks turning into a new record.

Your workflow: Adjust roles and share only the relevant information.

The result: The building history is preserved; access remains limited.

Less explaining. Less retyping.

This is how your team
really works together.

What you do here in practice

From daily tasks
to clear follow-up.

Open a feature for a practical example.
01Organise propertyHome, building, unit and installation each have a fixed place.

You: Record which buildings, units and spaces belong to your organisation.

ObraPad helps: Other workspaces refer to that same property structure.

Your benefitA new project does not start by recreating an address list.
02Contacts & access rightsDecide who can see and do what.

You: Link owners, colleagues, suppliers and other stakeholders to the correct record.

ObraPad helps: Access follows the configured role and property scope.

Your benefitFewer separate copies and less confusion about the people involved.
03Share documents & photosFind information where it belongs.

You: Store a plan, contract or photo with the property, space or installation.

ObraPad helps: The same document can be opened from a connected workflow.

Your benefitNo need to upload it again for every team.
04Bring tasks & schedules togetherSee what needs attention and who is working on it.

You: Work with assignees, dates and outstanding tasks.

ObraPad helps: Views and configured reminders follow the task data.

Your benefitFewer lists to maintain and fewer separate follow-up calls.
05Team communication in each person’s languageEveryone understands the same work, without a separate conversation for each language.Depending on your configuration
Configuration- or add-on-dependent

You: Set a preferred language and discuss tasks or records with people who speak another language.

ObraPad helps: Translation keeps the original, source version, numbers, units and object references recognizable. Available languages and features depend on the configuration.

Your benefitLess copying into translation apps and less repeated explanation; technical or unclear translations remain verifiable.
06History & handoverSee what happened without starting over.

You: Review previous activities and share the relevant record with authorised stakeholders.

ObraPad helps: New activities build on the same history.

Your benefitLess record reconstruction when a colleague or manager changes.
07Start with your existing informationDo not start with an empty system if the information already exists.Depending on your configuration
Configuration- or add-on-dependent

You: Gather your property list, contacts and documents. At the start, check what can be carried over and what still needs to be added.

ObraPad helps: A guided setup identifies missing fields and possible duplicate records; imports depend on supported sources.

Your benefitA focused start without having to enter everything at once.
08Collaborate without creating a new recordLet colleagues and partners work on the same property.

You: Choose which organisation, people and roles may view or edit a property or assignment.

ObraPad helps: The link to the same property identity is retained when you switch workspaces.

Your benefitFewer duplicate files and less searching for the correct record owner.
09Targeted access for the accountantAn accountancy connection without replacing your accounting software.Planned extension
Planned extension / roadmap

You: Let the client explicitly decide which accountant may view and export which data categories.

ObraPad helps: The roadmap includes auditable exports and, later, read-only API/accounting connectors. Accountancy partner status does not automatically grant access to financial data.

Your benefitFewer files to collect and fewer duplicate requests. No automatic external postings, filings or payments.
Convenience through automation

Less routine work.
With the right control.

01
According to your rules

Recurring follow-up

Reuse the same property, contact and document data.

02
With AI support

No need to start again

Search for or summarise information using the selected Copilot capabilities.

03
For decisions

You stay in control

Determine who gets access and which data may be shared.

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.

Without a connected workflow

Collect addresses, contacts and documents again for a new project.

With this workspace

Select the existing property and continue with the correct access rights.

See it step by step
How much time could this save you?Your own figures, not a marketing percentage

Make one recurring task measurable.

Formula: number of tasks × (minutes now − minutes after the change) ÷ 60.

Open a calculation example

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.

What information do we share with other workspaces?

Property entities · contacts · documents · access rights. You continue with the same property context; you do not create a second record.

What can I extend here with add-ons?

Core remains the shared foundation. Extensions add capabilities within the same data and rights.

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 →
Practical questions

Good to know.

Do I have to use all workspaces straight away?

No. Start with the work you want to organise. The shared property foundation means you do not have to start over when you add an extension. Which components are included depends on the configuration.

Does a supplier get access to all my property?

That is not the intention. The intended access follows the assigned organisation, records, objects and roles, not merely the fact that someone has been invited.

Help me choose