A business classification scheme (BCS) organises records by the functions and activities that create them, rather than by the department that happens to hold them. The file plan is its practical expression - the hierarchy of classes, folders and rules into which records are filed. Get this right and retention, security and findability largely follow; get it wrong and everything downstream is harder.

Functional vs organisational classification

Departments reorganise constantly; the functions an organisation performs are far more stable. A scheme built on functions ("Financial Management > Accounts Payable > Supplier Invoices") survives restructures, whereas one built on the org chart ("Finance Team > Jane's folder") breaks the moment people move. Functional classification is the standard recommended by ISO 15489 for exactly this reason.

Anatomy of a file plan

  • Function - the highest level (e.g. Human Resources, Financial Management, Property).
  • Activity - the sub-function (Recruitment, Payroll, Leasing).
  • Transaction / record series - the actual groups of records (Applications, Payslips, Lease Agreements).
  • Metadata - consistent title, dates, identifiers, author and security marking attached to each record.
  • Rules - each class carries a retention rule and a security/access rule, inherited by the records filed in it.

Why the file plan is the backbone

Because retention and security are attached to classes, correctly filing a record automatically gives it the right retention period and the right access controls. Findability improves because everyone uses the same vocabulary. Disposal becomes possible at scale because you can act on a whole class at once rather than record by record.

In practice. In SharePoint / Microsoft 365 the file plan maps onto sites and libraries (functions/activities), content types (record series with their own metadata) and retention labels (the retention rules). A good BCS is what makes an M365 rollout governable rather than a dumping ground - this is covered in depth in the SharePoint for Records course (SP-01).

Common pitfalls

  • Too deep - a plan more than 3-4 levels deep frustrates users and drives shadow filing.
  • Classifying by department or by person instead of by function.
  • Inconsistent metadata, which destroys search and retention automation.
  • Designing the plan in isolation from the people who actually create the records.

Key takeaways

  • Classify by stable business functions, not by the org chart.
  • The file plan carries retention and security rules that records inherit automatically.
  • Keep it shallow, use consistent metadata, and co-design it with real users.

Check your understanding

Last modified: Saturday, 1 August 2026, 10:06 AM