Handing things over

1 Where things go

The #finished-work channel in the team Slack is the handoff index. Post the finished result, link or platform ID, who should act next, and any real blocker. One thread per thing.

Some work has another proper home. The portal holds assignments and status. Public event facts come from the current event page. Original event photos go in the approved Shared Drive folder, with only the folder link and consent context in Slack. Technical work goes in its GitHub issue, branch or pull request. Slack points to those records; it does not replace them.

You join by an email invite from me, so there is no link to click here. If you are helping and no invite has arrived, tell me and I will sort it.

If it is urgent, message or call me directly as well: +47 984 41 663. Anything about somebody's safety, call whatever the hour. Everything else can wait for normal waking hours.

2 What "finished" means

Finished means I can read it once and act on it. I would copy-paste it and place it where it should be, whether that is on one of the social media accounts (if you can't post yourself), Meetup, the website, internal documentation and reports, or somewhere else.

The test it should pass: if I would have to come back and ask you a question you could have answered when you first sent it, it is not done yet. It is fine to not be perfect, so don't worry, it's just the test you should remember.

3 Useful handoff shapes

An event you want to run

• What it is, and the complete event description that would sit on Meetup and the website, which would include:
  • Date, start time, end time
  • Where, and the exact spot people meet. Not "the park"
  • What it costs a person, or free
  • Anything that has to be booked or paid for, and roughly what it costs
  • How many people it works for, at most
  • What happens if the weather turns, or if it is indoors, what happens if the room falls through
  • A photo or poster. You can generate it with AI, ask me to do it, or make it yourself without AI if you want
• All information an event would logically need. If it would bloat the event description, send it alongside as extra information

That list is for an event that is ready to publish. A raw idea needs none of it, just tell me the idea.

A recap of an event that happened

• Preferably within 24 hours, while you still remember it:
  • The mood
  • How many showed up, roughly
  • What they bought or did
  • How much of a success you would consider it
  • Any notes or thoughts you have about it
  • A link to the approved Drive folder, who took the images, and whether consent to take was asked. Do not attach identifiable originals in Slack

A finished post ready to publish

• The text exactly as it should go out, and the image if there is one
• One line on top: which channel and which account it is for, and when it should go up. That line is what lets whoever posts it paste it straight out
• Who presses post, you or me. If you have access to post it yourself, do that instead and say "done"
• The link: the event's own page on roomformore.no, unless the post is on Meetup itself

A message to a venue or a partner

• Who it is going to, and what we already agreed with them, if anything
• The draft, written as you would send it
• What you want back from them, in one line
• When you would chase if nothing comes
• Any other relevant thoughts or notes

Something that went wrong, or somebody who needs looking at

• Do not use #finished-work or any Slack channel for report contents or names
• Urgent safety matters go to Martin by phone; a Slack message may say only "call me"
• If you are the assigned moderator, send the minimum factual written handoff to safety@roomformore.no; it currently reaches Martin and is not an independent route
• Do not keep your own report file or investigate after the immediate handoff

A kit request

• What you need, and for which event and date
• Whether it should be bought or borrowed, if you know
• Roughly what it costs, if buying. Never buy it yourself, that goes through me

A status update needs no shape at all, just say where the thing stands and what happens next.

A technical contribution, once that route is open

The separate contribution workspace does not exist yet, so this is a future handoff shape rather than a task available today.

• The GitHub issue, branch or pull-request link
• What changed and which acceptance criteria are met
• Checks run, privacy/security effect, and anything the reviewer still needs to decide
• No credentials, production data or private-vault material in Slack or the contribution

4 A shape you can paste

5 What happens after you send it

The named owner or backup picks it up. If the task is yours to publish or close, do that and say "done" with the link. If a whole day passes and the result is time-sensitive, contact the owner directly. Safety is immediate and uses the phone/incident route.

Good work can support a more independent assignment in that same area. Access is still granted separately for the next task and never follows from a general trust status.

6 Things that never go out without me

7 Two things about timing

Nobody here is on call. If a message sits until tomorrow that is normal, and you never owe me an answer at a particular time of day.

The one exception is anything about somebody's safety, which gets dealt with the same evening. If you cannot deal with it, hand it to me at any hour.