Property Compliance & Compliance Records · How-to guide

Compliance Monitor module overview

This guide explains how property, tenancy, safety, licensing, governance, renewal and audit workflows connect in one module. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Compliance administrators and authorised property staffPermission: Compliance Monitor: ViewModule v1.0.0
Jump to steps
Where to goCore Compliance → Dashboard
Before you startConfirm the correct property, tenant, record and evidence before changing a compliance status.

What you’ll accomplish

Understand how property, tenancy, safety, licensing, governance, renewal and audit workflows connect in one module. The supplied Compliance Monitor module keeps live operational records, source documents, generated evidence and audit history connected through shared section keys, compliance types and linked-entity references.

How the workflow fits together

The module uses one shared compliance record layer while retaining area-specific intake, review, approval, notification and audit screens.

Follow these steps

  1. Go to Core Compliance → Dashboard.
  2. Check record, sync, renewal, notification, overdue and due-soon counts.
  3. Go to the relevant workspace from the grouped left menu.
  4. Follow the intake, review and approval state shown for the selected area.
  5. Check the final record, PDF and audit event before closing the task.

Fields and decisions to review

Linked entityThe property, supplier, tenant or business record connected through the sync index.
Section and compliance typeThe module area and record classification used for routing and reporting.
Status and datesThe current lifecycle state, issue date, expiry date and review timing.
Evidence and auditUploaded source documents, generated PDFs, notifications and chain-of-custody events.

Record, audit and evidence checks

Reopen the relevant workspace after saving. Confirm the intake ID or record reference, linked entity, status, dates, evidence list, generated PDF and any notification or audit entry. Where the module offers separate source evidence and system PDF buttons, review both rather than assuming they contain the same information.

How to confirm it worked

A verified compliance record remains linked to its source entity and available to the relevant register and audit workspace. A successful browser message confirms that the request was handled; the register and audit history confirm what was actually retained.

Controls, checks and common mistakes

  • Verify the linked property, tenant, company or record ID before uploading, approving, sending, exporting or deleting.
  • Do not treat OCR, parsing, confidence or a success alert as a substitute for human evidence review.
  • Verify the saved record and audit history after every state-changing action.
  • Keep original uploaded evidence distinct from system-generated PDFs and notification evidence.
  • Use least privilege and avoid administrator-only actions unless the task genuinely requires them.
  • This module supports operational compliance records; it does not replace professional legal, regulatory or safety advice.
Compliance and data safetyUse the module as an operational evidence and workflow tool. Verify legal, safety, tax, licensing, data-protection and regulatory decisions with the organisation’s authorised professional process.
Connected module guides

Connected discovery, service and API guides