Skip to main content
Records Authority
Category: Records Lifecycle Concepts

Recordness

Also known as: record-ness, qualities of a record
Simply put

Recordness refers to the set of qualities that make a piece of information a record, rather than just information or data. In broad terms, something has recordness when it captures the content of an activity, when that content is fixed, and when enough surrounding context is preserved to show what the record documents and why. The term reflects the recordkeeping community's ongoing effort to pin down what genuinely counts as a record.

Formal definition

Recordness denotes the characteristics that distinguish a record from undifferentiated information, data, or transitory material. Drawing on prevailing recordkeeping thought, these characteristics typically include content that preserves evidence of a human action or activity, fixity of that content, and the retention of at least some of the contextual information needed to interpret and rely upon the record. Definitions of what constitutes a record vary by jurisdiction and framework; for example, some define a record as information created or received in the course of business and preserved as evidence, while statutory definitions (such as those in certain state records laws) focus on information prepared, owned, used, or retained by an agency regardless of format. Recordness should not be confused with the everyday sense of any stored file; in recordkeeping practice it is closely associated with properties such as authenticity, reliability, integrity, and usability, and it helps differentiate an authoritative record from a copy, a draft, or transitory information. The precise threshold at which information acquires recordness depends on organizational policy, applicable law, and the framework applied.

Why it matters

Recordness matters because it marks the boundary between information an organization must manage as evidence of its activities and the far larger mass of data, drafts, and transitory material that flows through everyday operations. Not everything stored in a system is a record, and treating every file as one would make retention, disposition, and discovery obligations unmanageable. Conversely, failing to recognize that a given item has recordness, that it captures the content of an activity, in fixed form, with enough context to be understood, can lead to premature destruction, gaps in the evidentiary trail, or an inability to demonstrate what an organization did and why.

The concept also underpins trust in the records that organizations rely on. The qualities associated with recordness are closely tied to authenticity, reliability, integrity, and usability; without them, it becomes difficult to distinguish an authoritative record from a mere copy, a working draft, or something that should have been discarded. This distinction has practical consequences for legal proceedings, regulatory compliance, freedom of information responses, and audits, where the ability to show that a record genuinely documents an activity can be decisive.

Because definitions of what counts as a record vary by jurisdiction and framework, recordness is not a single fixed threshold but a set of qualities applied against applicable law and organizational policy. As the archival community itself acknowledges, pinning down the meaning of "record" has been a persistent and unfinished effort. Understanding recordness helps practitioners make defensible, consistent decisions about what to capture, keep, and eventually dispose of, rather than defaulting to keeping everything or nothing.

Who it's relevant to

Records managers
Records managers apply the concept of recordness when deciding what must be captured and controlled as a record versus what can be treated as transitory or a working copy. A clear grasp of the qualities involved, evidential content, fixity, and sufficient context, supports consistent classification, retention, and disposition decisions that align with organizational policy and applicable law.
Information governance officers
For those responsible for the broader accountability framework, recordness helps clarify where records management obligations begin within the wider universe of information and data. It informs policy on capture, ownership, and evidential value, and it helps scope which items attract the retention, privacy, and disposition controls that governance frameworks coordinate.
Archivists
Archivists are directly engaged with recordness as the archival community's ongoing attempt to define what a record is. The concept bears on appraisal and on preserving the authenticity, reliability, integrity, and usability of records selected for long-term retention or permanent preservation, including the context needed to interpret them over time.
Compliance and legal professionals
Because the distinction between an authoritative record and a copy, draft, or transitory item can be decisive in litigation, audits, and freedom of information responses, compliance and legal professionals benefit from understanding recordness. Definitions vary by jurisdiction and sector, so they should assess recordness against the statutory and regulatory definitions that apply in their context rather than a single universal standard.
Data protection professionals
Data protection professionals encounter recordness where personal information overlaps with material that qualifies as a record. Recognizing which information has acquired recordness, and therefore may be subject to specific retention or evidential obligations, helps reconcile records requirements with privacy principles, though the balance depends on applicable law and organizational policy.

Inside Recordness

Authenticity
The property of being what it purports to be, created or sent by the person purporting to have created or sent it, at the time purported. Authenticity supports the capacity of a record to serve as evidence of the activity it documents.
Reliability
The extent to which a record can be trusted as a full and accurate representation of the transaction, activity, or fact to which it attests. Reliability is typically linked to the circumstances of the record's creation and the authority of its creator.
Integrity
The completeness and unaltered state of a record. A record with integrity is protected against unauthorized or undocumented change; where authorized changes occur, they are typically tracked so the record remains reliable evidence.
Usability
The property that allows a record to be located, retrieved, presented, and interpreted over time. Usability depends on maintaining the connections between the record, its context, and the activity it documents.
Evidential context
The metadata and relationships that link a record to the business activity, the actors involved, and other related records. This contextual linkage is often what distinguishes a record from isolated information or data.
Fixity of content
The characteristic that a record captures and holds a stable representation of a transaction at a point in time. This distinguishes an authoritative record from dynamic information, working data, or transitory material.

