Deliveries

Managing creator deliverables and approval status

Organize content requirements, deadlines, review states, versions, notifications, and publication dates for a collaboration.

A deliverable is one agreed piece of work inside a collaboration. Use deliverables to make the scope observable: each item can have a platform, due date, requirements, review status, version history, notification context, and publication date.

Track a deliverable

  1. 1Create a delivery from the collaboration and describe the content, platform, due date, and client requirements.
  2. 2Move the item through planned, in progress, review, approved, revision requested, published, or cancelled as the work changes.
  3. 3Save new client requirements as a new version when the scope changes instead of overwriting the earlier agreement.
  4. 4Use the review and notification state to keep the creator and brand aligned on the next action.
  5. 5Confirm the publication date and final status after the content goes live.

When to create a new requirement version

  • The brand changes the required hook, format, platform, or call to action.
  • The number of revisions or included assets changes.
  • Usage, approval, or publication requirements change after the original brief.
  • A new version is needed to preserve the original request and explain the change summary.

Frequently asked questions

Does publishing a deliverable change its publication date?

The first transition into Published records the publication date. Later status changes do not erase that original publication timestamp.

Can older requirement versions be edited?

Older versions are retained as history. To make a change, create a new version from the current requirement so the history remains clear.

Related guides