Where to start
Admin Area → Property Management Flow → Autopilot
Before you begin
Compliance Autopilot highlights exceptions in native evidence. It does not approve certificates or determine legal compliance.
Follow these steps
- Choose Run compliance scan with the necessary compliance management permission.
- Review critical and warning cases, then open Detection evidence.
- Use Review native evidence or Review natively to inspect the original intake and its matching, extraction and approval state.
- Correct the native evidence or relationship through the appropriate Compliance screen.
- Scan again and check whether the case remains active, clears or reopens.
Check the result
Each actionable finding is connected to its property and native evidence where available. Review dates and approval state independently of the severity label.
If something does not look right
Expired evidence, evidence due within 60 days, pending approval, unhealthy record status and missing EICR/gas/EPC types can produce separate findings. A gas-free property can still be flagged by the fixed missing-type check; record the professional applicability decision in the case.
Questions and answers
Does a record existing mean it is current?
No. Check expiry, approval and status. Readiness checks reject specified unhealthy statuses and use the current evidence rules.
Does C1, C2 or FI prove the defect?
These are review flags extracted from native intake. Read the source report and obtain the appropriate professional decision.
Does resolving the Flow case approve the certificate?
No. Native evidence approval remains a separate workflow.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Acknowledge, resolve, dismiss or reopen a compliance case
- Create a compliance task or remedial repair
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.