Category: Systems and Technology

MoReq

Also known as: MoReq, Modular Requirements for Records Systems, Model Requirements for the Management of Electronic Records, MoReq2

Simply put

MoReq is a records management specification published by the DLM Forum that sets out requirements for the systems used to manage records, particularly electronic records. It aims to be practical and usable, helping organizations specify and evaluate systems that manage records reliably. The specification has been issued in more than one edition over time, including a version known as MoReq2.

Formal definition

MoReq is a specification published by the DLM Forum that describes modular requirements for records systems. Its stated purpose is to help ensure that an electronic records management system (ERMS) manages electronic records with desired levels of control, and it has been designed to be pragmatic and usable. The MoReq2 edition, an expansion of the title "Model Requirements for the Management of Electronic Records," comprises a formal requirements specification and, according to associated professional resources, supporting components such as a metadata model, an XML schema, and a testing framework. As a specification rather than a certifiable standard in the sense of ISO documents, MoReq functions primarily as a reference set of requirements for procuring, configuring, and evaluating records systems; its adoption and applicability depend on organizational and jurisdictional context. The evidence available here does not establish the current edition or specific clause-level content, so those details should be verified against the DLM Forum's published materials.

Why it matters

Selecting or building a system to manage electronic records is a consequential decision, yet organizations often lack a common, structured vocabulary for describing what such a system must actually do. MoReq addresses this gap by offering a published set of modular requirements against which records systems can be specified, procured, configured, and evaluated. This matters because a system that merely stores documents is not the same as one that manages records with defensible controls over their capture, classification, retention, and disposition. A shared reference specification helps buyers and suppliers communicate expectations precisely and reduces the risk of acquiring a system that fails to preserve the authenticity, integrity, and usability that distinguish an authoritative record from ordinary information.

Because MoReq is a specification published by the DLM Forum rather than a certifiable ISO standard, its influence is practical rather than mandatory. It provides a common baseline of requirements that organizations can draw on when writing tender documentation or assessing whether a candidate electronic records management system will manage records with the desired levels of control. Its stated design goals of being pragmatic and usable reflect an intent to serve real procurement and evaluation needs rather than to function as an abstract model.

Adoption and applicability depend heavily on organizational and jurisdictional context, and MoReq should not be treated as a universal requirement. The evidence available here does not establish the current edition or the specific clause-level content, so professionals relying on MoReq for procurement or compliance purposes should verify details against the DLM Forum's published materials rather than assuming any particular version or provision applies.

Who it's relevant to

Records managers and information governance officers

Those responsible for ensuring that records are managed as reliable evidence of activity can use MoReq as a structured reference for the controls a records system should provide over capture, classification, retention, and disposition. It offers a common vocabulary for articulating requirements, though its applicability should be assessed against organizational and jurisdictional context.

Procurement and IT teams evaluating records systems

Teams specifying, procuring, or configuring an electronic records management system can draw on MoReq's modular requirements when drafting tender documentation and assessing candidate systems. The MoReq2 edition's supporting components, reportedly including a metadata model, XML schema, and testing framework, are intended to assist with customizing and testing such systems.

Vendors and system implementers

Suppliers of records management systems may use MoReq as a reference for the capabilities their products are expected to demonstrate, helping align system design with a recognized set of requirements. Because MoReq is a specification rather than a certifiable ISO standard, implementers should confirm which edition and provisions a given customer expects against the DLM Forum's published materials.

Archivists and preservation professionals

Professionals concerned with the long-term control and integrity of electronic records may find MoReq useful as a reference for the system-level requirements that support authenticity, reliability, and usability. Its scope centers on records systems rather than on preservation strategy specifically, so it should be considered alongside other relevant guidance.

Inside MoReq

Modular Requirements Specification

MoReq (Model Requirements for the management of electronic records) is a specification setting out functional and non-functional requirements for records management systems, particularly electronic records management. Its modular structure allows organizations to select and apply the components relevant to their context rather than adopting the whole specification uniformly.

Functional requirements

MoReq typically articulates requirements for core recordkeeping capabilities such as classification, capture, retention scheduling, disposition, search and retrieval, and the maintenance of metadata. These describe what a compliant system should be able to do to manage records as evidence across their lifecycle.

Metadata and records controls

The specification generally emphasizes metadata that supports the authenticity, reliability, integrity, and usability of records, along with controls such as access permissions and audit trails intended to preserve evidential value over time.

European origin and orientation

MoReq originated in a European context and has been developed and revised through successive versions over time. It is intended to be adaptable across jurisdictions and sectors, though the precise applicability of any given version depends on organizational and jurisdictional context.

