Service
Retention, holds, and disposal audit
A retention schedule on paper does not dispose of anything. We check whether the application can apply the schedule, honour a hold, and prove that disposal happened.
Malaysian organisations keep records under the Personal Data Protection Act 2010, tax record rules, the Companies Act 2016, and sector licences. The application must be able to keep what must be kept and remove what must not linger.
We test label application on new and legacy content, conflict between multiple labels, hold behaviour during an investigation, and whether disposal is a logged event or a silent delete.
If the application cannot support the schedule, we say so plainly and describe the manual controls that would be needed until configuration or a different tool can close the gap.
What we examine
- Retention labels versus the written schedule
- Legal hold placement and release
- Disposal job history and exception queues
- Content with no label or conflicting labels
- Proof of destruction versus ordinary deletion
What you receive
A retention gap table mapped to your schedule, plus recommended label and hold configuration.