Compliance Monitor module overview
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains how property, tenancy, safety, licensing, governance, renewal and audit workflows connect in one module.
What this guide helps you do
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 it works
The module uses one shared compliance record layer while retaining area-specific intake, review, approval, notification and audit screens.
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 grouped left menu.
- Follow the intake, review and approval state shown for the selected area.
- Check the final record, PDF and audit event before closing the task.
Settings to check
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.
Check 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.
Common mistakes to avoid
- 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.