<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Submission Requirements Archives - Enago Articles</title>
	<atom:link href="https://www.enago.com/articles/category/submission-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.enago.com/articles/category/submission-requirements/</link>
	<description></description>
	<lastBuildDate>Mon, 04 May 2026 13:57:27 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Editorial Manager and ScholarOne: Troubleshooting Common Submission Portal Glitches and Errors</title>
		<link>https://www.enago.com/articles/editorial-manager-vs-scholarone-submission-errors/</link>
					<comments>https://www.enago.com/articles/editorial-manager-vs-scholarone-submission-errors/#respond</comments>
		
		<dc:creator><![CDATA[Roger Watson]]></dc:creator>
		<pubDate>Mon, 23 Feb 2026 13:20:30 +0000</pubDate>
				<category><![CDATA[Submission Requirements]]></category>
		<guid isPermaLink="false">https://www.enago.com/academy/?p=57524</guid>

					<description><![CDATA[<p>Few moments in the research publication process feel as high-stakes as clicking “Submit” after weeks (or months) of writing and preparation. Yet many delays happen for reasons unrelated to scientific quality mis-tagged files, stubborn PDF builders, missing metadata, or a final proof that looks “mostly fine” until a table splits across pages. Two platforms dominate [&#8230;]</p>
<p>The post <a href="https://www.enago.com/articles/editorial-manager-vs-scholarone-submission-errors/">Editorial Manager and ScholarOne: Troubleshooting Common Submission Portal Glitches and Errors</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Few moments in the research publication process feel as high-stakes as clicking “Submit” after weeks (or months) of writing and preparation. Yet many delays happen for reasons unrelated to scientific quality mis-tagged files, stubborn PDF builders, missing metadata, or a final proof that looks “mostly fine” until a table splits across pages.</p>
<p>Two platforms dominate the research <a href="https://www.enago.com/submission-preparation.htm" data-internallinksmanager029f6b8e52c="34" title="manuscript submission" target="_blank" rel="noopener">manuscript submission</a> experience across publishers and societies: Editorial Manager (EM) and ScholarOne Manuscripts (S1M). Both can support rigorous workflows, but each has predictable submission portal quirks researchers should plan for. This guide offers a practical comparison of common technical glitches, a reliable approach to ordering files for PDF auto-generation, and a repeatable method to verify the final HTML proof before approving <a href="https://www.enago.com/submission-preparation.htm" data-internallinksmanager029f6b8e52c="34" title="manuscript submission" target="_blank" rel="noopener">manuscript submission</a>.</p>
<h2><strong>What these systems do (and why the quirks matter)</strong></h2>
<p>Both EM and S1M are <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">journal submission</a> management systems designed to collect research manuscript files, author details, declarations, and metadata in a structured way. They also feed those inputs into downstream processes <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>, production, and archiving. That structure is helpful, but it also means small inconsistencies (file naming, figure labeling, reference formatting, permissions) can trigger errors that feel opaque to authors.</p>
<p>Many journals configure EM and S1M differently. Even within the same platform, two journals may impose different file types, different “item type” labels, or different rules for what the PDF builder will accept. That variability is why researchers often look for a website submission service or software submission service when deadlines are tight or when a journal’s portal has unusually strict requirements.</p>
<h2><strong>Editorial Manager vs. ScholarOne: the most common differences researchers notice</strong></h2>
<h3><strong>File taxonomy: EM is “item type–driven,” S1M is often “step-driven”</strong></h3>
<p>In Editorial Manager, successful submission often depends on assigning the correct item type to each uploaded file (e.g., manuscript, figure, supplementary material). Many journals also allow batch actions like changing item type for multiple files, which is useful when the system unpacks a ZIP and everything defaults to an incorrect label.</p>
<p>In ScholarOne, the workflow often feels more “wizard-like” (enter information → upload files → build PDF → review → submit). The portal may still ask for file designations, but authors often experience friction later during PDF building or when required fields trigger validation errors near the end.</p>
<p><strong>Practical implication:</strong> EM issues frequently come from incorrect item types or file packaging; S1M issues more often show up as late-stage validation or PDF build failures.</p>
<h3><strong>Packaging files: EM commonly supports zipped source uploads (journal-dependent)</strong></h3>
<p>Some EM journal configurations allow authors to upload a .zip or .tar.gz of source files that gets automatically unpacked, after which item types must be assigned.</p>
<p><strong>Practical implication:</strong> If a journal allows packaging, EM can be faster for LaTeX-heavy workflows, but only if file typing is done carefully after unpacking.</p>
<h3><strong>LaTeX handling and “do not upload PDF” rules can differ</strong></h3>
<p>Some EM journals provide explicit LaTeX instructions, including rules like uploading LaTeX sources under a LaTeX item type and not including a compiled PDF at that stage.</p>
<p><strong>Practical implication:</strong> When submitting LaTeX, treat the journal’s portal instructions as higher priority than personal habit. A “helpful” extra PDF can cause conflicts in automated rendering pipelines.</p>
<h2><strong>Common technical glitches (and what usually fixes them)</strong></h2>
<h3><strong>1) PDF auto-generation fails or stalls</strong></h3>
<p><strong>What it looks like:</strong> The build spins indefinitely, finishes but produces a blank PDF, or generates a PDF missing figures or tables.</p>
<p><strong>What typically causes it:</strong></p>
<ul>
<li>An unsupported figure format (or a corrupt image file)</li>
<li>A large file size that times out during conversion</li>
<li>Fonts or equations embedded in ways the converter cannot interpret (common in Word-to-PDF pipelines)</li>
<li>Mixed upload logic (e.g., uploading both a fully composed PDF and source files when the journal expects only one approach)</li>
</ul>
<p><strong>What usually works:</strong></p>
<ul>
<li>Re-export figures to a journal-safe format (always follow the journal’s guide)</li>
<li>Reduce file size without changing resolution requirements</li>
<li>If the portal accepts it, upload a single clean manuscript PDF for initial submission and provide sources later (journal-dependent)</li>
<li>Rebuild the manuscript PDF from a “clean” source file (accept tracked changes, embed fonts, re-render equations)</li>
</ul>
<h3><strong>2) “Required field missing” appears late in the process</strong></h3>
<p><strong>What it looks like:</strong> Everything seems complete, but the final submission page flags a missing checkbox, contributor role, funding line, or ethics statement.</p>
<p><strong>What typically causes it:</strong></p>
<ul>
<li>The system treats some fields as conditional (e.g., clinical trial registration appears only after selecting a study type)</li>
<li>A co-author’s email or affiliation formatting fails validation (extra spaces, special characters)</li>
<li>ORCID prompts not fully completed (journal-dependent)</li>
</ul>
<p><strong>What usually works:</strong></p>
<ul>
<li>Review each metadata tab again after file upload, because some portals re-check requirements after attachments are added</li>
<li>Copy-paste content into a plain-text editor first to remove hidden characters, then paste into the portal</li>
</ul>
<h3><strong>3) Tables break, float, or vanish in the generated PDF</strong></h3>
<p><strong>What it looks like:</strong> A table splits mid-row, appears at the end of the document unexpectedly, overlaps text, or becomes unreadable.</p>
<p><strong>What typically causes it:</strong></p>
<ul>
<li>The PDF builder is interpreting tables as images or as complex Word objects</li>
<li>Tables are embedded as pasted spreadsheets with merged cells and nested formatting</li>
<li>Table captions are not linked or are placed inconsistently relative to the table</li>
</ul>
<p><strong>What usually works:</strong></p>
<ul>
<li>Convert tables to simpler structures (avoid excessive merging, nested tables, and embedded objects)</li>
<li>Ensure each table has a consistent caption format and numbering</li>
<li>Where the journal allows separate table files, upload them as individual table files rather than embedding them inside the main text (only if the journal instructions support that workflow)</li>
</ul>
<h2><strong>How to correctly order files for PDF auto-generation (so tables and figures behave)</strong></h2>
<p>PDF builders generally behave best when the submission package has a predictable hierarchy: a clear “main manuscript” plus discrete, consistently labeled supporting components. However, EM and S1M can assemble files differently depending on journal configuration. That makes file order and item type labeling more important than many researchers realize.</p>
<h3><strong>A stable ordering strategy that works in most configurations</strong></h3>
<p>When the journal allows multiple file uploads to assemble a combined PDF, a conservative sequence is:</p>
<ol>
<li>Main manuscript file (Word or LaTeX main source, as required)</li>
<li>Tables (if submitted separately, one file per table or one consolidated tables file—follow journal rules)</li>
<li>Figures (one file per figure, numbered consistently)</li>
<li>Supplementary files (appendices, additional methods, datasets, reporting checklists)</li>
</ol>
<p>The goal is not aesthetic preference. It is to prevent the PDF generator from placing tables and figures unpredictably, or appending them in a confusing order that reviewers must fight through.</p>
<h3><strong>File labeling and naming conventions that reduce conversion errors</strong></h3>
<ul>
<li>Use simple filenames: Manuscript.docx, Table1.docx, Figure2.tif, SupplementaryMethods.pdf</li>
<li>Avoid special characters and long strings: no #, &amp;, parentheses stacks, or version trails like FINAL_final_revised3</li>
<li>Match in-text callouts precisely: “Table 2” in the text should map to a file named Table2…</li>
</ul>
<h3><strong>A note on ZIP uploads (common in EM journal setups)</strong></h3>
<p>If the portal allows zipped uploads, it can save time, but it also increases the risk of incorrect item types after unpacking. In EM, journals may expect authors to correct item types post-unpack and can support batch item-type changes.</p>
<h2><strong>How to verify the final HTML proof before approving submission</strong></h2>
<p>Many authors treat the final proof step as a quick visual scan. That is risky because conversion errors often affect exactly what editors and reviewers see first: the title page, abstract, headings, tables, figure callouts, and references. A structured review takes only a few minutes and can prevent avoidable resubmission requests.</p>
<h3><strong>What to check in the HTML proof (and why it matters)</strong></h3>
<ol>
<li><strong>Title, author list, and affiliations</strong><br />
Confirm spelling, order, and the corresponding author designation. Portal metadata can override what appears in the manuscript file.</li>
<li><strong>Abstract and keywords</strong><br />
Check for missing symbols, broken italics (e.g., species names), and truncated text, especially if the abstract was pasted into a form field.</li>
<li><strong>Headings and section order</strong><br />
Ensure headings did not collapse into plain text. If the journal uses automated screening, malformed structure can slow triage.</li>
<li><strong>Tables (highest priority)</strong><br />
Scroll every table start-to-finish:</p>
<ul>
<li>Are columns aligned?</li>
<li>Are footnotes present and correctly linked?</li>
<li>Did any table split mid-row or lose shading that carries meaning?</li>
</ul>
</li>
<li><strong>Figures and captions</strong><br />
Confirm each figure matches its caption and numbering. Look for swapped images, a surprisingly common conversion problem when multiple versions exist.</li>
<li><strong>References and special characters</strong><br />
Verify Greek letters, minus signs, superscripts, and diacritics. These often break when systems convert from Word or LaTeX to HTML or PDF.</p>
<pre id="posted-message-container" class="zcmsgcnt lazy-load lazy-load-lastmsg textL" dir="auto"><!-- INLINE SERVICE CARD: Plagiarism Checker -->
 <div class="svc">
    <div class="svc-body">
      <span class="svc-cat">
        Research Integrity <span class="svc-free">Free</span>
      </span>
      <div class="svc-row">
        <div class="svc-ic">
          <svg viewBox="0 0 200 200" fill="none" xmlns="http://www.w3.org/2000/svg">
            <g clip-path="url(#cp-plag-inline)">
              <path d="M140.26 34.7119H35.7568V39.9202H140.26V34.7119Z" fill="white"></path>
              <path d="M82.7998 56.3525H35.7568V61.5609H82.7998V56.3525Z" fill="white"></path>
              <path d="M66.8388 77.9932H35.7568V83.2015H66.8388V77.9932Z" fill="white"></path>
              <path d="M163.778 180.88V195.262H155.411H20.5653H12.1983V4.7379H20.5653H155.411H163.778V128.595H168.011V0H155.411H20.5653H7.99805V200H20.5653H155.411H168.011V180.88H163.778Z" fill="white"></path>
              <path d="M142.756 99.0334C138.521 95.029 134.41 90.706 129.718 87.4296C120.459 80.9679 110.327 78.1465 99.4068 81.2864C88.3203 84.4718 79.5175 91.5706 72.002 100.854V102.446H75.8635C77.3999 104.267 79.2684 106.724 81.4276 108.908C87.5729 115.142 94.9639 118.692 103.227 119.966C103.601 120.011 111.49 120.011 111.947 119.966C118.133 119.42 124.03 117.509 129.054 113.595C133.372 110.228 137.234 106.132 141.428 102.264H144.002C143.587 101.172 143.462 99.716 142.715 99.0334H142.756ZM107.711 115.643C95.9189 115.643 86.6179 109.818 79.7667 99.3065C96.6248 80.1033 117.677 78.9201 136.32 99.2155C129.386 110.137 119.711 115.643 107.711 115.688V115.643Z" fill="white"></path>
              <path d="M107.601 92.0023C103.648 92.0472 100.184 95.5428 100.007 99.7106C99.8289 104.237 103.293 107.912 107.867 108.002C112.175 108.046 115.817 104.685 115.994 100.383C116.172 95.8565 112.219 91.9575 107.556 92.0023H107.601ZM107.956 105.671C104.714 105.626 102.227 103.027 102.36 99.8003C102.494 96.8424 104.936 94.3776 107.734 94.3327C111.02 94.3327 113.818 97.0665 113.729 100.293C113.596 103.341 111.02 105.761 107.956 105.671Z" fill="white"></path>
              <path d="M185.519 165.491L148.322 128.293C154.504 120.06 158.201 109.845 158.201 98.7903C158.201 71.5725 136.057 49.4287 108.839 49.4287C81.6214 49.4287 59.4775 71.5725 59.4775 98.7903C59.4775 126.008 81.6214 148.152 108.839 148.152C119.894 148.152 130.076 144.456 138.342 138.273L175.539 175.47L185.519 165.491ZM64.2154 98.7903C64.2154 74.1599 84.2423 54.133 108.873 54.133C133.503 54.133 153.53 74.1599 153.53 98.7903C153.53 123.421 133.503 143.448 108.873 143.448C84.2423 143.448 64.2154 123.421 64.2154 98.7903ZM143.08 134.274C143.517 133.871 143.92 133.468 144.323 133.031C144.659 132.661 145.029 132.359 145.365 131.989L178.866 165.491L175.539 168.817L142.038 135.316C142.408 134.98 142.71 134.61 143.08 134.274Z" fill="white"></path>
            </g>
            <defs><clipPath id="cp-plag-inline"><rect width="177.52" height="200" fill="white" transform="translate(7.99805)"></rect></clipPath></defs>
          </svg>
        </div>
        <h4>Submit with complete integrity — every time.</h4>
      </div>
      <p class="svc-desc">Checked against 91 billion web pages and 82 million published works. Every result is reviewed by our expert editorial team, not just generated by an algorithm.</p>
      <a href="https://www.enago.com/plagiarism-checker/" class="svc-btn" target="_blank">Check for Plagiarism Free →</a>
    </div>
  </div>
    </pre>
