Category: Records Lifecycle Concepts

Record Format

Also known as: Recording Format, RECFM

Simply put

Record format refers to the way in which the information making up a record is encoded, structured, or presented, whether in analog/hardcopy or digital form. In recordkeeping, the format is generally treated as separate from the record itself, since something can qualify as a record regardless of the format in which it exists. In more technical computing contexts, the term can also describe how data is arranged or encoded for storage on a particular medium or system.

Formal definition

In records management, 'record format' denotes the physical or logical form in which recorded information is captured and maintained, spanning analog/hardcopy and digital manifestations. The status of information as a record is typically understood to be independent of format; format instead concerns the encoding, structure, and presentation of the record's content and, depending on the format, may bear on its ongoing usability, integrity, and preservation over the lifecycle. The term should be distinguished from related but narrower technical usages: a 'recording format' as a scheme for encoding data on a storage medium; a 'file format' as the encoding of information within a computer file; and system-specific senses such as IBM z/OS Record Format (RECFM) values (for example F, FB, V, VB, or U), which are data control block characteristics rather than recordkeeping concepts. Practitioners should note that format is not the same as medium, and that migration or reformatting activities may raise considerations of authenticity and integrity that fall within records management policy rather than being resolved by format choice alone.

Why it matters

The concept of record format matters because it separates two questions that are easily conflated: whether something is a record, and how that record is encoded or presented. In recordkeeping practice, information may qualify as a record regardless of the format in which it exists, whether captured in analog/hardcopy or digital form. Keeping this distinction clear helps organizations avoid the mistake of assuming that a change in format, or the absence of a familiar file type, removes the recordkeeping obligations attached to the underlying content.

Format also carries practical consequences over the record lifecycle. Depending on the format, encoding and structural choices may bear on a record's ongoing usability, integrity, and preservation, particularly where records must remain accessible for extended retention periods. Reformatting or migration activities can raise questions of authenticity and integrity that are matters of records management policy rather than issues resolved by format selection alone. Treating format as a lifecycle consideration, rather than a one-time technical decision, supports defensible retention and preservation.

Finally, the term is a frequent source of terminological confusion because it carries narrower technical meanings outside records management. In computing contexts, format may refer to how data is encoded on a storage medium or within a file. Professionals benefit from recognizing when a discussion concerns the recordkeeping sense of format and when it concerns a system-specific technical usage, so that policy conversations and technical conversations do not talk past one another.

Who it's relevant to

Records Managers

Records managers rely on the format-independence of records to ensure that recordkeeping obligations attach to content wherever it resides, whether analog/hardcopy or digital. They must also account for how format choices affect usability, integrity, and preservation across retention periods, and treat reformatting or migration as activities governed by policy rather than purely technical decisions.

Archivists and Preservation Specialists

Those responsible for long-term preservation are concerned with how format bears on the continued usability and integrity of records held for extended or permanent retention. Because migration and reformatting can raise authenticity and integrity considerations, format is a central factor in preservation planning.

Information Governance and Compliance Leads

Governance and compliance professionals benefit from the clear separation between record status and format, which prevents format from being used to argue that content is not a record. This distinction supports defensible retention and disposition decisions that turn on the nature of the information rather than its encoding.

IT and Systems Practitioners

Technical staff often encounter narrower senses of the term, such as recording formats for storage media, file formats within computer files, or system-specific values like IBM z/OS RECFM characteristics. Recognizing when a discussion concerns these technical usages versus the recordkeeping sense of format helps align systems decisions with records management requirements.

Inside Record Format

Physical or logical structure

The arrangement in which a record's content is organized and encoded, whether as a paper document, an image, an audio file, a database entry, or another form. Format concerns how the content is represented rather than the content itself.

File format specification

For digital records, the technical encoding standard that governs how the data is written and interpreted, such as a document, spreadsheet, image, or email format. The choice of specification affects how reliably a record can be rendered and read over time.

Metadata and structural relationships

The contextual and structural information that accompanies the record so that its content, structure, and context remain intelligible. Preserving format typically requires preserving these relationships, not only the content stream.

Rendering and dependency requirements

The software, hardware, or environment often needed to present a record in a usable form. A record's format may depend on specific applications or system environments, which has implications for long-term usability.

Bearing on record properties

The extent to which a chosen format supports the authenticity, reliability, integrity, and usability that distinguish a record from mere information. Format decisions can affect whether these properties can be maintained across the lifecycle.

