Export an audit register to CSV | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/export-an-audit-register-to-csv Publisher: Pixie Technologies LLC Legal Audit (https://pixiecrm.com/help-centre/topic/legal-audit) · How-to guide Export an audit register to CSV 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 create a filtered CSV from an allowed audit workspace. Audience: Compliance administrators and authorised property staff; Permission: Administrator; Module v1.0.0; Where to goAudit workspace → Export CSV Before you startConfirm the correct property, tenant, record and evidence before changing a compliance status. What this guide helps you do Create a filtered CSV from an allowed audit workspace. 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 - Apply the required workspace filters. - Select Export CSV. - Check the row count and columns. - Store the file in the approved audit location. - Remove unmanaged local copies after use. Settings to check Linked recordVerify the exact property, tenant, supplier or governance entity. StatusUse the lifecycle state shown by the module. Dates and referencesVerify dates and identifiers against source evidence. Audit evidenceCheck uploaded files, generated PDFs, notification logs and audit events. 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:legal audit (https://pixiecrm.com/help-centre/topic/legal-audit) Related guides Create authority or regulator exports (https://pixiecrm.com/help-centre/create-authority-or-regulator-exports)Export an audit pack PDF (https://pixiecrm.com/help-centre/export-an-audit-pack-pdf)Export an audit evidence ZIP (https://pixiecrm.com/help-centre/export-an-audit-evidence-zip)Run a compliance audit backbone check (https://pixiecrm.com/help-centre/run-a-compliance-audit-backbone-check)