Main scenario
From a resident's report to a closed repair
A property manager looks after dozens of buildings, and every report requires working out what it concerns, who pays and who repairs. Cases get lost in emails, and residents call because they don't know what's happening.
01
→
Phone / app / email
Resident report
A resident reports a fault via the app, a form, email or phone, often with a photo and a short description like “there's a leak in the basement”.
02
→
AI + property database
Assignment to property
AI identifies the building, stairwell, unit or common area, the fault category and urgency. Reports about the same fault from several people are merged into one case.
03
→
Contracts + regulations
Responsibility check
The system checks whether the repair is the responsibility of the owners' association, the unit owner, the tenant, the developer under statutory warranty or a company with a service contract.
04
→
Contractor database
Contractor order
The order goes to the right contractor with a description, photos, address and access information. Repairs above a set amount wait for the manager's approval.
05
Schedule + deadlines
Deadline tracking
The system tracks response and repair deadlines, reminds the contractor, keeps the resident informed of progress and closes the case once completion is confirmed.
In practice · example scenario
A leak in the underground car park
Within an hour, three residents report water in the car park, each through a different channel. The system merges the reports into one case, assigns it to the building and sees that the building is still under the developer's statutory warranty. The developer receives the report with a response deadline, the plumbing company under contract gets an order to secure the leak, and residents receive one update on what is happening.