Category: Classification and Taxonomy

Business Classification Scheme

Also known as: BCS, file plan, file classification scheme

Simply put

A Business Classification Scheme is a tool that organizes an organization's records according to the functions and activities it performs, rather than by department or physical location. It provides a consistent framework for classifying, titling, retrieving, and managing records and information across the organization. It is often regarded as a foundational information governance tool, though its exact structure depends on the organization and its work.

Formal definition

A Business Classification Scheme (BCS) is a hierarchical framework, typically derived from an analysis of an organization's business functions and the activities and processes within them, used to classify, title, access, and retrieve records. Rather than mirroring organizational structure, a BCS is generally organized by function and activity, which supports consistency as structures change over time. It commonly underpins related recordkeeping controls such as retention scheduling and metadata assignment, and in some contexts the term is used interchangeably with 'file plan' or 'file classification scheme,' though practitioners should note that specific arrangements, terminology, and the degree to which a BCS drives disposition vary by organization and jurisdiction.

Why it matters

A Business Classification Scheme matters because it provides a stable, function-based framework for organizing records that does not depend on an organization's current departmental structure. Because organizational structures are frequently reorganized, renamed, merged, or dissolved, classifying records by the functions and activities an organization performs, rather than by the units that happen to perform them, tends to produce a more durable and consistent arrangement over time. This consistency supports reliable classification, titling, access, and retrieval of records across the organization.

A BCS is often regarded as a foundational information governance tool because it commonly underpins other recordkeeping controls. Retention scheduling and metadata assignment, for example, are frequently linked to the functions and activities defined in a scheme, so a well-constructed BCS can improve the coherence of these downstream processes. Where classification is inconsistent or ad hoc, organizations may struggle to locate records, apply appropriate retention, or demonstrate control over their information holdings.

The practical value of a BCS depends heavily on how well it reflects the organization's actual business and on how consistently it is applied. A scheme derived from a genuine analysis of business functions and processes is more likely to remain useful, whereas one that simply mirrors a temporary organizational chart may become outdated quickly. Practitioners should note that the specific structure, terminology, and the degree to which a BCS drives disposition vary by organization and jurisdiction, so its benefits are realized through sound design and ongoing maintenance rather than by adoption alone.

Who it's relevant to

Records managers

Records managers are typically responsible for designing, implementing, and maintaining a Business Classification Scheme. They analyze business functions and activities to build the framework, oversee its consistent application, and often link it to retention scheduling and other recordkeeping controls. Keeping the scheme aligned with how the organization actually works, rather than with a transient organizational chart, is generally a core part of their role.

Information governance officers

For information governance professionals, a BCS is often treated as a foundational tool within a broader accountability framework. Because it supports consistent classification, titling, access, and retrieval across the organization, it can contribute to wider governance objectives, though it does not by itself address the full range of policy, risk, privacy, security, and value concerns that information governance encompasses.

Archivists

Archivists have an interest in how records are classified and arranged, since a function-based scheme can support the identification, description, and eventual disposition of records, including transfer or permanent preservation where applicable. The degree to which a BCS informs archival arrangement and disposition varies by organization and jurisdiction.

Staff who create and capture records

Employees across the organization who create, capture, and file records rely on a BCS, whether or not they use that term, to title and place records consistently. Clear, function-based classification helps ensure that records can be located and managed by others, though the benefits depend on staff applying the scheme correctly and on the scheme being designed to reflect their actual work.

Inside BCS

Function-based structure

A Business Classification Scheme (BCS) is typically organized around the functions and activities an organization performs, rather than around its organizational units or physical file locations. This function-based approach tends to be more stable over time, as functions often persist even when departments are reorganized or renamed.

Hierarchical levels

A BCS commonly arranges recordkeeping concepts in a hierarchy, frequently moving from broad functions to narrower activities and then to specific transactions or groupings of records. The exact number and naming of levels can vary depending on organizational policy and the methodology adopted.

Controlled terminology

The scheme provides a consistent, agreed vocabulary for describing and grouping records. This supports uniform classification across the organization and helps reduce ambiguity in how records are titled and located.

Basis for related controls

A BCS often serves as a foundation to which other recordkeeping controls can be linked, such as retention and disposition rules, access and security designations, and metadata. It is important to note that the BCS itself is a structuring tool and is distinct from the retention schedule or security model that may be mapped onto it.

Relationship to information governance

While a BCS is primarily a records management instrument concerned with organizing records as evidence of business activity, it can also support broader information governance aims. The two are related but distinct: the BCS addresses classification structure, whereas information governance encompasses a wider accountability framework spanning policy, risk, privacy, and value.

