Before you begin
- Decide whether the rules apply to the company or a specific building.
- Review the proposed wording and the intended tenant recipients.
- Keep any local legal or contractual review separate from the software acknowledgement record.
The illustrations use fictional demonstration records. Follow your organisation’s review and approval process before issuing changes.
An owner can communicate expectations consistently and find which version a tenant received.
What the workflow coordinates
The interface displays versions, issue state and opened/viewed/acknowledged counts and exposes the relevant rule sets in the portal. External notification delivery is simulated.
What people review
People approve wording, choose scope and recipients, read the rules and follow up on questions or missing acknowledgements.
Choose the right rule set and scope
Open House rules and select the company-default or building-specific rule set you intend to manage. Read its version, publication information and issue state before interpreting the acknowledgement counters; an unissued set can legitimately show zero activity.
The selected scope and version match the property and tenants who should receive it.
The selected scope and version match the property and tenants who should receive it.
Review the current wording
Read the complete rule text and any version notes before sending it to tenants. Check practical topics such as shared areas, noise, waste, fault reporting and planned access against the arrangements for this property rather than copying fictional example wording unchanged.
The content is suitable for the intended property and has an agreed owner for review.
The content is suitable for the intended property and has an agreed owner for review.
Make changes as a new version
Use Edit (new version) when the wording needs to change. The interface states that every change creates a version and tenants acknowledge the exact version received, so keep the earlier version as the reference for previous acknowledgements.
The revised wording has its own version identity and the previous record remains distinguishable.
The revised wording has its own version identity and the previous record remains distinguishable.
Issue the version deliberately
Use Issue to tenants for the reviewed version and inspect the recipient selection offered in that flow. Check the scope, version and selected recipients before issuing; afterwards, review the acknowledgement list for that version.
The intended version and recipients have been reviewed before issuance.
The intended version and recipients have been reviewed before issuance.
Show the tenant where to read and acknowledge
No house-rules document is seeded for this tenancy. Check My home and Documents for current availability. Use the adjacent current record or contact the team to confirm this workflow’s availability.
Versioned house rules and acknowledgement
No house-rules document is seeded for this tenancy. Check My home and Documents for current availability.
Confirm current availability before attempting this stage.
Follow acknowledgements and retain history
Return to Tenant acknowledgements to review the current version, using building/status filters and Earlier versions too when needed. Use Version history for wording changes and avoid treating a previous-version acknowledgement as acceptance of a newer issue.
Outstanding acknowledgements are identified against the correct version, with earlier history preserved.
Outstanding acknowledgements are identified against the correct version, with earlier history preserved.
What you should have at the end
The workflow is intended to leave a version-specific issue and acknowledgement trail that staff and tenants can revisit. Use the acknowledgement list to follow outstanding responses against the issued version.
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.
- Current demo limits: No house-rules document is seeded for this tenancy. Check My home and Documents for current availability.
- The current rules list is empty and Sofia has no rules document. New rules was opened as an unsaved form; version publication and tenant acknowledgement were not exercised.
Useful answers
Where do rules start?+
Use New rules from the current House rules list and inspect the form before saving.
Was a tenant acknowledgement verified?+
No. The current tenant has no house-rules document, and no publication or acknowledgement was submitted during this review.