A data management plan (DMP) explains how project data will be collected, stored, protected, documented, analyzed, shared and preserved across its lifecycle. For some donors, a DMP is a formal award requirement; for others, it is good project governance.
USAID guidance for some awards requires DMPs to cover the full data lifecycle, including data inventory, collection and storage protocols, privacy and security safeguards, documentation, preservation and terms of use.
What should a DMP include?
- What data will be collected.
- Who owns or manages each dataset.
- Collection methods and tools.
- Storage location and access controls.
- Privacy and security safeguards.
- File naming and version control.
- Documentation and metadata.
- Retention and preservation rules.
- Sharing or publication conditions.
Start with a data inventory
List the datasets the project expects to create or acquire: monitoring data, survey data, beneficiary records, geographic data, financial data and research outputs. Then assign ownership and controls to each.
Privacy should be designed in
If the project collects personal or sensitive information, define who can access it, how it will be protected and what legal or ethical rules apply. Do not wait until publication or reporting to decide.
Sharing does not mean sharing everything
Some funders encourage open data, but privacy, consent, contractual and safeguarding constraints may limit what can be shared. The DMP should make those boundaries explicit.
Use the Grant Evidence Inventory to connect project claims to the datasets and documents that will support them.
Frequently Asked Questions
Is a DMP the same as an M&E plan?
No. They overlap, but the DMP focuses specifically on how data is handled across its lifecycle.
Does every grant require a DMP?
No. Follow the donor’s current requirements.
Who should own the DMP?
Responsibility should be shared between program, MEL, data/IT and compliance roles where relevant.
Should the DMP include backups?
Yes where loss of data would affect project delivery or reporting.
Can the DMP change?
Yes. Update it when data sources, systems or sharing requirements change.
Conclusion
A data management plan turns data handling into an intentional project system. Strong DMPs define ownership, access, security, documentation and preservation before problems appear.