Common questions

Answers to the questions practitioners most commonly ask about Record Format.

Is the format of a record the same thing as its file type or extension?

Not quite. File type or extension (such as a particular document or image format) is one aspect of record format, but the concept is broader. Record format typically refers to the structural and technical characteristics that determine how the content, and often the associated metadata, is arranged and rendered. Two files sharing an extension may differ in internal structure, and a single logical record may be composed of multiple technical components. It is therefore more accurate to treat file type as a contributor to format rather than a synonym for it.

Does choosing an appropriate record format by itself make a record authentic or trustworthy?

No. Format supports usability and, in some cases, helps preserve integrity over time, but it does not on its own establish the properties that make something an authoritative record. Authenticity, reliability, and integrity generally depend on how the record was created and captured, how it has been managed and protected from unauthorized change, and the metadata that evidences its context and history. A well-chosen format can assist these aims, but format is one factor among several rather than a guarantee of trustworthiness.

How should an organization decide which record format to use for a given class of records?

Decisions typically weigh several considerations together, including how long the records must be retained, whether they may be transferred or preserved permanently, the need for future accessibility and rendering, and the requirements of any applicable standards, policies, or regulatory obligations. Because these obligations can vary by jurisdiction and sector, format choices are often documented in policy and reviewed periodically. The aim is generally to select formats that keep records usable and their integrity demonstrable for as long as they are needed.

What role does format play when records are retained for long periods?

Over extended retention periods, the risk that a format becomes difficult to render or interpret tends to increase as technologies change. Organizations often address this by favoring formats that are widely supported and well documented, and by monitoring for obsolescence. Where a format is at risk, migration or other preservation actions may be considered, ideally in ways that maintain the record's integrity and usability. The specific approach usually depends on organizational policy and the value and required retention of the records concerned.

How does record format relate to the metadata that accompanies a record?

Format and metadata are distinct but connected. The format concerns how content is structured and rendered, while metadata provides contextual information about the record, such as details supporting its identification, management, and evidential value. Some formats can carry certain metadata internally, while other metadata is held separately in a recordkeeping system. Managing both together is generally important, since losing the association between a record and its metadata can undermine usability and the ability to demonstrate context.

What should be considered when records in one format must be transferred to another system or custodian?

Transfer often raises questions about whether the receiving environment can render and manage the format, and whether the record's content, structure, context, and integrity can be preserved through the process. Any conversion or migration during transfer is typically planned so that the essential characteristics of the record are retained and the change is documented. Because transfer is a form of disposition and not necessarily destruction, the applicable requirements will usually depend on organizational policy and, where relevant, jurisdictional and sectoral obligations.

Common misconceptions

The format of a record is the same as its content, so changing the format does not affect the record.

Format concerns how content is structured and encoded rather than the content itself. Migrating or converting a record between formats can affect its structure, metadata, and rendering, which may in turn bear on properties such as integrity and usability. Such changes typically warrant control and documentation rather than being treated as neutral.

Any widely used file format is inherently suitable for records that must be kept over time.

Suitability depends on factors such as how well a format can be rendered without specialized software, how stable its specification is, and whether it supports the metadata and structural relationships a record requires. A format that is convenient for current use is not necessarily appropriate for longer retention, and the choice often depends on organizational policy and the retention required.

Preserving a record's format simply means keeping the data stream unchanged.

Maintaining a usable record often depends on more than the underlying bytes. The metadata, structural relationships, and rendering environment can all be needed for the record to remain intelligible and usable, so preservation frequently addresses these dependencies as well as the content itself.

Best practices

Assess candidate formats for their ability to preserve authenticity, reliability, integrity, and usability across the retention period required, rather than selecting solely for current convenience.

Where practicable, favor formats whose specifications are openly documented and widely supported, since these typically reduce dependence on specific software or environments over time.

Capture and retain the metadata and structural relationships alongside the content, as these are often needed for a record to remain intelligible and usable in its intended format.

Document the rendering, software, or environmental dependencies a record's format relies on, so that future usability requirements can be planned for and addressed.

Treat any format migration or conversion as a controlled activity, documenting what was changed and confirming that the record's essential properties have been maintained.

Align format decisions with organizational policy, retention requirements, and any applicable jurisdictional or sector obligations, recognizing that appropriate choices may vary by context.