A data availability statement tells editors, reviewers, and readers where research data can be found, how it can be accessed, and why any limits apply. This guide explains what to include, compares wording by study type, and provides adaptable templates plus a pre-submission workflow for checking repositories, accession numbers, embargoes, and ethical restrictions.
Overview
A data availability statement is a short section of a manuscript that describes the status of the data supporting the reported results. It is not the same as a data management plan, methods section, supplementary file, or statement about funding and conflicts of interest. Its purpose is to make the data situation clear without overstating what is available.
The appropriate wording depends on the study and on the journal's submission requirements. A statement may point to an openly accessible dataset, identify a repository deposit, explain a controlled-access process, describe privacy restrictions, or state that no new datasets were generated. Some journals request a data availability statement for every article, including articles based on publicly available sources or secondary analysis.
Before submission, check the target journal's author instructions, research-data policy, manuscript template, and any funder or institutional requirements. Policies can differ in whether they expect a repository link, a persistent identifier, an embargo end date, a request procedure, or a specific standard phrase. Treat the examples below as adaptable starting points rather than universal wording.
What to track
A useful statement answers four practical questions:
- What data are available? Identify the dataset, code, materials, or analysis files that support the article, and distinguish them from data that cannot be shared.
- Where are they located? Name the repository or platform and provide a working URL, DOI, accession number, or other persistent identifier when available.
- When and under what conditions can they be accessed? Note whether the files are public, embargoed, restricted, available by request, or accessible only to approved researchers.
- Why are any limits necessary? Give a concise, accurate reason such as participant confidentiality, legal restrictions, third-party ownership, or an approved ethical limitation.
Comparison by data situation
| Data situation | What to include | Adaptable template |
|---|---|---|
| Open dataset | Repository name, persistent link or identifier, and the files included. | “The data supporting the findings of this study are openly available in [repository] at [DOI or URL]. The deposit includes [brief description].” |
| Repository deposit with an accession number | Repository, accession number, version if relevant, and access status. | “The dataset generated and analyzed during this study is available in [repository], accession number [number]. The record contains [description] and is available at [URL].” |
| Embargoed dataset | Repository record, embargo status, release date if confirmed, and any currently available metadata. | “The data are deposited in [repository] under [identifier]. Access is subject to an embargo until [date, if confirmed]. Metadata and the record are available at [URL].” |
| Restricted-access data | Reason for restriction, responsible access body, application process, and any identifier. | “The data are not publicly available because [reason]. Qualified researchers may request access from [data custodian or committee] through [process or URL], subject to [approval or agreement].” |
| Participant privacy limits | Explain that identifiable or potentially re-identifiable information cannot be openly released; describe a safe alternative. | “The data cannot be made publicly available because they contain information that could compromise participant privacy. De-identified or summary data are available from [repository or corresponding author] on reasonable request, subject to [review or agreement].” |
| Proprietary or third-party data | Identify the owner where permitted, explain the license restriction, and provide the route for obtaining the data if possible. | “The study used data obtained under license from [provider]. The authors are not permitted to redistribute these data. Access may be requested directly from [provider] at [URL].” |
| Data generated during the study | State whether the underlying data are deposited, available on request, or unavailable, and explain the reason. | “The data generated during this study are available from [repository or corresponding author] at [URL or identifier]. Any restrictions on access are described in the record and arise from [reason].” |
| No new data generated | Clarify whether the article analyzes existing sources, presents theory, or reports no new dataset. | “No new data were generated for this study. The analysis used [publicly available or previously published source], identified at [URL or citation].” |
Do not use “available on request” as a substitute for a clear access plan. If data are not deposited, explain who holds them, what a request must contain, whether review is required, and what restrictions apply. If sharing is impossible, say so directly and identify the relevant ethical, legal, contractual, or technical reason.
Keep the statement consistent with the manuscript
The data availability statement should agree with the methods, results, supplementary material, repository record, and consent documentation. If the manuscript says that a dataset is public but the link leads to a private record, an incomplete deposit, or a different version, the inconsistency may delay review. Use the same dataset name, sample description, and version information across the manuscript and repository.
Cadence and checkpoints
Prepare the statement early, then verify it at each major manuscript stage. A practical workflow is:
- At study close: List the files that support the analysis, including processed data, code, metadata, protocols, and documentation. Separate files that can be shared from those that contain confidential, licensed, or regulated information.
- Before choosing a repository: Confirm that it accepts the relevant file types and subject area, provides a persistent identifier, supports versioning where needed, and allows the access conditions required by the study.
- At deposit: Add a descriptive title, authors, study dates, methodology, file descriptions, license or access terms, and links to related publications. Check that the repository record is complete rather than merely created.
- Before submission: Open every public link in a private browser window, confirm that the identifier resolves, verify the accession number, and check whether the record is public, embargoed, or restricted. A DOI and its associated metadata should also be checked using a reliable metadata workflow; see how to verify DOIs and clean publication metadata.
- During revision: Compare the statement with changes to sample size, analyses, supplementary files, repository versions, and reviewer requests. Update the identifier or version if the deposit changed.
- At acceptance and publication: Recheck the final article proof, repository landing page, embargo date, and access permissions. Confirm that the statement does not promise access that the final record does not provide.
For recurring projects, maintain a simple tracking sheet with the manuscript title, journal, policy URL, repository, dataset identifier, version, access status, embargo date, data custodian, and last verification date. Review it monthly or quarterly for active submissions and whenever a dataset, repository record, or manuscript version changes.
How to interpret changes
A change in repository status does not automatically mean that the research itself has changed, but it can affect what readers and reviewers can verify. For example, an embargo may move from pending to active, a repository may assign a new version identifier, or a once-public file may become restricted after a privacy review. Record what changed and revise the statement if the change affects access or interpretation.
Distinguish among three types of updates:
- Administrative changes: a corrected link, updated contact, new repository version, or improved metadata. These usually require a statement or identifier update but not a change to the study description.
- Access changes: an embargo, new approval process, altered license, or restriction on sensitive files. Explain the new condition accurately and avoid describing the data as fully open.
- Substantive data changes: added files, corrected records, revised code, or a newly documented exclusion. Use repository versioning and describe the relevant version in the manuscript when necessary.
When a journal transfers a manuscript, do not assume the original statement satisfies the new journal's requirements. Check whether the receiving journal asks for a specific heading, separate repository information, a data citation, or a distinction between raw and processed data. The same caution applies after a desk rejection, resubmission, or major revision: the repository record and the manuscript may no longer match.
Data sharing also interacts with other submission details. Ensure that supplementary files are named consistently and complete; the manuscript formatting checklist can help with file preparation. If an editor requests additional documentation, respond with a precise explanation of what can be shared, what cannot, and who can authorize access.
When to revisit
Revisit the data availability statement before the first submission, at every revision, before resubmission to another journal, and when the dataset or repository record changes. For manuscripts under review for several months, a monthly or quarterly check is sensible, especially when an embargo date, access application process, or repository link is involved.
Schedule an annual policy review for active research projects and manuscript templates. Journal policies, funder requirements, repository terminology, and publisher transparency guidance can change, so refresh the links and examples in an internal template at least once a year or whenever a target journal publishes a relevant update. Do not copy an old statement without checking its assumptions.
Before pressing submit, complete this final checklist:
- Read the target journal's current data-sharing instructions.
- Identify exactly which data, code, and materials support the article.
- Confirm that each repository link, DOI, or accession number resolves correctly.
- Check the public, embargoed, or restricted status of every relevant record.
- State privacy, legal, contractual, or ethical limits plainly.
- Match the wording to the manuscript, supplementary files, consent terms, and repository version.
- Save the verification date and revisit the statement after any editorial, repository, or policy change.
A strong research data availability statement is brief, precise, and verifiable. It should help a reader find the supporting data—or understand exactly why access is limited—without making promises that the authors, repository, or journal cannot fulfill.