November 16, 2026

How to Name and Organize Files for Journal Submission

You are finishing a course paper, a thesis chapter, or your first manuscript, and the draft exists in a folder somewhere. The writing is done. What often still separates a stressful submission from a smooth one is how th

Written byWisPaper TeamAI Research Workflow Team
Editorial illustration for How to Name and Organize Files for Journal Submission

You are finishing a course paper, a thesis chapter, or your first manuscript, and the draft exists in a folder somewhere. The writing is done. What often still separates a stressful submission from a smooth one is how the files around that draft are named, versioned, and arranged. This article gives you a submission-ready file system: a starting diagnosis, a naming scheme, a folder structure, a worked example, and a completion checklist you can reuse for every journal or supervisor review cycle.

The search intent behind this question is practical. Readers are not asking for an abstract theory of file management. They want to know what to call the manuscript, figures, tables, supplementary materials, and response letters, and where each piece should live so an editor, reviewer, or supervisor can open them without guessing.

Where Is Your Current State?

Before renaming anything, identify which of these three situations matches your files.

  • The single-folder draft: Every version is in one place, often with names such as final.docx, final_v2.docx, and final_REAL.docx.
  • The multi-app trail: Manuscript edits in one word processor, figure exports on a desktop, literature notes in a reference manager, and feedback in email attachments.
  • The post-review pile: Reviewer comments in one file, a revised manuscript in another, and a table of changes whose column headings no longer match either.

The fix for all three is the same in principle: make every file findable, make every version traceable, and make the supporting documentation understandable to someone who did not watch the project happen. This matches what the UK Data Service describes for technical preparation for data sharing: organized files, meaningful names, documented versions, open or suitable formats, and supporting documentation so research can be understood and reused. That recommendation was written for data sharing, but the same logic applies when a journal editor receives your submission package.

The FAIR principles point in the same direction. They describe research objects as findable, accessible, interoperable, and reusable, with persistent identifiers, rich metadata, provenance, and clear usage conditions. A manuscript package does not need to satisfy FAIR in the full data-repository sense, but treating the submission bundle like a FAIR object helps: one person should be able to identify each file, understand its role, and trace how the current version came to exist.

What Belongs in a Submission-Ready Name?

A useful filename answers three questions without opening the file: what this is, which project it belongs to, and which version it represents. One reliable pattern is:

ProjectShortName_ContentType_Version

For example:

  • LichenGrowth_Manuscript_v1.4.docx
  • LichenGrowth_Figure3_v2.tiff
  • LichenGrowth_ResponseLetter_v2.docx

Use the same project short name in every related file so the bundle stays coherent even after a reviewer saves individual files to their own desktop. For the content type, choose a small fixed vocabulary: Manuscript, CoverLetter, Figure, Table, Supplementary, ResponseLetter, TrackedChanges. The version field is the most abused part of file names, so give it a rule rather than creative labels.

Version rule: use a two-part number where the integer changes on a structural revision and the decimal changes on a minor edit. A draft sent to a supervisor for comments is v1.0. A fixed typo before another supervisor reads it is v1.1. A substantial rewrite after feedback is v2.0. Never use final, FINAL, or latest; those words stop meaningful sorting and hide which file actually went out.

How Should the Submission Folder Be Structured?

Create one top-level folder per submission event, not one catch-all folder per project. The project name can stay constant while the event gets a date, because submission cycles repeat.

A folder for a first submission might look like this:

LichenGrowth_Submission_2025-01/
├── 01_Manuscript/
├── 02_Figures/
├── 03_Tables/
├── 04_Supplementary/
├── 05_Cover_and_Forms/
└── 06_Working_Files/

For a revision, add a seventh folder for the response materials and the marked-up manuscript:

LichenGrowth_Revision_2025-02/
├── 01_Manuscript/
├── 02_Figures/
├── 03_Tables/
├── 04_Supplementary/
├── 05_Cover_and_Forms/
├── 06_Working_Files/
└── 07_Response_to_Reviewers/

The numbered folders preserve the order in which an editor expects to encounter the content. Keep the final, clean submission package separate from the working files with tracked changes, so the day before the deadline you are not hunting for the one clean PDF.

How Do Reference and Source Files Fit In?

Reference management and manuscript file management are related but should not be merged into one anonymous folder. A reference manager such as Zotero can record the same item in multiple project groupings without duplicating the PDF, and tags can record the topic, method, or workflow status of each item. That gives you a separate, searchable layer for the literature behind the manuscript. The submission folder, by contrast, should contain only what the journal actually receives plus the traced working files that explain how the final version was produced.

