ENG Data Management and Sharing Plan Guidance

Note: PAPPG requirements have changed, please refer to the latest PAPPG. The following guidance can be used for informational purposes until an update is available.

All proposals to U.S. National Science Foundation programs must include a data management and sharing plan (DMSP) created with the web-based tool released on Research.gov on April 27, 2026. NSF requirements for DMSPs are described in the NSF Proposal & Award Policies & Procedures Guide (NSF PAPPG) and the NSF PAPPG policy notice Implementation of Policy Changes to Proposal and Award Policies and Procedures Guide (PAPPG) 24-1, Supplement 2.

The NSF Directorate for Engineering (NSF ENG) provides additional guidance on this page. Questions about data management and sharing plans for proposals to NSF ENG may be addressed to Eric Miller at elmiller@nsf.gov.

ENG supports research covering a broad spectrum of communities of investigators, and each community has its own best practices. ENG is aware of the need to provide flexibility to programs, principal investigators (PIs) and reviewers in assessing the quality of individual DMSPs from various communities. Therefore, guidance has evolved to accommodate changing community standards and expectations. ENG relies on the merit review process to determine which DMSPs best serve each community.

The following guidance is to assist ENG investigators, reviewers and program officers in developing and evaluating effective, complete and competitive DMSPs. While all DMSPs should provide information as specified in the NSF PAPPG, PAPPG policy notice Implementation of Policy Changes to Proposal and Award Policies and Procedures Guide (PAPPG) 24-1, Supplement 2, and the Research.gov DMSP tool, they should not be generic.

Each DMSP should appropriately identify the data, metadata, samples, software, algorithms, curricula, documentation, publications and other materials generated during the proposed research. Moreover, DMSPs should describe how these materials will be disseminated, made accessible and archived while incorporating the best practices and standards for the proposed research.

DMSPs are subject to peer review. Please contact your specific program officer if you have questions regarding DMSPs in the program context.

All proposals must include a DMSP, as described in the PAPPG. The DMSP is not part of the 15-page project description. Proposals that do not include a DMSP will be returned without review.

Recipients are required to share all data supporting NSF-funded publications at the time of publication. Exceptions to this sharing requirement must be described and justified within the DMSP.

You may request funds to cover publication costs, page charges or data preparation as a direct cost in your budget proposal, which is evaluated as part of the merit review process. Any costs associated with implementing the DMSP should be explained in the budget justification. 

Some NSF program solicitations may contain specific and/or additional instructions that deviate from this guidance and/or provide exceptions to the two-page limit. Instructions in the solicitation take precedence over this guidance. Please check solicitations carefully for this information. 

The DMSP should clearly articulate how the investigators plan to manage and disseminate both the physical and digital data generated by the project, taking advantage of emerging information technologies and cyberinfrastructure. The plan must include sufficient detail to evaluate its appropriateness and feasibility during merit review. DMSPs often include existing practices in the principal investigator's laboratory and the larger research community.

The Research.gov DMSP tool requests the following information about each data or research product:

• Data or research product category.
• Access policies and limitations.
• Data standards and metadata.
• Data or research product provenance.
• Public archiving.
• Timeline for public accessibility.
• Data availability.
• Accountability.

To assist the ENG community in developing effective DMSPs, the types of questions PIs should consider when constructing their proposed DMSPs are listed below. 

1. Data and research products 
   What types of data (experimental, computational or text-based), metadata, samples, physical collections, models, software, curriculum materials and other materials will be collected and/or generated during the project? The DMSP should describe the expected data types to be retained, managed and shared and the plans for doing so. What descriptions of the metadata are needed to make the actual data products useful and reproducible for the general researcher? For collaborative proposals, the DMSP should describe the roles and responsibilities of all parties concerning data management and sharing (including contingency plans for the departure of key personnel from the project) both during and after the grant cycle. 
2. Access policies and limitations 
   What are your policies regarding the use of data provided via general access or sharing? Practices for appropriate protection of privacy, confidentiality, security, intellectual property and other rights should be communicated. The rights and obligations of those who access, use and share your data with others should also be clearly articulated. For example, if you plan to provide data and images on your website, will the website contain disclaimers or conditions regarding the use of the data in other publications or products? 
