Publishing and delivery

Publishing is the Editorial Manager’s decision on a particular content item. The item must already be Approved, and current rights must cover its intended use. The manager acknowledges the internal delivery event; its timestamp becomes the publication date. The item moves to Published only after those checks. This sequence gives the team a clear published record and avoids treating an approval as if it were delivery.

The publishing workflow closes production tasks genuinely linked to that delivery. A project can have several deliverables moving at different speeds. If one image is published while another still needs editing, the second item’s work must remain open. The Producer and Studio Manager can then review the published content alongside open production work before deciding whether the whole project is ready to be marked Delivered.

• Final state. Published content retains its project, owner, publication date and status.
• Delivery acknowledgement. The Editorial Manager records the internal event that establishes the time of publication.
• Linked task closeout. Only work belonging to the delivered item closes through the publishing action.

Agree who is allowed to acknowledge delivery and what event constitutes the handoff. Decide where the studio sends the final files and how it confirms receipt with the client. The app records the internal attestation; the studio should settle its client communication method as a separate operating choice. Agree how the manager checks rights on the publication day, especially where a contract is near its end date.

Set a practical project closure rule. A project can move through Review to Delivered after the Studio Manager has checked its content, production tasks and cost lines. Published content is evidence of a delivered item; it does not automatically describe every item under the project. Use the published list and the open work list together before closing the client job.

A project has a retouched hero image and several supporting images. The hero image’s file version has passed review, and its agreement covers the planned use today. The Editorial Manager acknowledges delivery of that image and publishes it. The publication date reflects the acknowledged event, and only the production work tied to the hero image closes. The supporting images remain in Review with their tasks still open. The Producer checks the published list against the review queue and gives the Studio Manager a clear account of what the client has received and what remains to be delivered.

• Published Content — Delivered items with project, owner and publication date.
• Open Production Work — Tasks that still need action after a partial delivery.
• Projects In Flight — Client jobs awaiting full delivery review.

Follow review and delivery for the final handoff, then use implementation to rehearse a partial delivery.