Skip to main content
Records Authority
Category: Disposition and Destruction

File Break

Simply put

A file break is a planned cut-off point at which an ongoing series of records is divided into regular segments, such as by year or by another interval. Grouping records this way allows a whole block to be stored, transferred, or destroyed together once it is no longer needed. This makes managing large, continuously growing record sets more practical.

Formal definition

In recordkeeping, a file break denotes a defined point at which a record series is separated into regular intervals so that discrete portions can be handled as a block for storage or disposition purposes. Establishing file breaks typically supports the consistent application of retention and disposition actions, since each segment can be closed off and subjected to its scheduled treatment, whether continued storage, transfer, or destruction, as a unit rather than record by record. The specific interval and criteria for a file break generally depend on organizational policy, the nature of the series, and applicable retention requirements, which vary by jurisdiction and sector. Note that 'file break' in this records management sense should not be confused with unrelated uses of the term in other domains, such as a fractured endodontic instrument, a corrupted computer file, or line-break characters in text files.

Why it matters

File breaks address a practical challenge in records management: series that grow continuously, such as ongoing correspondence, transaction logs, or case files, can be difficult to manage if each record must be assessed and dispositioned individually. By establishing a defined cut-off point, an organization can treat a whole segment of a series as a single unit, closing it off and subjecting it to its scheduled retention and disposition treatment as a block. This typically makes storage, transfer, and destruction more consistent and administratively feasible.

The significance of file breaks lies in how they support the reliable application of retention schedules. When a segment is closed at a regular interval, the clock on its retention period can begin against a clear reference point, and the entire block becomes eligible for its next disposition action at the same time. Without such breaks, an open-ended series can accumulate indefinitely, obscuring which records have met their retention requirements and complicating defensible disposition. The specific interval and criteria generally depend on organizational policy, the nature of the series, and applicable retention requirements, which vary by jurisdiction and sector.

Professionals should be careful not to confuse the recordkeeping sense of 'file break' with unrelated uses of the term in other domains. The phrase appears in contexts such as a fractured instrument in dentistry, a corrupted computer file, or line-break characters in text files, none of which bear on the records management concept. Maintaining this distinction helps ensure that policy, procedure, and system configuration discussions remain grounded in the correct meaning.

Who it's relevant to

Records Managers
Records managers use file breaks to structure continuously growing series into manageable segments, enabling storage, transfer, and destruction to be applied to whole blocks rather than individual records. This supports the consistent execution of retention schedules and more defensible disposition practices.
Archivists
Archivists encounter file breaks when appraising and processing record series, since breaks define the discrete portions that may be transferred for permanent preservation or otherwise dispositioned as a unit. Understanding where and how a series was broken helps clarify the boundaries of the material being handled.
Information Governance Officers
Those responsible for governance policy set the intervals and criteria that determine how file breaks are applied across the organization. Because appropriate intervals depend on the nature of each series and on retention requirements that vary by jurisdiction and sector, governance officers help ensure breaks align with policy and applicable obligations.
Compliance and Records Systems Administrators
Those configuring recordkeeping systems translate file break rules into practical system behavior, so that segments close at the defined points and become eligible for their scheduled treatment as blocks. Accurate configuration helps prevent series from accumulating indefinitely and supports the reliable timing of disposition actions.

Inside File Break

File Break Point
The defined moment at which an existing file or recordkeeping aggregation is closed and a new one is opened, typically triggered by criteria such as elapsed time, volume, or the completion of an activity, depending on organizational policy.
Cut-off Criteria
The rules that determine when a break occurs. Common bases include periodic cut-offs (for example, at the end of a defined time interval), event-based cut-offs tied to the conclusion of a matter or transaction, and volume-based cut-offs when a file reaches a size threshold. The applicable criteria vary by classification scheme and organizational practice.
Closed File
The aggregation that results once a break is applied. Closing a file generally means no further records are added to it, which supports the stability needed for consistent retention calculation. Closure is distinct from destruction or transfer, which are later disposition actions.
Retention Trigger Relationship
The link between the file break and the point from which a retention period is often calculated. In many recordkeeping systems, the retention clock begins at or after the cut-off rather than at the creation of individual records, though the precise trigger depends on the retention schedule and jurisdiction.
Successor Aggregation
The new file opened to receive subsequent records once the prior file is closed, maintaining continuity of the recordkeeping series while keeping each aggregation bounded and manageable for disposition purposes.

