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
- Process
- Content to approval
Content to approval
This process gives the team a shared handoff for a title. Start with an actual manuscript or project and let each named person find the records they must act on. The status on one record does not stand in for a decision on another.
Step by step
-
Prepare content Managing Editor
Managing Editor opens a content item under a project with an owner and due date.
- Managing Editor opens a content item under a project with an owner and due date
- Updates Content items, Projects, People
-
Assign production Production Lead
Production Lead assigns tasks for the project and follows open work.
- Production Lead assigns tasks for the project and follows open work
- Updates Production tasks, Projects, People
-
Upload version Production Lead
Production Lead attaches the versioned file to the content item.
- Production Lead attaches the versioned file to the content item
- Updates Content files, Content items
-
Review item Managing Editor
Managing Editor places the content item in review for a version decision.
- Managing Editor places the content item in review for a version decision
- Updates Content items, Content files
-
Approve content version Rights Reviewer
Rights Reviewer checks current rights and approves the selected file version.
- Rights Reviewer checks current rights and approves the selected file version. *Human gate.*
- Updates Rights agreements, Content files, Content items, People, Approval operations
ApprovalA person approves before the work moves on.
Who does what
Roles and permissions- Managing Editor
- , Production Lead, Rights Reviewer.
- See [roles](/publishing-house-erp/roles) for the working access model.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.