Room for More · comms and content

Comms and content

What happens at an event only exists afterwards if somebody wrote it down or photographed it. That is this job. How your work reaches me is in handing things over.

1 What the job is

Writing recaps of events, taking photos, and sharing things to your own networks. Your own posts reach people the brand accounts never will, so the last one counts for more than it sounds.

You are not running a marketing department.

2 Where you start

The recap. Go to an event you were going to anyway, and preferably within 24 hours post this in the team Slack, channel #finished-work:

Do that twice, and if it has been usable both times, it becomes yours: recaps go out substantially as you wrote them, you post them yourself, and I stop reading them first.

If writing is not your thing, send the rough version and I will shape it. That offer is real. If writing is your thing, I will only touch the facts and the odd comma.

3 Photos

Ask before you take a photo where somebody is recognisable, and if they say no, that is the end of it, no follow-up question. Before anything is published we ask again. That second ask is mine.

Some people genuinely cannot be visible online, for reasons they should not have to explain at a bar, and a photo taken without asking cannot be fixed afterwards.

4 How it reads

Warm, plain, and like a person wrote it. Short paragraphs, one idea each. If a post covers three separate things, give each one a short header in capitals.

Avoid sales language, urgency we do not actually have, and anything that would make somebody who came alone feel like they were the only one.

5 What you can do without asking, once you have done it twice

6 If you own a channel

As the business accounts get set up, each one gets one person responsible for it. If that becomes you:

7 What always gets checked

The first announcement of a new event, and anything carrying a price, date, venue or meeting point that is not already published. This is to make sure the information is right: both times a meeting point has gone wrong here, the mistake was in our own files, not in anybody's draft.

Putting something on the website is separate. That is a technical step on my side, not a permissions thing.