How do you classify and file records to a file plan?

Classifying and filing records is how an organization turns scattered documents into an organized, retrievable, and defensibly managed information system. The work rests on two connected tools: a classification scheme (how records are grouped by function or subject) and a file plan (the structured map that says where each group lives and how long it is kept).

Start With the File Plan

A file plan is typically built around what the organization does rather than who created a document. Functions and activities are broken into categories, often arranged hierarchically (function, then activity, then record series). Each category in the plan is usually tied to a retention schedule and a disposition instruction, so classification and lifecycle decisions happen at the same time.

A strong file plan also captures, for each category:

• A clear title and scope note describing what belongs there
• The retention period and final disposition (destroy or transfer)
• Any access, security, or sensitivity markings
• Ownership or responsible office

How to Classify a Record

1. Identify what the record documents. Look at the business activity or transaction it supports, not just its format.
2. Match it to a category. Use the scope notes in the file plan to find the best fit; pick the most specific applicable category.
3. Apply metadata. Record the title, date, author, classification code, and any sensitivity or access markings so the item can be found and governed later.
4. File it consistently. Place the record in the same location every time the activity recurs, so like records accumulate together as a series.

Why Consistency Matters

When records are classified consistently, retention runs automatically, searches return reliable results, and legal holds, audits, or access requests are far easier to satisfy. Inconsistent or ad-hoc filing is the most common reason records become unfindable or are kept far longer than they should be.

Good Practices

• Train staff on scope notes; ambiguity causes misfiling.
• Classify at the point of creation, while context is fresh.
• Review the plan periodically as functions change.

For more foundational guidance, see the fundamentals topic hub.