PLOS ONE Data Availability Statement: A Submission-Ready Checklist

A PLOS ONE Data Availability Statement is short compared with a manuscript, but it connects several things that are easy to prepare separately: the data underlying the findings, the repository record, the dataset identifier, the manuscript's own citations, and any supporting-information files. A final check should confirm that those pieces describe the same access path.

This guide answers one practical question: what should you check before submitting a PLOS ONE Data Availability Statement? The requirements below come from PLOS ONE's current submission guidelines. The workflow suggestions are conservative preparation steps, not additional journal rules.

Start with the data underlying the reported findings

PLOS ONE states that all data and related metadata underlying the findings in a submitted manuscript should be deposited in an appropriate public repository unless they are already provided as part of the submitted article. Its guidance also says that data may be placed in a repository or included within Supporting Information files.

For an author, the useful first step is therefore not to polish the statement's wording. It is to identify the material the statement needs to describe.

Make a simple inventory of the results that appear in the manuscript:

• Which datasets underlie the reported findings?
• Which data support the figures, plots, and summary statistics?
• Which material will be deposited in a repository?
• Which material, if any, will be included with the article as Supporting Information?
• Which repository records already have a DOI, accession number, or version number?

This inventory is a practical cross-check. PLOS ONE's guidelines control the actual data-policy decision, and authors remain responsible for determining what data can be shared and how.

Check the repository and access path

PLOS ONE allows subject-specific repositories, where available, as well as general or institutional repositories. The submission guidelines recommend selecting a repository appropriate to the field. They also say repository records should provide DOIs or accession numbers and that the data should be at least as open as CC BY.

Before writing the final statement, open the repository record as a reader would. Confirm that the record is the intended one and that the access path is ready for the relevant stage of submission. Record the exact identifier displayed by the repository rather than retyping it from memory.

A conservative preparation table can help:

| Item | What to verify | | --- | --- | | Repository | The repository is appropriate for the data and discipline | | Dataset record | The record corresponds to the data underlying this manuscript | | DOI or accession number | The identifier is copied exactly | | Version | A version number is included when appropriate | | Access route | The public or reviewer-access path matches the submission stage | | Manuscript references | Dataset identifiers are also used where the dataset is discussed |

The table is a working aid, not a journal form. Do not include private reviewer links, passcodes, or embargo credentials in the manuscript or in a public checklist.

Put the identifier in the right places

PLOS ONE's guidance says that accession numbers, including version numbers when appropriate, should appear in the Data Availability Statement. It also says that an accession number or DOI citation should be provided when the dataset is mentioned within the manuscript.

That creates a two-location check:

1. The Data Availability Statement identifies the dataset and its access route.
2. The relevant manuscript passage cites the DOI or accession number when it mentions the dataset.

Compare those locations character by character. A transposed digit, an omitted version, or an old repository record can leave the statement and the manuscript pointing to different objects. If a dataset appears in several sections, search the manuscript for the repository name, DOI prefix, and accession stem before submission.

PLOS ONE notes that, in some cases, authors may not receive an accession number or DOI until the manuscript is accepted. In those cases, the identifier must be provided at acceptance. In other cases, the submission guidelines require it at full submission. Authors should use the journal's current instructions and the repository's actual status rather than inserting a placeholder that looks final.

Handle integrated repository details carefully

The submission guidelines describe a specific workflow for PLOS submissions using an integrated repository partner. After a final deposit, the repository provides a provisional dataset DOI and a private URL for reviewer access. PLOS ONE instructs authors to enter the DOI in the full Data Availability Statement requested in the Additional Information section of the submission form, then provide the URL passcode in the Attach Files section.

The practical lesson is separation: the dataset identifier belongs in the statement, while restricted reviewer-access details belong only in the submission location designated by PLOS. Do not paste a private passcode into the manuscript, the public statement, a cover letter, or a shared preparation note.

This integrated workflow should not be assumed for every repository. Follow it only when the selected repository and the current PLOS process actually provide that route.

Reconcile Supporting Information with the statement

PLOS ONE permits underlying data to be included within Supporting Information files. Its manuscript-organization guidance says Supporting Information captions belong in the manuscript's ending section when applicable, while the files themselves are uploaded separately.

If Supporting Information carries part of the underlying data, check three details:

• The Data Availability Statement names the relevant file or access route consistently.
• The manuscript contains the matching Supporting Information caption.
• The separately uploaded file uses the same label referenced in the manuscript.

For example, if the manuscript calls a file S1 Data, avoid changing the upload label to a different numbering scheme during the final portal pass. The exact label is an author-controlled detail; the goal is consistency, not a new journal requirement.

Run a final consistency pass

Before submission, freeze the version of the statement you intend to use and compare it with the rest of the package.

Use this final pass:

1. Confirm that every dataset underlying the reported findings has a stated access path.
2. Confirm that repository names, DOIs, accession numbers, and versions match the live records.
3. Check that dataset identifiers also appear where those datasets are mentioned in the manuscript.
4. Check that Supporting Information labels match their captions and uploaded filenames.
5. Keep reviewer-only URLs and passcodes out of the public manuscript materials.
6. Re-read the current PLOS ONE submission guidelines immediately before submitting, because journal instructions and repository status can change.

This pass does not judge whether a repository choice satisfies every legal, ethical, consent, or discipline-specific obligation. Those decisions remain with the authors and the journal's policies.

What Articlo can check—and what remains with the author

Articlo formats and checks author-provided manuscripts against the stored journal profile. For this workflow, it can help keep the document structure, Supporting Information captions, and author-provided identifiers in a consistent preparation package. It does not select a repository, write the research, decide what data can be shared, verify that a dataset exists, or guarantee that a journal will accept the statement or manuscript.

Authors should treat the official PLOS ONE guidance as controlling, confirm every repository record themselves, and make the final submission decisions.

The practical takeaway

A submission-ready Data Availability Statement is not just a sentence. It is a reliable map from the manuscript's findings to the data and identifiers that support them. Build that map from the actual repository records, use the same identifiers throughout the manuscript, keep reviewer-access details in their designated submission fields, and finish with one deliberate consistency check.

Source reviewed July 31, 2026: PLOS ONE Submission Guidelines.