Sentencing, archiving, destruction: the three decisions every government record eventually forces

The retention decision nobody wants to make

Every jurisdiction in Australia sets out, in some form, the minimum period a record must be kept before it can even be considered for disposal. This process has a name – sentencing – and it is easy to misread as a countdown to deletion. It is not. A minimum retention period is a floor, not a deadline: reaching it means a record becomes eligible for review, not that review has already happened, and not that destruction is now required.

The gap between those two readings is where real risk lives. Picture an image distributed to media outlets, handed to stakeholders, and posted to a council or department's own social media accounts. Nobody in that organisation can ever fully confirm the image has stopped circulating – reposts and shares happen well outside the platform's visibility. Treat the minimum retention period as an automatic clock, and the consent record behind that image, the only evidence a subject ever agreed to appear in it, gets destroyed at the exact moment it might be needed. A well-intentioned compliance step becomes the thing that leaves the organisation exposed.

The organisations that get this right treat sentencing as a genuine decision point, not a scheduled job. Reaching the minimum period should open a review, gated behind a person's judgement, with that judgement recorded – who reviewed it, when, and what was decided. Retaining a record longer than its minimum is not a compliance failure. In a great many cases, it is the correct, defensible call.

Proving it was archived, not lost

Before anything is ever destroyed, most organisations move a record through an intermediate step: archiving. This is where a record's active life ends without its existence ending – it is set aside, its status changes, and it continues to exist until a further, separate decision is made about it.

The value of this step is entirely in what it proves. An auditable archiving event – who archived which assets, when, and under what action – creates a clean, defensible boundary between "still in active use" and "set aside, pending a future decision." Without that boundary recorded somewhere, an organisation asked to demonstrate when a record left active circulation has nothing concrete to point to.

Proving it was destroyed, intentionally

Destruction is the step that carries the most weight, because it cannot be undone. Treating archiving and destruction as two genuinely separate actions – never a single click that does both – is what turns permanent deletion into something always intentional and always reviewable, rather than a default outcome of tidying up a library.

A defensible destruction record needs the same rigour as the decision that preceded it: which assets were destroyed, by whom, when, and for what reason. That record is the organisation's evidence, produced on demand, that disposal happened lawfully rather than by accident or convenience.

Bringing the decision into the workflow itself

None of this is a new obligation. What is new is how much of it can now live directly inside the platform holding the assets, rather than in a parallel spreadsheet, a records-management system nobody in the communications team ever opens, or institutional memory that walks out the door when someone changes roles.

LookatmeDAM Asset Sentencing brings the classification decision itself into the platform – what a record is, which retention and disposal authority governs it, and what happens once its minimum period is reached – built on preset authority and class libraries for each jurisdiction's regulatory framework, starting with New South Wales, with other Australian jurisdictions to follow. Reaching a retention period never triggers deletion directly; it opens a review, and that review becomes part of the record's own audit trail.

That trail continues through the two events that follow. A Certificate of Archiving is generated the moment a record moves into archived status, recording every asset affected, by whom, and when. A separate Certificate of Destruction is generated only when destruction actually occurs, as a distinct, deliberate second step — never bundled into the archiving action itself. Together, the three pieces answer the same question a records officer, an auditor, or a subject raising a concern will eventually ask: not just what happened to this record, but who decided it, on what basis, and when.

The obligation was always there. The proof is what's been missing.

Government bodies have never been short on the requirement to manage records responsibly. What has been missing, for most, is a way to make that responsibility visible in the everyday tool their teams already use– without adding a second system, a manual log, or a records officer who has to be looped in for every routine decision.

If sentencing, archiving, or destruction is a workflow your team is still managing outside your DAM, or not managing with the confidence it deserves, talk to us about the workflow issues you face and how we can help