1. Publishing House ERP
  2. Features
  3. Publishing projects
Feature · Publishing projects

Publishing projects

Give each title an owner, production dates, budget and a visible status.

OverviewContent Approval Inbox
Publishing House ERP · Publishing projects

Content Approval Inbox

Approval conditions

New
TitleStatusOwnerProjectDue at
Review ci-541ReviewPRJ-514823 Oct
Review ci-878ReviewPRJ-290921 Oct
Review ci-747ReviewPRJ-119220 Oct
Review ci-442ReviewPRJ-832303 Oct
Review ci-871ReviewPRJ-608609 Oct
6 of 6 records
Review ci-541Content items · CI-92605
Review
ProjectPRJ-5148
Due at23 Oct
Example screen with sample data

What you can do

Plan the title

A project is the shared operating record for a title. The Publishing Director sets its owner, start date, due date and budget before the editorial and production teams attach their work. The project status gives the team a common answer about whether work is planned, approved, in production, under review or delivered. A cancelled project stays distinct from completed delivery.

How the work is organized

  • Project owner. Agree who changes the project status and who resolves a due date that no longer fits the planned work.
  • Budget baseline. Agree the amount to record before costs begin, so later cost entries can be read against the same approved scope.
  • Work boundary. Agree which content items and production tasks belong to this project before people begin recording them.

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

Take a new title with an editor assigned to its manuscript. The Publishing Director opens the project and names the project owner. The Managing Editor attaches the content items; the Production Lead attaches tasks. If the release date moves, examine the due dates on the affected work before changing the project date. The team should be able to identify who owns the project, which work is due soon and what costs have been recorded against it. Do not treat a delivered project status as evidence that every content item was published. Review those records independently.

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

  • Project Pipeline — Active publishing projects with their owners, status, dates and budget.
  • Content Items In Production — Content due within the projects still moving through production.

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
Projects
Publishing projects that group content production work
Content items
Individual content units produced within a project
Production tasks
Assigned production work for a project
Project costs
Cost entries booked against a publishing project
People
Staff and contributors of the publishing house

Who uses it

Permissions
Publishing Director
Owns the project decision.
Managing Editor
Links editorial content.
Production Lead
Plans assigned work.
Finance Lead
Reviews the budget and recorded costs.

Set up Publishing House ERP your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started