Skip to content

Running a creator collaboration

Recording a piece of work a creator has been engaged for, moving it through its lifecycle, tracking deliverables and reviewing what they submit.

Updated

A collaboration records work a creator has been engaged for: the brief, the dates, the agreed fee, and the deliverables. Its statuses record what your organisation has decided, and none of them claims anything was published or paid.

That distinction runs through the whole surface. Marking a collaboration finished records here that it is finished. Recording a submission records that one happened; nothing opens the link and nothing checks the content is live. Recording an agreement records a commercial commitment; no money moves.

BEFORE YOU START

  • The "create" permission to draft a collaboration, "edit" to manage deliverables, "approve" to review a submission, and "administer" to move the collaboration through its lifecycle.
  • Access to the workspace, and the creator recorded in it.
  • What you actually agreed, since every figure here is one you type.

STEPS

  1. Open Collaborations for the workspace, or go to /app/workspaces/{workspace}/creator-hub/collaborations.
  2. Draft one: choose the creator, give it a title and a brief, and set the dates.
  3. Open it and choose "Record as proposed" when you have put it to the creator.
  4. Choose "Record agreement" when they accept, and enter the currency and the agreed fee in the smallest unit of that currency.
  5. Add deliverables: a title, a kind, a platform and optionally a due date. Without a due date, a deliverable is never described as late.
  6. Record a submission against a deliverable, then review it as approved, changes requested or rejected.
  7. Choose "Record work started" and "Record as finished" as the work moves, or Cancel if it does not happen.

WHAT YOU SHOULD SEE

The collaboration at its recorded status, its deliverables with their review states, and messages that are careful about what they claim: "A submission was recorded for {title}. Nothing checked the link."

WHAT THIS WILL NOT DO

  • It will not pay anybody. There is no payment rail here.
  • It will not check that content went live. A submitted link is a link you were given.
  • It will not accept half a price. "An agreed fee needs both an amount and a currency, or neither. An amount without a currency is not a price."
  • It will not move backwards. Each status has legal successors and nothing else.
  • It will not review a deliverable twice, or review one that has not been submitted.

IF IT DOES NOT WORK

  • "A collaboration at status draft cannot move to completed." means you have skipped a step.
  • "Deliverable {id} was already approved." and "Deliverable {id} is draft; only a submitted deliverable can be reviewed." are the deliverable refusals.
  • "An agreed fee cannot be negative."
  • "This action was refused (...)" is the action gate declining before anything changed. Every lifecycle move passes through it.
  • "administer permission required." and "approve permission required." are the two permission refusals most people meet here.

COMMON QUESTIONS

Why is the fee in minor units?

Because it avoids any rounding argument. Fifteen thousand is one hundred and fifty pounds if the currency is GBP.

Does completing a collaboration report anything?

No. It records that you consider the work finished. Nothing measures what it achieved, because conversions in this product link to a contact and not to a campaign or an offer.

  • Tracking a creator relationship

    Moving a creator through seven recorded stages, what each stage actually means, and why there is no warmth, likelihood or forecast anywhere on the page.

  • Recording creator outreach

    Keeping a record of conversations you had with a creator elsewhere, and the reason there is no send button anywhere on the page.

  • Recording voice consent

    Keeping a record of who agreed to have their voice cloned, for what, and where the evidence is held, plus what happens the moment consent is withdrawn.