Assets
Installations, equipment and components placed on the building, floor and room, with condition, warranties and a full change history.
Starting point · Operate a portfolio
Operate a portfolio from one property record.
Assets, repairs, planned maintenance, service requests and compliance evidence for every building — connected, so a finding raises the work and the evidence closes it.
For operations teams, facility managers and managing agents who run many buildings day to day.
What you switch on first.
Maintenance
Work orders, planned maintenance and inspections on the same assets. Suppliers accept and report back by link.
Service
One conversation per request, by email or portal, with service-level clocks on every work item.
Compliance evidence
Every duty shows whether it is proven, not just ticked — and says "not yet proven" when evidence is missing.
From a reported fault to closed evidence.
How one request runs once the portfolio is live.
- Reported. A resident or occupant reports a fault by portal or email. It lands on the right unit and building, with its service-level clock running.
- In context. The team sees the asset, its history, open work and any related inspection — before deciding what to do.
- Ordered. A work order goes to the supplier, who accepts by link and reports back with photos and notes.
- Closed with evidence. The evidence is attached to the same asset record; if a duty depended on it, the duty now shows as proven.
Typical first use cases.
Chosen with you in the Scope phase.
- Asset register and building structure for one portfolio
- Repairs and planned maintenance in one flow
- Service desk with resident and supplier portals
- Compliance duties with their evidence
Commercial property operations · VvE and homeowners associations · Infrastructure asset operations
How a first deployment runs.
One portfolio, a few use cases that matter, and the people who own them. Each phase says what we do and what we need from you.
- Scope. Choose one portfolio and the first use cases, and name the person who owns each one. What we need from you: A list of the buildings in scope and a sponsor who can decide.
- Connect. Import buildings, units, assets, leases and documents, and connect the systems you keep. What we need from you: Your current registers and spreadsheets, and access to the systems you want connected.
- Configure. Set up workspaces, roles, approval steps and the country rules that apply to your properties. What we need from you: Who may see, approve and pay what — written down once.
- Go live and review. Your team runs the first workflows. Agents stay off until you turn them on, and every step is logged. What we need from you: Time from the people who will use it, and a review of data quality and the next use case.
Phases, not promises: timing depends on your data, your systems and the scope, and is agreed with you before work starts.
Available today. Configured for you. Connected. Governed.
What Residention does out of the box, what is set up for your portfolio, how it connects to your systems — and what always stays with your people.
Available today
- Property, building, floor, space and asset records
- Work orders, planned maintenance, inspections and compliance evidence
- Service desk with resident and supplier portals
- Lease register, invoices, approvals, journals and VAT per administration
- Maintenance plans, budgets, CapEx and projects
- Document index with versions, review and in-browser viewing
- smartAI assistance that shows its sources
Configured for your portfolio
- Organisations, portfolios and workspaces
- Roles, permissions and approval steps
- Country rules — VvE, HOA, WEG or Comunidad — currencies and dates
- English, Dutch, German and Spanish
- Custom fields, registers and inspection templates
Connected through integrations
- Registers, finance, calendar, mail, directory and meter connections listed on the integrations map
- File exchange for maintenance plans, project schedules and BIM (IFC, COBie)
- Excel, CSV, email intake and webhooks for everything else
- Building systems such as BMS and sensors: a read-only layer in development — Residention never controls plant
Always governed by your people
- Money, contracts, complaints, deletions and outside messages need a person
- Agents act only with an owner, a purpose, an expiry and exact permissions
- Every action logged with who, when, why and the evidence
- Access resolved per workspace; a request without scope returns nothing
Not claimed: universal live BMS or sensor connectivity, full BIM interoperability, real-time simulation, predictive maintenance or autonomous technical control.
See every integration · Security and governance · Trust Centre · Follow one day in one building
See it on your own portfolio.
Book a demo and we will walk through these workflows with your own buildings in mind.