Pre-Submission Review for Genomics Papers
Genomics papers need pre-submission review that checks data deposition, variant nomenclature, annotations, code, privacy, and biological claims.
Senior Researcher, Oncology & Cell Biology
Author context
Specializes in manuscript preparation and peer review strategy for oncology and cell biology, with deep experience evaluating submissions to Nature Medicine, JCO, Cancer Cell, and Cell-family journals.
Readiness scan
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.
How to use this page well
These pages work best when they behave like tools, not essays. Use the quick structure first, then apply it to the exact journal and manuscript situation.
Question | What to do |
|---|---|
Use this page for | Getting the structure, tone, and decision logic right before you send anything out. |
Most important move | Make the reviewer-facing or editor-facing ask obvious early rather than burying it in prose. |
Common mistake | Turning a practical page into a long explanation instead of a working template or checklist. |
Next step | Use the page as a tool, then adjust it to the exact manuscript and journal situation. |
Quick answer: Pre-submission review for genomics papers should test sequence-data deposition, accession numbers, genome build and annotation versions, variant nomenclature, metadata, code, privacy constraints, and whether the biological claim follows from the genomic evidence. This page is distinct from bioinformatics review because the primary risk is genomic evidence and reporting, not only the pipeline.
If you need a fast manuscript-specific diagnosis, start with the AI manuscript review. If the paper is mainly software or pipeline-focused, see pre-submission review for bioinformatics.
Method note: this page uses Nature Portfolio reporting standards, Genome Research author instructions, Oxford Genetics and Human Molecular Genetics guidance, HGVS variant nomenclature materials, and Manusights field-review patterns reviewed in April 2026.
What This Page Owns
This page owns genomics-specific publication readiness. It applies to genome assembly, sequencing, exome or genome analysis, transcriptomics, single-cell genomics, variant interpretation, functional genomics, population genomics, and clinical genomics manuscripts.
Query intent | Best owner |
|---|---|
Genomic data and variant-reporting readiness | This page |
Software or pipeline implementation | |
Computational modeling | |
Epidemiologic risk or cohort inference |
The boundary is evidence type. Genomics review asks whether the data, annotations, and variant language can survive scrutiny.
What Genomics Reviewers Check First
Reviewers often ask:
- Are raw and processed sequencing data deposited?
- Are accession numbers or controlled-access plans clear?
- Which genome build, annotation release, and reference database were used?
- Are variant names reported according to accepted nomenclature?
- Are phenotype terms, sample metadata, and cohort definitions clear?
- Is code or workflow information sufficient to reproduce the results?
- Are privacy and consent constraints handled explicitly?
- Do biological conclusions exceed what the genomic evidence supports?
Genomics papers can lose trust quickly when the data trail is unclear.
In Our Pre-Submission Review Work
In our pre-submission review work, genomics manuscripts often fail at the interface between data and interpretation. The dataset is large, but the manuscript does not tell reviewers exactly which reference, version, filters, annotations, or variant descriptions produced the result.
The common failure patterns are:
- Accession-number gap: data are promised but not practically accessible for review.
- Reference-version ambiguity: genome build, annotation release, or database version is unclear.
- Variant-language drift: gene symbols, variant descriptions, or phenotype terms are inconsistent.
- Metadata weakness: samples, batches, ancestry, tissue, or sequencing context are underdescribed.
- Biology overreach: genomic association or expression pattern is written as mechanism.
A genomics review should identify which gap threatens trust first.
Public Policy Signals
Nature Portfolio reporting standards state that DNA and protein sequence data should be deposited in appropriate databases and that reference genome papers should make both assemblies and sequence reads available. GENETICS requires public release of data and software code underlying published papers. Human Molecular Genetics asks for HGNC-approved gene symbols, OMIM references where relevant, HGVS nomenclature for variants, and Human Phenotype Ontology terms for phenotypes.
Those signals make one point clear: genomics readiness is a reporting and repository problem as much as a writing problem.
Genomics Review Matrix
Review layer | What it checks | Early failure signal |
|---|---|---|
Data deposition | Raw, processed, and controlled-access data | Data availability is vague |
Reference context | Genome build, annotation, database versions | Results cannot be reconstructed |
Variant reporting | HGVS, HGNC, HPO, OMIM where relevant | Naming is inconsistent |
Metadata | Sample, phenotype, batch, tissue, ancestry | Cohort cannot be interpreted |
Workflow | Code, filters, thresholds, software versions | Pipeline choices are invisible |
Interpretation | Association, prediction, or mechanism | Claim outruns evidence |
What To Send
Send the manuscript, target journal, data-accession plan, data availability statement, workflow or code repository, software versions, genome build, annotation release, variant nomenclature checks, sample metadata, and any consent or controlled-access constraints.
For human genomics, include privacy and consent context. For genome assembly papers, include assembly access, reads, annotation files, and quality metrics.
Pre-Submit Checklist
Before submission, check:
- raw and processed data are deposited or access-controlled with a clear plan
- accession numbers, reviewer tokens, or access instructions are ready
- genome build and annotation versions are stated
- software versions, filters, and thresholds are recorded
- variants use accepted nomenclature where relevant
- gene symbols and phenotype terms are standardized
- batch, sample, and cohort metadata are explained
- conclusions distinguish genomic signal from biological mechanism
If reviewers cannot reconstruct the data path, revise before submission.
What A Useful Review Should Deliver
A useful genomics review should make the data trail inspectable before reviewers ask for it.
Deliverable | Why it matters |
|---|---|
Repository-readiness verdict | Confirms whether data access is practical for review |
Reference and annotation audit | Checks genome builds, database versions, and annotation sources |
Variant-language review | Finds HGVS, HGNC, HPO, or phenotype naming issues |
Metadata critique | Tests whether samples, batches, tissues, and cohorts are interpretable |
Workflow review | Checks code, filters, thresholds, and reproducibility |
Claim-discipline call | Separates genomic signal from mechanism or clinical meaning |
The output should not only say "improve data availability." It should name which accession, metadata, annotation version, or variant statement blocks trust.
How To Avoid Cannibalizing Bioinformatics Review
Use this page when the manuscript's main evidence is genomic data: sequencing, variants, genome assembly, annotation, single-cell profiles, transcriptomics, population genomics, or clinical genomics. Use bioinformatics review when the main product is a tool, workflow, database, or pipeline.
The same manuscript can contain both. In that case, decide what reviewers will judge first. If the first question is "can I access and interpret the genome data?", genomics owns it. If the first question is "can I run this tool?", bioinformatics owns it.
What Not To Submit Yet
Do not submit if:
- accession numbers or reviewer access are not ready
- the genome build or annotation version is absent
- variant descriptions are inconsistent
- sample metadata are too sparse to interpret the finding
- privacy restrictions are mentioned but not explained
- the conclusion treats genomic association as validated mechanism
These problems make reviewers doubt the chain from sequence data to claim.
Journal-Fit Questions
Before choosing a target, ask whether the paper is a resource, a discovery, a method, a clinical genomics report, or a functional genomics study. Genome Research, Nature Genetics, Genome Biology, Human Molecular Genetics, and specialty biomedical journals often value different evidence.
If the novelty is the dataset, the data package must be unusually clear. If the novelty is biological, the genomics must support a claim that matters beyond the dataset itself.
When Manusights Fits
Use Manusights when the authors need to know whether the genomic evidence package is submission-ready. That includes cases where the data are mostly organized, but the team is unsure whether repositories, nomenclature, metadata, workflow, and interpretation will satisfy reviewers.
If the data are not deposited or the analysis is still changing, finish that work first. If the data package is close but the submission decision is unclear, readiness review can prevent a slow and avoidable rejection.
This is most useful when the manuscript has several moving parts: human data, controlled access, variant interpretation, code, and biological claims. A missed detail in one layer can make the whole result feel less trustworthy.
The review should identify that weak layer before submission, while revision is still cheap.
Submit If / Think Twice If
Submit if:
- data access and metadata are review-ready
- variant and gene language is standardized
- conclusions are proportional to the genomic evidence
Think twice if:
- key accession numbers are missing
- reference and annotation versions are unclear
- the paper treats association as mechanism without validation
Readiness check
Run the scan to see how your manuscript scores on these criteria.
See score, top issues, and what to fix before you submit.
Bottom Line
Pre-submission review for genomics papers should protect the data trail. It should make sure reviewers can follow the sequence, variant, annotation, and interpretation chain before judging novelty.
Use the AI manuscript review if you need a fast readiness diagnosis before submitting a genomics manuscript.
- https://genome.cshlp.org/site/misc/ifora.xhtml
- https://academic.oup.com/GENETICS/pages/general-instructions
- https://academic.oup.com/hmg/pages/author-guidelines
- https://www.hgvs.org/content/guidelines
Frequently asked questions
It is a field-specific review that checks whether a genomics manuscript is ready for submission, including sequence-data deposition, variant nomenclature, annotation quality, code, repositories, privacy, and claim discipline.
Bioinformatics review focuses on tools and pipelines. Genomics review focuses on genomic data, sequence repositories, variant reporting, genome assemblies, annotations, phenotype links, and privacy or controlled-access issues.
They often attack missing accession numbers, unclear genome build or annotation versions, weak variant nomenclature, inadequate metadata, missing code, and overbroad biological interpretation.
Use it before submitting genome, exome, RNA-seq, single-cell, variant, association, or functional genomics papers where repositories and reporting standards can decide review quality.
Sources
- https://www.nature.com/ncb/editorial-policies/reporting-standards
Final step
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan. See score, top issues, and journal-fit signals before you submit.
Anthropic Privacy Partner. Zero-retention manuscript processing.
Where to go next
Supporting reads
Conversion step
Find out if this manuscript is ready to submit.
Anthropic Privacy Partner. Zero-retention manuscript processing.