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
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].
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
When do I run this rather than writing a recap afterwards?
Before the event. A recap written on the train home is the usual output and it competes with every other recap that week. This plans the before and during posting, and the before posts do most of the work because they are the only ones you write calmly with a keyboard.
What do I need in front of me?
Event details, who is going and what they are doing there, why your audience cares, the platforms, and an honest account of what you can access. Paste the public agenda if one exists. Without it, every during row carries a [CHECK AGENDA] marker and needs verifying against the schedule anyway.
What comes back, and what should I read closely?
Three pre-event posts written in full, a capture table with a named person per row, and two reporting posts with gaps marked for what you will only have on the day. Read the cut list: it names what it dropped for needing a badge you do not hold or a stranger's permission.
What is the mistake?
Leaving a capture row unassigned. Rows without a name do not happen on a conference floor, where everyone is between commitments and nobody opens a spreadsheet. The second one is filling the marked gaps in the after posts from memory rather than from notes taken while the session was running.