Content Pipeline

A content item is the working record for a story, feature, column or advertising content. It holds the title, content type, due date, publication date, owner, project and status. The Editor can inspect the pipeline by status while the Reporter follows the stories assigned to them. Each content item points to the project it serves, so an edition review can focus on its own work.

Start a story as draft. Editing and review make the editorial handoff visible. Approved means the current content revision has passed the relevant checks; published is the result of the publication action. Archived keeps completed material out of the active queue. Use the status names consistently across the desk so a review queue really means work waiting for a decision.

• Ownership. Each content item names a person responsible for its progress.
• Project context. The project link puts a story in the edition, supplement or special section it serves.
• Lifecycle. Draft, editing, review, approved, published and archived distinguish writing, decision and release.

The content item is connected to versioned files and rights agreements. Those records matter at approval and publication. A changed file or expired agreement can invalidate a previous decision even if the story title has stayed the same. The Editor reviews the exact revision and current rights before publishing.

Decide how reporters identify content types and how they name stories that may be revised during production. Set due dates that precede the final edition deadline. Agree who moves a story into review and who resolves an item returned for more editing. Give every story a real owner and project before it enters the review queue.

For advertising content, use the same content lifecycle only when the desk will actually produce and review that material here. A commercial booking process should be connected separately if the team requires booking orders or customer billing. This page focuses on the content records and publication decision the app runs.

Create a feature for a weekend supplement, choose its owner and project, then set a due date before layout. Move it from draft through editing into review. Attach the current content file and inspect the linked rights agreement. Have the reviewer approve that revision, then let the Editor publish it. Check the publication date and the related production tasks after the publication action completes.

Repeat the review with a changed file revision. The team should check the new revision rather than rely on an earlier approval. Also inspect a story whose rights coverage ends before publication; the Editor should resolve that agreement before taking the approved-to-published step.

• Content Pipeline — Scan active stories by editorial status, owner and due date.
• Version Log — Inspect the file revision linked to a story in review.
• Rights Register — Check the agreement linked to that story.

Read desk to review, then rights and approval and publication.