Publishing looks simple from the outside. An author sends a manuscript. An editor reads it. A decision is made. The work moves toward publication or gets declined. Anyone who has worked inside a publishing process knows the real workflow is not that clean.
A publisher may receive manuscripts from email, submission forms, academic contributors, agents, returning authors, and direct referrals. One author sends a Word document. Another sends a PDF. A third sends a revised file with no version number. Then an editor replies from a different email thread, a reviewer adds comments, and someone else asks whether the contract was already sent.
I have seen this problem happen in small publishing teams, journal teams, and content-driven organizations. The issue is not always volume. Sometimes the problem is that the author, manuscript, notes, files, communication, and next steps are not stored in one clear system. When the workflow lives across inboxes, spreadsheets, shared folders, and memory, even a good team can lose track.
This matters more now because publishing activity keeps growing. According to Publishers Weekly, Bowker data showed that U.S. ISBN-registered book output topped 4 million titles in 2025, with self-published works driving much of that growth. More authors means more submissions, more revisions, more follow-ups, and more pressure on publishers to stay organized.
Why Author Submissions Become Hard to Manage
Most publishing teams do not lose manuscripts because they are careless. They lose track because the submission process grows in small steps. At first, one spreadsheet is enough. Then a second editor joins. Then authors start sending revisions. Then a reviewer asks for access to old notes. Then someone needs to check whether the author already signed an agreement.
The real problem is separation. The manuscript file is in one place. The author’s email is in another place. The revision request is inside a thread with a vague subject line. The contract may sit in a folder with no connection to the manuscript record. That makes the team spend too much time searching instead of reviewing, editing, and communicating.
In academic publishing, this problem can become even more serious. Peer review already takes time. The Publons Global State of Peer Review report found that researchers spend about 68.5 million hours reviewing each year, and the average peer review takes 19.1 days. If a publisher already depends on busy editors and reviewers, poor tracking only adds more delay.
What Publishers Should Track for Every Manuscript
A strong author submission process starts with a complete record. I do not mean a complicated database with too many fields. I mean one clear place where an editor can understand the manuscript, the author, the current status, and the next step without searching through several tools.
Every publisher can adjust the fields based on the type of work it accepts. A book publisher may need genre, word count, and contract status. A journal may need research category, reviewer status, and revision round. A digital publisher may need topic, publication date, editor, and content rights.
| Submission Field | What It Tracks | Why It Matters |
|---|---|---|
| Author name | The person who submitted the work | Keeps the manuscript tied to the right contributor |
| Contact details | Email, phone, or preferred contact method | Makes follow-up faster and cleaner |
| Manuscript title | The exact title submitted | Reduces confusion between similar files |
| Category or genre | Subject, book genre, journal field, or topic | Helps route the work to the right editor |
| Submission date | The date the manuscript arrived | Helps measure response time and backlog |
| Current status | New, under review, revision requested, accepted, or rejected | Gives the team a shared view |
| Assigned editor | The person responsible for the next step | Prevents ownership gaps |
| Version number | Original file, revised file, or final file | Stops editors from reviewing old drafts |
| Contract or payment status | Agreement, invoice, or fee stage | Connects editorial work with admin tasks |
| Final decision | Accepted, declined, published, or closed | Creates a useful publishing history |
This table may look basic, but these fields solve many daily problems. When a publisher can see the author, manuscript, status, version, and next action in one place, the team makes fewer mistakes. The process also becomes easier to explain to new editors, assistants, and reviewers.
A Simple Workflow for Managing Author Submissions
I like publishing workflows that people can follow without extra training. A system should not depend on one person remembering every detail. It should show the current state of each manuscript and make the next step clear.
A clean author submission workflow can follow this structure:
| Step | Status | What Happens |
|---|---|---|
| 1 | New submission | The manuscript is received and logged |
| 2 | Initial screening | The team checks fit, formatting, and completeness |
| 3 | Assigned to editor | One editor becomes responsible for the next step |
| 4 | Under review | The editor or reviewer reads the work |
| 5 | Revision requested | The author receives clear notes and a deadline |
| 6 | Waiting on author | The publisher waits for the revised file or missing details |
| 7 | Accepted or rejected | The team records the decision and reason |
| 8 | Contract or production | Accepted work moves into agreement, editing, layout, or upload |
| 9 | Published or closed | The final result is recorded |
The workflow does not need to be complex. The important part is consistency. Every manuscript should have a status. Every status should tell the team who needs to act next. Every action should be logged in the same place where the author and manuscript records live.
This also helps with reporting. A publisher can see how many manuscripts are new, how many are stuck in review, how many are waiting on authors, and how many are ready for production. That kind of view is hard to get from email alone.
Why Spreadsheets Stop Working as Submission Volume Grows
Spreadsheets can be useful when a publishing team is small. I still think they are a good starting point for early organization. The problem is that spreadsheets were not built to manage author relationships, communication history, file versions, reminders, reviewer comments, contracts, and payment notes in one place.
A spreadsheet can show that a manuscript is “under review.” It usually cannot show the full story behind that status. It may not show the author’s past submissions, the last email sent, the latest revision file, or the reason an editor asked for changes. Once a team needs that context, the spreadsheet becomes only one piece of the system.
The risk grows when several people edit the tracker. One person changes a status. Another adds a note in the wrong row. Someone downloads a copy. A filter hides active submissions. After a while, the team stops trusting the sheet and goes back to searching inboxes. That is when delays and duplicate work start to appear.
A good submission system should reduce searching. It should not create another place to check.
Treat Authors Like Long Term Publishing Relationships
A publisher is not only managing documents. It is managing people. Authors may submit more than once. Researchers may send related papers over several years. A book author may come back with a second title. A contributor who was not accepted today may become a strong fit later.
That is why author records matter. A useful author record should show past submissions, contact history, revision notes, agreement details, payment status, preferences, and future opportunities. When that information is connected, the publisher does not have to start from zero every time the same person reaches out.
This is where Smarfle CRM can fit a small publishing workflow in a practical way. A publisher can use client record management software to keep author details, manuscript notes, communication history, and follow-up tasks connected in one place. The word “client” does not have to mean a buyer only. In publishing, that record can represent an author, researcher, contributor, editor, reviewer, or partner.
The benefit is simple. When every author has a clean record, the team can work with more context. Editors can see what happened before. Admin staff can check contract notes. Managers can review open submissions. Authors get clearer replies because the publisher has the right information nearby.
Submission Statuses Every Publisher Should Use
Status labels should be specific. I avoid vague words like “active” or “pending” unless everyone on the team knows exactly what they mean. A good label should explain what is happening and who needs to act next.
| Status | Meaning | Next Action |
|---|---|---|
| New submission | Manuscript received but not reviewed | Screen the submission |
| Screening | Fit, format, and completeness are being checked | Assign or decline |
| Assigned | An editor owns the next step | Begin review |
| Under review | Editorial or peer review is active | Wait for notes or decision |
| Revision requested | Author has been asked to update the manuscript | Track deadline |
| Waiting on author | Publisher needs files, answers, or approval | Follow up if overdue |
| Accepted | Manuscript is approved for the next stage | Start contract or production |
| Rejected | Manuscript will not move forward | Record the reason |
| Contract pending | Agreement or payment step is open | Complete admin work |
| In production | Editing, layout, proofing, or publication work is active | Track production tasks |
| Published | Final work is live, printed, or released | Close or archive |
| Closed | No more action is needed | Keep the record for history |
These labels give structure without making the process heavy. They also help editors communicate with authors in a more professional way. Instead of saying “we are still looking at it,” the team can say the manuscript is in screening, under review, or waiting for the next revision.
How Better Tracking Improves the Author Experience
Authors notice how a publisher communicates. They notice when the team replies with the correct title, references the latest version, and gives clear instructions. They also notice when a publisher asks for the same file twice or cannot explain the current status.
Good tracking creates trust. It gives authors a sense that their work is being handled with care. That matters for independent publishers, academic publishers, and digital publishing teams because contributors often have choices. A clear process can make a small publisher feel more reliable than a larger organization with slower communication.
Digital publishing has also changed author expectations. The STM Open Access Dashboard reports that gold open access grew from 14% of global articles, reviews, and conference papers in 2014 to 40% in 2024. As more publishing activity moves through online systems, authors expect cleaner updates, better records, and less confusion.
My Recommended Setup for a Small Publishing Team
If I were setting up submission tracking for a small publisher, I would keep the system lean. I would create one record for every author and one record for every manuscript. The author record would store contact details, communication history, notes, past submissions, and business details. The manuscript record would store title, category, file link, assigned editor, current status, version, next action, and final decision.
I would also set simple rules. Every manuscript must have one owner. Every open item must have a follow-up date. Every revised file must have a version number. Every decision must be recorded. These rules sound small, but they stop the team from depending on memory.
A weekly review can keep the process clean.
| Weekly Review Question | Why It Helps |
|---|---|
| Which new submissions still need screening? | Stops intake from piling up |
| Which manuscripts have no assigned editor? | Finds ownership gaps |
| Which authors are waiting for a reply? | Protects communication quality |
| Which revisions are overdue? | Keeps manuscripts moving |
| Which accepted works are stuck before production? | Connects decisions to output |
| Which records are missing files or notes? | Keeps the system useful |
| Which closed submissions may be good for future follow-up? | Helps build long term author relationships |
I would not try to build a perfect system on day one. I would start with the fields that matter most, train the team to update them, and review the process every week. The goal is not to add admin work. The goal is to remove confusion.
Final Thoughts
Publishers lose track of manuscripts when the workflow is spread across too many places. The inbox receives the file. The spreadsheet tracks the title. The shared folder stores the draft. The editor keeps notes somewhere else. That setup may work for a short time, but it becomes fragile as submissions grow.
A better process connects the author, manuscript, files, status, notes, communication, and next action. Once those pieces are connected, the team can respond faster, review with more context, and avoid common mistakes. Authors get clearer updates. Editors waste less time searching. Managers can see what is moving and what is stuck.
For small publishers, academic editors, and journal teams, manuscript tracking is not just an internal task. It is part of the publishing experience. A clean system helps a publisher look professional, stay organized, and build better relationships with the authors behind the work.
