Where Most Victorian Government Records Retention Schedules Start
For Victorian government agencies, a spreadsheet is the most common starting point for records retention schedule management. Excel is accessible, flexible, and familiar to most records staff. It doesn’t require a procurement process, a training program, or a system integration project. You can get something functional built in an afternoon.
That accessibility is also what can let spreadsheet-managed schedules drift over time. Because there’s no system enforcing structure, the quality of the schedule depends entirely on the discipline of the people maintaining it, and on the time available to do so properly. The sections below walk through how to build and maintain a PROV-compliant retention schedule in Excel, covering structure, review cycles, version control and disposal documentation, and what to watch for when the spreadsheet approach starts to show its limits.
Step 1: Build the Right Column Structure From the Start
A retention schedule is only as useful as its structure. Most agencies have a spreadsheet that covers the basics: record types, a retention period, maybe a status column. The problem isn’t usually missing records; it’s missing fields. Without the right columns, the schedule can’t generate the information needed to make reliable, defensible disposal decisions.
At minimum, a functional Victorian government records retention schedule in Excel should include the following columns:
- PROV Authority Number: (e.g. PROS 07/01) Especially useful to hyperlink this cell directly to the live PROV RDA document so it can be recalled and verified quickly when needed.
- RDA Class Number: (e.g. Class 1.1.1)
- RDA Function/Activity: (e.g. COMMITTEES – Advisory committees)
- Record Description: A plain-language description of the record type, specific enough for your staff to recognise.
- Retention Trigger: The event that starts the retention period running (e.g. matter closure, financial year end, date of creation).
- Retention Period: The required holding period once the trigger is met.
- Disposal Action: (e.g. destroy, transfer to PROV, or retain permanently).
- Last Reviewed Date: When this entry was last verified for accuracy against the current authority.
- Status: (Permanent or Temporary)
- Responsible Officer: The person accountable for this record class within their business unit.
- Disposal Register Reference: Once a record has been disposed of, a cross-reference to the corresponding entry in your Disposal Register. The detail of what was disposed, when, by whom, and under which authority lives in the register itself (covered in Step 4), not in the schedule.
What to watch out for: The retention trigger/period distinction is where spreadsheet retention schedules can fail. ‘Seven years’ and ‘seven years from matter closure’ are entirely different instructions, and a schedule that records only the period with no trigger cannot support a defensible disposal decision. The deeper issue is structural: unlike a purpose-built system, Excel has no mechanism that demands a real-time RDA lookup when an entry is created or updated. It falls entirely on the user to be disciplined enough to verify the current authority every time, which is a reliable process until it isn’t. With more than 120 disposal authorities in PROV’s framework, see our guide to finding the right PROV RDA for a faster path to the right class.
Step 2: Set Up Review Triggers So Records Don’t Sit Past Disposal
One of Excel’s genuine advantages for retention management is conditional formatting. Without a visual prompt, records that have passed their disposal trigger stay buried in rows that nobody’s actively reviewing. A small amount of setup upfront means disposal eligibility becomes visible without anyone having to work through the spreadsheet manually.
Here’s how to set it up:
| Add an 'Eligible for Disposal From' column. | Use this formula to add the retention period to the trigger date. | = DATE(YEAR([Trigger Date])+[Retention Period]),MONTH([Trigger Date]),DAY([Trigger Date]) |
| Add a ‘Days Until Eligible’ column. | Use this formula to calculate how many days remain until the record is eligible for disposal. | = [Eligible for Disposal From] - TODAY() |
| Highlight records overdue for disposal. | Apply Red Fill conditional formatting to the ‘Days Until Eligible’ column. Negative values in this column are overdue for disposal. |
|
| Highlight values approaching their disposal eligibility.. | Apply Yellow Fill conditional formatting to the ‘Days Until Eligible’ column.Values between 0 and 180 in this column are within a 6 month window of being eligible for disposal. |
|
| Add a ‘Review Overdue’ column. | Use this formula to automatically populate with ‘Review Overdue’ or ‘OK’ based on the last reviewed date. Any records last reviewed more than 365 days ago will return a ‘Review Overdue’. If 1 year is too narrow of a review window, adjust the number of days in the calculation. | = IF(TODAY()-[Last Reviewed]>365,”Review Overdue”,”OK”) |
| Highlight records that are overdue for their review. | Apply Red Fill conditional formatting to the ‘Review Overdue’ column. |
|
Now that you’ve created new calculated columns and conditionally formatted them, it’s easy to filter down your data by cell colour. This becomes your working list for each review cycle.
What to watch out for: Conditional formatting surfaces what needs doing, but it doesn’t do the work. The flags only work if someone acts on them, and in a shared file they’re easy to ignore or accidentally override. The other limitation is RDA currency: PROV periodically updates its disposal authorities, and no formula can detect when a retention period you’ve been relying on has changed. The only way to catch that is a deliberate, manual review of each entry against the current version of the relevant authority. How reliably that happens, and who owns it, is one of the harder questions for any agency managing this in a spreadsheet.
Step 3: Manage Version Control Across Departments
A retention schedule managed by one person, in a local file, for a single business unit is one thing. The moment multiple departments start contributing (each responsible for their own record classes, with staff updating their sections at different times), the spreadsheet starts to introduce risks.
These steps won’t eliminate those risks, but they reduce them significantly:
- Store the master file in a single, authoritative location, like SharePoint or a managed network drive, and make clear to all users that this is the only version. Local copies saved to desktops are a version control problem waiting to happen.
- Lock the column headers and any formula cells using Excel’s cell protection feature (Review > Protect Sheet). Allow editing only in the data entry columns. This prevents structural changes from being made accidentally.
- Create a ‘Change Log’ tab. Every time an entry is updated, the responsible officer records: the date, their name, the record class affected, what changed, and the reason. Make this a documented part of the register review process, not a suggestion.
- Establish a review and sign-off process for any change to an existing entry’s RDA reference, retention period, or disposal trigger. These are compliance-critical fields that should require explicit approval before changing, not casual editing.
- Save a dated archive copy of the full spreadsheet at each review cycle. Label it clearly (e.g. ‘RetentionSchedule_Reviewed_2026-06.xlsx’). This gives you a recoverable record of the schedule’s state at any point in time.
- Nominate a single schedule owner — the person responsible for the master file, change approvals, and the review cycle. Without a named owner, accountability disperses and the schedule drifts.
What to watch out for: SharePoint and OneDrive do log last-modified timestamps and maintain version history, which is more than a local Excel file provides. But that’s different from a compliant audit trail. What those logs can tell you is that a cell changed and roughly when. What they can’t tell you is whether the person who made the change verified the RDA before doing so, whether the disposal trigger was correctly applied, or whether the change was reviewed and approved by a responsible officer. If a disposal decision is later questioned — in an audit, an FOI review, or a legal matter — the version history is background context, not evidence of a compliant process. A change log discipline (Step 3 above) bridges some of that gap, but it relies entirely on staff following the process. That’s a different kind of assurance from a system that enforces it.
Step 4: Document Disposal Actions So They’re Audit-Ready
An auditable Victorian government records retention schedule isn’t just one that contains the right information — it’s one that can demonstrate when decisions were made, by whom, and on what authority. The retention schedule holds the framework; the disposal record is the evidence. Most spreadsheet-managed schedules have the former and not the latter.
Here’s what a defensible disposal documentation process looks like in practice:
- Create a separate ‘Disposal Register’ tab (or a separate workbook if your volume warrants it). This is the log of every disposal action taken, distinct from the schedule itself.
- For each disposal event, record: the record class and description, the RDA authority cited, the disposal trigger and confirmation that it was met (e.g. ‘Matter closed 14 March 2024; seven-year trigger met 14 March 2031’), the disposal method (destruction, transfer to PROV, deletion), the date of disposal, and the authorised officer who approved it.
- Where physical records are destroyed, retain a destruction certificate from the destruction provider, and attach a reference to it in the Disposal Register. A disposal decision without a destruction certificate is incomplete.
- Update the Status column in the main schedule to ‘Disposed’ for each affected record class, with a cross-reference to the corresponding Disposal Register entry.
- Review the Disposal Register at each cycle for completeness. Entries should exist for every disposal action, not just the ones that felt significant at the time.
What to watch out for: Over-retention is a compliance risk that many government agencies don’t realise. There’s a natural instinct to leave records in storage when disposal feels complex or uncertain, but PROV’s disposal authorities define authorised retention periods, not minimum ones. Holding records past their trigger date creates ongoing privacy exposure and unnecessary storage costs. For agencies already managing significant physical holdings, the true cost of over-retention compounds quietly over time. A spreadsheet can document disposal actions, but it can’t enforce them, prompt them, or generate a formal disposal certificate. That step will always be manual.
The Signals That a Spreadsheet-Managed Schedule Has Outgrown Its Purpose
None of the above is a reason to abandon a spreadsheet-managed retention schedule today. For smaller agencies, for well-resourced records teams, and for organisations with a manageable volume of record classes, Excel can work well when maintained properly. The question is how to recognise when Excel is no longer fit for purpose.
Some of the signals worth paying attention to:
- The schedule hasn’t been reviewed against current PROV authorities in more than twelve months. PROV may have updated the RDAs that are sitting idle in your Excel file, meaning retention requirements may have changed without anyone realising.
- Multiple people are editing the file with no clear version control or documented change log
- Disposal actions aren’t being logged at the time they occur, only retrospectively or not at all
- Records are held past their disposal trigger because the review cycle hasn’t run, and the storage costs of those over-retained records are accumulating in the background
- An FOI request or audit has surfaced a record that couldn’t be located or whose status couldn’t be confirmed — the kind of retrieval delay that starts as an inconvenience and becomes a governance issue
- Physical records in storage never made it onto the retention schedule to begin with — a backlog of unindexed holdings that sits outside any review cycle, accumulating liability that the register can’t account for because it doesn’t know those records exist
- The person who built the schedule has left, and institutional knowledge of how to interpret it has left with them
These aren’t failures of the agencies managing the schedule. They’re the natural consequences of using a static tool to manage a dynamic, legally significant process at scale. The spreadsheet was never designed to enforce review cycles, produce disposal certificates, track changes with attribution, or flag when an RDA is updated. It does what it does — and those are the gaps that sit outside what it was built for.
There’s a More Manageable Way
For Victorian government agencies wanting to check that their current records retention schedule references the right PROV authorities before relying on it for disposal decisions, Compu-Stor’s PROV RDA Finder is a practical starting point. It’s a free, interactive tool that lets you search across PROV’s disposal authorities by keyword or function, find the right RDA class, and confirm the disposal trigger and action, without downloading a single PDF.
For agencies with a backlog of physical records that need to be reviewed, scheduled, or disposed of, Compu-Stor provides a complete, PROV-compliant pathway from retention assessment through to certified physical destruction, with full chain-of-custody documentation and a disposal certificate for your records.
If you’d like to talk through how that works for your agency, get in touch.
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.
The RDA Finder is designed to support retention decisions and should be used as a guide. For complex or edge-case record types, we recommend confirming the outcome with your Records Manager or contacting PROV directly.
This guide is intended as general guidance. For complex records or edge-case situations, we recommend confirming disposal decisions with your Records Manager or contacting PROV directly.
