Customer work, connected.

Help & supportMyAccount
Document Intake & Safety Certificates · How-to guide

Parse EPC / MEES evidence

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 run the module extraction step and inspect values detected from the uploaded EPC or MEES evidence.

Audience: Compliance administrators and authorised property staffPermission: Compliance Monitor: Edit or AdministratorModule v1.0.0
Jump to steps
Where to goSafety Certificates → EPC / MEES Tracking → Intake → Parse
Before you startConfirm the correct property, tenant, record and evidence before changing a compliance status.

What this guide helps you do

Run the module extraction step and inspect values detected from the uploaded EPC or MEES 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

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 pending intake.
  2. Select Parse or initialise extraction where the action is available.
  3. Check the raw or previewed text and the detected structured values.
  4. Treat confidence, parse status and match status as review aids, not approval.
  5. Continue to the review screen and correct any inaccurate extraction.

Settings to check

Parse statusShows whether extraction is pending, completed or needs attention.
Match statusIndicates whether the detected evidence appears to match the linked entity.
ConfidenceA technical indicator that still requires human verification.
Raw evidenceThe uploaded file remains the authoritative source for review.

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

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.

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.
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.
Browse connected topics:document intakesafety certificates

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page