Waypoints are the handbook's self-assessment framework. The maturity model lets you benchmark your institution's data stewardship practice across four domains. Use it to see where you are, identify where to invest next, and make the case for resources or organisational change.
How to use this page and the DSW knowledge model
This page is the reference guide for the RDM Maturity Model. It lists all domains, indicators, and maturity levels, and links to detailed guidance for each indicator. Use it to understand what each indicator means, how maturity levels are defined, and what good practice looks like at each stage.
To run an interactive self-assessment, use the RDM Maturity Model knowledge model published in the DSW Registry. Import it into your Data Stewardship Wizard instance to get a structured questionnaire that mirrors the indicators below. DSW lets you record your institution’s responses, track progress over time, collaborate with colleagues, and export results — making it suitable for periodic benchmarking or reporting.
Minimal or no documented RDM policies and procedures. Individual researchers or departments manage research data independently
Some RDM policies and procedures are defined but not yet fully implemented across the organization
Well-defined and written RDM policies and processes, supported by technology and formal oversight. A unified approach to research data management in the organisation.
Proactive, and continuous improvement of well-established research data governance.
Legal processes are ad hoc and reactive, with no standardized framework or templates regarding RDM. Legal tasks are handled informally by various departments. Agreements go through minimal review.
Standard templates and contractual clauses are being introduced, but not consistently used. The legal department exists but does not yet support project initiation or have fully defined processes for RDM issues.
The legal framework is well-defined and standardized across the organization. A dedicated personnel is responsible for supporting the establishment of a legal framework covering RDM requirements. Comprehensive templates and standardized contractual clauses for RDM issues.
Continuously improved and optimized legal framework for research data; regularly updated to reflect RDM best practices and regulatory changes. Use of advanced, customizable templates and optimized contractual clauses for RDM issues.
Security measures for RD and services are ad hoc or minimal. There are few or no documented policies and/or procedures. Staff have limited awareness of IT security. Basic protections like antivirus software and standard firewalls are used reactively.
Implementation of documented policies/procedures for security of RD; regular staff training of recognition and response to cyber threats; access control and password management systems are in place; regular software updates and patches.
Incident response and disaster recovery plans for RD are in place and tested; proactive security measures, vulnerability testing and assessment; Multi-Factor Authentication (MFA) is enforced for sensitive systems; tools for advanced threat detection and response are in place.
ISO certification or similar (ISO/ NIST, ...); real-time threat monitoring for RD and automated response mechanisms are in place; regular audits and continuous improvement.
The organisation has a part-time Data Protection Officer (DPO) with general responsibilities (consulting) for RD. Active monitoring for data protection compliance by the DPO. Mostly, there is no standardised framework or templates regarding RDM, and most of the work is reactive.
Organisation has a full-time DPO. Guidelines, documentations and consultations are actively done by DPO for RD. No procedures in place to involve the DPO.
Established systems for Data Protection legislation compliance (ROPA, consent management, DPIA, etc.) of RD. No procedures in place to involve the DPO. Sometimes a DPO is involved at the planning stages, but not always.
Procedures are in place and the organisation is willing and actively involves a DPO at the right stages of the project. The top leaders of the organisation understand the necessity of the DPO and the processes regarding data protection. The organisation does regular auditing (internal or external), and the ongoing evaluation is taking place regarding data protection for RD. Established procedures for the exercise of Data Subject Rights.
Ethics ELSI for research data (regarding animal / human subjects, Nagoya matters)
Ethical considerations for RD are minimal and reactive. There are no formal guidelines or processes for ensuring ethical compliance in research.
Basic ethical guidelines are established, but not consistently applied. Awareness of ethical issues is growing, and some training is provided.
Ethical guidelines regarding RD are well-defined and consistently applied. Regular training and monitoring ensure compliance, and there is a clear process for addressing ethical issues.
Ethical standards regarding RD are fully integrated into the research process. Continuous improvement and proactive measures are in place, with advanced training and robust mechanisms for ensuring ethical integrity.
Only internal interaction – RDM expertise is only shared and accumulated within the organization, i.e., no further networking
Informal interaction with external RDM experts – Sharing and exchange of RDM expertise is reaching beyond the own institute, but only informally
Established network participation – Formal interaction with external RDM expert network(s) with occasional collaboration with external partners
Formal support for RDM expert networking participation – Encouragement and/or funds to attend regular forums, meetings, or platforms enable regular collaboration and sharing of RDM expertise
Professional service provision with ticketing system, usage agreements, formal documents, templates, etc; relevant services are integrated with each other
No technical infrastructure for research / RDM is available
Technical infrastructure for research / RDM is available; general usage recommendation
Technical infrastructure for research / RDM facilitates data handling along the research data life cycle; more specific usage recommendations
Usage guidelines (and/or SOPs) and automated processes are present in the technical infrastructure for research / RDM regarding, e.g., storage conditions, archiving rules, deletion rules
Lists of data assets capturing basic (non-standardized) information do not exist or exist within separate sub-units
Central catalog exists (although incomplete) with basic metadata about data assets
Central catalog exists. Procedures are in place to capture most of the datasets of organizational interest. Search allows to find data asset of interest only based on basic metadata
Centralized searchable catalog with standardized metadata allowing search of datasets in alignment with organizational goals and retrieval of metadata via API. All assets have a unique accession number
No access standards are in place on the actual format and SOPs are not in place for access decision making – (e.g., unofficial approval of management)
Standard access channel is in place. The data access requests have to be submitted
Data use conditions are reviewed upon request. Full audit trail is in place for access
Data is easily accessible and retrieval is optimised for efficiency. Access is (semi-)automated – APIs and efficient transfer channels allowing fast automated retrieval. Following standard secure protocols. Data accessibility is seamless, with advanced search and retrieval capabilities following domain standards.
Consultancy and training available, more standardized guidelines; DMP writing may be required from some researchers
DMP tool available and machine actionability facilitate further integration; DMP writing may be required for all projects
Contributors
The maturity model is maintained by the RDM Community as a whole, so contributors are
recorded against the model rather than against individual indicators.
Aina Jene
AD
Alexander Douglass
AN
Anna Niehues
AS
Anna Strachotova
Aída Moure Fernández
Barcelona Supercomputing Center (BSC), (INB/ELIXIR-ES)
BL
Brane Leskošek
DC
Dafne Condori
Diana Pilvar
University of Tartu
Federico Bianchini
University of Oslo / ELIXIR-NO
Flora D'Anna
VIB Data Core / ELIXIR-BE
Gil Poiares-Oliveira
Hana Marčetić
Luxembourg Centre of Systems Biomedicine
Helena Schnitzer
Forschungszentrum Jülich GmbH
Heleri Inno
University of Tartu / ELIXIR-EE
IW
Ingeborg Winge
Ivan Mičetić
Jana Martínková
Jeanne Wilbrandt
MU
Magdalena Utko
MK
Maria Klapa
Marina Popleteeva
Luxembourg Institute of Health
MC
Miguel Cisneiros
Mijke Jetten
Minna Ahokas
NJ
Nick Juty
Niclas Jareborg
NL
Nils-Christian Lübke
RR
Riku Riski
RV
Rudolf Vohnout
Saliha Zenboudji-Beddek
French Institute of Bioinformatics (IFB -UAR 3601 - CNRS)