</li>
</ol>
<h3><strong>A practical “two-format rule”</strong></h3>
<p>If the portal offers both an auto-generated PDF and an HTML proof, compare them side-by-side for the elements above. If the HTML looks correct but the PDF is broken (or vice versa), treat that as a signal that the source files need simplification or the upload types need correction before final submission.</p>
<h2><strong>Portal quirks that frequently trigger preventable delays</strong></h2>
<h3><strong>Editorial Manager: item type mismatches are a common root cause</strong></h3>
<p>EM’s flexibility is powerful, but it increases the chance of labeling mistakes. When figures are uploaded as the wrong type, or when the main manuscript is not tagged correctly, the system may build an incorrect combined PDF or route files improperly for editorial checks.</p>
<h3><strong>ScholarOne: validations can feel “late” and non-obvious</strong></h3>
<p>S1M workflows often feel smooth until the end, when the system surfaces missing declarations, contributor details, or file requirements. Planning for a final “metadata sweep” before clicking submit reduces last-minute surprises, especially for multi-author papers with complex funding and ethics statements.</p>
<h2><strong>How to decide which workflow to use when journals allow options</strong></h2>
<ul>
<li>If the paper contains complex tables, heavy math, or specialized symbols, a single author-generated PDF may be safer for first-pass review (if permitted).</li>
<li>If the journal requires source files immediately, simplify formatting and keep tables and figures as clean, separate objects wherever possible.</li>
</ul>
<h2><strong>Final takeaways: a research manuscript submission process that stays under control</strong></h2>
<p>Editorial Manager and ScholarOne both support rigorous publishing workflows, but each has predictable friction points. Researchers can reduce delays by treating research <a href="https://www.enago.com/submission-preparation.htm" data-internallinksmanager029f6b8e52c="34" title="manuscript submission" target="_blank" rel="noopener">manuscript submission</a> as a technical handoff: label files cleanly, upload in a stable order, and review the HTML or PDF proof with the same care used for the manuscript’s final pre-submission read-through.</p>
<p>When internal bandwidth is limited, or when repeated portal rebuilds are slowing progress, research teams often consider a specialized <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">journal submission</a> management partner. Enago’s <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">Journal Submission</a> Service can help researchers navigate portal-specific requirements, ensure compliance with journal instructions, and manage the upload and verification steps without derailing research timelines. If the main risk is technical non-compliance rather than content quality, Enago Reports’ Technical Check Report can also help identify frequent pre-submission issues across structure and formatting before the manuscript enters a portal workflow.</p>
<p>The post <a href="https://www.enago.com/articles/editorial-manager-vs-scholarone-submission-errors/">Editorial Manager and ScholarOne: Troubleshooting Common Submission Portal Glitches and Errors</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.enago.com/articles/editorial-manager-vs-scholarone-submission-errors/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Data Availability Statement Requirements: Using Private Reviewer Links for Journal Submission</title>
		<link>https://www.enago.com/articles/data-availability-statement-requirements/</link>
					<comments>https://www.enago.com/articles/data-availability-statement-requirements/#respond</comments>
		
		<dc:creator><![CDATA[Roger Watson]]></dc:creator>
		<pubDate>Thu, 19 Feb 2026 10:39:59 +0000</pubDate>
				<category><![CDATA[Submission Requirements]]></category>
		<guid isPermaLink="false">https://www.enago.com/academy/?p=57515</guid>

					<description><![CDATA[<p>Mandatory open-data policies no longer apply only to a handful of “data-heavy” fields. Across disciplines, journals and funders increasingly expect authors to disclose what underlying data exist, where those data can be accessed, and under what conditions often at the initial submission stage, not after acceptance. Springer Nature, for example, has introduced a standard research [&#8230;]</p>
<p>The post <a href="https://www.enago.com/articles/data-availability-statement-requirements/">Data Availability Statement Requirements: Using Private Reviewer Links for Journal Submission</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Mandatory open-data policies no longer apply only to a handful of “data-heavy” fields. Across disciplines, journals and funders increasingly expect authors to disclose what underlying data exist, where those data can be accessed, and under what conditions often at the initial submission stage, not after acceptance. Springer Nature, for example, has introduced a standard research data policy that requires a Data Availability Statement (DAS) for original research, even when data cannot be shared openly.</p>
<p>For many researchers, the friction point is practical: the dataset is not ready to be fully public, the journal uses double-blind <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>, or the repository DOI is not yet active. This is where private reviewer links (also called “private links,” “reviewer links,” or “temporary sharing URLs”) become essential. This article explains how to navigate Data Availability Statement requirements during the <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">journal submission</a> process: selecting an appropriate repository workflow, generating reviewer-access links in repositories such as Figshare and Dryad, and writing a Data Availability Statement that editors can quickly verify before they send a manuscript for review.</p>
<h2><strong>Why Journals Ask for a Data Availability Statement (and What “Mandatory” Really Means)</strong></h2>
<p>A Data Availability Statement is a short section in the manuscript that tells readers and editors where the data supporting the results can be found (or why they cannot be shared). Increasingly, it also serves as a screening tool during submission: if the journal requires open data (or requires transparent disclosure), missing or vague statements can lead to avoidable delays, returned submissions, or desk rejections.</p>
<p>It is also important to recognize that “mandatory” has layers. Some journals mandate deposition of certain data types into specific community repositories. Others do not mandate sharing, but still require transparency about availability. Springer Nature explicitly positions its policy as requiring a DAS while acknowledging that not all data can be shared publicly (for instance, identifiable human participant data). PLOS, in contrast, generally requires authors to make data needed to replicate findings publicly available at publication, while allowing restrictions when legal or ethical rules prevent open sharing, as long as the DAS clearly explains the access pathway.</p>
<p>For authors trying to submit a paper to journal systems under tight deadlines, the practical takeaway is simple: the DAS is not “administrative filler.” It is a compliance artifact that editors use to judge whether the manuscript can proceed.</p>
<h2><strong>Decide the Right Data-Release Route Before Uploading Anything</strong></h2>
<p>Before generating links or drafting the DAS, authors typically benefit from a quick policy-to-workflow mapping. Most submission problems occur because the repository settings and the DAS are planned in isolation.</p>
<p>A workable decision sequence looks like this:</p>
<ol>
<li>Confirm the journal’s data policy level (required DAS only vs required deposition vs required public release at submission vs at publication).</li>
<li>Check whether the journal uses double-blind review. If it does, the dataset landing page and files should not reveal author identities during review.</li>
<li>Classify the data as open, restricted, or non-shareable:
<ul>
<li><strong>Open:</strong> can be shared publicly with appropriate licensing.</li>
<li><strong>Restricted:</strong> can be shared with controlled access (e.g., via a data access committee, application process, or restricted repository).</li>
<li><strong>Non-shareable:</strong> cannot be shared due to legal or ethical constraints; however, journals still expect transparent disclosure and, where feasible, a process for qualified access.</li>
</ul>
</li>
</ol>
<p>Springer Nature explicitly notes that reviewers may request access to data that are not publicly available, and that repositories can support peer-review access via private links that do not include author information, particularly relevant in double-blind workflows.</p>
<h2><strong>How to Generate Private Reviewer Links in Figshare (and What to Double-Check)</strong></h2>
<p>Figshare supports private links that allow access to files and metadata before the item is public, including for anonymous <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>. In Figshare’s user guide, the private link function is presented as a way to share unpublished or embargoed content privately (for example, during <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>), and it can also be configured with an expiration date.</p>
<p>A typical Figshare workflow during submission is:</p>
<ol>
<li>Upload files and complete the item metadata as required by the repository or journal integration.</li>
<li>Use the item’s sharing controls to select “Share with private link.”</li>
<li>Configure expiration (optional) and copy the generated URL for the submission system.</li>
</ol>
<p>Two details matter for compliance, and are easy to miss during a rushed <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">journal submission</a> process:</p>
<p><strong>First,</strong> Figshare notes that people accessing the private link will see an anonymized version of metadata (author information removed). However, the files themselves may still contain identifiers (for example, institution names in file properties, author names in a readme, or acknowledgments in supplementary PDFs). Figshare explicitly warns that anyone with the private link can view and download files, so the files should be anonymized when needed for double-blind <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>.</p>
<p><strong>Second,</strong> private links are not meant to be permanent scholarly identifiers. Figshare documentation and <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a> guidance emphasize that private links support anonymous access during review, whereas the DOI (once public) should be used for the final, published record.</p>
<h2><strong>How Dryad Handles “Private for Peer Review” Links (and What “Temporary” Means)</strong></h2>
<p>Dryad offers a specific setting called “Private for <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">Peer Review</a>.” When selected, the dataset remains private while the associated manuscript is under <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>, and Dryad provides a private URL that supports double-anonymous download for reviewers and journal staff.</p>
<p>Dryad also clarifies a key distinction that directly affects how the Data Availability Statement should be written:</p>
<ul>
<li>The reviewer sharing link is a temporary URL that provides access to uncurated data during review and is not a permanent identifier.</li>
<li>The dataset’s reserved DOI is permanent and will activate upon publication of the dataset.</li>
</ul>
<p>This matters because many journals want a stable pointer in the final article. A strong submission workflow therefore uses (a) the private URL for <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a> access and (b) the DOI once the dataset is released and published, updating the manuscript at the appropriate stage if the journal allows (often at acceptance or proofs).</p>
<p>Dryad also notes that submissions left in “Private for <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">Peer Review</a>” for one year with no activity may be withdrawn, which is another reason not to treat the peer-review link as an archival citation.</p>
<h2><strong>How to Format a Data Availability Statement That Editors Can Verify Quickly</strong></h2>
    <!-- INLINE SERVICE CARD: AI Disclosure -->
     <div class="svc">
    <div class="svc-body">
      <span class="svc-cat">
        AI Compliance <span class="svc-free">Free</span>
      </span>
      <div class="svc-row">
        <div class="svc-ic">
          <svg viewBox="0 0 200 200" fill="none" xmlns="http://www.w3.org/2000/svg">
            <path d="M52 20H122L158 58V182C158 184.209 156.209 186 154 186H52C49.791 186 48 184.209 48 182V24C48 21.791 49.791 20 52 20Z" stroke="white" stroke-width="5.4" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M122 20L158 58H126C123.791 58 122 56.209 122 54V20Z" stroke="white" stroke-width="5.4" stroke-linecap="round" stroke-linejoin="round"></path>
            <line x1="66" y1="80" x2="122" y2="80" stroke="white" stroke-width="5" stroke-linecap="round"></line>
            <line x1="66" y1="97" x2="140" y2="97" stroke="white" stroke-width="5" stroke-linecap="round"></line>
            <line x1="66" y1="114" x2="132" y2="114" stroke="white" stroke-width="5" stroke-linecap="round"></line>
            <path d="M103 130C103 130 78 139 78 155C78 166 88.5 174 103 178C117.5 174 128 166 128 155C128 139 103 130 103 130Z" stroke="white" stroke-width="5.4" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M92 155L99 162L115 147" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"></path>
          </svg>
        </div>
        <h4>Required by most journals. Done in 60 seconds.</h4>
      </div>
      <p class="svc-desc">Our editorial team built this generator from COPE, ICMJE, and leading publisher guidelines — so your <a href="https://www.enago.com/ai-disclosure-statement-generator" data-internallinksmanager029f6b8e52c="58" title="AI Disclosure" target="_blank" rel="noopener">AI disclosure</a> is fully compliant and authored with human care.</p>
      <a href="https://www.enago.com/ai-disclosure-statement-generator" class="svc-btn" target="_blank">Generate Statement Free →</a>
    </div>
  </div>
    
<p>Most journals do not require literary polish in a Data Availability Statement, but they do require precision. A strong statement answers, in a small number of sentences:</p>
<ul>
<li>What data are covered (raw data, processed data, code, materials).</li>
<li>Where they are (repository name + persistent identifier such as DOI or accession number).</li>
<li>When access applies (available now, available upon publication, under embargo).</li>
<li>How access works if restricted (who controls access, what process, what conditions).</li>
<li>Why data are not shared if applicable (privacy, consent limits, legal restrictions, third-party licensing).</li>
</ul>
<p>Springer Nature’s guidance is explicit that a DAS should describe how to access data supporting the results, include persistent identifiers (e.g., DOI or accession number) when deposited in repositories, and explain when data cannot be shared openly (for example, participant privacy).</p>
<h2><strong>Repository-Based DAS Templates (Adapt as Needed)</strong></h2>
<h3><strong>1) Data Publicly Available Now (Best When Allowed at Submission)</strong></h3>
<p>The datasets generated and/or analyzed during the current study are available in [Repository name] at [DOI or accession number].</p>
<h3><strong>2) Data Deposited but Private for Peer Review (Double-Blind Workflow)</strong></h3>
<p>The data supporting the findings of this study have been deposited in [Repository name]. During <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>, editors and reviewers can access the files via the private reviewer link provided in the submission system. Upon acceptance/publication, the dataset will be made publicly available and will be accessible via [reserved DOI, if available].</p>
<p>This approach aligns with how repositories differentiate temporary reviewer links from permanent identifiers (e.g., Dryad’s temporary private URL vs reserved DOI).</p>
<h3><strong>3) Restricted Access Due to Ethics/Legal Constraints (But Access Possible)</strong></h3>
<p>The data are not publicly available due to [brief reason, e.g., identifiable human participant information and consent limitations]. De-identified data may be made available to qualified researchers upon reasonable request and with approval from [data access committee / institution / ethics board], subject to [data use agreement / IRB conditions].</p>
<p>This direction matches major journal policies that accept restrictions when justified, as long as the DAS clearly states the pathway for access.</p>
<h3><strong>4) Third-Party/Licensed Data (Authors Cannot Share)</strong></h3>
<p>The study analyzed data obtained from [provider] under license and the authors do not have permission to share the data publicly. Researchers may obtain access by applying directly to [provider] at [instructions or access page]. Any derived data that can be shared are available at [repository/DOI].</p>
<p>PLOS explicitly addresses third-party data limitations and expects authors to provide enough information for others to seek access.</p>
<h2><strong>Common Mistakes That Trigger Avoidable Back-and-Forth During Submission</strong></h2>
<p>Several issues repeatedly slow down the <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">journal submission</a> process, especially for early-career researchers navigating open-data requirements for the first time.</p>
<p>A frequent problem is using a reviewer-only private link as the final citation. Repositories and journal guidance generally treat reviewer links as temporary access mechanisms; final publication should point to a DOI, accession number, or stable landing page. Dryad is particularly explicit that the reviewer sharing link is not a permanent identifier and should be replaced by the DOI later.</p>
<p>Another common issue is double-blind leakage. Even when repository metadata are anonymized, file contents may expose authorship (for example, a methods appendix with institutional letterhead). Figshare explicitly warns that private-link recipients can see any identifying information within the files, so anonymization should be handled before sharing.</p>
<p>Finally, many Data Availability Statement drafts fail because they are overly generic, such as “Data available upon request,” without naming who controls access or what qualifies a request as reasonable. Policies increasingly expect specificity, particularly when restrictions apply.</p>
<h2><strong>A Submission-Ready Workflow: What to Finalize Before Clicking “Submit”</strong></h2>
<p>For researchers aiming to submit a paper to journal portals smoothly, a short pre-submit sequence can reduce compliance surprises:</p>
<ol>
<li>Confirm the journal’s DAS wording requirements and whether the journal publishes the statement verbatim.</li>
<li>Deposit data in an appropriate repository (disciplinary if mandated; generalist if allowed).</li>
<li>If <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a> requires confidentiality, generate a private reviewer link (Figshare private link or Dryad “Private for <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">Peer Review</a>” URL) and verify it opens without logging in.</li>
<li>Review files for anonymization if the journal uses double-blind <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>.</li>
<li>Draft the Data Availability Statement with a persistent identifier when available (DOI/accession) and clear conditions if not.</li>
<li>Place the reviewer link only where the journal requests it (often in submission fields, not in the main manuscript), and plan to update the DAS at acceptance if needed.</li>
</ol>
<p>This is also where many authors benefit from practical research paper publication support. If the submission portal requires multiple disclosures and supplementary documents, a managed <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">journal submission</a> workflow can reduce returned submissions by ensuring all forms, declarations, and uploads align with the journal’s requirements. Enago’s <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">journal submission</a> assistance can help coordinate these compliance elements, especially when datasets, supplementary files, and policy statements must be aligned across systems.</p>
<h2><strong>Closing Perspective: Treat the DAS as Part of Research Transparency, Not a Last-Minute Formality</strong></h2>
<p>Data Availability Statements and repository linking have become integral to how journals operationalize transparency. When handled proactively, by aligning repository settings, private reviewer access, and a precise DAS, authors can reduce avoidable submission delays and keep editorial evaluation focused on the science.</p>
<p>Researchers preparing for a time-sensitive submission can also consider targeted support such as submission assistance to keep policy-driven details (including data statements and supplementary files) consistent across the manuscript and submission system, which can help streamline the overall paper submission process.</p>
<p>The post <a href="https://www.enago.com/articles/data-availability-statement-requirements/">Data Availability Statement Requirements: Using Private Reviewer Links for Journal Submission</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.enago.com/articles/data-availability-statement-requirements/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Resubmission Cover Letter: Addressing Previous Rejections</title>
		<link>https://www.enago.com/articles/resubmission-cover-letter-after-rejection/</link>
					<comments>https://www.enago.com/articles/resubmission-cover-letter-after-rejection/#respond</comments>
		
		<dc:creator><![CDATA[Roger Watson]]></dc:creator>
		<pubDate>Wed, 18 Feb 2026 10:27:30 +0000</pubDate>
				<category><![CDATA[Submission Requirements]]></category>
		<guid isPermaLink="false">https://www.enago.com/academy/?p=57510</guid>

					<description><![CDATA[<p>Rejection is a normal outcome of peer review, but it can feel like a publication dead-end especially for early career researchers who interpret “reject” as “unpublishable.” In practice, many rejected manuscripts are later published elsewhere after targeted revisions, clearer positioning, and a more strategic journal article submission package. What often changes the outcome is not [&#8230;]</p>
<p>The post <a href="https://www.enago.com/articles/resubmission-cover-letter-after-rejection/">The Resubmission Cover Letter: Addressing Previous Rejections</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Rejection is a normal outcome of <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>, but it can feel like a publication dead-end especially for early career researchers who interpret “reject” as “unpublishable.” In practice, many rejected manuscripts are later published elsewhere after targeted revisions, clearer positioning, and a more strategic journal article submission package. What often changes the outcome is not only the revised manuscript, but also the resubmission cover letter that helps a new editor quickly understand (1) what the study contributes and (2) how the submission has been strengthened since the last decision.</p>
<p>This article explains how to write a resubmission cover letter when a paper was rejected by another journal, including whether to disclose the prior rejection, how to incorporate reviewer feedback responsibly, and how to frame the new submission to maximize editorial confidence.</p>
<h2><strong>What Makes a Resubmission Cover Letter Different (and Why Editors Notice)</strong></h2>
<p>A standard cover letter introduces the manuscript, states fit with the journal, and highlights novelty. A resubmission cover letter must do all of that while also resolving an unspoken editorial concern: Has the manuscript meaningfully improved, or is it being “recycled” without addressing known weaknesses? A concise, evidence-based letter reduces uncertainty and signals professionalism.</p>
<p>Importantly, reputable guidance recognizes that prior <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a> can add value when handled transparently. The International Committee of Medical Journal Editors (ICMJE) notes that if a manuscript was previously submitted to another journal, it can be helpful to include previous editors’ and reviewers’ comments and the authors’ responses because this may expedite review and encourages transparency. However, this is framed as helpful rather than universally required, so authors should treat disclosure as a strategic decision guided by the target journal’s policies and the specifics of the case.</p>
<h2><strong>Should the Cover Letter Disclose the Previous Rejection?</strong></h2>
<h3><strong>When Disclosure Is Usually a Good Idea</strong></h3>
<p>Disclosure tends to help when it reduces editorial risk or prevents misunderstandings. For example, disclosure can be useful when the previous review raised substantive scientific issues that have been fully addressed and the authors want the new editor to see that the manuscript has already benefited from external critique. It can also help when the new journal’s submission system or policies explicitly request details of previous or concurrent submissions. Elsevier’s author guidance, for instance, notes that a cover letter may include “details of any previous or concurrent submissions,” especially if the journal’s guide for authors is silent.</p>
<p>Disclosure is also worth considering when there is a realistic chance the same reviewers will be invited again (common in specialized fields). If the revised manuscript is substantially improved and the authors can clearly document changes, the editorial process may move faster.</p>
<h3><strong>When Disclosure Is Often Unnecessary (and Can Distract)</strong></h3>
<p>Disclosure is usually not needed when the manuscript was desk-rejected for “fit” (aims and scope mismatch) and the authors have since targeted a more appropriate journal. In that scenario, the new editor mainly needs to see strong fit and clear contribution, not the previous journal’s decision. If disclosed clumsily, a prior rejection can shift attention away from the current submission’s value.</p>
<p>A practical rule: disclose only if it benefits the editor’s decision-making at the new journal. Otherwise, focus on fit, contribution, and readiness for review.</p>
<h3><strong>What Not to Do</strong></h3>
<p>Never use the resubmission cover letter to argue with the previous journal’s decision or to “appeal by proxy.” The new editor cannot adjudicate the prior rejection, and a defensive tone signals scrutiny.</p>
<h2><strong>How to Incorporate Previous Reviewer Feedback Without Overloading the Letter</strong></h2>
  <div class="svc">
    <div class="svc-body">
      <span class="svc-cat">
       
        Expert Editing
      </span>
      <div class="svc-row">
        <div class="svc-ic">
          <svg viewBox="0 0 200 200" fill="none" xmlns="http://www.w3.org/2000/svg">
            <path fill-rule="evenodd" clip-rule="evenodd" d="M198.207 70.1185C195.92 65.3714 193.104 61.0119 188.963 57.6453C185.159 54.5452 180.825 52.7771 175.986 52.1474C170.04 51.3966 164.31 52.3654 158.701 54.2061C155.282 55.3202 151.984 56.7734 148.854 58.5657C148.493 58.7836 148.3 58.711 148.036 58.4203C143.991 54.0123 138.959 51.6146 133.061 50.9364C129.739 50.5489 126.441 50.7669 123.094 51.4935C122.998 50.5247 122.926 49.6043 122.805 48.684C122.276 44.1791 120.976 39.9406 118.231 36.2592C115.053 31.9965 110.768 29.5019 105.664 28.412C99.5732 27.1283 93.6989 27.7338 88.1858 30.7613C82.769 33.7403 79.6152 38.4632 78.1226 44.3486C77.6411 46.3104 77.4485 48.3449 77.1355 50.3309C77.0874 50.6942 77.0392 51.0575 76.9911 51.445C75.7392 51.2755 74.5354 51.0333 73.3317 50.9122C65.1463 50.1614 57.8757 52.1716 52.0978 58.3719C51.7848 58.711 51.5922 58.7594 51.1588 58.5414C45.6939 55.4655 39.8919 53.31 33.7047 52.3412C27.2767 51.3482 21.0173 51.8326 15.143 54.9569C10.7373 57.282 7.31873 60.697 4.74273 64.9355C3.32232 67.2848 2.11858 69.7552 1.01114 72.2741C0.50557 73.4366 0.433346 74.7929 0.168523 76.0524C0.0722243 76.5126 0.0481495 76.9727 0 77.4087V79.0072C0.096299 79.7822 0.168523 80.5815 0.240748 81.3565C0.794467 86.8786 2.45562 92.1101 4.5742 97.2205C7.77614 104.85 11.917 111.97 16.6838 118.679C19.7654 123.015 23.0636 127.205 26.2896 131.443C26.6267 131.879 26.7711 132.267 26.7711 132.824C26.7711 142.1 26.7711 151.352 26.7711 160.628V161.403H173.242V160.604C173.242 151.328 173.242 142.076 173.242 132.799C173.242 132.291 173.386 131.879 173.699 131.492C179.405 124.516 184.726 117.25 189.276 109.452C192.911 103.251 196.041 96.8088 198.087 89.8819C199.146 86.2731 199.845 82.616 199.989 78.8377C200.085 75.8102 199.556 72.9038 198.207 70.1427V70.1185ZM116.931 72.6132C119.965 71.6202 122.878 72.0319 125.67 73.4366C131.183 76.2219 134.409 80.6784 135.083 86.8544C135.493 90.6085 134.698 94.2172 133.326 97.7049C131.207 103.057 128.005 107.732 124.274 112.043C123.239 113.254 122.107 114.417 121 115.579C120.831 115.773 120.518 115.942 120.277 115.942C116.594 116.088 112.911 116.209 109.227 116.33C109.083 116.33 108.938 116.33 108.794 116.306C108.794 113.036 108.794 109.863 108.794 106.69C108.794 102.791 108.866 98.8917 108.914 94.9681C108.962 89.7608 109.035 84.5535 109.131 79.3463C109.131 78.9345 109.299 78.4259 109.564 78.1111C111.562 75.6406 113.874 73.582 116.955 72.5647L116.931 72.6132ZM95.4082 42.7986C99.0195 41.6845 102.655 41.636 106.025 43.6947C108.818 45.4143 110.407 48.0785 111.394 51.1302C111.683 52.0505 111.851 53.0193 112.116 53.9397C112.261 54.3999 112.116 54.5936 111.707 54.8116C108.722 56.3617 105.76 57.936 102.799 59.5345C101.908 60.0189 101.114 60.6244 100.223 61.2056C98.3213 59.9946 96.3953 58.711 94.4212 57.5C92.6156 56.3859 90.7859 55.3444 88.7395 54.7632C88.5951 54.7147 88.4266 54.521 88.4025 54.3756C87.7043 49.8223 91.0266 44.1549 95.4082 42.7986ZM64.9778 87.024C65.5315 81.5503 68.1315 77.2876 72.802 74.357C74.9688 73.0007 77.28 72.1045 79.856 72.1045C82.7209 72.1045 85.2246 73.1702 87.3914 74.9867C88.5469 75.9555 89.5581 77.0938 90.5933 78.2079C90.834 78.4744 91.0026 78.9345 91.0026 79.3221C91.1229 88.1623 91.1952 97.0025 91.2915 105.867C91.3155 109.209 91.3637 112.576 91.4118 115.918C91.4118 116.039 91.4118 116.16 91.3878 116.33C90.6655 116.33 89.9914 116.33 89.3173 116.33C86.2117 116.209 83.082 116.112 79.9763 115.967C79.7115 115.967 79.3985 115.87 79.2059 115.7C73.8373 110.275 69.2631 104.293 66.5185 97.051C65.2907 93.8297 64.6407 90.4632 65.0018 87.024H64.9778ZM33.5843 116.064C28.649 110.614 24.4359 104.68 21.6432 97.826C20.2469 94.3626 19.3561 90.8022 19.5005 87.024C19.6931 82.0347 21.7154 77.9173 25.4952 74.6961C27.3248 73.146 29.5879 72.5163 31.9231 72.2256C36.3047 71.6928 40.4215 72.7343 44.3938 74.4054C44.5864 74.5023 44.8272 74.7929 44.8513 75.0109C45.0439 78.547 45.1402 82.1073 45.405 85.6434C45.9587 92.9336 46.7772 100.2 48.8236 107.248C49.5458 109.718 50.4125 112.091 51.857 114.247C52.1941 114.756 52.5793 115.216 53.0126 115.821C52.3385 115.87 51.8089 115.918 51.2551 115.918C45.6698 116.064 40.0604 116.209 34.475 116.354C34.1861 116.354 33.7769 116.257 33.6084 116.064H33.5843ZM160.94 152.999H40.4456V127.883H160.916V152.999H160.94ZM180.537 89.4944C180.031 95.0649 177.792 100.006 174.999 104.753C172.616 108.773 169.823 112.455 166.669 115.894C166.453 116.112 166.092 116.354 165.803 116.33C159.688 116.185 153.549 115.991 147.434 115.821C147.362 115.821 147.265 115.797 147.121 115.749C150.058 112.188 151.189 107.95 152.201 103.663C153.284 99.0612 153.958 94.411 154.319 89.7124C154.68 84.8684 154.921 80.0002 155.21 75.132C155.21 74.7687 155.258 74.5265 155.643 74.357C159.158 72.9038 162.769 71.935 166.621 72.0561C168.355 72.1045 170.064 72.4436 171.701 73.0491C175.144 74.357 177.262 77.0212 178.899 80.1697C180.392 83.0761 180.825 86.2247 180.537 89.4702V89.4944ZM27.0841 169.444H173.362V164.067H27.0841V169.444ZM56.4071 148.857C61.0054 148.857 64.8092 145.03 64.7852 140.429C64.7852 135.803 60.9813 132 56.3831 132C51.7848 132 47.981 135.827 48.0051 140.429C48.0291 145.03 51.8089 148.857 56.4071 148.857ZM78.5318 148.857C83.1301 148.857 86.9339 145.055 86.9339 140.429C86.9339 135.803 83.1301 132 78.5318 132C73.9336 132 70.1298 135.803 70.1298 140.429C70.1298 145.055 73.9336 148.857 78.5318 148.857ZM100.657 148.857C105.255 148.857 109.059 145.079 109.083 140.453C109.083 135.827 105.303 132 100.705 132C96.1064 132 92.3026 135.803 92.2785 140.404C92.2785 145.03 96.0583 148.857 100.657 148.857ZM122.829 148.857C127.428 148.857 131.207 145.03 131.207 140.404C131.207 135.778 127.404 131.976 122.805 131.976C118.207 131.976 114.427 135.803 114.427 140.429C114.427 145.055 118.231 148.857 122.829 148.857ZM144.954 148.857C149.552 148.857 153.356 145.055 153.356 140.429C153.356 135.803 149.552 132 144.954 132C140.356 132 136.552 135.827 136.552 140.429C136.552 145.055 140.356 148.857 144.954 148.857Z" fill="#FEC043"></path>
          </svg>
        </div>
        <h4>More than proofreading — a complete expert rework.</h4>
      </div>
      <p class="svc-desc">A dedicated human editor assesses argument flow, restructures paragraphs for logic and clarity, and strengthens your research story from the ground up.</p>
      <a href="https://www.enago.com/substantive-editing" class="svc-btn" target="_blank">Get Substantive Editing →</a>
    </div>
  </div>
    
<p>Reviewer comments are most useful when they are translated into concrete manuscript improvements. The cover letter is not a response-to-reviewers document, but it can briefly summarize high-impact changes that matter for editorial screening.</p>
<h3><strong>Step-by-Step Approach for Translating Old Reviews Into a Stronger Submission</strong></h3>
<ol>
<li>Classify the previous critiques into categories such as: fit/novelty, methods rigor, <a href="https://www.enago.com/publication-support-services/statistical-analysis.htm" data-internallinksmanager029f6b8e52c="32" title="Statistical Analysis">statistical analysis</a>, interpretation, structure/clarity, or reporting completeness.</li>
<li>Implement only the improvements that strengthen the science and presentation for the new journal’s audience (not every request is transferable across journals).</li>
<li>Document changes in an internal change log (even if it will not be submitted). This makes it easier to write an accurate, concise cover letter summary.</li>
<li>Select 2-4 changes that are genuinely decisive (e.g., expanded methods detail, additional robustness checks, improved framing of novelty, updated literature).</li>
<li>Describe changes as outcomes, not as emotions. Replace “Reviewer 2 was unfair” with “The limitations section now clarifies X; additional analyses Y were added to address Z.”</li>
</ol>
<p>If the target journal allows or encourages sharing prior reviews and responses, the ICMJE suggests that providing those materials can help and may expedite review. In such cases, the cover letter should mention what is attached and how it supports the submission.</p>
<h2><strong>Framing the New Submission: From “Rejected Paper” to “Publication-Ready Contribution”</strong></h2>
<p>Editors evaluate (1) fit, (2) technical soundness, (3) novelty and significance, and (4) clarity. A resubmission cover letter should be structured to support those checkpoints quickly.</p>
<h3><strong>Fit Comes First</strong></h3>
<p>Before mentioning any prior rejection (if at all), the letter should show why the manuscript belongs in the new journal. Springer Nature cover letter guidance emphasizes that the cover letter should explain why the submission will interest the journal’s readers and highlight any special considerations that the editor should know.</p>
<p>This is where many resubmissions fail: the manuscript may be improved, but the cover letter still reads like it was written for the previous journal. A mismatch between the manuscript’s positioning and the new journal’s scope increases desk-rejection risk.</p>
<h3><strong>Then Emphasize Novelty and Significance, Briefly</strong></h3>
<p>Elsevier cover letter guidance advises keeping cover letters short and focused, ideally under one page, and clearly stating aim, main findings, novelty, and broader implications. A resubmission cover letter benefits from the same discipline, with an added sentence or two that signals strengthening since the prior review.</p>
<h3><strong>Finally, Add a Controlled “Revision Narrative”</strong></h3>
<p>If prior reviews are mentioned, the language should be factual and minimal:</p>
<ul>
<li>What was improved</li>
<li>Why it improves reliability or clarity</li>
<li>How it aligns with the new journal’s readership</li>
</ul>
<p>Avoid implying that the new journal is a “backup.” The correct framing is “better fit” and “stronger manuscript,” not “second attempt.”</p>
<h2><strong>What to Include (and Avoid) in the Resubmission Cover Letter</strong></h2>
<p>A strong resubmission cover letter typically includes:</p>
<ul>
<li>Manuscript title and article type, aligned with the target journal’s categories</li>
<li>One-paragraph contribution summary (problem, method, key result, why it matters)</li>
<li>A clear fit statement tied to the journal’s aims/scope and readership</li>
<li>A brief “what changed” statement (2-4 improvements) if prior feedback is referenced</li>
<li>Required declarations requested by the journal (many journals handle these in forms; follow the target journal’s instructions)</li>
</ul>
<p>Common mistakes that trigger negative signals:</p>
<ul>
<li>Addressing the letter to the wrong journal (it does happen!)</li>
<li>Copy-pasting the abstract instead of offering editor-facing context</li>
<li>Overpromising impact (“paradigm-shifting”) without evidence</li>
<li>Long explanations of reviewer disagreements</li>
<li>Vague statements like “the manuscript has been thoroughly revised” with no specifics</li>
</ul>
<h2><strong>A Practical Comparison: Desk Rejection vs. Reject After Peer Review</strong></h2>
<table>
<thead>
<tr>
<th>Previous Outcome</th>
<th>What It Typically Means</th>
<th>Best Cover Letter Emphasis for the Next Journal</th>
</tr>
</thead>
<tbody>
<tr>
<td>Desk rejection (no external review)</td>
<td>Usually a fit, priority, or basic readiness issue</td>
<td>Fit to scope, clarity of contribution, compliance with author guidelines</td>
</tr>
<tr>
<td>Rejection after <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a></td>
<td>The work had potential but concerns prevented acceptance</td>
<td>Key improvements that address rigor/interpretation + renewed fit and significance</td>
</tr>
</tbody>
</table>
<p>This distinction prevents a common misstep: writing a resubmission cover letter that heavily discusses “revisions” when the paper was never reviewed. If there were no reviewer comments, the letter should focus on fit and contribution, not “responses.”</p>
<h2><strong>Template Language: How to Disclose Prior Rejection (Without Harming the Submission)</strong></h2>
<p>Use disclosure only when it is genuinely helpful. If used, keep it to one short block and make it outcome-focused.</p>
<p>Example phrasing (adapt as needed):</p>
<p>“The manuscript has benefited from prior external <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a> at another journal. The current version has been substantially strengthened, including (i) expanded methodological detail and robustness checks, (ii) revised interpretation to better distinguish confirmatory vs. exploratory analyses, and (iii) updated positioning to align with the target readership. If helpful, previous reviewer comments and a point-by-point summary of revisions can be provided.”</p>
<p>This avoids naming the rejecting journal (unless a policy or special circumstance requires it) and keeps attention on quality improvements.</p>
<h2><strong>When Additional Documents Help More Than the Cover Letter</strong></h2>
<p>Sometimes the cover letter cannot carry the entire resubmission narrative. Consider adding supporting items only if the journal allows them:</p>
<ul>
<li>A tracked-changes version (if requested)</li>
<li>A concise “summary of changes” page (if permitted)</li>
<li>Reporting checklists (CONSORT, PRISMA, STROBE, etc.) when relevant and required</li>
</ul>
<p>Editors are more persuaded by evidence of compliance and clarity than by rhetorical reassurance.</p>
<h2><strong>Conclusion: A Rejection Is Not the End, Unless the Resubmission Strategy Is Unchanged</strong></h2>
<p>A resubmission cover letter works best when it is treated as an editorial tool, not a formality. It should prioritize journal fit, summarize the manuscript’s contribution in a reader-centered way, and, only when helpful, briefly explain how the manuscript has improved after prior review. Disclosure of prior rejection is not universally required, but transparency can be advantageous when it accelerates evaluation or clarifies the manuscript’s history in a policy-aligned way.</p>
<p>The next step is straightforward: revise the manuscript with the new journal’s audience in mind, distill the strongest 2-4 improvements into a short revision narrative, and build a submission package that signals readiness for review from the first page.</p>
<h2><strong>Strategic Support: Navigating the Resubmission Phase</strong></h2>
<p>Turning a rejected paper into an accepted one requires a shift from &#8220;defending the old work&#8221; to &#8220;optimizing the new submission.&#8221; Specialized services can help bridge this gap by handling the technical and strategic burdens of resubmission:</p>
<ul>
<li><strong>Refining the Core:</strong> If your previous rejection was based on methodological concerns or data interpretation, a Research Paper Revision service ensures that critiques are addressed with scientific rigor before the next editor sees them. This moves beyond simple editing to ensure the logic and evidence meet the standards of the new target journal.</li>
<li><strong>Executing the Submission:</strong> To avoid the &#8220;recycled&#8221; look and ensure every portal field, declaration, and formatting requirement is perfect, <a href="https://www.enago.com/publication-support-services/journal-submission" data-internallinksmanager029f6b8e52c="24" title="Journal Submission" target="_blank" rel="noopener">Journal Submission</a> Support takes the administrative weight off your shoulders. Professionals handle the task of writing a new cover letter, uploading files and managing metadata, ensuring your resubmission package is professional, compliant, and ready for an immediate &#8220;yes&#8221; to <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>.</li>
</ul>
<p>By treating resubmission as a fresh opportunity to showcase quality, you ensure that your research eventually finds the home and the impact it deserves.</p>
<p>The post <a href="https://www.enago.com/articles/resubmission-cover-letter-after-rejection/">The Resubmission Cover Letter: Addressing Previous Rejections</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.enago.com/articles/resubmission-cover-letter-after-rejection/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Reality Of “Format-Free Submission: What Authors Actually Need To Prepare</title>
		<link>https://www.enago.com/articles/format-free-submission-guide/</link>
					<comments>https://www.enago.com/articles/format-free-submission-guide/#respond</comments>
		
		<dc:creator><![CDATA[Roger Watson]]></dc:creator>
		<pubDate>Thu, 12 Feb 2026 08:28:07 +0000</pubDate>
				<category><![CDATA[Submission Requirements]]></category>
		<guid isPermaLink="false">https://www.enago.com/academy/?p=57473</guid>

					<description><![CDATA[<p>Format-free submission (also marketed as Free Format or Your Paper, Your Way) is now widely promoted across major scholarly publishers. The promise is straightforward: reduce time spent on cosmetic manuscript formatting so researchers can focus on the science and speed up the research publication process. Wiley, for example, notes that hundreds of its journals accept [&#8230;]</p>
<p>The post <a href="https://www.enago.com/articles/format-free-submission-guide/">The Reality Of “Format-Free Submission: What Authors Actually Need To Prepare</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>Format-free submission</em> (also marketed as <strong>Free Format</strong> or <strong>Your Paper, Your Way</strong>) is now widely promoted across major scholarly publishers. The promise is straightforward: reduce time spent on cosmetic <a href="https://www.enago.com/publication-support-services/manuscript-formatting" data-internallinksmanager029f6b8e52c="25" title="Manuscript Formatting" target="_blank" rel="noopener">manuscript formatting</a> so researchers can focus on the science and speed up the research publication process. Wiley, for example, notes that hundreds of its journals <a href="https://authorservices.wiley.com/author-resources/Journal-Authors/Prepare/free-format-submission.html">accept submissions in <strong>any consistent format</strong></a>, without requiring authors to match the journal’s exact formatting rules at first submission.</p>
<p>Yet many authors still face delays during the initial technical check because <em>format-free</em> does not mean <em>requirement-free</em>. Most journals still expect accurate citations, complete submission metadata, and mandatory manuscript sections (plus declarations and required files) before the research manuscript can be sent to an editor or peer reviewers. <a href="https://www.elsevier.com/en-in/subject/next/guide-for-authors">Elsevier’s “Your Paper Your Way”</a> similarly highlights simplified initial formatting and may allow a <em>single file</em> for review, but it does not remove the need for complete, readable, policy-compliant content.</p>
<p>This article explains what <em>format-free submission</em> really means, what still triggers avoidable technical-check holds, and how to submit an academic manuscript efficiently while meeting manuscript guidelines.</p>
<h2><strong>What “Format-Free Submission” Actually Means (and What It Does Not)</strong></h2>
<p>At its core, format-free submission means the journal does not require strict adherence to its final layout rules at the first submission. This usually includes flexibility on items such as reference style, line numbering, and whether figures must be placed at the end or embedded in the text. Wiley describes free format submission as allowing manuscripts in any consistent format, making submission “easier and faster,” with journal formatting typically enforced after revision or acceptance.</p>
<p>Elsevier’s “Your Paper Your Way” approach also allows authors to submit a manuscript as a single file for the refereeing process (for example, a Word document or PDF), with formatting requirements becoming more relevant later in the workflow.</p>
<p>What it <em>does not</em> mean is that a journal will overlook missing manuscript components, incomplete author information, unclear figures, absent declarations, or inconsistent citations. In short, format-free submission reduces styling work, but it does not eliminate technical screening for your research manuscript.</p>
<h2><strong>Why Journals Still Run Technical Checks Even for Format-Free Submissions</strong></h2>
<p>Before <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>, journals typically perform an administrative screening to confirm the submission is complete, readable, and compliant with journal and publisher policies. This protects editorial time and reduces reviewer burden caused by incomplete or non-compliant research manuscripts.</p>
<p>Even when reference formatting is flexible, journals still need enough structure to:</p>
<ol>
<li>Route the paper to the right editor</li>
<li>Assess whether the study type fits the journal</li>
<li>Verify required disclosures</li>
<li>Ensure the submission can be reviewed without confusion</li>
</ol>
<p>That is why the “submit academic manuscript” process still includes mandatory portal fields and required statements, even under format-free submission models.</p>
<h2><strong>What Still Matters: The Non-Negotiables That “Format-Free” Does Not Remove</strong></h2>
<h3><strong>Consistent Citations and a Complete Reference List (Style-Flexible, Not Accuracy-Flexible)</strong></h3>
<p>Most format-free submission policies relax <em>reference style</em>, not <em>reference quality</em>. Elsevier explicitly notes there are no strict requirements on reference formatting at submission and references can be in any style, as long as the style is consistent.</p>
<p>In practice, consistency means readers can reliably connect claims to sources. That requires:</p>
<ul>
<li>Stable in-text citation behavior (author–date or numbered, but not both)</li>
<li>A reference list that includes all cited works</li>
<li>Enough bibliographic detail to identify sources (authors, title, journal/book, year, volume/issue, pages, and DOI when available)</li>
</ul>
<p>Common technical-check problems that still occur under format-free submission include:</p>
<ul>
<li>Missing references that are cited in the text</li>
<li>References listed but never cited</li>
<li>Inconsistent author name formatting across entries</li>
<li>Broken or incomplete DOI details</li>
</ul>
<h3><strong>Complete Submission Metadata (What Authors Type Into the Portal)</strong></h3>
<p>Format-free submission does not remove the requirement to fill in the journal’s online fields. Journals still rely on accurate metadata for indexing, peer reviewer matching, and editor assignment critical steps in the research publication process.</p>
<ul>
<li>Full title and running title (if requested)</li>
<li>Author names exactly as they should appear in publication</li>
<li>Institutional affiliations</li>
<li>Corresponding author details</li>
<li>Abstract and keywords</li>
<li>Funding information (if any)</li>
<li>Conflict of interest disclosures</li>
<li>Ethical approvals (where applicable)</li>
<li>Data availability details (if required by the journal)</li>
</ul>
<p>Taylor &amp; Francis, for example, provides a <a href="https://authorservices.taylorandfrancis.com/publishing-your-research/making-your-submission/using-taylor-francis-submission-portal/">step-by-step guide</a> to using its submission portal, reflecting how much of the process depends on correct portal completion rather than visual formatting.</p>
<h3><strong>Mandatory Manuscript Sections (and Study-Type Requirements)</strong></h3>
<p>Format-free submission rarely changes the expectation that the academic manuscript includes the core components editors and reviewers need. While section names vary by discipline and journal, most research manuscripts still require: title, abstract, introduction, methods, results, discussion, conclusions (or an equivalent structure), plus references and figure/table legends as applicable.</p>
<h3><strong>Declarations and Policy Statements (Often the Real Technical-Check Gate)</strong></h3>
    <!-- INLINE SERVICE CARD: AI Disclosure -->
     <div class="svc">
    <div class="svc-body">
      <span class="svc-cat">
        AI Compliance <span class="svc-free">Free</span>
      </span>
      <div class="svc-row">
        <div class="svc-ic">
          <svg viewBox="0 0 200 200" fill="none" xmlns="http://www.w3.org/2000/svg">
            <path d="M52 20H122L158 58V182C158 184.209 156.209 186 154 186H52C49.791 186 48 184.209 48 182V24C48 21.791 49.791 20 52 20Z" stroke="white" stroke-width="5.4" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M122 20L158 58H126C123.791 58 122 56.209 122 54V20Z" stroke="white" stroke-width="5.4" stroke-linecap="round" stroke-linejoin="round"></path>
            <line x1="66" y1="80" x2="122" y2="80" stroke="white" stroke-width="5" stroke-linecap="round"></line>
            <line x1="66" y1="97" x2="140" y2="97" stroke="white" stroke-width="5" stroke-linecap="round"></line>
            <line x1="66" y1="114" x2="132" y2="114" stroke="white" stroke-width="5" stroke-linecap="round"></line>
            <path d="M103 130C103 130 78 139 78 155C78 166 88.5 174 103 178C117.5 174 128 166 128 155C128 139 103 130 103 130Z" stroke="white" stroke-width="5.4" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M92 155L99 162L115 147" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"></path>
          </svg>
        </div>
        <h4>Required by most journals. Done in 60 seconds.</h4>
      </div>
      <p class="svc-desc">Our editorial team built this generator from COPE, ICMJE, and leading publisher guidelines — so your <a href="https://www.enago.com/ai-disclosure-statement-generator" data-internallinksmanager029f6b8e52c="58" title="AI Disclosure" target="_blank" rel="noopener">AI disclosure</a> is fully compliant and authored with human care.</p>
      <a href="https://www.enago.com/ai-disclosure-statement-generator" class="svc-btn" target="_blank">Generate Statement Free →</a>
    </div>
  </div>
    
<p>Many delays happen not because the manuscript “looks wrong,” but because required declarations are missing. Conflict of interest disclosure is a common requirement across journals and is often supported by standardized forms (for example, the <a href="https://www.icmje.org/disclosure-of-interest/">ICMJE disclosure form</a> is widely used in medical publishing).</p>
<p>Similarly, data sharing and data availability expectations are increasingly common across fields, and publishers often require a data availability statement when applicable (even if the dataset is restricted or available on request). A useful starting point for data availability norms is the <a href="https://www.cos.io/">Center for Open Science</a>’s guidance and resources around open research practices.</p>
<h2><strong>What “Format-Free” Typically Relaxes (and How Far Authors Can Safely Go)</strong></h2>
<p><strong>Reference style:</strong> Any consistent style is often acceptable at first submission.</p>
<p><strong>File packaging:</strong> Many journals accept a single combined file for initial review.</p>
<p><strong>Layout details:</strong> Strict template adherence is often deferred until revision/acceptance.</p>
<h2><strong>How to Submit an Academic Manuscript Under Format-Free Rules Without Getting Stuck at Screening</strong></h2>
<h3><strong>Step-by-Step Workflow That Survives the Technical Check</strong></h3>
<ol>
<li>Confirm the journal truly offers format-free submission</li>
<li>Choose one citation system and keep it consistent</li>
<li>Prepare a complete “metadata pack” before opening the submission portal</li>
<li>Include all mandatory sections and required statements</li>
<li>Keep figures and tables review-friendly</li>
<li>Use the cover letter strategically (even if optional)</li>
</ol>
<h2><strong>Common Mistakes That Still Cause “Format-Free” Submissions to Be Returned</strong></h2>
<ul>
<li>Inconsistent citation behavior</li>
<li>Missing required declarations</li>
<li>Incomplete author metadata</li>
<li>Poor figure legibility</li>
<li>Non-compliant file uploads</li>
</ul>
<h2><strong>A Practical Pre-Submission Checklist for Format-Free Submission Journals</strong></h2>
<ul>
<li>Confirm the journal offers <em>format-free submission</em> for initial submission.</li>
<li>Ensure the research manuscript is complete.</li>
<li>Use one citation approach consistently.</li>
<li>Prepare complete portal metadata.</li>
<li>Add required declarations.</li>
<li>Confirm figure and table readability.</li>
</ul>
<h2><strong>Conclusion: Efficiency Without Compromising Excellence</strong></h2>
<p>While &#8220;format-free&#8221; submission significantly reduces the time spent on cosmetic adjustments, the responsibility for scientific rigor and policy compliance remains with the author. A manuscript that is internally consistent and metadata-complete will always move through the technical check faster than one treated with an &#8220;anything goes&#8221; approach.</p>
<ul>
<li><strong>Target the Right Venue:</strong> <a href="https://www.enago.com/publication-support-services/journal-selection">Journal Selection</a></li>
<li><strong>Audit Your Submission:</strong> <a href="https://www.reports.enago.com/reports/technical-check-report">Technical Check Report</a></li>
<li><strong>Polished Presentation:</strong> <a href="https://www.enago.com/publication-support-services/manuscript-formatting">Manuscript Formatting</a></li>
<li><strong>End-to-End Handling:</strong> <a href="https://www.enago.com/publication-support-services/journal-submission">Journal Submission</a></li>
<li><strong>The Total Solution:</strong> <a href="https://www.enago.com/publication-support-services/premium-package">Premium Package</a></li>
</ul>
<p>By balancing publisher flexibility with professional oversight, you can focus on your next discovery while we ensure your current one reaches the reviewers without delay.</p>
<p>The post <a href="https://www.enago.com/articles/format-free-submission-guide/">The Reality Of “Format-Free Submission: What Authors Actually Need To Prepare</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.enago.com/articles/format-free-submission-guide/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Surviving the Cascade: How to Navigate Publisher Transfer Desks (and Make a Smarter Manuscript Submission Decision)</title>
		<link>https://www.enago.com/articles/journal-manuscript-transfer-guide/</link>
					<comments>https://www.enago.com/articles/journal-manuscript-transfer-guide/#respond</comments>
		
		<dc:creator><![CDATA[Roger Watson]]></dc:creator>
		<pubDate>Wed, 11 Feb 2026 07:33:38 +0000</pubDate>
				<category><![CDATA[Submission Requirements]]></category>
		<guid isPermaLink="false">https://www.enago.com/academy/?p=57469</guid>

					<description><![CDATA[<p>A fast “rejected for scope” decision can feel like a dead end especially when the editor adds a crucial qualifier: the work appears sound, but it does not fit the journal. Increasingly, that message is paired with an option to transfer the manuscript through a cascade system (often routed via a transfer desk), which can [&#8230;]</p>
<p>The post <a href="https://www.enago.com/articles/journal-manuscript-transfer-guide/">Surviving the Cascade: How to Navigate Publisher Transfer Desks (and Make a Smarter Manuscript Submission Decision)</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A fast “rejected for scope” decision can feel like a dead end especially when the editor adds a crucial qualifier: the work appears sound, but it does not fit the journal. Increasingly, that message is paired with an option to transfer the manuscript through a cascade system (often routed via a transfer desk), which can move submission files, metadata, and sometimes peer-review reports to another journal within the same publishing portfolio.</p>
<p><a href="https://www.springernature.com/gp/authors/transferdesk">Springer Nature’s Transfer Desk</a>,<br />
<a href="https://www.elsevier.com/en-in/researcher/author/submit-your-paper/submit-and-revise/article-transfer-service">Elsevier’s Article Transfer Service</a>, and<br />
<a href="https://authorservices.wiley.com/author-resources/Journal-Authors/submission-peer-review/manuscript-transfer.html">Wiley’s journal transfer workflows</a> are well-known examples of this <a href="https://www.enago.com/submission-preparation.htm" data-internallinksmanager029f6b8e52c="34" title="manuscript submission" target="_blank" rel="noopener">manuscript submission</a> process design.</p>
<p>For researchers, the real question is not whether a transfer desk is “good” or “bad,” but whether accepting the transfer is the most strategic path or whether withdrawing and submitting to a competitor will better protect time and publication goals. This article explains what a publisher cascade transfer desk is, when it helps, and how to decide quickly without losing momentum.</p>
<h2><strong>What a Publisher Transfer Desk Actually Does (and What It Does Not)</strong></h2>
<p>A transfer desk is a centralized journal publishing service run by a publisher to redirect manuscripts that are unsuitable for a specific journal but still potentially publishable elsewhere in the publisher’s network.</p>
<h3><strong>The Promise: Efficiency</strong></h3>
<p>Instead of starting over, authors can transfer:</p>
<ul>
<li><strong>Submission Files &amp; Metadata:</strong> Title, authorship, affiliations, and keywords.</li>
<li><strong>Administrative Details:</strong> Disclosures, suggested reviewers, and original submission dates.</li>
<li><strong><a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">Peer Review</a> Reports:</strong> In some cases, existing reviews can be carried over to accelerate the next decision.</li>
</ul>
<h3><strong>The Reality: No Guarantees</strong></h3>
<p>A transfer desk does not guarantee:</p>
<ul>
<li><strong>Acceptance:</strong> The receiving journal conducts its own fresh editorial assessment.</li>
<li><strong>Faster Review:</strong> Timelines still depend on the new journal’s specific backlog.</li>
<li><strong>Identical Standards:</strong> Every journal is editorially independent.</li>
</ul>
<p><strong>Practical Tip:</strong> Treat a transfer offer as a signal that your work is publishable, but keep in mind that the publisher is reducing <em>process friction</em>, not necessarily lowering the bar for acceptance.</p>
<h2><strong>Why “Rejected for Scope” Happens Even When the Work Is Strong</strong></h2>
<p>Scope rejection is often about fit, not quality. A manuscript might be methodologically rigorous but misaligned with a journal’s:</p>
<ul>
<li>Aims and readership.</li>
<li>Specific article types (e.g., a paper is too long for a &#8220;Brief Communication&#8221; venue).</li>
<li>Novelty threshold or editorial priorities.</li>
</ul>
<p>Cascade transfers are valuable here because they preserve momentum when the issue is mismatched positioning. However, if the rejection letter mentions deeper concerns such as weak framing or insufficient validation a transfer might just move the paper toward another rejection later on.</p>
<h2><strong>What Changes After a Cascade Transfer and What Can Be Reused</strong></h2>
<table>
<thead>
<tr>
<td><strong>Feature</strong></td>
<td><strong>Typical Status after Transfer</strong></td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Metadata</strong></td>
<td>Seamlessly moved to the new journal&#8217;s system.</td>
</tr>
<tr>
<td><strong>Reviewer Reports</strong></td>
<td>Policy-dependent; Wiley and Nature often allow portable reviews if reviewers consent.</td>
</tr>
<tr>
<td><strong>Ethics/Consent</strong></td>
<td><a href="https://publicationethics.org/">COPE guidance</a> highlights that reviewer permission is often required to move reports.</td>
</tr>
<tr>
<td><strong>Submission Date</strong></td>
<td>Some journals preserve the original submission date for &#8220;priority&#8221; purposes, but most reset the clock.</td>
</tr>
</tbody>
</table>
<h2><strong>When Accepting a Transfer Desk Offer Is Usually the Better Move</strong></h2>
<ul>
<li><strong>Speed is the Priority:</strong> If the work is sound and the editorial letter explicitly states it is a scope issue, the transfer desk can save you days of re-formatting and data entry.</li>
<li><strong>Portable Reviews:</strong> If the original journal already conducted a review and those reports move with the paper, the receiving editor might make a &#8220;fast-track&#8221; decision without a full new round of reviewers.</li>
<li><strong>Goal Alignment:</strong> If the suggested journals match your needs for <strong>Open Access</strong>, indexing (Scopus/Web of Science), or specific funder mandates.</li>
<li><strong>Early Career Efficiency:</strong> For PhD students or postdocs, the reduced administrative burden helps maintain research productivity across multiple projects.</li>
</ul>
<h2><strong>When Withdrawing and Submitting Elsewhere Is the Smarter Strategy</strong></h2>
<ol>
<li><strong>Journal Fit Uncertainty:</strong> Sometimes transfer &#8220;recommendations&#8221; are AI-generated or include journals only loosely connected to your field. If the new audience won&#8217;t cite or read your work, decline the transfer.</li>
<li><strong>Pricing and Licensing:</strong> Many cascade pathways lead to Open Access journals with high Article Processing Charges (APCs<strong>)</strong>. Check the costs before clicking &#8220;Accept.&#8221;</li>
<li><strong>Competitive Repositioning:</strong> A scope rejection might be a sign that you need to reframe the paper for a different discipline entirely, rather than just moving to a &#8220;smaller&#8221; journal under the same publisher.</li>
<li><strong>Major Revision Needed:</strong> If the feedback was critical, rushing into a transfer without fixing the core issues usually results in a second desk rejection.</li>
</ol>
<h2><strong>What to Check Before Clicking “Transfer”: A Decision Framework</strong></h2>
    <div class="svc">
    <div class="svc-body">
      <div class="svc-cat">Research Impact</div>
      <div class="svc-row">
        <div class="svc-ic">
          <svg viewBox="0 0 200 200" fill="none" xmlns="http://www.w3.org/2000/svg">
            <path d="M16.6304 20.6889V16.6306H20.6886" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M29.02 16.6307H175.117" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M179.284 16.6307H183.342V20.689" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M183.34 29.0201V175.117" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M183.342 179.284V183.342H179.284" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M170.948 183.34H24.8511" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M20.6886 183.342H16.6304V179.284" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M16.6304 170.948V24.8514" stroke="white" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"></path>
            <path d="M160.754 50.0011H38.2476C36.462 50.0011 35.001 51.4582 35.001 53.2391V146.763C35.001 148.544 36.462 150.001 38.2476 150.001H160.754C162.54 150.001 164.001 148.544 164.001 146.763V53.2391C164.001 51.4582 162.54 50.0011 160.754 50.0011Z" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
            <path d="M188.777 8.0011H178.225C176.444 8.0011 175.001 9.44686 175.001 11.2303V21.7719C175.001 23.5553 176.444 25.0011 178.225 25.0011H188.777C190.557 25.0011 192.001 23.5553 192.001 21.7719V11.2303C192.001 9.44686 190.557 8.0011 188.777 8.0011Z" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
            <path d="M188.777 175.001H178.225C176.444 175.001 175.001 176.445 175.001 178.225V188.777C175.001 190.558 176.444 192.001 178.225 192.001H188.777C190.557 192.001 192.001 190.558 192.001 188.777V178.225C192.001 176.445 190.557 175.001 188.777 175.001Z" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
            <path d="M21.7768 8.0011H11.2251C9.44447 8.0011 8.00098 9.44686 8.00098 11.2303V21.7719C8.00098 23.5553 9.44447 25.0011 11.2251 25.0011H21.7768C23.5575 25.0011 25.001 23.5553 25.001 21.7719V11.2303C25.001 9.44686 23.5575 8.0011 21.7768 8.0011Z" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
            <path d="M21.7768 175.001H11.2251C9.44447 175.001 8.00098 176.445 8.00098 178.225V188.777C8.00098 190.558 9.44447 192.001 11.2251 192.001H21.7768C23.5575 192.001 25.001 190.558 25.001 188.777V178.225C25.001 176.445 23.5575 175.001 21.7768 175.001Z" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
            <path d="M35.001 145.001L90.6926 81.0011L106.001 101.491" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
            <path d="M164.001 140.788L116.263 86.0011L105.601 101.084L91.001 150.001" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
            <path d="M106.501 79.0011C111.208 79.0011 115.001 75.1803 115.001 70.5011C115.001 65.8219 111.18 62.0011 106.501 62.0011C101.822 62.0011 98.001 65.8219 98.001 70.5011C98.001 75.1803 101.822 79.0011 106.501 79.0011Z" stroke="white" stroke-width="3" stroke-miterlimit="10"></path>
          </svg>
        </div>
        <h4>Turn your findings into a visual that gets cited.</h4>
      </div>
      <p class="svc-desc">Our science communication designers work with you directly to create graphical abstracts that communicate your research to any audience — human expertise meets scientific rigour.</p>
      <a href="https://www.enago.com/research-impact/graphical-abstract" class="svc-btn" target="_blank">Create Your Graphical Abstract →</a>
    </div>
  </div>
    
<ol>
<li><strong>Read the Decision Letter like a Routing Document:</strong> Does it emphasize <em>scope</em> (Accept Transfer) or <em>flaws</em> (Withdraw and Revise)?</li>
<li><strong>Verify the Receiving Journal’s Fit:</strong> Check Aims/Scope, indexing, and turnaround times. Don&#8217;t transfer into a journal that will desk-reject for the same reason.</li>
<li><strong>Confirm APCs and Funder Compliance:</strong> Ensure you aren&#8217;t accidentally agreeing to a fee your grant doesn&#8217;t cover.</li>
<li><strong>Co-author Alignment:</strong> Ensure every co-author is comfortable with the new target journal and any potential costs.</li>
</ol>
<h2><strong>Common Mistakes That Make Cascade Transfers Backfire</strong></h2>
<ul>
<li><strong>The &#8220;One-Click&#8221; Fallacy:</strong> Assuming transfer equals acceptance and skipping due diligence.</li>
<li><strong>Ignoring Formatting:</strong> Most receiving journals still expect you to eventually follow their specific template or word limits.</li>
<li><strong>Failing to Adapt: </strong>Not updating the Cover Letter or Introduction to address the new journal&#8217;s specific audience.</li>
</ul>
<h2><strong>Conclusion: Strategic Control Over Your Publication Path</strong></h2>
<p>When faced with a publisher’s &#8220;cascade transfer&#8221; offer, it is easy to prioritize administrative convenience over long-term research impact. While the technical integration of a transfer desk is seamless, accepting the offer should be a calculated decision rather than a default response. The goal is to ensure your manuscript doesn&#8217;t just find a home, but the <em>right</em> home where it will be read, cited, and valued.</p>
<p>To move beyond the limitations of automated publisher routing, consider a more proactive strategy:</p>
<ul>
<li><strong>Objective Market Evaluation:</strong> If a suggested transfer feels like a step down or a poor fit, <strong><a href="https://www.enago.com/publication-support-services/journal-selection">Enago’s Journal Selection Service</a></strong> provides an unbiased analysis across all major publishers. This ensures you target high-impact venues that align with your specific career goals, rather than staying restricted to a single publisher’s portfolio.</li>
<li><strong>Testing the Waters:</strong> Before committing to a new submission, use <strong><a href="https://www.enago.com/publication-support-services/pre-submission-inquiry-assistance">Pre-submission Inquiry Assistance</a></strong> to gauge interest from alternative high-profile journals. This direct approach can save months of wasted time by confirming interest before you even hit &#8220;submit.&#8221;</li>
<li><strong>Refining the Narrative:</strong> Often, a &#8220;scope&#8221; rejection is a symptom of a manuscript that hasn&#8217;t fully articulated its disciplinary significance. Professional <strong><a href="https://www.enago.com/editing-services">English Editing Services</a></strong> can help reframe your findings and polish the language, ensuring your next attempt whether it’s a transfer or a fresh start meets the rigorous standards of top-tier journals.</li>
</ul>
<p>Ultimately, a transfer desk is just one tool in your kit. By combining publisher efficiency with expert strategic support, you retain full control over your publication timeline and ensure your research receives the prestige it deserves.</p>
<p>The post <a href="https://www.enago.com/articles/journal-manuscript-transfer-guide/">Surviving the Cascade: How to Navigate Publisher Transfer Desks (and Make a Smarter Manuscript Submission Decision)</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.enago.com/articles/journal-manuscript-transfer-guide/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to avoid Intellectual Property conflicts during the submission process</title>
		<link>https://www.enago.com/articles/avoid-ip-conflicts-journal-submission/</link>
					<comments>https://www.enago.com/articles/avoid-ip-conflicts-journal-submission/#respond</comments>
		
		<dc:creator><![CDATA[Roger Watson]]></dc:creator>
		<pubDate>Tue, 25 Nov 2025 07:16:21 +0000</pubDate>
				<category><![CDATA[Submission Requirements]]></category>
		<guid isPermaLink="false">https://www.enago.com/academy/?p=56939</guid>

					<description><![CDATA[<p>A surprising proportion of submitted manuscripts trigger intellectual property (IP) concerns during journal screening: a case-study analysis of 400 consecutive submissions found unacceptable levels of plagiarized material in 17% of papers. At the same time, publishers and screening services are scanning millions of manuscripts annually. iThenticate now checks millions of documents each year as part [&#8230;]</p>
<p>The post <a href="https://www.enago.com/articles/avoid-ip-conflicts-journal-submission/">How to avoid Intellectual Property conflicts during the submission process</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A surprising proportion of submitted manuscripts trigger intellectual property (IP) concerns during journal screening: a case-study analysis of 400 consecutive submissions found unacceptable levels of plagiarized material in 17% of papers. At the same time, publishers and screening services are scanning millions of manuscripts annually. iThenticate now checks millions of documents each year as part of editorial workflows making early prevention essential.</p>
<p>For researchers, IP conflicts (including plagiarism, undisclosed prior publication, improper use of third‑party material, and authorship disputes) can delay <a href="https://www.enago.com/publication-support-services/peer-review-process" data-internallinksmanager029f6b8e52c="26" title="Peer Review" target="_blank" rel="noopener">peer review</a>, lead to rejection, or result in retraction and reputational damage. This article explains what those conflicts are, when they typically arise, why they matter, and most important how you can avoid them at the submission stage. You will find a practical pre‑submission checklist, permission and licensing guidance, recommended tools and institutional actions, plus actionable tips for common mistakes.</p>
<h2>What intellectual property conflicts mean</h2>
<ul>
<li>Intellectual property (IP) is the set of legal rights that protect creations of the mind for academic authors this mainly includes <em>copyright</em> in written text, figures, and datasets, and (in some contexts) patents and trade secrets.</li>
<li>Common IP conflicts in <a href="https://www.enago.com/submission-preparation.htm" data-internallinksmanager029f6b8e52c="34" title="manuscript submission" target="_blank" rel="noopener">manuscript submission</a> include:
<ul>
<li><em>Plagiarism</em> and <em>text recycling</em> (self‑plagiarism).</li>
<li>Use of <em>third‑party copyrighted material</em> (figures, tables, long text excerpts) without permission.</li>
<li><em>Undisclosed prior publication or dual submission</em>, including unclear preprint handling.</li>
<li><em>Authorship disputes</em> and disagreements over contributorship or ownership of data.</li>
<li><em>Undeclared competing interests</em> that bear on IP or commercialization claims.</li>
</ul>
</li>
</ul>
<h2>Why these conflicts occur</h2>
<ul>
<li>When multiple collaborators contribute without clear documentation, authorship and ownership become ambiguous. Journals increasingly ask for explicit contribution statements to reduce disputes.</li>
<li>When language is reused across versions (conference paper → preprint → journal article) without citation or disclosure, editors may treat text recycling as unethical duplication. Preprint policies vary by publisher; some accept preprints but expect transparency about licensing and versioning.</li>
<li>When authors include images, tables, or reproduced material without securing permissions, the publisher or a rights holder can raise a claim that halts publication or triggers legal action.</li>
<li>Plagiarism often results from poor note‑taking, translation issues, or misunderstanding of citation norms; detection rates in submissions are nontrivial. Proactive screening and revision reduce risk.</li>
</ul>
<h2>How is IP during submission different from general IP concerns</h2>
<ul>
<li>Submission IP checks are narrowly focused on originality, attribution, licensing of included material, and prior dissemination; they are not full legal IP audits. The aim is to ensure ethical publication and avoid infringement prior to formal acceptance. Publishers use policies and screening tools to identify problems early, not to adjudicate complex ownership disputes (which may be referred to institutions).</li>
</ul>
<h2>Practical steps to avoid IP conflicts</h2>
<!-- INLINE SERVICE CARD: Plagiarism Checker -->
 <div class="svc">
    <div class="svc-body">
      <span class="svc-cat">
        Research Integrity <span class="svc-free">Free</span>
      </span>
      <div class="svc-row">
        <div class="svc-ic">
          <svg viewBox="0 0 200 200" fill="none" xmlns="http://www.w3.org/2000/svg">
            <g clip-path="url(#cp-plag-inline)">
              <path d="M140.26 34.7119H35.7568V39.9202H140.26V34.7119Z" fill="white"></path>
              <path d="M82.7998 56.3525H35.7568V61.5609H82.7998V56.3525Z" fill="white"></path>
              <path d="M66.8388 77.9932H35.7568V83.2015H66.8388V77.9932Z" fill="white"></path>
              <path d="M163.778 180.88V195.262H155.411H20.5653H12.1983V4.7379H20.5653H155.411H163.778V128.595H168.011V0H155.411H20.5653H7.99805V200H20.5653H155.411H168.011V180.88H163.778Z" fill="white"></path>
              <path d="M142.756 99.0334C138.521 95.029 134.41 90.706 129.718 87.4296C120.459 80.9679 110.327 78.1465 99.4068 81.2864C88.3203 84.4718 79.5175 91.5706 72.002 100.854V102.446H75.8635C77.3999 104.267 79.2684 106.724 81.4276 108.908C87.5729 115.142 94.9639 118.692 103.227 119.966C103.601 120.011 111.49 120.011 111.947 119.966C118.133 119.42 124.03 117.509 129.054 113.595C133.372 110.228 137.234 106.132 141.428 102.264H144.002C143.587 101.172 143.462 99.716 142.715 99.0334H142.756ZM107.711 115.643C95.9189 115.643 86.6179 109.818 79.7667 99.3065C96.6248 80.1033 117.677 78.9201 136.32 99.2155C129.386 110.137 119.711 115.643 107.711 115.688V115.643Z" fill="white"></path>
              <path d="M107.601 92.0023C103.648 92.0472 100.184 95.5428 100.007 99.7106C99.8289 104.237 103.293 107.912 107.867 108.002C112.175 108.046 115.817 104.685 115.994 100.383C116.172 95.8565 112.219 91.9575 107.556 92.0023H107.601ZM107.956 105.671C104.714 105.626 102.227 103.027 102.36 99.8003C102.494 96.8424 104.936 94.3776 107.734 94.3327C111.02 94.3327 113.818 97.0665 113.729 100.293C113.596 103.341 111.02 105.761 107.956 105.671Z" fill="white"></path>
              <path d="M185.519 165.491L148.322 128.293C154.504 120.06 158.201 109.845 158.201 98.7903C158.201 71.5725 136.057 49.4287 108.839 49.4287C81.6214 49.4287 59.4775 71.5725 59.4775 98.7903C59.4775 126.008 81.6214 148.152 108.839 148.152C119.894 148.152 130.076 144.456 138.342 138.273L175.539 175.47L185.519 165.491ZM64.2154 98.7903C64.2154 74.1599 84.2423 54.133 108.873 54.133C133.503 54.133 153.53 74.1599 153.53 98.7903C153.53 123.421 133.503 143.448 108.873 143.448C84.2423 143.448 64.2154 123.421 64.2154 98.7903ZM143.08 134.274C143.517 133.871 143.92 133.468 144.323 133.031C144.659 132.661 145.029 132.359 145.365 131.989L178.866 165.491L175.539 168.817L142.038 135.316C142.408 134.98 142.71 134.61 143.08 134.274Z" fill="white"></path>
            </g>
            <defs><clipPath id="cp-plag-inline"><rect width="177.52" height="200" fill="white" transform="translate(7.99805)"></rect></clipPath></defs>
          </svg>
        </div>
        <h4>Submit with complete integrity — every time.</h4>
      </div>
      <p class="svc-desc">Checked against 91 billion web pages and 82 million published works. Every result is reviewed by our expert editorial team, not just generated by an algorithm.</p>
      <a href="https://www.enago.com/plagiarism-checker/" class="svc-btn" target="_blank">Check for Plagiarism Free →</a>
    </div>
  </div>
    
<ol>
<li>Clarify authorship and contributions
<ul>
<li>At project start, agree on roles and update contributors as work changes. Use a contributor taxonomy (e.g., CRediT) and keep a written record. This prevents later disputes and aligns with journal requirements.</li>
</ul>
</li>
<li>Run an originality check before submission
<ul>
<li>Use the same class of tools publishers use (e.g. iThenticate/Turnitin) to detect problematic overlaps and to distinguish legitimate overlaps (methods, standard phrases) from plagiarism. Enago’s <a href="https://www.enago.com/publication-support-services/plagiarism-check">plagiarism check</a> uses iThenticate and provides expert, annotated reports to help you act on flagged sections.</li>
</ul>
</li>
<li>Declare prior dissemination and preprints
<ul>
<li>If the manuscript or substantial parts were posted to a preprint server, state this in the cover letter and manuscript, and follow the target journal’s preprint/licensing rules (some journals accept preprints but may restrict licensing choices). Keep preprint versions updated to link to the accepted article once published.</li>
</ul>
</li>
<li>Secure permissions for third‑party material
<ul>
<li>For figures, long tables, or large text extracts: identify the rights holder early, request written permission (retain records), and include a permissions statement in the submission. If content is under a Creative Commons license, check the exact CC terms before reuse.</li>
</ul>
</li>
<li>Avoid self‑plagiarism
<ul>
<li>If reusing previous material (e.g., methods text), cite the original work and paraphrase; where verbatim reuse is unavoidable, obtain permission or declare it explicitly. Many journals allow limited methods overlap with attribution.</li>
</ul>
</li>
<li>Disclose conflicts of interest and funding
<ul>
<li>Full disclosure of financial and intellectual interests protects you and the journal. If an author has a patent application or commercial relationship related to the topic, disclose it in the cover letter and article.</li>
</ul>
</li>
</ol>
<h2>Permissions, licensing, and copyright transfer: what to know</h2>
<ul>
<li>Copyright transfer agreements (CTAs) and exclusive license agreements differ: a CTA typically assigns copyright to the publisher; an exclusive license lets authors retain copyright while granting publishing rights. Read the agreement carefully and consider whether it limits your ability to reuse your own material (e.g., in a thesis).</li>
<li>For preprints: avoid assigning copyright before formal publication; many publishers advise authors to retain copyright when posting preprints and to prefer no‑reuse licenses on preprint servers unless necessary. Check the journal’s policy before choosing a CC license for preprints.</li>
</ul>
<h2>Tools, institutional resources, and good practices</h2>
<ul>
<li>Use a version control system for manuscripts (track changes, dated drafts) and maintain a source log that records where images/data originated and any permission correspondence.</li>
<li>Use ORCID IDs for all authors to reduce identity confusion and link contributions. Encourage co‑authors to review all submission materials and the cover letter prior to submission.</li>
<li>If flagged by a similarity check, review matches carefully. Context matters: methods or common phrases may be harmless, whereas unattributed ideas or copied text are not. If in doubt, revise and cite or quote properly.</li>
</ul>
<h2>Common mistakes and how to fix them</h2>
<ul>
<li>Mistake: Assuming short copied passages are “too small” to matter.<br />
Fix: Even short unattributed phrases can be flagged; always quote or paraphrase with citation.</li>
<li>Mistake: Uploading a preprint without checking journal policy.<br />
Fix: Declare the preprint at submission and verify license compatibility.</li>
<li>Mistake: Last‑minute author list changes without documented consent.<br />
Fix: Use an authorship change form and obtain written agreement from all authors before submission.</li>
</ul>
<h2>Final practical checklist</h2>
<ul>
<li>Confirm authorship and obtain written consent from all authors.</li>
<li>Run an originality check and address flagged items.</li>
<li>List and attach permissions for any third‑party material.</li>
<li>Declare preprints and related submissions in the cover letter.</li>
<li>Disclose conflicts of interest, funding, and patent/commercial links.</li>
<li>Read the target journal’s CTA/licensing terms before acceptance.</li>
</ul>
<p>By implementing these steps, you reduce the risk of IP conflicts slowing or derailing your manuscript. Aim for transparency, documentation, and early use of the same screening tools publishers use. Enago’s <a href="https://www.enago.com/publication-support-services/premium-package">publication support packages</a> combine subject‑expert <a href="https://www.enago.com/manuscript-editing-services" data-internallinksmanager029f6b8e52c="9" title="Manuscript Editing" target="_blank" rel="noopener">manuscript editing</a> with iThenticate‑powered plagiarism checks and annotated reports, plus guidance on permissions and submission letters. These services can help identify and resolve IP risks before you submit, so you can focus on the science rather than administrative work.</p>
<p>The post <a href="https://www.enago.com/articles/avoid-ip-conflicts-journal-submission/">How to avoid Intellectual Property conflicts during the submission process</a> appeared first on <a href="https://www.enago.com/articles">Enago Articles</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.enago.com/articles/avoid-ip-conflicts-journal-submission/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
