Journal Proposal Requirements

Navigation: Resources > For New Journal Proposals > Journal Proposal Requirements

CorayNova requires journal proposals from scholarly societies, institutions, academic groups, prospective Editors-in-Chief, existing journal owners, and other potential partners to include sufficient information for a thorough assessment. Proposals must explain the scholarly need and proposed scope, governance structure, editorial capacity, peer review arrangements, and safeguards for publication ethics. They must also address the access model, funding, platform and metadata requirements, preservation arrangements, and long-term sustainability.

To request the proposal template, please contact editorial@coraynova.com. Enquiries about partnerships with societies or institutions, other forms of cooperation, or agreements may also be directed to marketing@coraynova.com.

• Required Proposal Information

Each journal proposal should include sufficient information to assess its academic merit, editorial arrangements, ethical safeguards, operational and platform requirements, and long-term sustainability. Where further details are needed, CorayNova may request clarification or additional information before proceeding with the evaluation.

Required Element
Information Expected

Journal title
Proposed title, title rationale, abbreviation where relevant, and evidence that the title is clear and not misleading.

Disciplinary field
Primary field, related subfields, interdisciplinary position, and any emerging-field context.

Aims and scope
Clear scope boundaries, included and excluded topics, intended contribution, and relationship to existing journals.

Rationale
Scholarly need, field gap, community need, educational or societal relevance, and reasons for proposing the journal now.

Target readership
Expected author and reader communities, including researchers, practitioners, students, policymakers, societies, institutions, or regional communities where relevant.

Article types
Planned article categories, such as research articles, reviews, methods, case studies, short communications, editorials, commentaries, data papers, or other approved types.

Editorial structure
Proposed Editor-in-Chief, associate or section editor roles, editorial office support, advisory roles, and reporting lines.

Proposed Editor-in-Chief
Academic profile, leadership experience, affiliation, ORCID where available, conflict-of-interest disclosure, and availability.

Editorial board plan
Planned expertise coverage, diversity of expertise, appointment route, role expectations, conflicts management, and onboarding plan.

Peer review model
Proposed review model, reviewer number or expectations, reviewer selection method, decision process, confidentiality model, and appeal route.

Publication frequency
Expected publication model, issue or continuous publication plan, launch schedule assumptions, and realistic operational capacity.

Language
Publication language, abstract language where relevant, language editing expectations, and audience implications.

OA / access model
Open access, hybrid, subscription, or other proposed model, with rationale and disclosure plan.

APC or funding model
APC assumptions, society or institutional support, sponsorship, waiver or discount expectations, and separation from editorial decisions.

Ethical safeguards
Publication ethics, research ethics, competing interests, authorship, complaints, appeals, corrections, retractions, and special issue safeguards.

Data / research integrity expectations
Data availability, code / materials statements, reporting guidelines, AI-use disclosure, image integrity, human/animal research, consent, and personal data expectations.

Metadata / discoverability plan
DOI, ORCID where provided, funding metadata, references where available, license display, indexing readiness, Crossref metadata where applicable, and platform metadata needs.

Archiving / preservation plan
PKP Preservation Network eligibility, DOI persistence, platform records, metadata maintenance, backups, and any additional preservation service adopted by the journal.

Sustainability plan
Editorial workload, reviewer capacity, funding or support, projected operations, community development, governance continuity, and risk controls.

• Academic Case and Differentiation

The proposal should explain how the journal would differ from existing CorayNova journals and other relevant journals in the field. Where the proposed scope substantially overlaps with an existing journal, a clear scholarly rationale should be provided. CorayNova may decline proposals that do not adequately establish this distinction or rationale. The proposal should also identify potential sources of manuscripts and the author communities it would serve. CorayNova does not encourage commitments to fixed submission numbers, publication volumes, or acceptance rates, nor does it rely on such commitments when assessing proposals.

Area
Required Explanation

Scope differentiation
How the proposed journal is distinct from existing journals, including CorayNova journals and other field journals.

