A Familiar Moment in Most Council Records Functions
For many Victorian council records managers, PROV Retention and Disposal Authority (RDA) lookups happen reactively, usually triggered by an FOI request, a box retrieval, an audit, or a department asking whether they can finally clear out that 2016 file series. The retention schedule spreadsheet gets opened, the relevant row gets found, and somewhere in the process there’s a moment of uncertainty: is this the right RDA? Is the trigger date right? Has this class been updated since the schedule was last reviewed?
Those questions are reasonable. PROV’s framework is comprehensive and regularly updated, and mapping it accurately into a shared spreadsheet, let alone keeping that mapping current as disposal authorities are revised, is a genuine challenge.
The four-step process below is designed to get you to the right PROV RDA class and disposal trigger with confidence, whether you’re navigating a familiar record type or working through something less clear-cut for the first time.
What is a Retention and Disposal Authority?
A Retention and Disposal Authority (RDA) is a legal instrument issued by the Public Record Office Victoria (PROV). It specifies how long particular classes of public records must be kept and what must happen to them at the end of that period, whether that’s destruction, transfer to PROV, or permanent retention. It’s the legal basis for every disposal decision a Victorian council makes, which is why identifying the right one for a specific record is crucial.
Why Is It Difficult To Find The Correct RDA Class?
Finding the correct RDA seems straightforward in principle. In practice, the time it takes to confirm an RDA class through PROV’s website is one of the genuine friction points in day-to-day records management.
- There are over 120 different RDAs. Finding the right one to start with is confusing and time-consuming. As a general rule of thumb, Victorian councils will typically draw on PROS 09/05 (Local Government Functions). However, there are also a range of RDAs listed as “General” that provide guidelines for common functions across all organisations. These include PROS 07/01 (Records of Common Administrative Functions), PROS 24/03 (Records of the Human Resources Management Function), and PROS 25/06 (Records of the Financial Management Function), amongst others.
- Each RDA is a substantial document. PROV’s website is authoritative and comprehensive, but it was designed to serve as a definitive reference across Victoria’s entire public sector, not as a fast lookup tool. The typical process of locating the relevant RDA, downloading the PDF or Excel file, working through dozens of pages, and interpreting the Function hierarchy can take minutes per record. If you’re classifying dozens of records at a time, the minutes can add up quickly.
- The PROV website’s keyword search only scans document metadata, not the contents of each RDA. This means searches using the language records managers naturally reach for often return nothing at all. Searching “minutes,” for example, returns zero results on the PROV website, because that term doesn’t appear in the high-level metadata associated with any RDA document. The same search in Compu-Stor’s RDA Finder returns 17 entries, because it scans the actual content of each class description, not just the document title.
- When the search does return results, it only shows the Function level, not the Activities or Classes that carry the actual retention periods. Searching “council,” for instance, returns four different PROS numbers. The results page lists the Functions covered by each, but gives no view into the sub-activities or classes needed to accurately categorise a record. From there, the only option is to navigate to each PROS page individually, download the PDF or spreadsheet, and manually work through the document to find the right entry. That process is time-consuming even when you know what you’re looking for.
Four Steps to Finding the Right RDA Class
Step One: Establish What the Record Does Before Consulting Any Schedule
The most useful starting point isn’t the schedule. It’s four questions about the record itself.
- What business activity produced it?
- What decision or action does it document or support?
- What function of council was being performed when it was created?
- And who created it, in what capacity?
These questions do the work of identifying the right Function in PROV’s hierarchy, which is where reliable classification begins. Describing a record as ‘correspondence’ tells you about its format but nothing about its Function, and the applicable retention period follows the Function, not the format.
Step Two: Match the Record to the Relevant PROV Function
PROV’s RDAs are structured around the Functions that the public sector performs: Governance, Financial Management, Human Resources Management, Asset Management, Planning, and others. Records relating to each function will carry their own retention requirements, even for records that appear very similar on the surface.
The Function isn’t always as obvious as it first appears. A complaint about a planning permit may be sentenced as a planning record, but only if it directly relates to an endorsed permit or a permit that was withdrawn, not issued, or not approved. If the complaint escalated beyond the permit itself, it may instead fall under the Complaints class in the Common Administrative Functions RDA.
Similarly, a record about a rates dispute belongs in Financial Management if it concerns the payment or non-payment of rates. But if a ratepayer is disputing the rate they’ve been charged, or arguing for an exemption, it sits under Rates Management in the Local Government Functions RDA instead. Same general subject matter; different function; different retention period.
This is why Step One is crucial. What the record documents, and in support of which function it was created, determines where it sits in the schedule. Where a record genuinely spans two functions, the standard approach is to classify it according to the primary function it was created to support, and to document that reasoning so the decision is defensible on review.
Step Three: Navigate to the Right Class and Read the Entry in Full
Within each Function in a PROV RDA are Activities (more specific categories of work) and within each Activity are Classes, which carry the actual retention periods and disposal actions. The description field in a schedule entry defines the precise scope of the class, and it’s the field most often skimmed too quickly. A record that doesn’t fit that description belongs in a different class, regardless of how similar the Function or Activity heading looks. For any disposal decision, three things do the operative work: the retention period, the disposal trigger, and the disposal action. The remaining fields provide useful context, but those three determine what happens next.
Step Four: Confirm and Apply the Disposal Trigger
Disposal triggers vary considerably by record type, and applying the right one is where compliant and non-compliant disposal decisions can diverge. Some governance record classes carry permanent retention with no disposal trigger at all.
It’s also worth noting that the retention period and the disposal trigger are not the same thing. The retention period specifies how long a record must be kept (seven years, for example). The disposal trigger specifies the event that starts that period running. ‘Seven years after matter closure’ and ‘seven years after the record was created’ are entirely different instructions that could produce disposal dates years apart in practice. A schedule entry that records only ‘seven years’ with no associated trigger is incomplete, and can’t reliably support a compliant disposal decision, which is a realistic gap in spreadsheet-managed retention schedules.
‘We’ve Scanned It — Can We Destroy the Original?’
Digitisation is a recognised pathway to lawful disposal of physical records, but only when specific process requirements have been met. Scanning alone doesn’t satisfy those requirements.
The question comes up regularly, and the reasoning behind it is understandable. If a record has been scanned and the image is accessible, backed up, and retrievable, retaining the physical original can seem redundant. However, under PROV’s framework, the Public Records Act 1973 and the Local Government Act 2020, digitisation only authorises physical disposal when the digitisation process itself meets defined standards.
A compliant digitisation process involves documented scanning standards, quality assurance procedures, metadata capture at a minimum of document title, date, author, and functional classification, appropriate file format and storage, and a formal declaration by an authorised officer that the process was completed in accordance with the relevant standard. Scanning a document and saving the image to a shared drive doesn’t satisfy those requirements. Until they are met, the physical record remains the authoritative copy.
Even where digitisation has been completed to the required standard, some record classes require retention of the physical original regardless. Records carrying evidentiary signatures, records bearing original seals, and records that may be required as exhibits in legal proceedings are not eligible for physical disposal through digitisation alone. Confirming whether a specific class falls into this category is worth doing before any irreversible decision is made.
When physical records are lawfully destroyed following an authorised digitisation process, that destruction needs to be documented with a disposal certificate recording what was destroyed, when, the RDA authority cited, the disposal trigger confirmed as met, and the authorised officer who approved the action. That certificate is what makes the disposal decision defensible under review. And it’s frequently the piece that’s missing when a decision is questioned later.
Four Compliance Gaps That Commonly Develop Over Time
These are predictable consequences of managing a complex, regularly updated framework through a static tool, like a spreadsheet. Recognising them early makes them straightforward to address.
- Disposal without a confirmed trigger. The retention period is identified correctly and the RDA is cited, but the disposal trigger isn’t verified as met. A record held for seven years from creation, when the applicable trigger is seven years from matter closure, may have been disposed of years before it was eligible, with documentation that looks entirely correct.
- Over-retention as a default risk-management approach. Holding records past their authorised disposal trigger creates ongoing privacy exposure, unnecessary storage costs, and a records position outside compliance. PROV’s disposal authorities define authorised retention periods, not minimum ones.
- Relying on a schedule entry that has since been revised. PROV updates its disposal authorities periodically. A retention decision made against a class that has since changed may not be compliant under the current authority, and a spreadsheet that hasn’t been reviewed against current schedules won’t surface that gap.
- No defined ownership of schedule maintenance. Keeping a retention schedule current requires a named owner, a defined review process, and a regular review cycle. Where those aren’t formally established, the schedule tends to drift gradually out of currency through accumulated inaction rather than any single decision.
A Faster Way to Find the Right RDA
The four steps above work reliably when followed carefully. The challenge is that working through them manually (navigating a PDF or spreadsheet, interpreting the Function hierarchy, confirming the disposal trigger) takes time that isn’t always available, particularly when queries arise alongside everything else the role demands.
Compu-Stor’s PROV RDA Finder is a guided, interactive tool designed specifically for Victorian council records managers. Rather than downloading a schedule and working through the hierarchy manually, our Finder provides an interactive guide that allows you to manually click through Function, Activity and Class designations, or search based on a keyword.
For councils wanting to increase productivity, Compu-Stor provides a complete, PROV-compliant pathway from digitisation through to certified physical destruction, with full chain-of-custody documentation and a disposal certificate for your records. Get in touch to find out more.
