Use Building Safety / Higher-Risk Buildings tracking
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to manage the end-to-end intake, review, approval and evidence lifecycle for building safety evidence.
What this guide helps you do
Manage the end-to-end intake, review, approval and evidence lifecycle for building safety evidence. 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 Building Safety / Higher-Risk Buildings workspace separates uploaded source evidence from the approved compliance record. This preserves a review checkpoint before dates, references and status are relied upon elsewhere.
Follow these steps
- Go to Safety Certificates → Building Safety / Higher-Risk Buildings.
- Check current workflow counts, recent uploads and latest notification activity.
- Search for the linked property or entity before creating a new intake.
- Go to the relevant intake and follow its displayed parse, review and approval state.
- Check the approved record and PDF in the compliance register.
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
An approved building safety evidence record is linked to its source entity and available to records, notification and audit tools. 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.