File Plans and Classification

A file plan is the organizing backbone of a records program — the classification scheme that defines the categories records are filed into and links each category to its retention schedule. Classifying a record against the file plan is what determines how long it’s kept and how it’s ultimately disposed of.

What a file plan contains

A typical file plan defines a hierarchy — often functions → activities → record series — and, for each category, the retention period and disposition, plus access/security rules and ownership. It’s the bridge between what a record is about and how it must be managed.

Designing one that works

The hardest part isn’t drawing the hierarchy; it’s making one people and systems can apply consistently. Principles that help:

• Classify by function/activity, not org chart. Organizational structures change; business functions are more stable.
• Favor “big buckets.” Broad categories with shared retention are far easier to apply correctly than hundreds of granular ones — and consistency is what makes disposition defensible.
• Keep it shallow. Deep, complex hierarchies invite misfiling. Aim for the simplest structure that supports retention and retrieval.
• Use plain language. Categories should be obvious to the people filing into them.

Classification at scale

Relying on individuals to file every record correctly never worked at scale. Modern programs lean on auto-classification — rules and machine learning that assign records to file-plan categories automatically — with human review for ambiguous cases. A simpler file plan makes auto-classification more accurate, which is another reason to favor big buckets.

File plan vs. retention schedule

The two are related but distinct: the retention schedule says how long each series is kept and what happens at the end; the file plan is the structure that organizes records into those series and connects them to the schedule. You need both, and they should be designed together.

Why it matters

A clear, well-maintained file plan makes records findable and consistently managed; a confusing one quietly undermines the whole program because neither people nor automation can apply it reliably. It’s one of the highest-leverage design decisions in electronic records management.