Skip to content

Data Management Plan Generator

Answer the questions a data management plan has to settle — what data, which formats, where it is stored, how it is shared and preserved, who is responsible — and lay the answers out as a generic DCC-style plan, NSF's current Research.gov sections, a classic two-page plan, or the Horizon Europe template. Empty answers appear as the questions still to settle. Honest templates, no AI; nothing leaves your browser. Free, no sign-up.

Template

Built on the eight sections of the DCC Checklist for a Data Management Plan (v4.0, 2013). If your funder or institution has its own template — DMPTool and DMPonline host many — that template comes first.

The project

The data

Documentation and standards

Ethics, rights and security

Sharing and preservation

People and resources

Plan check

8 sections still need answers. About 367 words.

  • 1. Administrative dataNeeds answers
  • 2. Data collectionNeeds answers
  • 3. Documentation and metadataNeeds answers
  • 4. Ethics and legal complianceNeeds answers
  • 5. Storage and backupNeeds answers
  • 6. Selection and preservationNeeds answers
  • 7. Data sharingNeeds answers
  • 8. Responsibilities and resourcesNeeds answers

Your data management plan

Data Management Plan

Project: [project title]Template: DCC Checklist for a Data Management Plan (v4.0)

1. Administrative data

[Summarise the project and the purpose of the data in two or three sentences.]

2. Data collection

2.1 What data will you collect or create?

[What data will you collect or create — types, sources, and whether they are new or reused?]

[Which file formats will you use, and do they suit sharing and long-term access?]

[How much data do you expect — in MB, GB or TB?]

2.2 How will the data be collected or created?

[How will data be collected, organised, named, versioned and quality-checked?]

3. Documentation and metadata

3.1 What documentation and metadata will accompany the data?

[What documentation and metadata will accompany the data — a README, a codebook, a metadata standard?]

4. Ethics and legal compliance

4.1 How will you manage any ethical issues?

[How will you handle consent, personal data and anonymisation?]

4.2 How will you manage copyright and intellectual property rights?

[Who owns the data, and under what licence will it be shared?]

5. Storage and backup

5.1 How will the data be stored and backed up during the research?

[Where will data be stored during the project, and how will it be backed up?]

5.2 How will you manage access and security?

[Who can access the data, and how will sensitive data be protected?]

6. Selection and preservation

6.1 Which data should be retained, shared and/or preserved?

[Which data will be kept, and for how long?]

6.2 What is the long-term preservation plan?

[Which repository or archive will hold the data?]

7. Data sharing

7.1 How will you share the data?

[How, with whom and on what terms will the data be shared?]

[When will the data be made available?]

7.2 Are any restrictions on data sharing required?

[Are any restrictions on sharing needed? Say why — or say that there are none.]

8. Responsibilities and resources

8.1 Who will be responsible for data management?

[Who is responsible for each data management task?]

8.2 What resources will you require to deliver your plan?

[What will data management cost — storage, repository fees, staff time — and how will it be covered?]

How to Use the Data Management Plan Generator

  1. 1. Pick the template your funder expects. Generic follows the DCC checklist; NSF follows the Research.gov form; Horizon Europe follows the Commission's FAIR template. You can switch at any time — your answers stay.
  2. 2. Answer in short, concrete sentences. Name formats, volumes, repositories, licences and people. One line per point; each line becomes a paragraph.
  3. 3. Watch the plan check. Each section shows whether it has its required answers, and unanswered questions stay in the draft in brackets. Fields a template does not use are listed so nothing you typed vanishes silently.
  4. 4. Copy it where it has to go. Copy for Word or Google Docs, download text or Markdown, or — for NSF — paste each answer into the matching box of the Research.gov form.

Four Templates, One Set of Answers

What each layout follows
TemplateBased onSections
GenericDCC Checklist for a Data Management Plan, v4.0 (2013)Administrative data; data collection; documentation and metadata; ethics and legal compliance; storage and backup; selection and preservation; data sharing; responsibilities and resources
NSF DMSPResearch.gov webform, required for proposals from 27 April 2026Product categories; access policies and limitations; data standards and metadata; provenance; public archiving; timeline for public accessibility; data availability; accountability
Classic NSFPAPPG 24-1, Chapter II.D.2.i(ii)Types of data and products; data and metadata standards; access and sharing; re-use and derivatives; archiving and preservation
Horizon EuropeEuropean Commission DMP template, v1.1 (2022)Data summary; FAIR data (findable, accessible, interoperable, re-usable); other research outputs; allocation of resources; data security; ethics; other issues

