Backfill retention metadata
Populate policy and due-date metadata for existing module records that lack it. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Populate policy and due-date metadata for existing module records that lack it. 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 the workflow fits together
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
- Check policy definitions first.
- Run the backfill action.
- Note the processed and updated counts.
- Go to a sample of records to confirm due dates and policy keys.
- Run a dry run before execution.
Fields and decisions to 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.
How to confirm 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.
Controls, checks and common mistakes
- 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.