These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Publishing House ERP
- Features
- Manuscript review
Manuscript review
Follow a submitted manuscript through an assigned editor and editorial decision.
OverviewManuscript Intake Inbox×
Publishing House ERP · Manuscript review
New
Manuscript Intake Inbox
Review waits for the managing editor
| Title | Author name | Submitted at | Editor | Status | |
|---|---|---|---|---|---|
| Submitted mns-905 | Author 788 | 22 Oct | Submitted | ||
| Submitted mns-826 | Author 359 | 22 Oct | Submitted | ||
| Submitted mns-621 | Author 772 | 19 Oct | Submitted | ||
| Submitted mns-196 | Author 189 | 06 Oct | Submitted | ||
| Submitted mns-698 | Author 986 | 23 Oct | Submitted |
6 of 6 records
Submitted mns-905Manuscripts · MNS-32156
SubmittedAuthor nameAuthor 788
Submitted at22 Oct
What you can do
Review each submission
A manuscript holds its title, author name, submission date, assigned editor and editorial status. These records let the Managing Editor see what arrived and who must make the next judgment. The statuses separate a newly submitted work from a manuscript under review, accepted for further work, rejected, or already moving through editing and production. The editor can focus on the assigned title without losing the original intake date.
How the work is organized
- Editor assignment. Agree who selects the editor and how reassignment is handled when a manuscript changes hands.
- Decision point. Agree who records acceptance or rejection after review and when the next stage may begin.
- Intake convention. Agree how titles and author names are entered so duplicate submissions can be spotted during review.
What to agree during setup
Start with one real title and name the person who is responsible for the record. Decide who can revise dates or statuses, and when a change needs another person’s review. Check each actual project, manuscript, content or person reference before using that record in a handoff. The agreed practice should be visible in the record, not held only in an email thread.
For each handoff, identify the person expected to act next. Check that their user and People record are connected before relying on an approval decision. Keep the source attachment or agreement with the relevant record when the decision depends on it. This makes the working lists useful during a busy production week.
Check the handoff on an actual case
Imagine an author sends a revised manuscript while an earlier submission is already under review. The Managing Editor checks the existing title, author and submission date before adding another record. The assigned editor can then see whether the current work is still submitted, in review or accepted. When the editorial decision is made, record the status on the manuscript and tell the production team which project and content work should follow. A rejected manuscript remains visible as a distinct decision; it should not be counted as production work.
Before expanding to other titles, ask the people named above to walk through this case in the app. They should be able to point to the current record, explain the next decision and find the owner without reconstructing the history from messages.
What your team sees
- Manuscripts Awaiting Review — Submitted and reviewing manuscripts with editor and intake date.
- Manuscripts Review List — Manuscripts in review with the editor responsible for the decision.
Follow the work through
See the related process and the data model for the records behind this handoff.
What it keeps track of
Data model- Manuscripts
- Submitted manuscripts under editorial review
- People
- Staff and contributors of the publishing house
- Print editions
- Print editions and ISBN records for manuscripts
Who uses it
Permissions- Managing Editor
- Coordinates intake and the decision.
- Production Lead
- Follows accepted manuscripts when an edition is prepared.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.