Two duties, one drawer

Records management in Australia pulls in two directions. Funders, auditors and statutes require records to be kept, sometimes for seven years. Privacy principles require personal information not to be kept longer than needed. Most organisations resolve this by keeping everything, which covers neither duty.

A schedule replaces the annual clean-up day

The cost of the undisciplined archive

An archive without a schedule increases exposure when a dispute, a breach investigation or a request for documents forces a search through material that should have been destroyed. Staff pay a daily cost: the larger the pile of “we might need it”, the longer any search takes.

A schedule, not a standing decision

A retention schedule aligned to the published authorities for the sector records each keep-or-destroy decision once and applies it by default. In Insight Docs, schedules surface what is due for disposal and a human reviews and confirms before anything is destroyed. Automated deletion is not used.

What to do about it, whatever you buy

Three practices carry most of the value. Classify on arrival, not years later — a document that enters with a record class can be managed by rule forever after. Review annually, not continuously — one scheduled hour per year beats a standing intention nobody executes. And keep the decision trail: what was destroyed, when, under which rule, approved by whom. If your software cannot produce that trail, it is not helping you with retention; it is merely holding your files.

Why keep-everything fails

The cost of an archive is not storage; it is retrieval under pressure, permissions that are too broad, and discovery obligations. A shared drive with forty thousand files holds personal information that cannot be found and records that cannot be relied on. A retention schedule addresses all three.

Questions this view raises

What retention schedule should a small organisation actually adopt?
Start from the published authority for your sector rather than from invention — most industries have one, and it will cover ninety per cent of what you hold. Adopt it wholesale, then document the handful of exceptions your funders or contracts genuinely require. The common failure is writing a bespoke policy from scratch: it takes months, satisfies nobody, and usually omits the one class that ends up mattering. Borrowed-and-adopted beats original-and-abandoned.
How do we handle the backlog nobody has time to index?
Prioritise by age of use, not age of document: the current year first, active programs second, cold history last, scheduled across quarters so it stops competing with daily work. The archive becomes searchable as each tranche lands, so the benefit starts before the project ends.
Where this shows up in our software

Insight Docs carries retention schedules with a human disposal review before anything is destroyed. You can see these principles applied on the projects pages and throughout the InsightSuite module pages.