HockeyStick Knowledge Base Knowledge Base Open Command Centre

Running Activate

Generation, changes and approval

How campaign assets are generated, what happens on failure, requesting changes, and the Story approval rules.

Generation, changes and approval

Once setup has started, the client generates the campaign assets in the workspace, reviews them and approves them. Each asset is either Draft or Approved. Approval does not publish anywhere. It marks the asset as ready for the client to use.

Generation

  • Stories: the client adds interview source material and presses Generate story. Progress runs through "Reading brief and source material", "Drafting Story and companion assets", "Scoring the draft against quality checks" and "Refining and finalising the asset set". This usually takes a few minutes.
  • Social: a LinkedIn post set from the social setup.
  • Webinars: Generate activation kit from the webinar setup.
  • Events: Generate Event draft, then Improve on any section.

Generation started through the HockeyStick connector or Slack is queued and retried automatically. A job that runs past its time limit fails permanently. The client then creates the brief again or uses the regenerate path. Failures show in Monitoring; see Monitoring agent runs.

When generation fails

The workspace shows the failure with a support reference and a retry button: Retry generation (Story and Social), Retry saved setup (Social), or Repair missing items / Retry kit renders (webinar kit). In the mirror you see the same status, including the support reference, so you can quote it when you escalate.

Changes

  • On a Draft: Regenerate, or Regenerate this section for Stories.
  • On an Approved asset: Request changes. The approved revision stays unchanged, and a new Draft is created from the saved setup plus the client's note.

Story approval rules

Approve story is blocked until all of these are true:

  • The complete Story asset set exists.
  • No [PLACEHOLDER] remains. Generation inserts one wherever the transcript has no evidence. The editor shows "Resolve placeholders before approval" with a link to each one.
  • Source support has been checked for every sentence.
  • The latest generation has a complete, passing QA run, with every QA score at least 4/5.
A short interview produces placeholders. The setup warns when the source is short, because a finished Story needs 800 to 1,000 words. More interview detail is the fix, not more regeneration.

Social approval

The client approves each post with Approve · attach partner link. If the tracked PartnerStack link is not available yet, the option is Approve · mark untracked.