1. How it usually happens
Everything starts with pure enthusiasm: volunteers, local sponsors, stage set, coloured lights, sandwiches, music, kids running, elderly watching and giving unsolicited advice.
Organisation is often done well... up to a certain point. Then reality kicks in:
Stage is solid, but cables take a creative route.
Lights work, but an area stays in suspicious semi-darkness.
Emergency exit exists, but it's behind a stack of beer crates.
Fire extinguisher exists, but you must pass a quiz to find it.
Music starts, but nobody clearly settled public performance rights.
On the other side, organisers live a delicate balance: tired volunteers, tight deadlines, a thousand micro-decisions. Those controlling or participating only see final result: it either works, or it doesn't.
Typical anecdote: summer festival, all perfect until concert starts. Mid-evening, power trips on half the area. It turns out one power line fed stage, fridge, and coffee machine "because it holds anyway". Meanwhile someone notices emergency lights are decorative, not functional. Evening ends anyway, but next day questions begin.
Here documentation serves before something happens, not after.
2. What you need to prove
Here the point is demonstrating you organised the event in a compliant and reasonable manner, not improvised.
It can be useful to prove:
- existence and content of necessary authorisations
- correct setup of emergency exits and evacuation routes
- presence and accessibility of fire extinguishers and safety devices
- lighting conditions, including emergency
- management of electrical systems and structures
- compliance of music use regarding foreseen rights
- general state of area before opening
- communications with suppliers, technicians, and volunteers
The goal is being able to say: "this is how it was organised and verified before opening".
3. What to collect
Here you need to build a simple but concrete dossier.
Collect:
- authorisations, permits, and official communications
- floor plans or layouts of event area
- contracts with suppliers (stage, lights, audio, food)
- technical documentation of systems and equipment
- screenshots or emails on music management and rights
- photos of free and signposted emergency exits and routes
- photos of fire extinguishers and their position
- photos and videos of lighting system and general illumination
- images of electrical system (without getting technical, but visible)
- communications with volunteers and staff
A key point: photograph everything when it is in order. Afterwards, it will always be "more or less like this".
4. How to proceed
The secret here is anticipating. You don't document to defend yourself, you document to prove you did things sensibly.
Before opening, tour the area with different eyes: not as a tired organiser, but as someone who must verify.
Look at exits, not just stage. Look where fire extinguishers are, not just the bar. Look at lighting, not just decorations.
Practical procedure:
- gather and save all organisational documentation
- do a final inspection before opening
- photograph clear and signposted emergency exits
- photograph visible and accessible fire extinguishers
- document general and any emergency lighting
- take photos of stage, systems, and wiring in normal conditions
- verify and save communications on music and usage rights
- organise everything in chronological sequence
- use ExistBefore to timestamp event's state before opening
- keep original files without modifying them
A useful trick: take a slow walking video of the area. In one minute you tell more things than in ten scattered photos.
5. Mistakes to avoid
Here mistakes are the ones seen... when it's too late.
Beware of:
- taking safety elements for granted
- documenting only stage and not the rest
- leaving exits or routes even partially obstructed
- not knowing where fire extinguishers are
- ignoring lighting in secondary areas
- neglecting music rights management
- having no trace of communications with suppliers
- taking photos after something already changed
Besides timestamping, prevention counts. Free timestamping adds a technical time reference proving how the event was organised before opening.
6. After documenting
Once everything is collected, you have a solid foundation.
If event goes well, you archive and reuse material for next editions. If problems or checks emerge, you have a clear trail of how it was organised.
You can share documentation with those assisting you in organisation, consultants, or those managing technical and administrative aspects.
In the European context, where local events involve shared responsibilities among associations, volunteers, and suppliers, having orderly documentation helps prove it wasn't all improvised. And this, often, makes the difference between "it went well by luck" and "it went well because it was organised".