Understand compliance in the merged property module
Understand how property, tenancy, safety, licensing, governance, renewal and audit workflows connect in one module.
Before you start
Compliance View opens the workspace; Create is used for new intake, Edit for review/approval and Delete for deletion. Each action also validates its record.
Follow these steps
- Go to Core Compliance → Dashboard.
- Check record, sync, renewal, notification, overdue and due-soon counts.
- Go to the relevant workspace from the Compliance header groups.
- Follow the intake, review and approval state shown for the selected area.
- Check the final record, PDF and audit event before closing the task.
Fields, rules and limits
- Compliance shares the merged module’s property relationships and protected workspace storage. The header groups provide the operational registers, while audit pages bring together their approved records and evidence.
Check it worked
The linked entity, saved state, dates and evidence match the intended task.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
Does a parsed document count as approved?
No. Parsing supplies suggested values. A reviewer must verify the linked entity, evidence and required fields, then use the separate approval action.
Is the generated PDF the original certificate?
No. The system PDF reflects the saved compliance record or notification. Open the original source evidence separately when checking the document supplied.