PyMunich

shown, and actual

When It Is Cancelled

Nobody plans for this and it is the scenario that ends organisations. We went through it in 2020, and the useful part is not the story but the order the decisions arrive in — and what it exposed that was already true. For a commercial example of related workforce measurement, see how to identify mouse jigglers among remote teams from Monitask.

One community's experience. Legal treatment of refunds and contracts varies by country; this is not legal advice. For broader conference and speaking context, PCMA is another useful reference.

What actually happened

The event was cancelled after the fixed costs were committed and after tickets had been sold.

We refunded the tickets. That was the correct decision and it was made with money that had partly already been spent — the cash timeline had already put us past the point where the two balance.

We ran out of money. The organisation did not continue in the form it had. The meetups survived, because they need one person and a room, and the conference came back in 2025 as a different event.

The order the decisions arrive in

Faster than anybody expects, and mostly at once.

One. Cancel or postpone. Postponing preserves ticket revenue and defers rather than removes the risk. Cancelling is cleaner and more expensive immediately.

Two. Refund or credit. Refunding is right and it is the decision that determines whether the organisation survives. Offering credit for a future event is legitimate only if a future event is genuinely likely — otherwise it is a promise you cannot keep.

Three. What is owed to the venue. The cancellation clause you did not read carefully becomes the most important document in the process.

Four. Sponsors. Some will forgive it, some will want a refund, and some will not respond for two months. Those who have not paid yet largely will not.

Five. Speakers. Booked travel, sometimes non-refundable. This is the cost that gets forgotten in the planning and lands on individuals.

And six. Who pays what remains, which is where the personal liability question stops being theoretical.

What we would have done differently

Read the cancellation clauses. Not to change them — to know the exposure and plan for it.

Understood the personal liability position. We did not know, precisely, until it mattered.

Held a reserve. The hardest thing for a volunteer organisation to do and the one that would have changed the outcome.

And separated the meetup from the conference financially and organisationally, deliberately rather than by accident. It survived because it happened to be independent, not because anybody planned that.

What to do now, if you organise

Three hours of work, this month.

Read your venue and supplier cancellation clauses and write the numbers in one place: what is owed at six months, three months, one month, one week.

Establish who is personally liable. For an informal group in many jurisdictions the answer is individuals, and it is worth an hour with somebody who knows.

And write a refund position before you sell a ticket. Published, so nobody has to invent it under pressure and so attendees know what they bought.

Insurance is worth investigating and its availability and terms vary enormously; it is not a substitute for knowing the exposure.

The thing that made it survivable

The community was not the event.

Monthly meetups need a room and a person. The conference needed a team, a venue, sponsors and a cash cycle. When the second failed, the first continued — and it is what the conference eventually came back out of.

That distinction is worth building deliberately, because a community whose only activity is an annual conference has a single point of failure and usually does not know it.

The short version