Common questions

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

Does a file break mean the file is being destroyed or deleted?
No. A file break does not itself involve destruction or deletion. It is the point at which an existing file is closed to further additions and a new file is opened to continue capturing related records. Closing a file typically starts, rather than ends, the retention and disposition process; the closed file is then subject to whatever retention period and disposition action apply under organizational policy and applicable requirements. Destruction, if it occurs at all, is a separate disposition outcome that happens later and only where permitted, and disposition may instead involve transfer or permanent preservation.
Is performing a file break the same as archiving the records?
Not necessarily. A file break marks the closure of one file and the opening of a successor file, whereas archiving refers to moving records into arrangements for longer-term keeping, which in some jurisdictions and organizations may include transfer to an archival authority for permanent preservation. A closed file may be retained in place, moved to secondary storage, transferred, or eventually disposed of, depending on its retention rules. Treating the file break as automatically equivalent to archiving can obscure these distinct downstream steps, so the two concepts are best kept separate.
What events typically trigger a file break?
Triggers vary by organizational policy and the classification scheme in use, but common ones include the end of a defined period such as a calendar or financial year, the file reaching a set size or volume threshold, the completion of a transaction, case, or project, or an administrative change such as a reorganization. Some schemes apply periodic breaks by default, while others break on event completion. The appropriate trigger often depends on how retention is calculated, since the closure point frequently influences when a retention period begins to run.
How should the relationship between a closed file and its successor be recorded?
It is generally advisable to maintain metadata that links the closed file to the new file that continues the same activity, so the continuity of the record series remains clear over time. This often includes recording the closure date, the reason for the break, and cross-references in both directions. Preserving these links supports the authenticity and usability of the records as evidence and helps ensure that related records can be located together even though they sit in separate files.
When does the retention period start relative to a file break?
In many recordkeeping schemes the retention period for a file is calculated from its closure rather than from its opening, so the file break often functions as the reference point from which retention is measured. However, this depends on how the retention schedule is defined and on applicable requirements, which vary by jurisdiction and sector. Because of this, it is important to confirm how each retention rule treats the trigger date rather than assuming a single approach applies to all files.
How can file breaks be handled consistently in an electronic recordkeeping system?
Consistency is typically supported by configuring the system so that closure rules are applied according to defined triggers, by preventing further additions to a closed file, and by ensuring that closure events and the links to successor files are captured in metadata. Documenting the rules in policy and applying them systematically helps maintain the integrity of file structures across large volumes. The specific capabilities available will depend on the system in use and on how it has been configured against the organization's classification and retention framework.

Common misconceptions

A file break is the same as destroying or disposing of the records in the file.
A file break closes an aggregation to further additions; it does not by itself destroy, transfer, or otherwise dispose of the contents. Disposition is a separate lifecycle action that typically occurs later, once any applicable retention period has elapsed, and disposition may include transfer or permanent preservation rather than destruction.
File breaks always happen at the end of a fixed calendar period.
Periodic cut-offs are common, but breaks may instead be based on the completion of an event or matter, or on file volume, depending on the classification scheme and organizational policy. The appropriate basis depends on the nature of the activity being documented.
The retention period is measured from when each record was created, so file breaks have no bearing on retention.
In many recordkeeping systems the retention period is calculated from the file break or cut-off rather than from the creation of individual records. Consistent application of file breaks therefore supports defensible and repeatable retention calculation, though the exact trigger depends on the applicable schedule and jurisdiction.

Best practices

Define clear, documented cut-off criteria in your file plan or classification scheme, specifying whether breaks are periodic, event-based, or volume-based for each type of aggregation.
Apply file breaks consistently so that retention periods can be calculated reliably and disposition decisions remain defensible.
Keep the file break (closure to further additions) conceptually and operationally separate from later disposition actions such as transfer, permanent preservation, or destruction.
Ensure that closing a file and opening its successor aggregation preserves continuity of the record series without leaving gaps or overlaps.
Confirm how each retention schedule defines its trigger point, since the retention clock may start at the file break rather than at individual record creation, and align system configuration accordingly.
Review file break rules periodically against organizational policy and any applicable jurisdictional or sector requirements, recognizing that these may vary.