Use cases

What a shared standard could make easier

These are intended benefits of a common data model for strata information. They depend on adoption and are not guaranteed outcomes.

Have a workflow we should consider? Real examples from councils, managers and vendors directly shape what the standard covers. Share a use case.

Moving data between property management platforms

Today: Changing platforms today often means spreadsheets, manual re-entry and lost history.
Intended benefit: If both platforms can export and import standard records, core data — the corporation, strata lots, owners, council, meetings and documents — could move with far less manual work.
Relevant entities: StrataCorporation StrataLot OwnershipInterest Document

Connecting maintenance and contractor systems

Today: Maintenance requests and work orders are re-keyed between management software and contractor tools.
Intended benefit: A shared shape for requests, work orders and assets is intended to let these systems exchange work without one-off integrations.
Relevant entities: MaintenanceRequest WorkOrder CommonAsset

Normalising financial reporting

Today: Budgets and fund balances are structured differently by every accounting tool.
Intended benefit: Consistent definitions of the operating fund, contingency reserve fund, budgets and levies are intended to make reports comparable across years and providers.
Relevant entities: Fund Budget Levy FinancialTransaction

Making strata records easier to analyse

Today: Records spread across PDFs and incompatible exports are hard to search or analyse.
Intended benefit: Structured, consistently categorised records could make it easier to answer questions such as when a component was last replaced.
Relevant entities: Document CommonAsset Resolution

Consistent reporting across many strata and condo corporations

Today: Managers of many corporations reconcile different formats for each one.
Intended benefit: A common model is intended to support consistent reporting across a portfolio, regardless of which tools each corporation uses.
Relevant entities: StrataCorporation InsurancePolicy GeneralMeeting

AI assistants that understand strata entities

Today: AI tools must guess what fields mean when every system names them differently.
Intended benefit: Clearly defined entities and vocabularies give AI applications a reliable vocabulary for strata concepts, which may improve accuracy and make answers easier to verify.
Relevant entities: Bylaw Resolution Budget

Less duplicate integration work for developers

Today: Each new integration means another bespoke mapping between two proprietary models.
Intended benefit: Mapping once to a shared standard is intended to replace many pairwise mappings.
Relevant entities: Organization Person StrataLot