QuQi
REDES SOCIAIS

Conference coverage plan

Use when someone from the team is attending an event and the posting usually amounts to a photo of the stand.

conference-coverage-plan.md
Transferir .md
You are planning social coverage of an event our team is attending. You are not writing a recap after the fact.

Event, dates and location: {{EVENT_DETAILS}}
Who is going and what they are doing there: {{WHO_IS_GOING}}
Why our audience cares about this event: {{AUDIENCE_INTEREST}}
Platforms we will post on: {{PLATFORMS}}
Sessions, people or areas we can actually access: {{ACCESS}}

Output three numbered sections.

1. Before: three posts giving {{AUDIENCE_INTEREST}} something useful without attending, such as what to watch for or a question worth asking on the floor. Write these in full.
2. During: a table with Day | Time slot | What to capture | Who captures it | Platform from {{PLATFORMS}} | Caption angle. Every row must be doable by the people in {{WHO_IS_GOING}} within {{ACCESS}}, on a phone, between other commitments.
3. After: two posts reporting what was actually said, with marked gaps for the specifics we will only have on the day.

Rules:
- No post may be a photo of our stand captioned "Come and say hi".
- Cut anything needing a stranger's permission, a badge we do not hold, or a quiet room, and list what you cut for that reason.
- Do not name speakers or describe session content beyond {{EVENT_DETAILS}}. Where an idea depends on the agenda, write [CHECK AGENDA].

Preencher antes de executar

Substitua cada espaço pelos seus próprios dados. Quanto mais específico for, menos o modelo inventa.

  • {{EVENT_DETAILS}}
  • {{WHO_IS_GOING}}
  • {{AUDIENCE_INTEREST}}
  • {{PLATFORMS}}
  • {{ACCESS}}

Como obter um resultado melhor

  1. Put a named person in every capture row; unassigned rows do not happen on a conference floor.
  2. The before posts do most of the work, because they are the only ones you write calmly.
  3. Paste the public agenda if there is one, otherwise every during row needs checking anyway.