Category: Classification and Taxonomy

File Plan

Simply put

A file plan is a planning tool that helps an organization keep track of what records it holds, where those records are located, and how they should be managed throughout their lifecycle. It typically acts as a roadmap that lists the different records an office maintains and often includes guidance on how and when those records may be disposed of. File plans can differ considerably from one organization to another.

Formal definition

A file plan is a primary records management planning document that defines how an organization's records are organized, located, and controlled across their lifecycle, from creation through disposition. In many implementations it takes the form of a structured or hierarchical arrangement, for example one composed of record categories and subcategories, record folders, and volumes, that establishes the organizing framework for records. A file plan commonly associates records with disposition authorities, indicating how records are to be handled at the disposition stage; in some contexts it is intended to carry up-to-date and accurate disposition authorities so that staff can apply them consistently. The precise structure, contents, and level of detail of a file plan depend on organizational policy and the recordkeeping system in use, and file plans should be maintained so that they remain current as records and requirements change.

Why it matters

A file plan is foundational to consistent recordkeeping because it establishes a shared understanding of what records an organization holds, where they are located, and how they are to be managed across their lifecycle. Without such a roadmap, records tend to accumulate in inconsistent locations under inconsistent labels, making it difficult for staff to locate authoritative records, distinguish them from copies or transitory information, and apply management controls uniformly. A well-maintained file plan reduces this fragmentation by giving offices a common framework for organizing records from creation through disposition.

The file plan also plays a central role in disposition. In many implementations it associates records with disposition authorities and is intended to carry up-to-date and accurate authorities so that staff can determine how and when records may be handled at the disposition stage and apply those decisions consistently. It is worth noting that disposition in this context is broader than destruction and may, depending on organizational policy and applicable requirements, include transfer or continued retention rather than only deletion. Because a file plan can support the consistent application of retention and disposition decisions, keeping it current is important; an outdated plan may cause staff to apply superseded authorities or lose track of where records live.

File plans can differ considerably from one organization to another in structure, contents, and level of detail. This variation reflects differences in organizational policy, sector, jurisdiction, and the recordkeeping system in use, so a file plan should be understood as a tool tailored to a specific context rather than a universal template.

Who it's relevant to

Records Managers

Records managers typically own the design and upkeep of the file plan, using it to define how records are organized and to associate them with disposition authorities. They are generally responsible for keeping the plan current so that staff can locate records and apply retention and disposition decisions consistently.

Office and Program Staff

Staff in individual offices use the file plan as a practical roadmap to determine what records they maintain, where those records live, and how they should be handled through their lifecycle. In many organizations the file plan is the reference that tells staff how to dispose of their records at the appropriate stage.

Information Governance and Compliance Leads

Those responsible for the broader governance and compliance framework may rely on the file plan as evidence that records are organized and controlled and that disposition is being managed against defined authorities. It can support consistent application of retention decisions, though specific obligations depend on jurisdiction, sector, and organizational policy.

System Administrators and Implementers

Administrators configuring records management systems often implement the file plan within the system, for example as a hierarchy of record categories, subcategories, folders, and volumes. Because implementations differ across products and organizations, they translate the organization's policy-driven plan into the structure the recordkeeping system supports.

Inside File Plan

Hierarchical classification structure

A file plan typically organizes records into a logical hierarchy, often expressed through levels such as function, activity, and transaction, or through business-based groupings that reflect the organization's work rather than its departmental structure.

Records categories or classes

The defined groupings under which records are captured and managed. These categories provide the anchor points to which classification, retention, and disposition rules are applied consistently.

Retention and disposition rules

Associations between records categories and the retention periods and disposition actions that apply to them. Depending on organizational policy and jurisdiction, disposition may include transfer, permanent preservation, or destruction, and should not be treated as synonymous with destruction alone.

Metadata and naming conventions

Descriptive and contextual information, together with consistent naming and coding conventions, that supports the identification, retrieval, and management of records within each part of the plan.

Access and security controls

Indications of who may access records in a given category and under what conditions, which may vary depending on sensitivity, privacy obligations, and organizational policy.

