Records And Information Management

Records and information management (RIM) is the discipline of controlling the documents an organization creates in the course of its business—not for their historical interest, but because they are needed to run the organization, prove what it did, and defend it in court.

12 frameworks, from 1500 to today · Information Science · Social Sciences

still a working view ended · each leads to its entry below

Overview

Records and information management (RIM) is the discipline of controlling the documents an organization creates in the course of its business—not for their historical interest, but because they are needed to run the organization, prove what it did, and defend it in court1. Its central problem is scale and consequence: a government, a hospital, or a corporation generates millions of documents, most of which are routine, some of which are legally binding, and a few of which must survive for decades. RIM's practitioners decide which is which, how long each is kept, who may see it, and how it is destroyed1. The field matters because the answer to those questions determines whether an organization can find what it needs, whether it can prove a claim, and whether it can protect the people whose lives are recorded in its files.

From registries to filing systems

Before there was a profession, there was the registry: a central office that received incoming correspondence, entered it in a log, assigned it a number, and filed it. European chanceries and government offices ran registries from the medieval period onward, and the practice spread with colonial and imperial administration. The registry's logic was registration—every document got an entry and an identifier, so that its existence and movement could be traced. The great registries of the nineteenth century, such as those of the British and Dutch colonial administrations, produced elaborate systems of numbered files with indexes and registers.

The late nineteenth and early twentieth centuries brought a competing idea: filing by subject, decentralized to the office that used the records. In the United States, the vertical file and the alphabetic subject file replaced bound letterbooks, and commercial filing systems—cabinet manufacturers, index-card suppliers—sold standardized schemes to businesses. The problem these systems solved was retrieval by topic rather than by sender or date; the problem they created was inconsistency, since each office devised its own headings. The response was the records manager as a specialist who designed and controlled the file plan. By the mid-twentieth century, large organizations employed records managers to run central files, mail rooms, and filing equipment, and the profession had its own associations and training.

The records life cycle

The conceptual breakthrough that made RIM a discipline rather than a clerical skill was the records life cycle, articulated in the United States in the mid-twentieth century and closely associated with the work of Emmett Leahy and the federal records management programme that followed the Second World War. The idea is simple and powerful: a record passes through stages—creation, active use, semi-active storage, and final disposition (destruction or transfer to an archive). Each stage has different requirements and costs. The life cycle gave managers a framework for deciding when a record should move from expensive office space to cheaper storage, and when it should be destroyed or preserved.

The life cycle made possible the retention schedule: a document that specifies, for each class of records, how long it must be kept and what happens at the end1. Retention scheduling turned disposition from an ad hoc decision into a planned, auditable rule. It also connected RIM to law: retention periods are driven by statutes of limitation, tax rules, and regulatory requirements, so the records manager had to read law and translate it into a schedule2. The schedule became the central artifact of the profession, and the appraisal decision—what to keep and for how long—its central judgment.

Diplomatics, metadata, and the record's identity

Running alongside the administrative tradition was a scholarly one. Diplomatics, developed in seventeenth-century Europe for authenticating medieval charters, taught that a document's trustworthiness depends on its form: who issued it, in what manner, with what seals and signatures, and according to what procedure. Archival thinkers in the nineteenth and twentieth centuries adapted diplomatics to modern records, asking what makes a record authentic and reliable. The answer lay in metadata—information about the record rather than its content: its creator, date, transaction, and chain of custody34.

This mattered practically when records moved from paper to electronic systems1. A paper file carried its context on its face and in its filing; an electronic record could be copied, altered, or orphaned from its context with no trace. The response was to build metadata requirements into systems, so that the record's identity and integrity were captured at creation. The archival diplomatics tradition, especially the work of Luciana Duranti and the InterPARES projects from the late 1990s onward, made this explicit: authenticity is not a property of the document alone but of the system that kept it.

The records continuum

In the 1990s, Australian archivists and records managers proposed an alternative to the life cycle: the records continuum5. The continuum model, associated with Frank Upward and the Monash University school, argued that the life cycle's sequential stages misrepresent how records actually work5. Records are created, used, and preserved simultaneously and continuously; the same record serves operational, regulatory, and cultural purposes at once5. The continuum reframed records management as the management of a record's multiple dimensions—its creation, its capture into systems, its organization, and its pluralization into collective memory—rather than a one-way passage through stages5.

The continuum's practical consequence was to insist that recordkeeping requirements be designed into systems from the start, not applied after the fact. It also gave the field a vocabulary for thinking about records across organizational and jurisdictional boundaries, and it influenced the development of standards.

Standards and the design-in approach

The 1990s and 2000s saw RIM professionalize through standards6. The most influential was ISO 15489, first published in 2001, which set out principles for records management: what a record is, what qualities it must have (authenticity, reliability, integrity, usability), and how a records management programme should be designed and operated. ISO 15489 gave the field a common language and a benchmark against which organizations could be audited.

Alongside the standard came a shift in method: design-in. Rather than managing records after they were created, the design-in approach—sometimes called the EDRMS (electronic document and records management system) approach—sought to build recordkeeping requirements into the systems that created records. The problem it addressed was the proliferation of electronic documents outside any controlled filing system. The solution was to make the system itself capture, classify, and schedule records automatically. The approach had mixed success: large EDRMS implementations were often expensive and unpopular with users, and the rise of shared drives, email, and later cloud collaboration tools showed how hard it was to impose central control on distributed creation.

