Why three rules beat three hundred
A business can't run hundreds of separate retention rules. The aim of a schedule is the fewest rules that still meet every requirement, with exceptions made visible.
Say a business has found 1,125 retention requirements that apply to it. The obvious schedule has 1,125 lines. It’s complete, and nobody will ever use it.
Why long schedules fail
- Nobody can remember them. Staff need to know how long to keep a client file, not look up thirty different provisions.
- They can’t be applied in systems. A payroll or CRM system can take a handful of rules. It can’t take hundreds.
- They can’t be kept current. Every change to the law touches a line, and the more lines, the more places for the schedule to be out of date without anyone noticing.
- They bury what matters. When everything is a line, the records that need decades are indistinguishable from the ones that need a year.
Why a single rule fails too
At the other extreme, “keep everything seven years” is easy to follow and wrong. It’s too short for some records, too long for others, and silent about the records the law requires you to destroy.
The aim
The target is a middle path: the fewest rules that still meet every requirement, with the rest shown as exceptions.
In ScheduleOne’s example NSW aviation company, three rules meet 997 of the 1,125 requirements. The other 128 are shown individually, each with the law that sets it apart: records kept longer, records destroyed sooner, records kept until an event, and periods the business has to decide.
That is a useful way to look at any schedule:
| What the schedule shows | What it tells you |
|---|---|
| A few rules | The business has something it can run |
| A short list of exceptions | The law has been read, not averaged |
| Each linked to its source | The schedule can be checked |
What it costs to get there
Rules like these can’t be chosen by looking at the list. Each one has to meet every requirement it covers, respect any maximum, and count from a date the business can find. Getting that right across a thousand requirements is real work, which is why most schedules end up either too long or too blunt.
Where to go next
- The 7·7·7 method: what it achieves.
- Exceptions: the records that need longer.