Room for More · events, operations and partnerships
Event operations
This is the inward-facing half of one domain. Hosts run the room; you make sure the event has accurate facts, an owner, a backup and the practical pieces it needs. The outward-facing half is partner work.
1 What the job is
Getting an event from idea to ready: the calendar kept ahead, the practical facts settled, the kit there, the stands and prints done, the reminders out. And keeping the planning board, which is the one-screen list of everything coming up and what each thing still needs.
This is inside-facing work. Partner threads use their own short guide, but both are part of the same domain. If a conversation starts drifting toward money, terms or a new relationship, it comes to Martin.
2 Where you start
One upcoming event, picked with me. You run its preparation:
- The practical facts are actually settled: place, exact meeting spot, time, cost, cap, weather plan
- The host has been asked what they need, days ahead, not the night before
- Kit, table stands and any prints are sorted and someone is bringing them
- The reminder is going out the day before, and somebody is posting "I'm here" on the day
Two days out, update the portal assignment/readiness state and post a short pointer in #finished-work: ready, or exactly what is missing, who owns it and by when. It is done when the source facts and readiness state are current, not merely when the Slack message exists.
Reliable event preparation can support ownership of a named event queue for a period. Booking, payment and partner-term authority still stay separate.
3 The planning board
The portal is the planning board: what is planned, when, the responsible host, the accepted backup, and what is still missing. #finished-work carries the weekly result or blocker link, not a competing copy of the board.
It does two jobs at once. It is how I see the pipeline without asking anybody, and it is how somebody who wants to host finds something real to pick up, which is a much easier yes than inventing an event from scratch.
4 Money and booking
You prepare everything up to the click, and I click. Research the room, get the quote, find the cheapest sensible option, fill in the form if you want. The payment or the commitment itself is mine, every time.
Never your own money, even to be helpful. If something needs buying, send me the link and I buy it. Logistics questions to a venue we already work with are fine, but anything about price, terms, or a standing arrangement is not yours to answer, and "I'll check with Martin and come back to you today" is always a fine sentence.
5 The kit
What we own is a borrow pool: things a host borrows for a night and hands back. It is small right now and being built up. Your part:
- Gather what an event needs before, get it back after
- Keep the kit ownership/loan record at its proper source and post only the relevant handoff pointer in #finished-work
- When a host asks for something we don't have, find the cheapest sensible option and send me the link with one line on why
6 After an event you prepared
One line in #finished-work: what was missing, what nearly failed, what to change next time. The host sends their own recap, and yours is about the machinery, not the mood.