How we organize events: five gates, seven lanes and two debriefs

The problem we had

Organizing an event isn't a software project, and treating it as one is the
fastest way to get hurt. A festival has a date that doesn't move: the stage
arrives that day, the permit either exists or it doesn't, and there's no such
thing as "we'll ship it next week."

For a while we tried using the same work boards we used for our ongoing
associative activities. They worked as long as the event was small. Then
RestArt grew, the Salento Block Battle started needing permits, contracts and
suppliers, and we realized the board told us how many things were done, but
never told us the thing we actually needed to know: are we ready or not?

That's where Sipario came from, the method we use now. It fits in one line:
five gates, seven lanes, two debriefs.

The five gates

A gate is a point where we stop and decide, together, whether to move
forward. There are five, in a fixed order:

1. Purpose — why we're doing this event, for whom, and how we'll know if
it went well. Until there's a written answer to these three questions, we
don't start.
2. Feasibility — how many people we expect, which capacity bracket we
fall into, what rough budget is needed, which authorizations are required.
3. Frozen plan — venue confirmed, suppliers under contract, paperwork
filed. From here on, changing anything has a cost, and everyone knows it.
4. Ready — the eve of the event: everything that had to be there, is
there.
5. Closing — the event is over, the accounts are closed, the memory has
been gathered.

Every gate has a list of evidence to declare. The word "declare" matters:
the evidence is confirmed by a person, not calculated by the software.
The system doesn't know whether the SCIA — the notice of commencement of
activity required by Italian law — has actually been filed; it only knows
that someone has taken responsibility for saying it has, with a name and a
date attached.

The gate is the only point in the method that actually blocks anything. If a
piece of evidence remains unmet, the gate doesn't open. If the previous gate
hasn't been passed, the next one doesn't open either. And stopping a gate
requires writing down why: there's no such thing as a block without an
explanation.

Everything else — workloads, dependencies between tasks — raises warnings but
blocks nothing. We decided this on purpose: if everything blocks, people
learn to work around the system, and at that point you might as well not have
one.

The seven lanes

The lanes are the crafts that coexist inside an event: **content, venue,
operations, people, communications, money, compliance**.

They serve one purpose only: making it visible who's falling behind. In a
volunteer-run association the risk isn't that work goes undone, it's that all
the work piles up on two people while an entire lane stays uncovered right up
to fifteen days before the event. Looking at the lanes, you notice it in
March, not in July.

The "compliance" lane deserves a note. This is where paperwork, venue permits,
insurance and obligations toward volunteers end up. It's the lane that in an
association tends to be treated as a last-minute nuisance, and it's exactly
the one that can sink an evening.

The buffer

Between the day we declare ourselves ready and the day of the event there's a
gap. That gap has a name — buffer — and a color: green, yellow, red.

It blocks nothing. It exists to say something that no one likes to say out
loud: we're arriving ready too late. A red buffer two weeks before the
event means that whatever goes wrong next has no room left to be fixed.

The two debriefs

At the end we run two, and they're different on purpose.

The first is hot, the same evening or the next day, while the exhaustion
is still fresh: what we keep, what we change. It's there to capture the
things no one will remember in a week.

The second is cold, a few weeks later: the same two questions plus a
third, which issues remain open. Hot, you see the stumbles; cold, you see
the patterns.

What comes out of the debriefs doesn't end up in a document no one will ever
reopen. It becomes material for the "purpose" gate of the next edition.

The night itself

For the day of the event there's a dedicated section: the physical zones, the
four phases of the day (pre-event, load-in, the night, load-out), the tasks
positioned in time and space, and the materials each of them needs.

Whoever is on shift sees their own night in read-only mode, with no
management software to learn: they open the page and find what they're
doing, where, and when.

There's a readiness check that flags issues. We already know it produces
false alarms: it flags a conflict every time two tasks in the same phase
request the same piece of equipment, because it doesn't know how many units
we own. We chose to risk one warning too many over one warning too few, but
it's fair to say that number needs to be read, not trusted at face value.

What isn't there, and we don't pretend it is

The site has no ticketing system. We don't sell entry: registrations for
events are free, they generate a QR code and are used for entrance control.
What people actually buy are drinks and food, with orders that go through
the till or through card payment online and land on the prep-station monitor.

At the till, "card" payment is just a bookkeeping label: no terminal is
connected. Anyone paying by card does so online; at the physical till the
system just records the method to make the accounts balance — it doesn't
actually take payment.

And above all: Sipario has not yet been tested on a full edition. It's
written, it's implemented, and the Salento Block Battle 2026 will be the
first time we use it from start to finish. Until that edition is closed and
the second debrief is written, this is a proposed method, not a proven one.
There are also a few open regulatory questions on which we want a
professional's opinion before running the first event entirely this way.

We're saying this now because in a year's time we'll be the ones wanting to
read it again: if it worked, it will help to remember what we expected; if it
didn't, it will help to remember that we wrote it down before we knew.