If your citation list is built manually or exported from a tool, the submission step is the moment to screen it. Heading into submission with an error in the BibTeX entry can introduce a reference that looks plausible but does not exist in the literature. Running a BibTeX file through a citation checker before generating the final reference list fits naturally at the same checkpoint where you freeze the manuscript version. TrueCite checks BibTeX against real academic databases to flag hallucinated references, which makes it a concrete pre-submission step if any of your references came from AI-assisted drafting or an old, hand-edited .bib file. You can run that screen at WisPaper TrueCite.

Where Does This Fit in a Larger Research Workflow?

The file reset is one checkpoint in a longer pipeline. Earlier stages include collecting papers, organizing them into a library, asking questions over the papers you saved, and planning the next project. Those stages deserve their own spaces so the submission folder does not become a dumping ground for every downloaded PDF.

If you are doing this cleanup because you plan to start a new project in January, a practical order is: first save and organize the papers you already have in My Library, then create a separate workspace for the next research question in Research Projects, and only after that begin new searches. When the next search returns many candidates, WisPaper's scholarly search gives you a focused starting point for academic papers. Keeping the submission archive closed and the new project open prevents the old project's final.docx from contaminating the new project's first draft.

Worked Example: The Winter-Break Reset

A student finished a thesis chapter in December and received supervisor feedback in two annotated files plus several inline email comments. The goal is a clean January revision package.

Before:

  • chapter 3 USE THIS ONE.docx
  • chapter3_new_final (1).docx
  • Chapter 3 supervisor comments.docx
  • figure results final.png
  • Twelve PDFs in a folder called papers

Step 1: Freeze the source of truth. Open the most recent draft the supervisor commented on. Save a new copy as ThermalComfort_Manuscript_v2.0.docx. Do not edit it further in place; further edits become v2.1 and above.

Step 2: Create the event folder. Build ThermalComfort_Revision_2025-01 with the seven numbered subfolders above.

Step 3: Separate submission files from working files. Place the clean manuscript in 01_Manuscript, the exported figures in 02_Figures, and the supervisor's annotated copies in 06_Working_Files. Rename the annotated copies to ThermalComfort_SupervisorComments_v1.docx and ThermalComfort_SupervisorComments_v2.docx.

Step 4: Build the response file. Combine the supervisor comments into ThermalComfort_ResponseLetter_v1.docx with a table: comment number, quoted comment, location in manuscript, action taken, and revised page or section. This is also the structure to reuse later if the chapter becomes a journal submission and a reviewer letter arrives.

Step 5: Screen the bibliography. Export the reference list as BibTeX and check it before freezing the citation list. For a thesis chapter this catches refactoring errors; for a journal version it prevents a nonexistent reference from reaching reviewers.

Step 6: Run the checklist below. The package is ready when every line is satisfied without exceptions.

How Do You Know the Package Is Ready?

This is the completion criteria checklist. A submission package is ready only when all of the following are true.

AreaReadiness check
NamesEvery file uses a consistent project short name and a clear content type.
VersionsNo file is named final, latest, or FINAL; the version reflects the actual revision history.
Folder orderThe submission folders are numbered, and folder 01 contains the clean, unmarked manuscript.
Working traceAll tracked-change and commented files sit in a separate working folder, not beside the clean files.
Figures and tablesEach figure and table is in its own named file with the version matching the manuscript callout.
SupplementarySupporting files have descriptive names and a short readme or index listing what each file is.
ReferencesThe BibTeX or reference list has been screened, and every citation resolves to a real source.
One clean exportYou can open the top folder and hand the entire folder to someone who has never seen the project, and they can identify each piece.

Run this checklist at three moments: before sending a draft to a supervisor, before first submission, and before resubmitting a revision. Reusing it is what makes the second paper faster than the first.

What Is the Next Concrete Action?

Do not reorganize every past project at once. Pick the one manuscript you are submitting or revising next, freeze its current draft, create one event folder using the structure above, and rename only the files that journal or supervisor will actually receive. Then run the readiness table. If the reference list came from a .bib file or AI-assisted drafting, screen it at TrueCite before you send the package. For a broader reset, collect the supporting papers for the next project in My Library and open a fresh workspace in Research Projects so the new January question starts with clean boundaries.

FAQs

Spaces generally work on modern systems, but they create friction when files move through different portals or operating systems. A more reliable habit is to replace spaces inside each filename with underscores or hyphens and keep the same separator across all files in a package. The folder structure can still use human-readable names. The real requirement is consistency, not the choice between underscore and hyphen.