3. Data standards 
   In what format and/or media will the data or products be stored (e.g., hardcopy notebook and/or instrument outputs, ASCII, HTML, JPEG or other formats)? For data to be deemed "reusable," it must be accompanied by any metadata needed to reproduce the data, e.g., how it was generated, detailed analytical and procedural information required to reproduce experimental results, and other pertinent metadata. Where data are stored in unusual or not generally accessible formats, how may the data be converted to more accessible formats or made available to interested parties? When existing standards are absent or deemed inadequate, this should be documented along with any proposed solutions or remedies. In general, solutions and remedies for providing data in an accessible format should be offered with minimal added cost. 
4. Public accessibility 
   What specific dissemination approaches will be used to make data available and accessible to others, including any pertinent metadata needed to interpret the data? In this case, "available and accessible" refers to data that can be found and obtained without a personal request to the PI, for example, by downloading from a public repository. What plans, if any, are in place for providing access to data, including websites maintained by the research group and contributions to public databases/repositories? For software or code developed as part of the project, include a description of how users can access the code (e.g., licensing, open source) and specific details of the hosting, distribution and dissemination plans. If maintenance of a website or database is the direct responsibility of the research group, what is the period during which the website or database is expected to be maintained? What are the practices or policies regarding the release of data? "Data sharing" refers to the release of data in response to a specific request from an interested party. What are the policies for data sharing, including, where applicable, provisions for protection of privacy, confidentiality, intellectual property, national security or other rights or requirements? Research centers and major partnerships with industry or other user communities should also address how data will be shared and managed with partners, center members and other major stakeholders; publication delay policies (if applicable) should be clearly stated. 
5. Public archiving and availability of data 
   When and how will data be archived, and how will access be preserved over time? For example, will hardcopy logs, instrument outputs and physical samples be stored in a location that has safeguards against fire or water damage? Is there a plan to transfer digitized information to new storage media or devices as technological standards or practices change? Will there be an easily accessible index that documents where all archived data are stored and how they can be accessed? If the data will be archived by a third party, please refer to their preservation plans (if available). Where no data or sample repository exists for collected data or samples, metadata should be prepared and made publicly available over the internet, and the PI should employ alternative strategies to comply with the general philosophy of sharing research products and data as described above. 

After an award is made, the PI(s) must manage their data as described in the DMSP, which will be monitored primarily through the normal annual and final report process and evaluation of subsequent proposals. NSF guidance on technical reporting requirements states that annual and final reports should describe actions taken during the reporting period to complete a proposal's DMSP. While these reports are a critical mechanism for communication between the PI and the award's managing program officer, PI(s) are encouraged to reach out to the relevant program officer about changes to or difficulty implementing the proposed DMSP.

Annual reports required for all NSF multiyear awards should include information about progress made in data management and sharing of research products (e.g., identifiers or accession numbers for data sets, citations of relevant publications, conference proceedings and other types of data sharing and dissemination). These activities may be documented under accomplishments, as major activities, other achievements or in response to how the results have been disseminated, as appropriate. NSF encourages investigators to employ persistent identifiers for all research products (where these exist) as a long-lasting reference to digital resources. URLs for archived metadata and data may be included in the section entitled "Products-Websites."

Final reports should describe the implementation of the DMSP and include any changes from the original DMSP. The final report should clearly describe the following information:

• The data produced during the award period.
• The data that will be retained after the award expires.
• How the data will be disseminated, along with verification that the data will be accessible or made available for sharing.
• The format (including reference to any and all pertinent metadata) that will be used to make the data available and usable by others.
• Where the data generated by the project have been deposited/are being stored for long-term public access.

Final reports must document compliance or explain why it did not occur. In cases where the final report is due before the required date of sample or data submission, the PI must report the submission of metadata and plans for final submission. The PI should email the relevant program officer after the final data and/or sample submission has occurred, even if this is after the expiration date of the award.

Subsequent proposals submitted by the PI(s) to NSF will be partially evaluated on the implementation of the DMSPs from previous awards. As described in the PAPPG, data management and sharing outcomes must be reported in the section "Results from Prior NSF Support" of future proposals.

Many sites provide specific guidance on data management and sharing practices. The following list is neither exhaustive nor intended to endorse these resources. These provide an entry point for assistance:

• Journals and data repositories may require specific formatting and metadata for data publishing or archival deposit.
• Professional and scholarly societies may provide guidance for the community.
• Nongovernmental organizations are now offering resources and training.
• Re3data.org is a repository registry (and search) service.
• Finally, many university libraries now provide resource guides on data management and sharing planning and best practices; some directly support DMSP development.