Privacy, litigation, and the compliance turn

From the 1970s onward, privacy and data protection law gave RIM a new set of obligations. Statutes such as the U.S. Privacy Act of 1974 and, later, the European Data Protection Directive of 1995 and the General Data Protection Regulation of 2018 required organizations to limit collection, secure data, and honor access and erasure rights789. Records managers found themselves balancing retention requirements against deletion obligations: the same record might need to be kept for legal reasons and destroyed for privacy reasons, and the schedule had to reconcile them1.

A parallel pressure came from litigation. In the United States, the Federal Rules of Civil Procedure were amended in 2006 to address electronically stored information, making e-discovery—the process of identifying and producing electronic records for lawsuits—a routine organizational concern1011. Litigation readiness meant knowing what records existed, where they were, and how to suspend their destruction when a legal hold was issued11. The records manager's schedule became a legal document, and failure to follow it could be sanctioned.

Information governance

By the 2010s, the field had absorbed these pressures into a broader concept: information governance. Information governance treats records not in isolation but as one asset among many—data, documents, email, social media—and asks how an organization should govern all of it: who owns it, who may access it, how long it is kept, and how it is protected. The concept descends from RIM's retention and compliance traditions but extends them to the whole information estate, and it brings in legal, IT, security, and business stakeholders12. Its central claim is that records management is not a back-office function but a governance function, and its central problem is the same one the registry clerks faced: how to impose order on a mass of documents without losing the context that makes them trustworthy.

The present

Today RIM operates through retention schedules, classification schemes, and standards such as ISO 15489, applied increasingly to cloud platforms and collaboration tools rather than to filing cabinets. The life cycle and the continuum coexist as frameworks, the first guiding disposition planning and the second guiding system design. Privacy compliance and e-discovery remain live pressures, and information governance has become the umbrella under which they are managed12. The open questions are familiar in new form: how to capture records created in systems the organization does not control; how to preserve authenticity when records are copied across platforms; and how to reconcile the competing demands of retention, privacy, and access. The profession's history is a record of successive attempts to answer the same question—how to keep the working record findable, trustworthy, and lawfully disposed of—as the medium of the record changed beneath it.

References

  1. Records management (introduction, Concepts of record, Key records management terminology, Records management practices and concepts, Records retention schedule, Managing digital records, Current issues), Wikipedia
  2. Retention period, Wikipedia
  3. Metadata, Wikipedia
  4. Preservation metadata, Wikipedia
  5. Records continuum model, Wikipedia
  6. ISO 15489, Wikipedia
  7. Information privacy (History), Wikipedia
  8. Data Protection Directive, Wikipedia
  9. General Data Protection Regulation, Wikipedia
  10. Electronic discovery, Wikipedia
  11. Legal hold, Wikipedia
  12. Information governance, Wikipedia

The frameworks of Records And Information Management

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1500-1940

    Registry system

    How should incoming correspondence be logged and tracked?

    Fly to its tower in Nousfarer

  2. 1681-Present

    Diplomatics

    What makes a document authentic and trustworthy?

    Fly to its tower in Nousfarer

  3. 1890-1960

    Subject filing

    How should documents be filed so they can be found by topic?

    Fly to its tower in Nousfarer

  4. 1945-Present

    Records life cycle

    What stages does a record pass through from creation to disposal?

    Fly to its tower in Nousfarer

  5. 1950-Present

    Records Retention Scheduling

    How long must each kind of record be kept?

    Fly to its tower in Nousfarer

  6. 1974-Present

    Privacy and data protection compliance

    How can personal data be protected while records are kept?

    Fly to its tower in Nousfarer

  7. 1990-Present

    Archival Diplomatics and Records Metadata

    What metadata must be captured to prove a record is authentic?

    Fly to its tower in Nousfarer

  8. 1990-Present

    Records continuum model

    How are records created, used and preserved at the same time?

    Fly to its tower in Nousfarer

  9. 1995-2015

    Design-in recordkeeping

    How can recordkeeping requirements be built into systems from the start?

    Fly to its tower in Nousfarer

  10. 2001-Present

    Standards-based records management

    What principles should a records management programme follow?

    Fly to its tower in Nousfarer

  11. 2006-Present

    E-discovery and litigation readiness

    How can an organization find and produce records for lawsuits?

    Fly to its tower in Nousfarer

  12. 2010-Present

    Information governance

    Who owns and controls an organization's information?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Registry systemDiplomaticsSubject filingRecords life cycleRecords Retention SchedulingPrivacy and data protection complianceArchival Diplomatics and Records Meta…Records continuum modelDesign-in recordkeepingStandards-based records managementE-discovery and litigation readinessInformation governance

Beyond the field

Where Records And Information Management's ideas came from in other fields, and what they led to there: the strongest 12 of 58 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Records And Information Management is a planet in Nousfarer

Its city has a tower for each of these 12 frameworks. Land, walk in, and climb one concept at a time.

Land on Records And Information Management

Related fields

Fields its ideas are linked to

More in Information Science

See where Records And Information Management sits on the Map of Human Knowledge