The DCC checklist from the UK's Digital Curation Centre distils what funders and institutions ask for, which is why so many university templates read like it. Free planning tools such as DMPTool in the US and DMPonline in the UK and Europe host funders' own templates; if yours is there, use it, and paste in the answers drafted here.

What Changed at NSF in 2026

For years an NSF proposal carried a supplementary document of no more than two pages that could describe five things: the types of data and other products, the data and metadata standards, access and sharing policies, policies for re-use and derivatives, and plans for archiving. Policy Notice NSF 26-202, issued in January 2026, replaced that upload with a Data Management and Sharing Plan built in a Research.gov webform, live from 27 April 2026. The form is generated from the proposal's primary directorate and asks the same set of questions for each of up to four data or research product categories.

The notice also tightened sharing: data supporting NSF-funded publications must be shared at the time of publication, and any exception has to be described and justified in the plan. A plan saying no detailed plan is needed is still allowed, but now needs a clear justification. Directorates publish their own guidance, so check yours before you fill in the form.

What a Specific Answer Looks Like

Reviewers read dozens of plans that promise data "will be shared as appropriate." A useful answer names the repository, the licence, the timing and the reason for any restriction. For a study of bedroom heat and sleep in older adults, the sharing section of the generic template could read:

7. Data sharing

7.1 How will you share the data?

De-identified data, code and codebook deposited openly for anyone to download.

Timeline: at the time the main paper is published.

7.2 Are any restrictions on data sharing required?

Exact home locations are withheld to protect participants' privacy.

Common Mistakes in Data Management Plans

  • "Available on request." That leaves sharing to chance, and NSF now expects data behind a publication to be shared when the paper appears. Name a repository and a date.
  • Sharing data your consent form never mentioned. If participants were not told their de-identified data might be shared, you may not be able to share it. Write the plan and the consent form together.
  • No README or codebook. A spreadsheet without variable definitions is barely reusable, even when it is open.
  • Proprietary formats only. Keep a copy in an open format — CSV rather than a statistics package's own file type — for long-term access.
  • Forgetting the cost. Preparing data for deposit takes time, and some repositories charge. Budget it, or explain who covers it.
  • Nobody in charge. Name the person responsible for backups, for the deposit, and for keeping the plan up to date.

Your funder's template comes first

Funders and universities publish their own DMP templates, and many funders add requirements of their own on top of the structures above. Use their template where one exists, check your directorate's or programme's guidance, and treat this draft as the content you fill it with.

Frequently Asked Questions

What is a data management plan?
A data management plan (DMP) is a short document describing what data a project will collect or create, how it will be documented, stored and protected during the research, and how it will be shared and preserved afterwards. Most major funders require one with the proposal or early in the grant, and many universities expect one for theses.
What should a data management plan include?
At minimum: the types, formats and volume of data; the documentation and metadata; ethics, consent and intellectual property; storage, backup and security during the project; which data will be kept, where and for how long; how and when data will be shared and any restrictions; and who is responsible and what it will cost. Those are the eight headings of the DCC checklist.
Does NSF still require a two-page data management plan?
No. For proposals submitted from 27 April 2026, NSF collects the Data Management and Sharing Plan through a webform in Research.gov rather than as a two-page PDF. The form asks about access, standards, provenance, archiving, timeline, availability and accountability for each data or research product category. Choose the NSF DMSP template here to draft answers in that order.
When is the Horizon Europe data management plan due?
In Horizon Europe the DMP is a project deliverable rather than part of the proposal, usually due by month 6 and updated during the project as decisions change. The Commission's template is recommended but not mandatory; whatever format you use has to meet the research data management obligations of Article 17 of the Grant Agreement.
What does FAIR data mean?
FAIR stands for Findable, Accessible, Interoperable and Reusable, from the FAIR Guiding Principles published in Scientific Data in 2016. In practice: give data a persistent identifier and rich metadata, deposit it where people and machines can retrieve it, use shared formats and vocabularies, and attach a clear licence and documentation. The Horizon Europe template is organised around these four ideas.
Which repository should I choose for my data?
Prefer a trusted repository in your discipline, such as ICPSR for social science or GenBank for sequence data, because its users are the people most likely to reuse your work. Where none fits, general repositories such as Zenodo, Dryad, Figshare, OSF or Harvard Dataverse assign DOIs and are widely accepted. Check whether your funder or institution names a preferred one.

Related Tools

More in Research & Publishing

See all Research & Publishing