Before you begin
- Identify who handles leasing, finance, maintenance and tenant service in your organisation.
- Define which application, tenancy and property information each responsibility needs.
- Use the demo to discuss the controls and services you need for your deployment.
The illustrations use fictional demonstration records. Follow your organisation’s review and approval process before issuing changes.
Understand where staff decisions, document visibility and activity history fit into a more organised rental operation.
What the workflow coordinates
Connected records bring evidence, statuses, documents and activity together for staff review. AI assistance is a development direction; the illustrated application review remains staff-led.
What people review
People choose necessary information, evaluate applicants, approve sensitive actions and define their organization’s handling and retention processes; software support does not transfer those responsibilities.
Keep applicant decisions with the reviewer
Open the application review and bring documents, check states, meeting notes and the decision controls together. Use the score as an aid and keep missing evidence visible before a staff member decides how to proceed.
The evidence, unresolved items and person responsible for the decision are clear.
The evidence, unresolved items and person responsible for the decision are clear.
Understand the direction for AI assistance
Use the connected dashboard and application records to identify where your team spends time searching and preparing summaries. AI assistance is being developed for this kind of support; discuss current availability and the human review process with the team.
Planned assistance is distinguished from the staff-led workflows illustrated in the demo.
Planned assistance is distinguished from the staff-led workflows illustrated in the demo.
Review responsibilities and company access
Open Users & roles and compare the displayed responsibilities with the people who handle leasing, finance, maintenance and tenant service. The permissions matrix is marked Draft in the prototype, so confirm production enforcement when defining your team setup.
Each operational responsibility has a considered company and information scope.
Each operational responsibility has a considered company and information scope.
Check the audience for documents
In Documents, check the linked record, version and Internal or Tenant can see label before preparing a file for use. Keep applicant evidence, office records and tenant-facing documents associated with their purpose.
The intended document audience and the record it belongs to are understood.
The intended document audience and the record it belongs to are understood.
Separate internal notes from tenant updates
On a repair, choose the appropriate message audience before writing an update. Internal notes and tenant-visible messages have separate labels, helping the team keep its working discussion distinct from the tenant conversation.
The author has checked the visibility of the update before sending or saving it.
The author has checked the visibility of the update before sending or saving it.
Use activity history to explain a change
Open the audit history and filter by person, area, event type or date when an action needs explanation. Follow the linked records and review the relevant report alongside the event history when discussing an operational question.
The review connects the event, responsible person and underlying record.
The review connects the event, responsible person and underlying record.
What you should have at the end
A clear understanding of the staff decisions, intended information boundaries, activity records and service availability to review when adopting the platform.
Demonstration notes and availability
- Reviewed against the official demo at demo.estatereal.io. Screenshots are native 3× captures in English/light mode. Preset records and enabled functions can change.
- This review followed navigation, record tabs and unsaved forms. It did not submit payments, signatures, invitations, messages or irreversible record changes.
Useful answers
Does the screening score approve an applicant?+
No. The application screen describes the score as an aid and keeps the decision with staff. Review the evidence, unresolved items and your organisation’s criteria before deciding.
Where does AI fit into the product direction?+
AI assistance is being developed around summaries, missing-information checks and clearer next actions. These screenshots illustrate connected records and staff review; discuss the currently enabled AI functions with the team.
How do visibility and roles fit together?+
A role describes someone’s responsibility, while a document or repair-note visibility label describes its intended audience. Review both when defining who should see information; the demo permissions matrix is explicitly marked Draft.
What does GDPR support mean here?+
Organised application and tenancy records, document handling and intended access boundaries can support your privacy procedures. Your organisation determines lawful collection, use, access and retention, and should review the production controls for its deployment.