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
- Who it's for
- Academic publishing
Academic publishing
An academic publisher can assign an editor to each manuscript, keep submission and decision statuses visible, and open project and content records for accepted work. The separate manuscript and content statuses help editorial staff distinguish a decision about the submission from the review of a file version. Print editions retain ISBN, edition number and release date beside the manuscript.
How Publishing House ERP is set up for you
Editorial intake
Keep the author name, submission date, editor and manuscript decision together so the next handoff starts from the accepted record.
Production ownership
Give content and tasks separate owners, statuses and due dates under the title project.
Rights decision
Review the agreement term and allowed uses before approving a content file version.
Edition identity
Link the ISBN and edition details to the manuscript that the team actually plans to print.
An academic publisher can assign an editor to each manuscript, keep submission and decision statuses visible, and open project and content records for accepted work. The separate manuscript and content statuses help editorial staff distinguish a decision about the submission from the review of a file version. Print editions retain ISBN, edition number and release date beside the manuscript.
Start with a recently accepted manuscript and an existing project. Enter the editor, content owner and production tasks that reflect the real handoff. Add a rights agreement for the relevant content and test the version approval with the intended reviewer. Agree how editorial staff will distinguish revised submissions and later print editions in the record.
During setup, agree the meaning of project budget and print quantity for this operation. Those entries are useful only when the people preparing and reading them use the same convention. Finance Lead can compare categorized project costs with the recorded budget; Production Lead can identify work still open against the title. A rights agreement and a content version decision remain separate records, so a change in the agreement term should prompt a fresh review before the next approval.
Review the pilot with the people who will change these records every week. Ask each person to find their next task in a working list, open the linked title and explain the decision they are making. Then confirm the next owner sees the result. See [implementation](/publishing-house-erp/implementation) for the staged setup and [data model](/publishing-house-erp/data-model) for the linked records.
Features to start with
Roles on the team
- Publishing Director
- Owns publishing project decisions and reviews the portfolio.
- Managing Editor
- Assigns editors and manages editorial and content progress.
- Production Lead
- Coordinates project tasks, content files and edition records.
- Rights Reviewer
- Checks agreement coverage and decides content version approval.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.