How do you classify records to a file plan so they map to the right retention category?

Classifying records to a file plan is the step that connects a document to the rule that governs how long it must be kept and what happens to it afterward. When done consistently, every record “inherits” the retention period and disposition instruction tied to its place in the plan, so no one has to decide case by case.

Understand the building blocks

A file plan is a structured map of the categories of records your organization creates, usually organized by business function and activity rather than by department or person. Each category in the plan is linked to a records schedule that defines the retention period and the final disposition (destroy, transfer, or permanent retention).

The goal is to assign every record to the category that best reflects what the record documents and the function it supports — not where it happens to be stored.

How classification works in practice

1. Identify the business function and activity. Ask what process the record is evidence of (for example, a contract, a personnel action, a policy decision). Function-based classification is more stable over time than org-chart-based filing.
2. Match to the file plan category. Place the record in the category whose scope note describes that activity. Scope notes and examples help resolve ambiguous cases.
3. Inherit the retention rule. Once the record sits in a category, it picks up that category’s retention period and disposition automatically.
4. Set the retention trigger. Most schedules start the clock from an event — case closed, contract expired, employee separated. Capture that trigger so the disposition date can be calculated.

Keep classification reliable

• Write clear scope notes and decision rules so different people classify the same record the same way.
• Classify at creation or capture, while context is fresh, rather than retroactively.
• Apply metadata (function, record type, trigger date) consistently so retention can be applied and audited systematically.
• Review the file plan periodically as functions and schedules change, and document a defensible process.

Strong classification depends on a well-maintained file plan and current schedules. For related guidance, see the retention and disposition topic hub.