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
- Trade publishing
Trade publishing
A trade publisher can use a project for each planned title while the Managing Editor follows submitted manuscripts and content work. Rights Reviewer checks coverage before approving a file version, and Production Lead keeps the edition record connected to the manuscript. The title team can see which work is in review, which tasks remain open and which edition facts are ready for a printer discussion.
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.
A trade publisher can use a project for each planned title while the Managing Editor follows submitted manuscripts and content work. Rights Reviewer checks coverage before approving a file version, and Production Lead keeps the edition record connected to the manuscript. The title team can see which work is in review, which tasks remain open and which edition facts are ready for a printer discussion.
Begin with one seasonal list and a small set of representative titles. Include a new manuscript, a content item in review, an agreement with a current term and an edition record. Set the owner on each project and content item, then rehearse the file version decision. Compare the edition record with the team's print plan and agree who records later corrections.
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.
- Finance Lead
- Maintains project cost entries and reviews budget exposure.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.