Community need
Evidence that researchers, practitioners, institutions, societies, or emerging communities need the journal.

Potential manuscript sources
Realistic description of author communities, conferences, research groups, societies, or fields that may submit, without promising volume or acceptance.

Readership
Who will read and use the journal and why the proposed content matters to them.

Risk of overlap
Any overlap with existing journals and how confusion, duplication, or unnecessary fragmentation will be avoided.

• Editorial Team Information

The proposal must identify initial editorial team members where available and explain their expertise, affiliations, ORCID identifiers where available, conflicts of interest, and role expectations. Proposed editors are not publicly presented as appointed CorayNova journal editors until CorayNova has completed the relevant approval and public announcement route. For journals published and distributed by CorayNova, the public name of the Editor-in-Chief is issued through CorayNova's official route.

• Template Request and Contact Route

To request the proposal template, contact editorial@coraynova.com. Society, institutional, cooperation, promotion, or agreement discussions may also be sent to marketing@coraynova.com. General enquiries may be sent to info@coraynova.com, and serious institutional-level matters may be sent to executive@coraynova.com.

Required Element	Information Expected
Journal title	Proposed title, title rationale, abbreviation where relevant, and evidence that the title is clear and not misleading.
Disciplinary field	Primary field, related subfields, interdisciplinary position, and any emerging-field context.
Aims and scope	Clear scope boundaries, included and excluded topics, intended contribution, and relationship to existing journals.
Rationale	Scholarly need, field gap, community need, educational or societal relevance, and reasons for proposing the journal now.
Target readership	Expected author and reader communities, including researchers, practitioners, students, policymakers, societies, institutions, or regional communities where relevant.
Article types	Planned article categories, such as research articles, reviews, methods, case studies, short communications, editorials, commentaries, data papers, or other approved types.
Editorial structure	Proposed Editor-in-Chief, associate or section editor roles, editorial office support, advisory roles, and reporting lines.
Proposed Editor-in-Chief	Academic profile, leadership experience, affiliation, ORCID where available, conflict-of-interest disclosure, and availability.
Editorial board plan	Planned expertise coverage, diversity of expertise, appointment route, role expectations, conflicts management, and onboarding plan.
Peer review model	Proposed review model, reviewer number or expectations, reviewer selection method, decision process, confidentiality model, and appeal route.
Publication frequency	Expected publication model, issue or continuous publication plan, launch schedule assumptions, and realistic operational capacity.
Language	Publication language, abstract language where relevant, language editing expectations, and audience implications.
OA / access model	Open access, hybrid, subscription, or other proposed model, with rationale and disclosure plan.
APC or funding model	APC assumptions, society or institutional support, sponsorship, waiver or discount expectations, and separation from editorial decisions.
Ethical safeguards	Publication ethics, research ethics, competing interests, authorship, complaints, appeals, corrections, retractions, and special issue safeguards.
Data / research integrity expectations	Data availability, code / materials statements, reporting guidelines, AI-use disclosure, image integrity, human/animal research, consent, and personal data expectations.
Metadata / discoverability plan	DOI, ORCID where provided, funding metadata, references where available, license display, indexing readiness, Crossref metadata where applicable, and platform metadata needs.
Archiving / preservation plan	PKP Preservation Network eligibility, DOI persistence, platform records, metadata maintenance, backups, and any additional preservation service adopted by the journal.
Sustainability plan	Editorial workload, reviewer capacity, funding or support, projected operations, community development, governance continuity, and risk controls.

Area	Required Explanation
Scope differentiation	How the proposed journal is distinct from existing journals, including CorayNova journals and other field journals.
Community need	Evidence that researchers, practitioners, institutions, societies, or emerging communities need the journal.
Potential manuscript sources	Realistic description of author communities, conferences, research groups, societies, or fields that may submit, without promising volume or acceptance.
Readership	Who will read and use the journal and why the proposed content matters to them.
Risk of overlap	Any overlap with existing journals and how confusion, duplication, or unnecessary fragmentation will be avoided.