Common questions

Answers to the questions practitioners most commonly ask about Recordness.

Does saving a file or storing information automatically make it a record?
No. Storing information does not by itself confer recordness. A record is distinguished from mere information or data by properties such as authenticity, reliability, integrity, and usability, together with its function as evidence of an activity or transaction. Much stored content, drafts, working copies, and transitory information, may never acquire these qualities. Whether something is a record typically depends on its role in documenting a business activity and on how it is captured and managed, not simply on the fact that it was saved.
Is every copy of a record also a record?
Not in the sense that matters most for recordkeeping. Recordness is usually associated with an authoritative record, the version relied upon as evidence, rather than with every duplicate in circulation. Copies, drafts, and convenience versions may share content but generally lack the same status, controls, and evidential weight. Organizations often designate an authoritative or official record and treat other instances differently, though the precise treatment depends on organizational policy and, in some matters, on jurisdictional requirements.
How can we tell whether a given item should be treated as a record?
Assessing recordness typically involves examining whether the item provides evidence of a business activity or decision, and whether it can be shown to be authentic, reliable, and to have integrity and usability over time. Many organizations apply this test through classification and capture processes, distinguishing records that must be controlled from transitory information that can be deleted routinely. The specific criteria and thresholds usually derive from organizational policy and any applicable legal or regulatory obligations, which vary by jurisdiction and sector.
What steps help preserve recordness once something has been captured?
Recordness is generally sustained by maintaining the qualities that define it. In practice this often includes controlling changes so integrity can be demonstrated, keeping contextual and structural metadata that supports authenticity and reliability, and ensuring the record remains usable and retrievable across its lifecycle. These controls typically apply from capture through retention and up to disposition, which may involve destruction, transfer, or permanent preservation depending on policy and applicable requirements.
How does metadata contribute to establishing recordness?
Metadata often supports several of the properties associated with recordness. Contextual metadata can help establish authenticity and reliability by linking the record to the activity, agent, and time of creation, while metadata documenting management actions can support demonstrable integrity. Metadata may also aid usability by enabling retrieval and interpretation over time. The particular metadata considered necessary typically depends on organizational policy and any relevant standards or obligations.
How should transitory information be handled so it does not accumulate as if it were a record?
Organizations commonly distinguish transitory information from records at the point of capture or classification, so that material lacking evidential value is not managed with the same controls or retention as records. This often supports routine, defensible deletion of transitory content under organizational policy. Because obligations to retain certain information can arise, for example under a legal hold or statutory retention requirement that varies by jurisdiction and sector, such disposal is generally governed by policy rather than left to individual discretion.

Common misconceptions

Any stored document or piece of data automatically qualifies as a record.
Recordness depends on properties such as authenticity, reliability, integrity, and usability, together with contextual links to the activity documented. Information, data, drafts, and transitory material may lack these properties and therefore may not function as records.
A copy of a record carries the same authoritative status as the record itself.
The distinction between an authoritative record, a copy, and a draft is central to recordness. A copy may serve reference purposes but does not necessarily hold the same evidential weight, and organizational policy typically governs which instance is treated as the authoritative record.
Recordness is a fixed, one-time judgment made at creation.
The properties supporting recordness must often be maintained across the lifecycle. Integrity and usability, in particular, depend on ongoing controls, since loss of context or uncontrolled alteration can erode a record's evidential value over time.

Best practices

Assess whether an object exhibits authenticity, reliability, integrity, and usability before treating it as an authoritative record, rather than assuming all stored content qualifies.
Capture and maintain the contextual metadata that links a record to its originating activity, actors, and related records, since this linkage is often what confers recordness.
Distinguish clearly between authoritative records, copies, drafts, and transitory information in classification and naming conventions so users understand which instance carries evidential status.
Apply controls that protect integrity, documenting any authorized changes so that alterations are transparent and the record remains reliable evidence.
Sustain usability throughout the lifecycle by ensuring records can be located, retrieved, and correctly interpreted, giving particular attention to format and context preservation over time.
Align local definitions of what constitutes a record with organizational policy and applicable requirements, recognizing that specific obligations may vary by jurisdiction and sector.