Property Compliance & Compliance Records · How-to guide

Synchronise linked properties

Refresh property relationships from the real-estate source into the Compliance Monitor sync index. 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: EditModule v1.0.0
Jump to steps
Where to goCore Compliance → Dashboard → Sync Property Links
Before you startConfirm the correct property, tenant, record and evidence before changing a compliance status.

What you’ll accomplish

Refresh property relationships from the real-estate source into the Compliance Monitor sync index. 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

This feature sits inside the Compliance Monitor lifecycle. Source evidence is attached to a linked entity, reviewed by authorised staff and converted into an approved record only when the required fields and evidence are complete.

Follow these steps

  1. Go to the dashboard as an administrator or user with Edit access.
  2. Run Sync Property Links.
  3. Wait for the success message and synced count.
  4. Verify the property-link count changed as expected.
  5. Go to an intake form and verify the required property is selectable.

Fields and decisions to review

Source entityThe real-estate property relationship copied into the module index.
Display nameThe property label presented in intake and review screens.
Source identifierThe external record ID retained for traceability.
Sync timestampThe latest time the module refreshed linked records.

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

The resulting status, evidence, PDF, notification or audit event remains available through the relevant Compliance Monitor register. 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.