03 · After

Wrapping up.

The thing most hosts forget is also the thing that turns one event into a regular thing.

Send a thank-you within a day or two.

The platform doesn't send this for you. Open the management page, export the RSVP list, paste it into your email client, send something short. Mention one specific moment from the night, not a generic “thanks for coming”.

This is the message that decides whether they say yes the next time you run something.

Recurring events take five minutes, not five again.

There's no “duplicate event” button yet. To run the same gathering again, create a new event and re-enter the details. The second event takes about a third the time of the first.

If you have a regular thing (a fortnightly run, a monthly book club), publish two or three at a time. The platform doesn't care; people prefer it.

A photo of how it actually went.

If you took a real photo at the event, upload it to the next instance as the cover. People who came see themselves. People who didn't see something real. Stock photos read as stock; phone photos read as evidence.

Get the contact list out before you delete the event.

Once you delete the event, the registrations go with it. There's no recovery. If you turned on Collect emails in the event options, the management panel has a CSV download for everyone who opted in. Pull it before you clean up.

If you're running a regular thing, consider an organisation page for the group itself. It gives the kaupapa a public address that lives longer than any one event.

Build the next thing on what you saw.

If half the people stayed an hour past the end, your next event probably wants more time. If a quarter of RSVPs didn't show, your next event probably wants a smaller venue. The platform won't tell you any of this. The list will.