Basis for evaluation and procurement

MoReq is often used as a reference against which records management software can be assessed or specified during procurement, and as a benchmark for evaluating whether a system meets defined recordkeeping needs.

Common questions

Answers to the questions practitioners most commonly ask about MoReq.

Is MoReq a legally binding standard that organizations are required to comply with?

No. MoReq is a model specification of functional requirements for electronic records management systems rather than a binding legal standard. It is intended to guide the specification, procurement, and evaluation of recordkeeping systems. Whether any particular recordkeeping obligation is mandatory depends on the applicable jurisdiction, sector, and organizational policy, not on MoReq itself. Organizations often use MoReq as a reference point, but adopting it is typically a matter of choice rather than legal compulsion.

Is MoReq the same thing as a certified records management software product?

No. MoReq describes requirements that a records management system may be designed to meet; it is not a software product and does not, in itself, manage records. A vendor system may be assessed against MoReq requirements, but the specification and any given product remain distinct. Professionals should be careful to distinguish the model requirements from claims made about specific tools, and should evaluate whether a product actually satisfies the requirements relevant to their context.

How can MoReq be used during procurement of a records management system?

MoReq is often used as a source of functional and non-functional requirements that can be incorporated into procurement documents, such as requirements specifications or tender criteria. Organizations typically select and adapt the requirements that are relevant to their operating context, jurisdiction, and risk profile rather than applying the full set uniformly. This allows prospective systems to be compared against a common, structured baseline, though the weighting of requirements generally depends on organizational needs.

Do organizations need to implement all MoReq requirements?

Not necessarily. MoReq is generally intended to be applied selectively, with organizations tailoring the requirements to their circumstances. Some requirements may be treated as essential and others as optional or inapplicable depending on the type of records, business processes, and regulatory environment involved. Determining which requirements apply is typically part of a scoping and requirements-analysis exercise informed by organizational policy and jurisdictional obligations.

How does MoReq relate to broader records management standards and frameworks?

MoReq focuses on functional requirements for systems that manage electronic records, and it is often used alongside broader records management standards and frameworks that address principles, processes, and management systems more generally. Rather than replacing such standards, MoReq can complement them by translating higher-level recordkeeping principles into system-level requirements. Organizations should confirm how the specification aligns with the other standards and guidance applicable in their jurisdiction and sector.

What role does MoReq play in evaluating an existing records management system?

MoReq can serve as a benchmark against which the capabilities of an existing system are assessed, helping to identify gaps between current functionality and desired recordkeeping requirements. Such an evaluation typically involves mapping the relevant MoReq requirements to the system's actual features and controls, and considering how the system supports lifecycle activities such as capture, classification, retention, and disposition. The findings often inform decisions about configuration changes, additional controls, or replacement, subject to organizational priorities and constraints.

Common misconceptions

MoReq is a legally binding standard that organizations are required to comply with.

MoReq is a model requirements specification rather than a mandatory legal instrument. It is not itself a national or statutory standard, and whether or to what extent it applies depends on organizational policy, sector, and jurisdiction. Legal and regulatory obligations for recordkeeping derive from separate sources that vary across jurisdictions.

Adopting a MoReq-aligned system automatically ensures good records management.

MoReq describes system requirements, but effective records management also depends on governance, policy, classification practices, retention scheduling, and disciplined disposition carried out by people and processes. Software conformance to a specification does not by itself guarantee that records are being properly managed as evidence.

MoReq and records management are interchangeable concepts.

MoReq is one specification supporting records management by defining requirements for systems. Records management is the broader discipline concerned with controlling records across their lifecycle, and it sits within an even wider information governance framework. MoReq addresses part of this landscape rather than the whole of it.

Best practices

Treat MoReq as a modular reference, selecting and adapting only the components relevant to your organization's context, sector, and jurisdictional requirements rather than assuming wholesale adoption is necessary.

Confirm which version or profile of MoReq is being referenced, since the specification has evolved through successive revisions and requirements may differ between versions.

Use MoReq requirements as one input to system evaluation or procurement, while separately verifying that a system's conformance claims are demonstrated in practice for classification, retention, disposition, metadata, access controls, and audit trails.

Map MoReq requirements against your applicable legal, regulatory, and retention obligations, recognizing that these derive from jurisdiction- and sector-specific sources that MoReq itself does not replace.

Complement any MoReq-aligned system with governance measures, policies, and trained personnel, since sound records management depends on people and processes as well as system capability.

Document how selected MoReq components support the authenticity, reliability, integrity, and usability of records, so that the evidential value of records can be defended over their lifecycle.