An event should have one structure, not five versions of the truth.

The organiser has a spreadsheet. The audience sees a website. Speakers receive separate documents. Crew work from another showflow. The presenter uses a different script.

None of those are wrong on their own. The problem is that they are copies. By the time the doors open, the same information has been retyped, reformatted and rechecked in five places, and at least one of them is out of date — usually the one on a screen in front of an audience.

Then something moves. A speaker lands late, a session overruns, a room changes. The change is easy. Propagating it to five documents, three teams and a published programme is what actually costs the day.

The programme, the audience portal, the speaker material, the locations, the showflow and the prompter script all read from the same event structure. Change the event and the views change with it — because they were never separate copies to begin with.

EventBlok comes out of nearly three decades of live production — conferences, global hybrid events, main-stage entertainment, multi-camera streaming, speaker management and show control. Enough years to see the same failure repeat in different buildings with different budgets.

An early AWS-supported proof of concept, developed with Devoteam, explored how AI could make the most repetitive part of event planning faster: turning messy source material into structured sessions, speakers, timings and locations that a producer could then review.

The aim was never to let AI run an event. Live events need judgement — someone who understands the room, the crew, the presenter, the audience and the inevitable change five minutes before doors open. That principle survived into the product: AI can organise, suggest and accelerate; people approve.

What was left after the proof of concept was the more useful idea underneath it. An event should have one connected structure. Build the programme once, then use it to power the audience agenda, speaker preparation, locations, production showflow and presenter tools.

I have spent years producing live events, calling shows, directing multi-camera productions and working with the people who have to make an event work when the clock is running. I have also built the websites and platforms behind those events, which means I have watched the same information get rebuilt on both sides of the wall.

Every producer I know has a version of the same evening: a change comes in, and the next twenty minutes are spent making five documents agree instead of making the show better. That is not a tooling gap anyone celebrates. It is just the water we swim in.

EventBlok is my attempt to drain it. Not another isolated agenda tool, and not another production spreadsheet — a connected workspace for the people planning the event, publishing the programme and running the show.

If you run events and something here is wrong, tell me. I would rather hear it from an operator than discover it at 14:00 on a show day.

Features are shaped in conversation with the people who will be holding the comms when they get used: producers, show callers, operators, speaker managers and the organisers who have to publish the thing. If a feature cannot survive a real running order, it does not ship.

The work is written up as it happens in the Journal — what was built, what broke, and what a live show taught us that a roadmap could not.

A better event experience should still look and feel like your event. For your first month, publish EventBlok under your own brand — with your logo, colours and event identity — at no additional white-label charge. Build the event, create the programme, run the show and publish an agenda attendees can use, all under your event brand.