Follow evidence from intake to audit export
Select the appropriate safety, tenancy, licensing or governance area and retain the distinction between source evidence, review, approval, notifications and audit output.
Before you start
Select the appropriate safety, tenancy, licensing or governance area and retain the distinction between source evidence, review, approval, notifications and audit output.
Follow these steps
- Upload or open the evidence in the correct area and verify the linked entity.
- Parse where supported, then review extracted values against the source document.
- Correct dates, classification and property/tenant matching before approval.
- Use the supported approval action and verify the retained compliance record.
- Review renewal/notification evidence where required.
- Open the relevant audit register, PDF, CSV or evidence-pack workflow and verify the selected scope.
Check it worked
The approved record, source document, generated PDF and audit evidence remain traceable to the same entity.
If something does not look right
A parser confidence score is not a legal conclusion. Exporting an authority/regulator pack does not itself submit it to an authority. Use the organisation’s applicable professional review and official submission process.
Questions and answers
Where are renewal submissions reviewed?
Use the Notification / Intimation Engine and its supported renewal-submission review flow.
Where are chain-of-custody checks?
Compliance → Audit Trail Chain → Audit Logs & Chain of Custody.
Where is retention managed?
Compliance → Agency Governance → GDPR Retention / Deletion Controls. Review the relevant policy, dry-run and legal hold before any deletion action.