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
- Content production
Content production
Keep owned content and assigned production work moving toward review.
OverviewPublished Content×
Publishing House ERP · Content production
New
Published Content
Content items
| Title | Published at | Project | Owner | |
|---|---|---|---|---|
| Published ci-477 | 22 Oct | PRJ-3877 | ||
| Published ci-690 | 19 Oct | PRJ-5416 | ||
| Published ci-876 | 19 Oct | PRJ-4645 | ||
| Published ci-324 | 27 Oct | PRJ-3824 | ||
| Published ci-746 | 22 Oct | PRJ-7116 |
6 of 6 records
Published ci-477Content items · CI-25300
Published at22 Oct
ProjectPRJ-3877
What you can do
Run the content board
Content items represent the units a project produces. Each item has an owner, content type, due date and status. The Content Items page places these records on a horizontal state board, alongside a chronological list and an inspector for the selected record. The Managing Editor can see what is still in draft, being edited, waiting in review or approved. Production tasks carry the separate assignments needed to make that content ready.
How the work is organized
- Item ownership. Agree who owns a content item when several people contribute to the same title.
- Task handoff. Agree when an assigned task moves into review and who records completion.
- Due date practice. Agree whether a changed project date also requires individual content and task dates to be revised.
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
For a title with cover copy and a chapter extract, create separate content items under the same project and assign each owner. Add the production tasks for editing and preparation with their own due dates. As one task finishes, its status can move through review to completed while the content item remains under editorial review. Check the file version and rights term before the content version is approved. The team should see the next owner and due date in the working lists without treating task completion as publication.
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
- Content Items Board — Content work by status, with the selected item’s owner, project and due date in the inspector.
- Open Production Tasks — Assigned tasks still open, in progress or under review.
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- Content items
- Individual content units produced within a project
- Content files
- Versioned file evidence attached to a content item
- Production tasks
- Assigned production work for a project
- Projects
- Publishing projects that group content production work
- People
- Staff and contributors of the publishing house
Who uses it
Permissions- Managing Editor
- Owns content progress.
- Production Lead
- Assigns and follows tasks.
- Rights Reviewer
- Decides the 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.