Linkage to business functions

A mapping between the file plan's categories and the organization's functions and activities, so that records are grouped according to the work they evidence rather than by physical location or media type.

Common questions

Answers to the questions practitioners most commonly ask about File Plan.

Is a file plan the same thing as a folder structure on a shared drive?

No, although the two are often confused. A folder structure on a shared drive is typically an ad hoc arrangement created for storage convenience, whereas a file plan is a deliberately designed classification scheme that organizes records according to business functions and activities and links them to retention and disposition rules. A folder structure may reflect a file plan, but the mere existence of folders does not constitute one. A file plan carries governance intent that a storage hierarchy, on its own, generally does not.

Does having a file plan mean records will be automatically retained and destroyed correctly?

Not on its own. A file plan provides the classification framework that associates records with retention periods and disposition actions, but it does not by itself execute those actions. Correct retention and disposition typically depend on the file plan being applied consistently, on supporting processes or system configuration, and on decisions such as legal holds that can suspend scheduled disposition. The file plan is an enabling instrument rather than a guarantee of compliant outcomes.

How is a file plan typically structured?

A file plan is often structured hierarchically, commonly moving from broad business functions to more specific activities and then to individual record groupings or file classes. Many organizations prefer a function-based structure because functions tend to be more stable over time than organizational units, which can be reorganized. The appropriate level of granularity depends on organizational needs, the volume and variety of records, and how the plan will be applied in practice.

How does a file plan relate to a retention schedule?

A file plan and a retention schedule are distinct but closely connected instruments. The file plan classifies records into categories, while the retention schedule specifies how long records in each category should be kept and what disposition action applies at the end of the retention period. In many implementations the two are mapped together so that classifying a record under the file plan also associates it with the relevant retention and disposition rules.

Who should be involved in developing a file plan?

Developing a file plan typically benefits from collaboration between records management or information governance staff and the business areas whose records are being classified, since those areas understand the functions and activities the plan must represent. Depending on organizational structure and jurisdiction, input from legal, compliance, privacy, and IT stakeholders may also be valuable to ensure the plan supports retention obligations and can be implemented in relevant systems.

How often should a file plan be reviewed or updated?

A file plan is generally treated as a living instrument rather than a fixed document, and many organizations review it periodically and when significant changes occur, such as new functions, reorganizations, or changes to legal or regulatory requirements. The appropriate review cycle depends on organizational policy and the pace of change in the business. Uncontrolled or undocumented changes should typically be avoided, as consistency over time supports the plan's usefulness for classification and disposition.

Common misconceptions

A file plan is simply a folder structure or a directory tree on a shared drive.

While a file plan may be implemented through folders, it is a governance instrument that links records categories to classification, retention, and disposition rules. A folder tree created for convenience, without associated retention and control rules, does not by itself constitute a file plan.

A file plan and a retention schedule are the same thing.

They are related but distinct. A file plan establishes how records are classified and organized, while a retention schedule specifies how long records are kept and what disposition applies. In practice the two are often connected, with the file plan providing the categories to which retention rules attach, but each serves a different purpose.

A file plan should mirror the organization's departmental or org-chart structure.

File plans are often built around business functions and activities rather than organizational units, because departments change over time while the functions an organization performs tend to be more stable. Basing the plan on functions typically produces a more durable and defensible structure.

Best practices

Base the file plan on the organization's business functions and activities rather than on departmental structure, so that it remains stable as the organization changes.

Link each records category to appropriate retention and disposition rules, keeping in mind that disposition may include transfer or permanent preservation as well as destruction, depending on organizational policy and jurisdiction.

Apply consistent naming conventions and metadata across categories to support reliable identification and retrieval of records.

Define access and security controls at the category level, taking account of sensitivity and any privacy obligations that may apply in the relevant jurisdiction and sector.

Review and update the file plan periodically to reflect changes in functions, systems, and regulatory or organizational requirements.

Develop the file plan collaboratively with the business areas whose work it represents, to ensure the categories reflect how records are actually created and used.