Event campaign For event organisers and marketers who promote an event with posts and e-mails. Steps 9
Checklist items 34
Language English
What it is for
Plan and publish the promotion of an event, from the sources and a brief to checked batches of posts and e-mails.
For event organisers and marketers who promote an event with posts and e-mails.
Steps and what they prove 9
Intake of the event and sources mode (NEW or CONTINUE) was stored in the run context with setContext Event name, date, time zone, place or link, organiser and goal were collected or listed as missing Every source (page, agenda, bios, prices) was listed with its link or pasted text The user saw the intake summary with each fact marked confirmed or missing Event brief (source of truth) Every speaker name, title, date, time, price and link in the brief was compared with the source and mismatches are listed The brief names audience, one-sentence promise, agenda, offer with deadlines, tone and claims to avoid Open questions were listed and each was resolved or accepted by the user The user approved the brief explicitly after seeing it in full Product card and content anchors Each benefit and claim on the card is tied to a brief section and nothing was added from outside the brief Five to eight content anchors exist, each resting on a named brief fact A primary CamelCase hashtag (and at most two supporting tags) and the approved phrases are listed The user approved the card or its requested changes were applied and shown Facebook event description Date, time with zone, place or link and audience appear in the opening lines, matching the brief The text contains value proposition, agenda, verified speakers, price with deadline and one specific call to action with the link Only brief facts are used; logistics answers not in the brief were asked about, not guessed The user approved the title, short version and full text Campaign plan Phases were dated backwards from the event date, and each weekday was checked against the calendar A table lists date, channel, angle, format, CTA and UTM link for every planned item One UTM convention (lowercase, dashes, one campaign name, no internal tags) was written down The user confirmed dates, cadence and channels Content batch Each item has date, channel, angle, caption, visual description, alt text, CTA and UTM link Captions differ by channel and no angle repeats in neighbouring items Every fact in the captions was matched to the brief and nothing was invented, including results in CONTINUE mode The user reviewed the first items and the requested edits were applied Newsletter blocks Each email has subject, preheader, body blocks and one main CTA with a UTM link marked as email medium Subject lines start with the main message and are under about 50 characters; preheaders are 30 to 80 Date, time, place or link, price and deadline in each email match the brief exactly The user approved the sequence or the changes were applied Quality check and log Names, dates, weekdays, prices and links in every item were compared with the brief and the defects found are listed Every link was opened and every UTM link checked against the convention Tone, unsupported claims and accessibility (alt text, hashtags, captions) were checked and defects listed A publication calendar and campaign log with status per item was shown and confirmed by the user Campaign ready The closing summary lists the approved artefacts and the dates of what is still to be written The after-event actions and the way to continue the campaign with mode CONTINUE were told to the user The assistant closes a checklist item only with evidence of what it did, so a finished run shows the work was done, not only claimed.
Use it
Create a free account, connect your assistant and run this workflow in a chat. You come back to this page after signing up.
Use this template
Not sure yet? Watch a demo run first, no account needed.
Already have an account? Sign in