Common questions

Answers to the questions practitioners most commonly ask about BCS.

Is a business classification scheme the same as a file plan?

Not exactly, although the terms are often used interchangeably in practice. A business classification scheme is typically a hierarchical representation of an organization's functions and activities, used to group records according to the business context in which they are created. A file plan is generally the more operational instrument that maps records into containers or aggregations for day-to-day filing, and it is often derived from or aligned with the classification scheme. In many implementations the file plan applies retention rules and access controls at the aggregation level, while the classification scheme provides the underlying functional structure. The relationship depends on organizational policy and the recordkeeping system in use.

Should a business classification scheme mirror the organization's departmental or org-chart structure?

This is a common assumption, but classification schemes are more typically built around functions and activities rather than around organizational units. Structuring a scheme by department can create difficulties because organizational structures tend to change more frequently than the underlying functions an organization performs. A function-based approach is often considered more stable and more resilient to restructuring, since the classification remains valid even when reporting lines or business units are reorganized. The appropriate approach depends on organizational needs and how the scheme will be maintained over time.

How do we decide how many levels a classification scheme should have?

The number of levels depends on the size and complexity of the organization and on how the scheme will be used. Many schemes use a small number of levels, often moving from broad functions to activities and then to more granular groupings, but there is no single correct depth. Practitioners typically balance the need for enough granularity to support consistent classification, retention, and retrieval against the risk that excessive depth makes the scheme hard for users to navigate and maintain. It is often advisable to design for the level at which retention rules and access controls will realistically be applied.

Who should be involved in developing a business classification scheme?

Development commonly draws on records and information governance staff working alongside representatives from the business areas whose functions and activities are being described. Input from those who perform the work is often valuable for capturing how functions and activities actually operate, while records specialists help ensure the structure is consistent and supports retention and disposition. Depending on organizational policy, legal, compliance, privacy, and IT stakeholders may also be consulted so that the scheme aligns with retention obligations, access requirements, and system capabilities. The mix of participants varies by organization and sector.

How can we keep a classification scheme current as the organization changes?

Ongoing maintenance is generally treated as a governance responsibility rather than a one-time project. Because functions can evolve and new activities emerge, many organizations establish a review process, assign clear ownership, and use change-control procedures to add, amend, or retire classes in a documented way. Basing the scheme on functions rather than organizational structure can reduce the frequency of major changes. The appropriate review cycle and level of formality depend on organizational policy and the rate of change in the business.

How does a classification scheme relate to retention and disposition?

A classification scheme often provides the framework to which retention and disposition rules are applied, so that records grouped under a given function or activity can be managed consistently through their lifecycle. In many implementations, retention periods and disposition actions are linked to classes or to the aggregations derived from them, allowing decisions about retention, transfer, permanent preservation, or destruction to be applied systematically rather than record by record. The classification scheme itself does not determine retention outcomes; those are set by a retention schedule informed by business, legal, and regulatory requirements that vary by jurisdiction and sector.

Common misconceptions

A Business Classification Scheme is the same as a retention schedule.

The two are related but serve different purposes. A BCS organizes records according to functions and activities, while a retention schedule specifies how long records are kept and what disposition action applies. Retention and disposition rules are often mapped onto a BCS, but the classification structure and the retention instrument remain conceptually separate.

A BCS should mirror the organization's departmental or reporting structure.

A BCS is typically built around functions and activities rather than organizational units precisely because functions tend to be more durable. Structuring the scheme by department can make it fragile, since it may require rework whenever the organization is restructured.

A BCS is simply a folder structure or a file plan for storing documents.

Although a BCS can inform how records are grouped and located, its purpose is broader than a storage layout. It provides a controlled, function-based framework for classifying records as evidence of activity and for linking recordkeeping controls, which distinguishes it from an ad hoc folder hierarchy used for convenience.

Best practices

Base the scheme on the organization's functions and activities rather than on its current departmental structure, so that the classification remains stable through reorganizations.

Use consistent, controlled terminology throughout the scheme to reduce ambiguity and support uniform classification across the organization.

Keep the BCS conceptually distinct from, but capable of linking to, related controls such as retention and disposition rules and access or security designations.

Develop the scheme in consultation with the business areas whose functions and activities it describes, to ensure the structure reflects actual work and is usable in practice.

Review and maintain the scheme periodically so that it continues to reflect the organization's functions as they evolve, while avoiding unnecessary churn to the underlying structure.

Document the scope and intended purpose of the scheme so that users understand what it covers and how it relates to other records management and information governance instruments.