Running a disposal review

Most people’s retention policy is “keep everything, forever, in slightly the wrong place”. It has the merit of never destroying something needed and the defect of making everything harder to find, every year, permanently.

A retention scheme only becomes real when something actually leaves. That requires a deliberate, scheduled pass — and the pass can be designed and run without this site telling you a single number.

Why the pass has to be scheduled

Disposal decisions made item by item, in the moment, are always “keep”. Facing one document with no context, the safe answer is to hold it. Facing a labelled batch whose retention decision was made in advance, the answer is mechanical. The difference is not diligence, it’s the unit of decision.

Retention periods only exist in relation to a date. Something is kept “until” — until a period elapses, until a matter closes, until a warranty ends. Nothing tells you when the until has arrived unless something goes looking, and that something is the review.

Deferring the pass is invisible. Nothing breaks if you skip a year. The cost is diffuse: the archive grows, search results get noisier, and any obligation to dispose of things you shouldn’t still hold quietly goes unmet.

Before the first pass: the classes

The pass needs something to act on, and that something is a small set of classes — groups of records that share a disposal rule. Not categories of expense; groups that go at the same time.

Four or five is usually enough. Something like: tax-relevant financial records; records supporting an asset you still own; records relating to an open matter; warranty and proof-of-purchase; and everything else. The exact list depends on what you actually hold.

For each class you need one line: what triggers disposal, and who decided that trigger. The trigger is a period after an event or the closing of a matter. The decider is your tax authority, your adviser, a contract, a warranty term, or you.

That last column is the useful discipline. It makes visible which of your retention rules are externally imposed and which are personal preference, and it means the next person to look at the scheme — including you, in four years — knows which lines can be changed freely and which cannot. This is the structure set out at more length in how long to keep things; the numbers in it come from your own sources, not from here.

The pass itself

Once a year is the right cadence for most people. Tie it to something that already happens, so it doesn’t need remembering as a separate obligation.

Work by batch, never by item. If your archive is organised so that a year, or a class within a year, can be considered as a unit, the pass takes twenty minutes. If it can only be considered document by document, it takes a weekend and won’t happen twice.

Four questions per batch:

1. Which class is this?
2. Has its trigger occurred?
3. Is anything in it subject to something that overrides the trigger — an open dispute, an ongoing query, an asset still owned, a matter not yet closed?
4. If it’s going: is it going from everywhere?

The third question is the one that saves you. A general retention trigger is subordinate to anything live. A record about an open matter stays regardless of its age, and it stays until the matter closes and its own clock starts.

The fourth is the one people miss, and it belongs to digital archives specifically. Deleting from a live folder leaves copies in backups, in version history, in a synced device’s local cache, and in the offline drive in a drawer. Whether that matters depends on why you were disposing of it — see a synced folder is not a backup for why those copies exist and how independent they are.

Log the disposal, not the contents. One line: what class, which period, when disposed, on what basis. It’s the only way to answer “what happened to 2021” later without checking whether it’s missing or destroyed.

Keep or bin

KEEP OR BIN — a disposal pass

  · A written class list with a trigger and
    a decider per class
                    → KEEP. Without it there is no
                      scheme, only a habit.

  · A disposal log of one line per batch
                    → KEEP. Distinguishes "destroyed
                      deliberately" from "lost".

  · Anything relating to an open matter
                    → KEEP regardless of age. Live
                      overrides periodic, always.

  · Records supporting an asset you still
    own
                    → KEEP. The clock generally has
                      not started; check with whoever
                      set the rule.

  · Duplicates and superseded drafts
                    → BIN at every pass. They are
                      pure search noise.

  · "Deleted" from the live folder only
                    → NOT DISPOSED OF. Backups,
                      version history and offline
                      drives still hold it.

  · The trigger periods themselves, and
    whether disposal is ever required
                    → ASK LOCALLY. Set by your tax
                      authority, adviser or contracts,
                      and they vary.

Disposal is not always optional in the other direction

One asymmetry worth naming, because it cuts against the instinct to keep everything.

Records about other people — a contractor’s expense claim, a customer’s details, an employee’s receipts — carry handling obligations that can include not keeping them indefinitely. Receipts are richer in personal detail than people assume; what a receipt reveals goes through what is actually printed on them.

Whether any such obligation applies to you, and what it requires, is a legal question that varies considerably by jurisdiction and by what you do. This site doesn’t answer it. The practice point is only that “keep everything forever” is a decision with two kinds of risk attached, not one, and a review is the mechanism that lets you act on either.

When the pass produces nothing

Fine, and common in the first years. The output of a review can legitimately be “nothing has reached its trigger yet”, and the twenty minutes was still worth it: you checked, you know, and the classes got their annual sanity check.

What should not happen is a pass that produces nothing because the batches couldn’t be assessed. That is a filing problem rather than a retention one, and it means the archive isn’t organised into units that can be reasoned about — the naming and structure question in finding it again, and the over-keeping cost in the cost of keeping everything.

What this doesn’t settle

Any period. Any threshold. Whether disposal is permitted, or required, or forbidden in your situation. Whether a record may be disposed of once a copy exists. Whether obligations differ for personal and business records, or for records about other people.

All of that comes from your tax authority, your adviser, or the law where you are, and it varies enough that a number stated here would be wrong for most readers. What this page gives you is the machinery: classes, triggers, a cadence, and a log. Fill in the numbers from a source that knows your jurisdiction.